Two Plugins Live Inside AgentKits Marketing. Its Marketplace Listing Shows One.

One Entry in marketplace.json

marketplace.json, the file that tells Claude Code’s /plugin system what’s installable from the agentkits-marketing repository, lists exactly one plugin. Its name is agentkits-marketing, its source is ./ — the repo root — and its description reads “Full marketing automation suite - 20 agents, 90+ commands, 28 skills.” Run /plugin install against this repo today and that’s what you get: the whole kit, in one shot. There’s no lighter option.

That single-entry manifest undersells what’s actually sitting in the repo. Two directories under plugins/ — content-factory and campaign-manager — are fully-formed, self-contained products in their own right. Each has its own PLUGIN.md, its own commands, its own agents, its own installation instructions, and its own version number. Neither one appears in marketplace.json at all.

What’s Actually in the Folder

Content Factory (internally “CF”) is the batch-content half: /cf:generate for producing blog posts, emails, and social copy in parallel across formats from a single brief; /cf:repurpose for turning one asset into several; /cf:schedule for building content calendars. It has its own specialist agents — @blog-writer, @email-copywriter, @social-media-creator, @video-scriptwriter — layered on top of shared quality-assurance agents like @brand-voice-guardian and @seo-specialist. Its own roadmap, written into PLUGIN.md, marks the current state as “v0.1 (Current - MVP)” — basic plugin structure, a first-pass /generate, a template library, brand-voice validation — with /repurpose, /schedule, and parallel agent processing pushed to “v0.2 (Next Release).”

Campaign Manager (“CM”) is the planning half, built explicitly around what it calls the Compounding Marketing philosophy — “each campaign you run documents patterns, creates templates, and builds knowledge that makes future campaigns faster and better,” credited in its own docs as inspired by EveryInc’s Compounding Engineering approach. /cm:plan ships today; /cm:execute and /cm:review are marked “Coming Soon,” alongside a jump from 6 persona and specialist reviewer agents to a planned 12+. CM’s PLUGIN.md even carries its own release line — “Current: v0.1.0 (MVP), Released: 2025-01-14” — a version and date that belong to the sub-plugin, tracked independently of the parent repo’s own package.json, which currently sits at 1.7.2.

Both plugins’ own documentation describes a marketplace install path that doesn’t quite exist yet. Content Factory’s PLUGIN.md gives installation instructions as /plugin marketplace add https://github.com/aitytech/agentkits-marketing followed by /plugin install cf@marketing-tools-marketplace — a command that names a plugin id, cf, and a marketplace, marketing-tools-marketplace, that marketplace.json in this repository doesn’t define. The only id that manifest actually exposes is agentkits-marketing itself. The docs and the manifest describe two different products.

Composed, Not Yet Composable

None of this reads as a bug so much as a build order. plugins/README.md lays out how the pieces are meant to fit together once they do connect: CF’s commands are meant to surface through the core kit’s /content:* namespace, CM’s through /campaign:*, with the plugin layer adding specialized agents and templates on top of what the core kit already ships. The architecture for composing a smaller marketing toolkit out of independent, swappable pieces is already written down. What’s missing is the one manifest entry per plugin that would let someone install Campaign Manager without also pulling in Content Factory’s video-script templates, or vice versa.

That gap matters because of where Claude Code’s own plugin system has been heading. A plugin marketplace, as Anthropic’s docs describe it, is a catalog described by a marketplace.json file that can list many independently installable plugins from one repository or registry — the whole point of the format is that a marketplace doesn’t have to mean “one bundle.” Recent write-ups of the plugin ecosystem describe the same pattern from the user side: a plugin is meant to be “a self-contained directory that bundles skills, agents, hooks, MCP servers, and more into one versioned unit” — implicitly one of several such units a marketplace can offer, not the only one. Right now, agentkits-marketing’s marketplace.json uses the format to describe a single unit anyway.

The wider marketing-technology category is pushing the same direction from a different angle. Industry coverage of MarTech stacks going into 2026 describes a broad move away from all-in-one platforms toward composable architecture — organizations “breaking big suites into composable services” so a team can adopt the piece it needs without buying (or configuring) the whole platform. A marketing team that only wants systematic campaign planning, and doesn’t need parallel batch content generation across five formats, is exactly the kind of buyer that composable trend describes — and exactly the buyer today’s single-entry marketplace.json doesn’t yet serve on its own.

The Honest Read

AgentKits Marketing didn’t set out to build one plugin; the repository already contains two, each with real commands, real agents, and its own MVP-to-v1.0 roadmap written down in its own file. What hasn’t happened yet is the last, smaller step — publishing content-factory and campaign-manager as entries in marketplace.json so /plugin install cf@... resolves to something real instead of a documented command that doesn’t currently match the manifest. Composed already, not yet composable from the outside. Given how much of the rest of the marketing-tooling category is moving toward exactly that kind of modularity, closing that specific gap looks less like a nice-to-have and more like unfinished business.

---

AgentKits is open source and free forever under the MIT license. Explore the Marketing Kit, browse the plugins/ folder yourself, or follow what ships next at agentkits.net, or reach us at [email protected].