I built 18 AI marketing agents for Claude Code

When someone drops into r/ClaudeAI and announces they've built 18 specialized AI marketing agents, 93 slash commands, and 28 marketing skills inside Claude Code, the right reaction isn't skepticism — it's curiosity about the architecture. As someone who builds production AI agents for Google Ads (including Buddy, an open-source Claude-powered agent), I've lived through every version of "AI marketing automation" from prompt-stuffed ChatGPT wrappers to genuinely orchestrated multi-agent systems. This post breaks down what AgentKits Marketing-style systems actually are, how they work inside Claude Code, and how you should think about adopting or building something similar for your own marketing workflows.

What Does "18 AI Marketing Agents in Claude Code" Actually Mean?

Before we get excited (or dismissive), it's worth being precise. In the r/ClaudeAI thread, the creator describes AgentKits Marketing as a set of specialized AI agents with slash commands and skills that operate directly inside Claude Code — Anthropic's terminal-based, agentic coding environment.

This is meaningfully different from:

• A collection of saved prompts in a notes app
• A ChatGPT custom GPT with a system prompt
• A no-code automation in Zapier that calls an LLM

Claude Code agents can read and write files, execute code, browse the web (with the right tools), call APIs, and chain tasks together autonomously. When you add slash commands and structured skills on top of that, you get something closer to a real software system than a fancy chatbot.

Think of it this way: a single "SEO Content Agent" in this kind of system might be able to pull a keyword list from a CSV, research SERP intent using a browser tool, draft a blog post structure, write the content, check it against readability targets, and output a formatted Markdown file — all from one slash command like /seo-content.

The Architecture: How Slash Commands and Skills Work Together

If you haven't used Claude Code much, here's a quick orientation. Claude Code runs in your terminal and has access to your local filesystem and, depending on configuration, external tools. It supports a concept of slash commands — shorthand triggers that load specific instructions, context, or workflows.

In a system like AgentKits Marketing, the architecture typically looks like this:

1. Skills (the building blocks): Discrete capabilities the agent can perform — things like "extract keyword data," "write ad copy in a given tone," or "score a landing page for CRO." These are usually defined in structured prompt files or tool definitions.
2. Agents (the orchestrators): Each agent is scoped to a domain — Paid Search, Content Marketing, Email, Social, SEO, Analytics, etc. The agent knows which skills to call and in what order.
3. Slash commands (the interface): These are how you invoke agents or individual skills. /ppc-audit might trigger the Paid Search Agent to run a full account audit skill chain. /email-subject might call a single skill that generates subject line variants.

The 93 slash commands across 18 agents and 28 skills in this system suggests a fairly granular taxonomy — probably something like 5-6 commands per agent, covering both full workflow triggers and individual skill invocations.

The 18 Agent Categories: What Marketing Functions Make Sense to Automate?

We don't have the exact list from the thread, but based on standard marketing operations and what makes architectural sense for Claude Code, here's how a mature 18-agent marketing system would break down:

As practitioners often discuss in the r/ClaudeAI community, the highest-value automation targets are tasks that are high-volume, structurally repetitive, and data-rich — not tasks that require genuine strategic creativity or stakeholder judgment. Paid search keyword work, ad copy generation, and reporting narratives sit in the sweet spot. Brand strategy and creative direction stay with humans.

Real-World Performance: What to Expect When You Deploy Something Like This

Let me ground this in actual numbers from production use. When I built Buddy (the open-source Google Ads agent running on Claude), the performance gains weren't theoretical — they were measurable in hours saved and decision speed.

Time Savings by Task Type

• Keyword expansion and clustering: Manual process that took 2-4 hours per campaign now runs in 8-15 minutes with human review. The agent handles the mechanical work; the strategist handles judgment calls about match types and negatives.
• Ad copy variants: Generating 10-15 RSA headline and description variants manually takes 45-90 minutes for a thoughtful copywriter. An agent with proper brand context and constraints does it in under 3 minutes, with quality that passes review >70% of the time without significant edits.
• Weekly performance reporting narratives: Pulling numbers and writing the "so what" used to take a junior analyst 2-3 hours. An analytics agent with dashboard access turns this into a 12-minute task — data in, narrative out, human sanity-checks the interpretation.
• Competitive ad copy analysis: Manually reviewing Meta Ad Library or Google Ads Transparency for 5 competitors took half a day. A scraping-enabled agent does this in <30 minutes with structured output.

