Marketing Skills for AI agents

Install

npx skills add coreyhaines31/marketingskills

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.

Example request

Review our SaaS pricing page with the cro skill and suggest three A/B test hypotheses

Limitations

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.

Security check

• Skills are markdown instructions

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.

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

Related