Marketing Skills for AI agents
Marketing Skills for AI Agents
About fifty skills for CRO, copywriting, SEO, analytics, ads and launches, built for coding agents
- 57,199 ★ on the repository
- Last commit
- MIT
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/marketing-skills-for-ai-agentsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- Skills are markdown instructions
This is third-party code. Review the repository files before installing.
What it does
A set of markdown skills that give an agent working frameworks for marketing tasks: A/B tests, landing pages, emails, pricing, onboarding, SEO audits, ads and competitor pages. The product-marketing skill stores product and audience context, and every other skill reads it first. Skills cross-reference each other, for example copywriting, cro and ab-testing.
Who it is for. Technical marketers and founders who run growth work through Claude Code, Codex or Cursor.
Good fit when
- You need to rewrite landing page or signup copy
- You are planning an A/B test and want a sound experiment design
- You are preparing an email sequence, a launch or a competitor comparison page
- You are running an SEO audit or adding schema markup
Not a fit when
- You need Russian ad platforms such as Yandex Direct: examples target Google, Meta and LinkedIn
- You need live data from ad accounts: the skills provide method, not integrations
Example request
Review our SaaS pricing page with the cro skill and suggest three A/B test hypothesesLimitations
Skills are in English and rely on Western channels and tools. Output quality depends on a filled product-marketing context file. When installed from inside an agent session, the CLI may only write to .agents/skills, which Claude Code does not read.
How to disable. Delete the skill folders from .claude/skills or .agents/skills, or remove the marketing-skills plugin in Claude Code.
FAQ
Why do I need the product-marketing skill?
It is the foundation: every other skill reads product, audience and positioning context from it first.
Why does Claude Code not see the skills after installing from a session?
Inside a session the CLI runs non-interactively and may only install to .agents/skills. Pass the agent explicitly with -a claude-code.
Discussion
No questions or reviews yet.
Related
SkillsMarketing & SEO Skills
Marketing & SEO Skills for AI Agents
A library of hundreds of marketing and SEO skills for agents: content, page types, channels, ads and strategies
A skill of the author's marketing principles and playbooks that the agent reads before writing copy, emails and funnels
Skills for positioning, content, LinkedIn, cold outreach and landing page audits with quick and deep modes
A bilingual pack of marketing skills for agents: strategy, content, performance, design and role operations
AI Marketing Suite
AI Marketing Suite for Claude Code
A set of marketing skills for Claude Code: site audit, copywriting, emails, content calendars, competitor analysis and client reports
A set of agent skills for affiliate marketing: program search, trend research, articles and posts, landing pages and analytics
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Repository stars | Main difference |
|---|---|---|---|
| Marketing Skills for AI agents (this entry) | no | 57,199 | |
| Email Marketing Bible | no | 358 | an email marketing skill for AI agents |
| OpenDirectory | no | 686 | a library of 64 skills for founders |
| AI Employees | no | 814 | eight open source AI employees for business roles |
README in short
Corey Haines' repository of marketing skills following the Agent Skills spec, MIT licensed. Skills are grouped into SEO and content, CRO, copy, paid and measurement, growth and retention, sales and strategy. Install via npx skills, a Claude Code plugin, copying, git submodule or SkillKit. The project has partners, but the README states they do not affect what skills recommend.
README badge
Original SKILL.md
--- name: ab-testing description: When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro. metadata: version: 2.0.0 --- # A/B Test Setup You are an expert in experimentation and A/B testing. Your goal is to help design tests that produce statistically valid, actionable results. ## Initial Assessment **Check for product marketing context first:** If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Before designing a test, understand: 1. **Test Context** - What are you trying to improve? What change are you considering? 2. **Current State** - Baseline conversion rate? Current traffic volume? 3. **Constraints** - Technical complexity? Timeline? Tools available? --- ## Core Principles ### 1. Start with a Hypothesis - Not just "let's see what happens" - Specific prediction of outcome - Based on reasoning or data ### 2. Test One Thing - Single variable per test - Otherwise you don't know what worked ### 3. Statistical Rigor - Pre-determine sample size - Don't peek and stop early - Commit to the methodology ### 4. Measure What Matters - Primary metric tied to business value - Secondary metrics for context - Guardrail metrics to prevent harm --- ## Hypothesis Framework ### Structure ``` Because [observation/data], we believe [change] will cause [expected outcome] for [audience]. We'll know this is true when [metrics]. ``` ### Example