Quality Benchmarks That Matter

Raw speed means nothing if quality degrades. Here's what I've seen hold up in production:

• Ad copy from a well-prompted agent with strong brand context achieves comparable CTR to human-written copy in A/B tests roughly 60-65% of the time. The remaining 35-40% still benefits from human creative intervention.
• SEO content outlines from agents are usable as-is about 80% of the time when the agent has access to SERP data and keyword context. Without that context, drop to ~50%.
• Keyword clustering quality degrades significantly without proper negative keyword input and campaign structure context. Garbage in, garbage out — agents don't magically know your account history.

How to Evaluate or Build Your Own Agent System

Whether you're considering adopting something like AgentKits Marketing or building your own system in Claude Code, here's a practical evaluation framework:

Step 1: Map Your Highest-Pain Marketing Tasks

Before you touch a terminal or write a slash command, spend 30 minutes listing every marketing task you or your team does that is:

• Done more than once per week
• Structurally similar each time (even if the specifics change)
• Currently taking >30 minutes of focus time
• Not dependent on political judgment or stakeholder relationships

That list is your agent roadmap. Build agents for those tasks first — not the ones that sound impressive.

Step 2: Define the Input/Output Contract for Each Agent

Every agent needs a clear answer to: "What goes in, what comes out?" This is harder than it sounds. "Give me better ad copy" is not an input/output contract. "Given a product description, target audience brief, 3 competitor headlines, and a character limit — output 15 headline variants with notes on the angle each uses" is an input/output contract. Write these out before you write a single line of agent configuration.

Step 3: Start With 3 Agents, Not 18

The temptation with a system like AgentKits is to deploy all 18 at once. Don't. Start with the 3 agents that address your highest-pain tasks. Run them in production for 2-4 weeks. Measure time saved and output quality. Then expand. Agents you don't use regularly will have stale context and you'll forget how they work — which defeats the purpose.

Step 4: Build a Feedback Loop

Every agent output that gets significantly edited before use is signal. Track what gets changed and why. Use that feedback to update your agent's system prompt, skill definitions, or context loading. Agents that don't improve over time become liabilities — they lock in mediocre output and people stop trusting them.

Claude Code vs. Other Platforms for Marketing Agents

A common question in the r/ClaudeAI community is why Claude Code specifically, versus building agents in ChatGPT, n8n, Make, or a custom Python stack. Here's an honest comparison:

For marketing practitioners who are comfortable in a terminal and want maximum agent capability without a full engineering build, Claude Code with a structured command system is genuinely the best current option. For teams that need a GUI or have non-technical stakeholders who need to interact with agents directly, a hybrid approach — Claude Code for building and testing, a simple web wrapper for stakeholder-facing output — makes more sense.

What to Do Next

If this has you thinking seriously about building or adopting a Claude Code marketing agent system, here are your concrete next steps:

1. Install Claude Code and run your first agent session this week. Don't start by building 18 agents. Start by having Claude Code help you with one real task from your current workload — a keyword list, a creative brief, a reporting narrative. Get a feel for how it thinks and what context it needs before you architect anything.
2. Check out the AgentKits Marketing project on GitHub. Even if you don't adopt it wholesale, reading through the agent definitions and slash command structure will give you a concrete reference architecture for building your own. Seeing how someone else structured 18 agents is faster than figuring it out from scratch.
3. Write your input/output contracts first. Before building any agent, write one paragraph describing exactly what goes in and what comes out. If you can't write that paragraph clearly, you're not ready to build the agent yet.
4. Pick your top 3 pain-point tasks and build agents for those only. Resist scope creep. Three agents that you use daily will generate more value than 18 agents that you forget about by month two.
5. Build the feedback loop from day one. Set up a simple log for tracking output quality. This is the single habit that separates teams that get compounding value from AI agents from teams that plateau at "it's fine, I guess."

The promise of 18 marketing agents, 93 commands, and 28 skills is real — but only if the architecture is sound and the context is rich. The practitioners who win with systems like this aren't the ones who deploy the most agents. They're the ones who pick the right problems, feed the agents the right context, and actually close the feedback loop. Start there.

Related Reading