The best Claude plugins and skills for marketing in 2026

Why Claude skills matter for marketing

A Claude Code skill is a folder of markdown files that documents a method, a framework or a checklist. Claude loads it into context automatically when the matching task comes up. In practice, it replaces a prompt you rewrite every time with a structured, versioned and reusable instruction. That shift from ad hoc prompts to documented skills is what made the first public marketing skill repos, released over the course of 2025 and 2026, so successful.

The format standardized fairly quickly: one folder per skill, a SKILL.md file describing the trigger and the method, sometimes with scripts or templates attached. This standardization lets a skill written for Claude Code work almost unchanged on Cursor, Codex or Gemini CLI. It also explains why so many different repos coexist: publishing one costs little, and so does adopting one. One prerequisite before the comparison: knowing how to use Claude day to day. My guide to learning Claude covers that foundation in 2 hours.

An overview of the repos that matter

Figures checked in early July 2026, on each repo's public GitHub page.

Star rankings only partly reflect real usage. Below is what each repo contains, skill by skill.

coreyhaines31/marketingskills: the dominant generalist

With about 36,300 stars, it's by far the most adopted repo in this overview, and probably the first one anyone searching for “Claude Code marketing” on GitHub comes across. Its 32 skills fall into 9 families: conversion (cro, signup, onboarding, popups, paywalls), content (copywriting, copy-editing, cold-email, emails, social, image), SEO (seo-audit, ai-seo, programmatic-seo, site-architecture, competitors, schema), paid and distribution (ads, ad-creative), measurement (analytics, ab-testing), retention (churn-prevention), growth engineering, strategy (marketing-ideas, marketing-psychology, launch, pricing) and sales/revops. The repo's strength is that breadth: there are few gaps in functional coverage. Its limit is that it assumes there's only one brand to serve. Nothing in its structure keeps one client account's doctrine separate from another's.

ericosiu/ai-marketing-skills: depth on growth and sales

With about 2,800 stars, this second repo (easy to confuse with superamped/ai-marketing-skills, which has an almost identical name) goes further on everything related to sales and growth: Growth Engine, Sales Pipeline, Content Ops, Outbound Engine, SEO Ops, Finance Ops, Revenue Intelligence, Conversion Ops, plus rarer modules like Deck Generator (turns a brief into a sales presentation) or YT Competitive Analysis (competitive audit of YouTube channels). It's the most relevant choice for a growth team that pushes beyond marketing content toward acquisition and sales.

aitytech/agentkits-marketing: the training center

562 stars, but a different profile: 18 agents, 93 slash commands, and above all 23 interactive training modules in several languages. Its skills cover conversion (page-cro, form-cro, popup-cro, signup-flow-cro, onboarding-cro, paywall-upgrade-cro), copywriting and email (copywriting, copy-editing, email-sequence), and growth (seo-mastery, programmatic-seo, schema-markup, competitor-alternatives, launch-strategy, pricing-strategy, referral-program). It works mainly as a resource for upskilling an entire team on AI in marketing, and only secondarily as a production kit.

superamped/ai-marketing-skills and thatrebeccarae/claude-marketing

2 repos with fewer stars (52 and 68), each with a sharp focus. superamped focuses on niche research: Ad Angles, Ad Campaign Analyzer, Content Strategy, Social Post Writer, Reply Writer (for Reddit), Channel Discovery, Community Discovery, Influencer Discovery. thatrebeccarae, with its 56 skills, comes closest to a full marketing department on the paid media side: Google Ads, Meta Ads, Microsoft Ads, LinkedIn, TikTok, plus SEO/AI, email/lifecycle, analytics, creative and reporting.

None of the first 5 repos tackles head-on the question of managing several brands in parallel with different brand guidelines. They organize their skills by marketing task (SEO, ads, email). That's where mine differs structurally: Cockpit organizes its skills by brand folder first, with doctrine encoded per account, before any task comes into play. And to avoid starting from scratch on each family of skills, I aggregated several of the best ones the community had already published, as the next section explains.

The community skills Cockpit aggregates

As an outsourced marketing and communications lead for several clients, I can easily find a good SEO skill or a good standalone copywriting skill. Those skills already exist, often excellent, scattered across dozens of repos. The hard part was getting them to work side by side in one place, wired to the same brand doctrine and the same editorial strategy, so I wouldn't have to redo the setup for every new client account. That's what Cockpit does: it aggregates several of the best community skills and attaches them to its 01-brand / 02-strategy structure, so they stop running as separate silos.

