About Tri Vo
Hi, I'm Tri. I spent years as a marketer doing the boring parts of the job manually — pulling reports, rewriting briefs, chasing down assets — before I realized AI could absorb most of that work if I just learned how to talk to it properly.
CC4.Marketing came out of that realization. It's the course I wish someone had handed me on day one of using Claude Code: not a tour of features, but a working playbook for the actual jobs marketers do every week. Campaign briefs, content calendars, SEO audits, competitive analysis — turned into repeatable workflows you can hand to an AI and trust.
I write about what I'm building in public: tools like Threadmark and castmd, slash-command systems for shipping, and the moments when a workflow finally clicks and a four-hour task turns into ten minutes. The goal isn't to replace marketers. It's to take the busywork off the table so the strategy work gets the attention it deserves.
If something I've written is useful to you, the best thing you can do is steal it, remix it, and tell me how you bent it to your own job.
What I'm working on now
Shipping the v0.4 release of Threadmark, refining the /publish-post skill so blog posts go from markdown to live in one command, and writing up the patterns behind "the last mile of shipping" — the unglamorous final 20% that turns a working prototype into something a team can actually rely on.
Last updated April 29, 2026
Prompts to use with AI
Copy any of these into Claude, ChatGPT, or your AI of choice. They're written
to draw on Tri Vo's voice and the work they've shipped on CC4.Marketing.
-
Write in Tri Vo's voice
I want you to write in the voice of Tri Vo, Course Creator & Lead Writer at CC4.Marketing. Their writing tends to focus on Claude Code workflows, Marketing automation, AI for non-developers, Slash commands, Shipping practices, and Workflow extraction.
Their voice is direct and pragmatic. They prefer concrete examples over abstract frameworks. They lead with what they actually shipped, not what they wish they did. They name specific tools, files, and steps instead of staying vague. They don't pad with throat-clearing.
I'll give you a topic. Draft a short blog post (300-500 words) on that topic in Tri Vo's voice. Include at least one specific, named example. End with a single sentence that invites the reader to try the thing themselves.
Topic: {your topic here} -
Find Tri Vo's posts on a topic
I'm trying to figure out what Tri Vo (Course Creator & Lead Writer at CC4.Marketing) has written that's relevant to a problem I'm working on.
Their main themes are: Claude Code workflows, Marketing automation, AI for non-developers, Slash commands, Shipping practices, and Workflow extraction.
The CC4.Marketing blog index lives at https://cc4.marketing/blog/. Tri Vo's author page lists all their posts: https://cc4.marketing/blog/authors/tri-vo/.
My problem: {describe what you're trying to solve}
Look at Tri Vo's posts and tell me:
1. Which 1-2 posts are most relevant to my problem.
2. The specific section or workflow in each post I should focus on.
3. One concrete next step I can take after reading them. -
Build a slash command from one of my posts
Read this post by Tri Vo: {paste post URL or excerpt here}.
Identify the workflow he describes. Then turn it into a Claude Code slash command (a Markdown skill file with frontmatter, a Steps section, and any helper scripts). Match the level of specificity in the post — if he names tools or files, use those names; if he leaves room for the reader to fill in, leave the same room in the command. Output the full skill file ready to drop into .claude/skills/. -
Audit my marketing workflow Tri-style
Pretend you're Tri Vo doing a 10-minute audit of my current marketing workflow. I'll describe what I do step by step. After I finish, give me:
1. The two highest-leverage steps to automate first (with the rationale).
2. One step that should NOT be automated and why.
3. A specific Claude Code prompt or slash command that would handle the highest-leverage step.
Be direct. No throat-clearing. If you'd skip something, say "skip" and move on.
My workflow: {describe here}
