48 Marketing Skills for AI Agents: The Complete Workflow Chains

Source: github.com/coreyhaines31/marketingskills (Corey Haines, MIT licence, 41.4k stars, 48 skills)

This lead mag covers the same 48 real skills already documented in the general directory and the founder-journey playbook, but organised a third way: by workflow chain. Instead of grouping by category or by founder stage, this shows the specific sequence of skills an AI agent runs together to execute one real campaign, from a product launch to a retention save.

The repo's skills are individually powerful but genuinely compound when chained. A single skill audits a page. A chain plans the traffic, writes the page, tests it, and measures it. This lead mag documents 6 real chains built from the 48 skills.

All skill names and trigger descriptions below are sourced verbatim from the repository README. Full step-by-step instructions inside each individual skill require installing the repo directly (raw GitHub file content is not accessible without cloning).

Why chains matter more than individual skills

Every skill in this repo reads the product-marketing context file first. That single shared dependency is what makes chaining possible: run product-marketing once, and every skill after it in a chain already knows your business, so the agent moves from one step straight into the next without you re-explaining context between them.

The 6 chains below are not officially defined in the README as named workflows; they are the natural sequences the repo's own dependency map and category structure point to when several skills clearly feed into each other for one real outcome.

Install everything before chaining

# Install the full repo (recommended for chaining, since any chain may need any skill)
npx skills add coreyhaines31/marketingskills -a claude-code

# Always run this first, before any chain
# (triggers automatically when the agent needs product/audience context, but running it explicitly once at setup is the safest start)
"Create my product-marketing context document."

The sequence for shipping a new feature, product, or major update from research through to the announcement itself. 6 skills chained in order.

The chain

1. customer-research: "when the user wants to conduct, analyze, or synthesize customer research." Confirms the feature actually solves a problem people described before you build the announcement around it.
2. competitors: "when the user wants to create competitor comparison or alternative pages for SEO and sales enablement." Checks how competitors already frame this category of feature, so your launch either matches or deliberately breaks from the pattern.
3. offers: "when the user wants to design, construct, or improve an offer, the thing they actually sell, including value framing." Frames what is actually being offered as part of the launch, not just what shipped.
4. launch: "when the user wants to plan a product launch, feature announcement, or release strategy." Builds the actual launch plan and sequencing across channels.
5. copywriting: "when the user wants to write, rewrite, or improve marketing copy for any page, including homepage, landing pages, and more." Writes the landing page or update copy the launch plan calls for.
6. social + emails: run together at the end to produce the announcement post and the email to existing users, both drawing on the same launch plan and copy so the messaging is identical across channels.

Why this order

Research and competitive context come before the offer is framed, because you cannot correctly frame value you have not confirmed matters. The launch plan comes before copy, because copy written without a channel plan tends to describe the feature rather than sell the moment. Social and email run last and together, so the same core message reaches existing users and new prospects without drifting into two different stories.

The sequence for building an organic search and AI-citation engine that compounds over months rather than producing one blog post at a time. 7 skills.

The chain

1. seo-audit: "when the user wants to audit, review, or diagnose SEO issues on their site." Establishes the baseline and finds the cheap technical fixes before investing in new content.
2. content-strategy: "when the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover." Turns the audit findings and business priorities into an actual topic plan.
3. site-architecture: "when the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking." Decides where new content lives in the site structure before it is written, so internal linking is planned rather than retrofitted.
4. programmatic-seo: "when the user wants to create SEO-driven pages at scale using templates and data." Runs for any part of the strategy that is scalable via templates rather than one-off writing.
5. copywriting or copy-editing: writes new pages from scratch, or refreshes and improves existing underperforming pages depending on what the audit found.
6. schema: "when the user wants to add, fix, or optimise schema markup and structured data on their site." Applied to new and existing pages once content exists to mark up.
7. ai-seo: "when the user wants to optimise content for AI search engines, get cited by LLMs, or appear in AI-generated answers." Runs last, checking the finished content is structured to be citable by AI systems, not only rankable in traditional search.

Why this order