On top of that come my own production skills, tested with clients before being published (HTML slide decks with Playwright QA, LinkedIn carousels, brand image generation), and a fourth wave being integrated: 4 web animation skills (animation-gsap, animation-animejs, animation-lottie, animation-scroll-reveal) vendored from claudedesignskills, described in my article on v2.

n8n automations and MCP connectors

The aggregation also covers automation and ad tools. The n8n module ships with 3 dedicated skills, n8n-builder, n8n-audit and n8n-debugger, which build, audit and debug n8n workflows with a 5-phase method and access to a library of more than 5,100 templates. These workflows continuously feed the 00-intel/ folder, market monitoring and reporting, on a self-hosted n8n instance (a VPS deployment guide is included in the repo).

For ad tools and outbound, Cockpit uses the Model Context Protocol so each tool doesn't need its own custom script: Google Ads runs over MCP to audit and optimize paid search campaigns, and Lemlist over MCP to send prospecting sequences and manage their deliverability. The .mcp.json file (never committed, with secrets kept locally) centralizes these connections.

The rest of the stack follows the same tool-agnostic logic as the production roles: editorial calendar (Notion, Airtable, Trello, ClickUp, Google Sheets), email (MailerLite, Mailchimp, Resend, Brevo, ConvertKit), CRM (HubSpot, Pipedrive, Odoo, Notion, Airtable), knowledge base (Outline, Notion, Confluence, GitBook), social scheduling (Buffer, Hootsuite, Later, Typefully, or Postiz directly), analytics (GA4, Plausible, Fathom). The /tools-setup wizard detects what you already use and regenerates the connectors to match, so you keep your current stack.

None of the 5 repos in the overview above does this aggregation work, either for skills or for connectors. Each one is good on its own turf, but stays a silo: an SEO skill that knows nothing about your brand guidelines, a design skill that knows nothing about your editorial strategy. The credit for these SEO, copywriting, design and n8n methods goes to the community projects behind them. Cockpit brings them together in one place and runs them on the same foundations: the brand, the strategy, and the tools you already use.

How to choose for your situation

Nothing stops you from picking a single skill from a repo that isn't your main base. The risk is installing several at once without checking for name collisions: 2 repos can define a “content-strategy” skill with different behaviors, and Claude won't know which one to favor. Choose one base, then add skills one at a time when needed.

To see what this looks like once it's in place at a client, the HR firm Horizon Humain has produced its carousels, slides and guidebooks in-house since its training: the case study, with their video testimonial in French.

Cockpit: the all-in-one system for multi-brand marketing

Running marketing for several client accounts in parallel, each with its own brand guidelines, archives and tone, is my everyday job as an outsourced marketing and communications lead. The generalist repos in the overview above work very well for producing a LinkedIn post or an SEO audit for a single brand. A different question remains open: how do you get an SEO skill, a copywriting skill and a design skill to work together on the same account, without any of the 3 forgetting the client's brand guidelines or strategy, and without rewiring everything for each new client?

That's the role of the 3 foundations on which Cockpit runs all the aggregated skills:

The Cockpit I built and published as a template attaches claude-seo, claude-blog, claude-ads, ui-ux-pro-max, taste-skill and frontend-design to these 3 foundations, one brand folder at a time. A technical hook checks every production output before publishing, whichever skill generated it. I explain how it works in my full case study and in the article on agency memory.

If what you need is a single skill for a specific task on one brand, the first 5 repos in this overview will serve you very well, individually. If what you need is several of these skills running together, without stepping on each other, across several brands at once, that's exactly the problem Cockpit solves.

Conclusion

The market for Claude skills in marketing is young and consolidating fast: this overview will probably be out of date within 6 months. The selection criterion will stay the same. GitHub stars measure adoption, and fit with your case is a separate question. A poorly chosen repo with 36,000 stars produces less value than a 5-star repo that matches your structure exactly.

First look at how each repo organizes its skills (by task or by account), then at how many people have already adopted it. And if your real problem is holding several good skills together across several brands, Cockpit already does that wiring: it's precisely what I built it for.