How we make AI skills composable to run WPVibe
We’re a small team, and we run most of WPVibe’s marketing with AI. Not as an experiment, and not as a demo. It’s just how we work now.
What made that possible wasn’t a smarter model or a longer prompt. It was a shift in how we structure the work. Instead of one giant “do our marketing” instruction, we build small, single-purpose skills that snap together. If you’ve written good software, the idea will feel familiar.
The pattern: three rules
- One skill, one job. Each skill does one thing well. A skill that writes in our brand voice. A skill that strips out AI-sounding writing. A skill that generates an on-brand image. Small enough to trust, small enough to reuse.
- Skills call other skills. A skill isn’t a dead end. Our blog-banner skill doesn’t know how to generate an image, so it calls our image-generation skill. It just knows what a good banner looks like.
- Compose, don’t duplicate. When every skill has one job, you stop rewriting the same instructions in ten places. Our brand-voice skill shows up inside almost everything. Fix it once, and every skill that uses it gets better.
What this looks like in practice
Take our weekly newsletter. “Write this week’s newsletter” isn’t one big instruction. It’s a stack of small skills, composed:
- a Reddit-search skill and a web-search skill pull what’s actually happening
- our brand-voice skill sets the tone
- a humanizer removes anything that reads like a robot wrote it
- our announcement-post skill handles the “what we shipped” section
And that announcement-post skill composes its own smaller skills, including the blog-banner skill, which composes the image generator. Skills nested inside skills, each doing one job.

The result is that a few people can produce a lot, without any single prompt turning into a tangled mess.
The part we’re proud of
The skill that publishes a finished post doesn’t paste anything by hand. It uses WPVibe itself to push the post live to WordPress. We run our own marketing on the product we sell. When we say “connect the AI you already use to your WordPress site,” we mean it literally. It’s how this post got published.
AI drafts. A human approves.
Here’s the part that matters most, and it isn’t a technicality. The AI drafts. We read and approve everything before it goes out. Nothing publishes on its own.
That’s the same philosophy the product is built on. WPVibe lets AI operate your WordPress site, but it never makes a destructive or permanent change without showing you exactly what it’s about to do and waiting for your go. The AI does the work. You stay in control.
Composable skills are how we scale the doing. Human approval is how we keep the judgment. You want both.
Try it on your own site
If you run a WordPress site, you can point the AI you already use (Claude, ChatGPT, whatever you like) at it and start handing off the work. Connect in about a minute at wpvibe.ai.