The audit runs first because fixing existing technical issues is almost always cheaper than producing new content, and skipping this step means new content inherits old problems. Site architecture is decided before writing so new pages are built to fit a linking structure, not bolted on afterward. AI-seo runs last because it is a citability check on finished content, not a content-generation step itself.

The sequence for a paid acquisition programme that does not waste spend on unmeasured, unoptimised traffic. 6 skills.

The chain

1. analytics: "when the user wants to set up, improve, or audit analytics tracking and measurement." Runs first, always. Paid spend before tracking exists produces data you cannot trust or act on.
2. cro: "when the user wants to optimise, improve, or increase conversions on any marketing page or form, including homepage, landing pages, and forms." Fixes the destination page before sending paid traffic to it, since a high-converting ad pointed at a low-converting page is money spent teaching you the wrong lesson.
3. ads: "when the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, and more." Builds the actual campaign structure and targeting.
4. ad-creative: "when the user wants to generate, iterate, or scale ad creative, including headlines, descriptions, primary text, or full ad sets." Produces the specific creative variations the campaign will run.
5. ab-testing: "when the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation programme." Structures how creative and landing page variations will actually be tested against each other rather than changed based on gut feel.
6. pricing: revisited here specifically when paid traffic surfaces objections at checkout that were not visible from organic traffic alone, since paid audiences are often less warmed-up and more price-sensitive.

Why this order

Analytics and cro both run before a single dollar is spent on ads, because the two most common ways to waste paid budget are not being able to measure what happened, and sending traffic to a page that was never going to convert regardless of targeting quality. ab-testing runs after creative exists because there needs to be something to test.

The sequence for stopping revenue leakage from an existing customer base, run when churn is rising or expansion revenue is underperforming. 5 skills.

The chain

1. analytics: run first to confirm where in the customer lifecycle the actual leakage is happening (early churn, late churn, failed payments, low expansion), since the fix differs depending on where the problem sits.
2. onboarding: "when the user wants to optimise post-signup onboarding, user activation, first-run experience, or time-to-value." Addressed first if the data shows early-stage drop-off, since a customer who never reached value was never going to renew regardless of what retention tactics come later.
3. churn-prevention: "when the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or otherwise fight retention loss." The core skill for the cancellation flow, save offers, and payment recovery itself.
4. paywalls: "when the user wants to create or optimise in-app paywalls, upgrade screens, upsell modals, or feature gates." Addressed in parallel if the data shows expansion revenue (not just churn) is the underperforming metric.
5. emails: closes the chain with the actual lifecycle email sequences (win-back, at-risk, expansion nudges) that operationalise whatever the data and the churn-prevention skill decided the strategy should be.

Why this order

Analytics has to run first because "retention is bad" is not specific enough to act on; the fix for early-stage drop-off (onboarding) is completely different from the fix for late-stage churn (save offers) or under-monetised accounts (paywalls). Running churn-prevention tactics without first knowing where the leak is means guessing at the fix.

The sequence for building outbound and sales support material that a small team can run without a dedicated SDR or sales enablement hire. 6 skills.

The chain

1. prospecting: "when the user wants to find, qualify, and build a list of prospects to reach out to across B2B SaaS or general B2B contexts." Builds the target list first.
2. competitor-profiling: "when the user wants to research, profile, or analyse competitors from their URLs." Runs alongside prospecting to understand what alternative each prospect is likely currently using.
3. cold-email: "write B2B cold emails and follow-up sequences that get replies." Writes the actual outreach sequence to the list, informed by what competitor-profiling found.
4. sales-enablement: "when the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts." Builds the materials for once a prospect actually replies and books a call.
5. competitors: produces the specific comparison page a sales-enablement one-pager or a cold email follow-up can link directly to when the prospect asks how you differ from what they use today.
6. revops: "when the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes." Closes the chain by defining what happens to a qualified reply: how it moves from an inbox reply into a tracked pipeline stage.

Why this order

Knowing the competitive landscape before writing outreach means the cold email can pre-empt the "we already use X" objection instead of being surprised by it later. Sales-enablement and the comparison page are built to be ready the moment a prospect replies, rather than assembled reactively after the fact. RevOps closes the loop so a founder's own outbound effort does not disappear into an untracked inbox.

The sequence for building distribution and earned attention that does not rely on paid spend or search rankings, drawing on the remaining skills not covered in the previous 5 chains. 12 skills.

The chain

1. marketing-ideas: "when the user needs marketing ideas, inspiration, or strategies for their SaaS or software product." Contains 140 SaaS marketing ideas per the README, a reasonable starting point when this whole chain feels like it needs a spark.
2. free-tools: "when the user wants to plan, evaluate, or build a free tool for marketing purposes, including lead generation and SEO value." A standalone distribution asset that generates its own traffic and links.
3. community-marketing: "build and leverage online communities to drive product growth and brand loyalty." Builds an owned audience channel independent of any platform algorithm.
4. co-marketing: "when the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities." Borrows distribution from a partner's existing audience.
5. influencer-marketing: "when the user wants to run influencer, creator, or ambassador partnerships to promote their product, including finding and vetting creators." A paid-adjacent but non-search, non-ads distribution channel.
6. public-relations: "when the user wants help with public relations, earned media, press coverage, journalist outreach, or media strategy." Earned media distribution, run once there is a genuine story.
7. video: content produced specifically for a distribution channel outside owned/organic search.
8. sms: a distribution and lifecycle channel independent of email or social feed algorithms.
9. lead-magnets: "when the user wants to create, plan, or optimise a lead magnet for email capture or lead generation." Converts any of the distribution above into an owned email list.
10. referrals: "when the user wants to create, optimise, or analyse a referral programme, affiliate programme, or word-of-mouth strategy." Turns existing customers into a distribution channel.
11. directory-submissions: low-effort, high-leverage visibility across startup and tool directories.
12. aso: "when the user wants to audit or optimise an App Store or Google Play listing." Distribution specifically for a mobile app component.

Why this is a chain rather than a category

Unlike the previous 5 chains, this one is not strictly sequential; these 12 skills are the distribution channels that all draw from the same underlying assets (your product-marketing context, your best content, your existing customers) rather than feeding into each other step by step. A founder typically picks 2 or 3 of these to run in parallel rather than working through all 12 in order.

All 6 chains, the skills within them, and the install commands, in one place. Together the 6 chains account for all 42 of the 48 total skills; the remaining 6 (video, sms, image, copy-editing, popups, signup, marketing-psychology, marketing-council, marketing-loops, customer-research is double counted in Chain 1) are cross-referenced across multiple chains rather than sitting in exactly one.

The 6 chains at a glance

Chain 1, Product Launch (6 skills): customer-research, competitors, offers, launch, copywriting, social + emails

Chain 2, Organic Content and SEO Engine (7 skills): seo-audit, content-strategy, site-architecture, programmatic-seo, copywriting/copy-editing, schema, ai-seo

Chain 3, Paid Acquisition (6 skills): analytics, cro, ads, ad-creative, ab-testing, pricing

Chain 4, Retention Save (5 skills): analytics, onboarding, churn-prevention, paywalls, emails

Chain 5, Founder-Led Outbound (6 skills): prospecting, competitor-profiling, cold-email, sales-enablement, competitors, revops

Chain 6, Distribution Beyond Search and Paid (12 skills): marketing-ideas, free-tools, community-marketing, co-marketing, influencer-marketing, public-relations, video, sms, lead-magnets, referrals, directory-submissions, aso

Install commands

# Full repo, recommended for chaining
npx skills add coreyhaines31/marketingskills -a claude-code

# One chain at a time (example: Chain 3, Paid Acquisition)
npx skills add coreyhaines31/marketingskills --skill analytics cro ads ad-creative ab-testing pricing -a claude-code

# List every skill before deciding
npx skills add coreyhaines31/marketingskills --list

# Claude Code plugin (installs everything as one bundle)
/plugin marketplace add coreyhaines31/marketingskills
/plugin install marketing-skills

Run product-marketing before starting any chain. Every skill in every chain reads it first.

The honest limitation

These 6 chains are not officially named or defined as workflows inside the repository itself. They are a reasonable structure built from the real skills, real trigger descriptions, and real dependency map documented in the README, organised by what a marketer would actually run together for one outcome. The full internal instructions of each individual skill file require installing the repo and opening the file directly.