feat: consolidate page-cro and form-cro into unified cro skill

- Create skills/cro/ with shared CRO analysis framework
- Move page-specific content to references/page.md
- Move form-specific content to references/form.md
- Copy experiments reference from page-cro
- Remove skills/page-cro/ and skills/form-cro/
- Update all cross-references across skills, tools, README, AGENTS.md

BREAKING: page-cro and form-cro are replaced by cro.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

.claude-plugin/marketplace.json

@@ -5,42 +5,52 @@
     "url": "https://corey.co"
   },
   "metadata": {
-    "description": "Marketing skills for Claude Code — conversion optimization, copywriting, SEO, paid ads, and growth",
+    "description": "Marketing skills for AI agents — conversion optimization, copywriting, SEO, paid ads, and growth",
     "version": "1.0.0",
     "repository": "https://github.com/coreyhaines31/marketingskills"
   },
   "plugins": [
     {
       "name": "marketing-skills",
-      "description": "25 marketing skills for technical marketers and founders: CRO, copywriting, SEO, paid ads, pricing strategy, referral programs, and more",
+      "description": "34 marketing skills for technical marketers and founders: ASO, CRO, copywriting, cold email, SEO, AI SEO, paid ads, ad creative, churn prevention, pricing strategy, referral programs, revenue operations, sales enablement, customer research, site architecture, and more",
       "source": "./",
       "strict": false,
       "skills": [
-        "./skills/ab-test-setup",
-        "./skills/analytics-tracking",
-        "./skills/competitor-alternatives",
+        "./skills/ab-testing",
+        "./skills/ad-creative",
+        "./skills/ai-seo",
+        "./skills/analytics",
+        "./skills/aso-audit",
+        "./skills/churn-prevention",
+        "./skills/cold-email",
+        "./skills/community-marketing",
+        "./skills/competitors",
         "./skills/content-strategy",
         "./skills/copy-editing",
         "./skills/copywriting",
-        "./skills/email-sequence",
-        "./skills/form-cro",
-        "./skills/free-tool-strategy",
-        "./skills/launch-strategy",
+        "./skills/customer-research",
+        "./skills/cro",
+        "./skills/emails",
+        "./skills/free-tools",
+        "./skills/launch",
+        "./skills/lead-magnets",
         "./skills/marketing-ideas",
         "./skills/marketing-psychology",
-        "./skills/onboarding-cro",
-        "./skills/page-cro",
+        "./skills/onboarding",
         "./skills/paid-ads",
-        "./skills/paywall-upgrade-cro",
-        "./skills/popup-cro",
-        "./skills/pricing-strategy",
-        "./skills/product-marketing-context",
+        "./skills/paywalls",
+        "./skills/popups",
+        "./skills/pricing",
+        "./skills/product-marketing",
         "./skills/programmatic-seo",
-        "./skills/referral-program",
-        "./skills/schema-markup",
+        "./skills/referrals",
+        "./skills/revops",
+        "./skills/sales-enablement",
+        "./skills/schema",
         "./skills/seo-audit",
-        "./skills/signup-flow-cro",
-        "./skills/social-content"
+        "./skills/signup",
+        "./skills/site-architecture",
+        "./skills/social"
       ]
     }
   ]

.github/FUNDING.yml

@@ -0,0 +1,4 @@
+# These are supported funding model platforms
+
+github: coreyhaines31
+buy_me_a_coffee: coreyhaines

.gitignore

@@ -1,2 +1,25 @@
+# Dependencies
+node_modules/
+
+# Environment variables / secrets
+.env
+.env.*
+!.env.example
+
+# macOS
+.DS_Store
+**/.DS_Store
+
+# macOS / iCloud duplicate files
+* 2.*
+* 2/
+
 # Remotion video project
 video/
+
+# Editor
+*.swp
+*.swo
+*~
+.idea/
+.vscode/

AGENTS.md

@@ -4,7 +4,7 @@ Guidelines for AI agents working in this repository.
 
 ## Repository Overview
 
-This repository contains **Agent Skills** for AI agents following the [Agent Skills specification](https://agentskills.io/specification.md). It also serves as a **Claude Code plugin marketplace** via `.claude-plugin/marketplace.json`.
+This repository contains **Agent Skills** for AI agents following the [Agent Skills specification](https://agentskills.io/specification.md). Skills install to `.agents/skills/` (the cross-agent standard). This repo also serves as a **Claude Code plugin marketplace** via `.claude-plugin/marketplace.json`.
 
 - **Name**: Marketing Skills
 - **GitHub**: [coreyhaines31/marketingskills](https://github.com/coreyhaines31/marketingskills)
@@ -20,6 +20,11 @@ marketingskills/
 ├── skills/                # Agent Skills
 │   └── skill-name/
 │       └── SKILL.md       # Required skill file
+├── tools/
+│   ├── clis/              # Zero-dependency Node.js CLI tools (51 tools)
+│   ├── composio/          # Composio integration layer (quick start + toolkit mapping)
+│   ├── integrations/      # API integration guides per tool
+│   └── REGISTRY.md        # Tool index with capabilities
 ├── CONTRIBUTING.md
 ├── LICENSE
 └── README.md
@@ -27,14 +32,19 @@ marketingskills/
 
 ## Build / Lint / Test Commands
 
-**Not applicable** - This is a content-only repository with no executable code.
-
-Verify manually:
+**Skills** are content-only (no build step). Verify manually:
 - YAML frontmatter is valid
 - `name` field matches directory name exactly
 - `name` is 1-64 chars, lowercase alphanumeric and hyphens only
 - `description` is 1-1024 characters
 
+**CLI tools** (`tools/clis/*.js`) are zero-dependency Node.js scripts (Node 18+). Verify with:
+```bash
+node --check tools/clis/<name>.js   # Syntax check
+node tools/clis/<name>.js           # Show usage (no args = help)
+node tools/clis/<name>.js <cmd> --dry-run  # Preview request without sending
+```
+
 ## Agent Skills Specification
 
 Skills follow the [Agent Skills spec](https://agentskills.io/specification.md).
@@ -64,7 +74,7 @@ description: What this skill does and when to use it. Include trigger phrases.
 - No consecutive hyphens (`--`)
 - Must match parent directory name exactly
 
-**Valid**: `page-cro`, `email-sequence`, `ab-test-setup`
+**Valid**: `cro`, `emails`, `ab-testing`
 **Invalid**: `Page-CRO`, `-page`, `page--cro`
 
 ### Optional Skill Directories
@@ -114,7 +124,7 @@ The `description` is critical for skill discovery. Include:
 3. Related skills for scope boundaries
 
 ```yaml
-description: When the user wants to optimize conversions on any marketing page. Use when the user says "CRO," "conversion rate optimization," "this page isn't converting." For signup flows, see signup-flow-cro.
+description: When the user wants to optimize conversions on any marketing page. Use when the user says "CRO," "conversion rate optimization," "this page isn't converting." For signup flows, see signup.
 ```
 
 ## Claude Code Plugin
@@ -141,7 +151,7 @@ See [Claude Code plugins documentation](https://code.claude.com/docs/en/plugins.
 Follow the [Conventional Commits](https://www.conventionalcommits.org/) specification:
 
 - `feat: add skill-name skill`
-- `fix: improve clarity in page-cro`
+- `fix: improve clarity in cro`
 - `docs: update README`
 
 ### Pull Request Checklist
@@ -158,7 +168,8 @@ This repository includes a tools registry for agent-compatible marketing tools.
 
 - **Tool discovery**: Read `tools/REGISTRY.md` to see available tools and their capabilities
 - **Integration details**: See `tools/integrations/{tool}.md` for API endpoints, auth, and common operations
-- **MCP-enabled tools**: ga4, stripe, mailchimp, google-ads, resend, zapier
+- **MCP-enabled tools**: ga4, stripe, mailchimp, google-ads, resend, zapier, zoominfo, clay, supermetrics, coupler, outreach, crossbeam, introw, composio
+- **Composio** (integration layer): Adds MCP access to OAuth-heavy tools without native MCP servers (HubSpot, Salesforce, Meta Ads, LinkedIn Ads, Google Sheets, Slack, etc.). See `tools/integrations/composio.md`
 
 ### Registry Structure
 
@@ -175,11 +186,13 @@ tools/
 ### When to Use Tools
 
 Skills reference relevant tools for implementation. For example:
-- `referral-program` skill → rewardful, tolt, dub-co, mention-me guides
-- `analytics-tracking` skill → ga4, mixpanel, segment guides
-- `email-sequence` skill → customer-io, mailchimp, resend guides
+- `referrals` skill → rewardful, tolt, dub-co, mention-me guides
+- `analytics` skill → ga4, mixpanel, segment guides
+- `emails` skill → customer-io, mailchimp, resend guides
 - `paid-ads` skill → google-ads, meta-ads, linkedin-ads guides
 
+For tools without native MCP servers (HubSpot, Salesforce, Meta Ads, LinkedIn Ads, Google Sheets, Slack, Notion), Composio provides MCP access via a single server. See `tools/integrations/composio.md` for setup and `tools/composio/marketing-tools.md` for the full toolkit mapping.
+
 ## Checking for Updates
 
 When using any skill from this repository:
@@ -206,3 +219,36 @@ When using any skill from this repository:
 ## Skill Categories
 
 See `README.md` for the current list of skills organized by category. When adding new skills, follow the naming patterns of existing skills in that category.
+
+## Claude Code-Specific Enhancements
+
+These patterns are **Claude Code only** and must not be added to `SKILL.md` files directly, as skills are designed to be cross-agent compatible (Codex, Cursor, Windsurf, etc.). Apply them locally in your own project's `.claude/skills/` overrides instead.
+
+### Dynamic content injection with `!`command``
+
+Claude Code supports embedding shell commands in SKILL.md using `` !`command` `` syntax. When the skill is invoked, Claude Code runs the command and injects the output inline — the model sees the result, not the instruction.
+
+**Most useful application: auto-inject the product marketing context file**
+
+Instead of every skill telling the agent "go check if `.agents/product-marketing-context.md` exists and read it," you can inject it automatically:
+
+```markdown
+Product context: !`cat .agents/product-marketing-context.md 2>/dev/null || echo "No product context file found — ask the user about their product before proceeding."`
+```
+
+Place this at the top of a skill's body (after frontmatter) to make context available immediately without any file-reading step.
+
+**Other useful injections:**
+
+```markdown
+# Inject today's date for recency-sensitive skills
+Today's date: !`date +%Y-%m-%d`
+
+# Inject current git branch (useful for workflow skills)
+Current branch: !`git branch --show-current 2>/dev/null`
+
+# Inject recent commits for context
+Recent commits: !`git log --oneline -5 2>/dev/null`
+```
+
+**Why this is Claude Code-only**: Other agents that load skills will see the literal `` !`command` `` string rather than executing it, which would appear as garbled instructions. Keep cross-agent skill files free of this syntax.

CONTRIBUTING.md

@@ -33,7 +33,7 @@ Optional frontmatter fields: `license` (default: MIT), `metadata` (author, versi
 
 ### 3. Follow the naming conventions
 
-- **Directory name**: lowercase, hyphens only (e.g., `email-sequence`)
+- **Directory name**: lowercase, hyphens only (e.g., `emails`)
 - **Name field**: must match directory name exactly
 - **Description**: 1-1024 characters, include trigger phrases
 

README.md

@@ -1,47 +1,93 @@
-# Marketing Skills for Claude Code
+# Marketing Skills for AI Agents
 
-A collection of AI agent skills focused on marketing tasks. Built for technical marketers and founders who want Claude Code (or similar AI coding assistants) to help with conversion optimization, copywriting, SEO, analytics, and growth engineering.
+A collection of AI agent skills focused on marketing tasks. Built for technical marketers and founders who want AI coding agents to help with conversion optimization, copywriting, SEO, analytics, and growth engineering. Works with Claude Code, OpenAI Codex, Cursor, Windsurf, and any agent that supports the [Agent Skills spec](https://agentskills.io).
 
-Built by [Corey Haines](https://corey.co?ref=marketingskills). Need hands-on help? Check out [Conversion Factory](https://conversionfactory.co?ref=marketingskills) — Corey's agency for conversion optimization, landing pages, and growth strategy. Want to learn more about marketing? Subscribe to [Swipe Files](https://swipefiles.com?ref=marketingskills).
+Built by [Corey Haines](https://corey.co?ref=marketingskills). Need hands-on help? Check out [Conversion Factory](https://conversionfactory.co?ref=marketingskills) — Corey's agency for conversion optimization, landing pages, and growth strategy. Want to learn more about marketing? Subscribe to [Swipe Files](https://swipefiles.com?ref=marketingskills). Want an autonomous AI agent that uses these skills to be your CMO? Try [Magister](https://magistermarketing.com?ref=marketingskills).
 
 New to the terminal and coding agents? Check out the companion guide [Coding for Marketers](https://codingformarketers.com?ref=marketingskills).
 
 **Contributions welcome!** Found a way to improve a skill or have a new one to add? [Open a PR](#contributing).
 
+Run into a problem or have a question? [Open an issue](https://github.com/coreyhaines31/marketingskills/issues) — we're happy to help.
+
 ## What are Skills?
 
-Skills are markdown files that give AI agents specialized knowledge and workflows for specific tasks. When you add these to your project, Claude Code can recognize when you're working on a marketing task and apply the right frameworks and best practices.
+Skills are markdown files that give AI agents specialized knowledge and workflows for specific tasks. When you add these to your project, your agent can recognize when you're working on a marketing task and apply the right frameworks and best practices.
+
+## How Skills Work Together
+
+Skills reference each other and build on shared context. The `product-marketing-context` skill is the foundation — every other skill checks it first to understand your product, audience, and positioning before doing anything.
+
+```
+                            ┌──────────────────────────────────────┐
+                            │      product-marketing-context       │
+                            │    (read by all other skills first)  │
+                            └──────────────────┬───────────────────┘
+                                               │
+    ┌──────────────┬─────────────┬─────────────┼─────────────┬──────────────┬──────────────┐
+    ▼              ▼             ▼             ▼             ▼              ▼              ▼
+┌──────────┐ ┌──────────┐ ┌──────────┐ ┌────────────┐ ┌──────────┐ ┌─────────────┐ ┌───────────┐
+│  SEO &   │ │   CRO    │ │Content & │ │  Paid &    │ │ Growth & │ │  Sales &    │ │ Strategy  │
+│ Content  │ │          │ │   Copy   │ │Measurement │ │Retention │ │    GTM      │ │           │
+├──────────┤ ├──────────┤ ├──────────┤ ├────────────┤ ├──────────┤ ├─────────────┤ ├───────────┤
+│seo-audit │ │cro  │ │copywritng│ │paid-ads    │ │referral  │ │revops       │ │mktg-ideas │
+│ai-seo    │ │signup-cro│ │copy-edit │ │ad-creative │ │free-tool │ │sales-enable │ │mktg-psych │
+│site-arch │ │onboard   │ │cold-email│ │ab-test     │ │churn-    │ │launch       │ │customer-  │
+│programm  │ │cro  │ │email-seq │ │analytics   │ │ prevent  │ │pricing      │ │research   │
+│schema    │ │popups │ │social    │ │            │ │          │ │competitor   │ │           │
+│content   │ │paywall   │ │          │ │            │ │          │ │             │ │           │
+└────┬─────┘ └────┬─────┘ └────┬─────┘ └─────┬──────┘ └────┬─────┘ └──────┬──────┘ └─────┬─────┘
+     │            │            │              │             │              │              │
+     └────────────┴─────┬──────┴──────────────┴─────────────┴──────────────┴──────────────┘
+                        │
+         Skills cross-reference each other:
+           copywriting ↔ cro ↔ ab-testing
+           revops ↔ sales-enablement ↔ cold-email
+           seo-audit ↔ schema ↔ ai-seo
+           customer-research → copywriting, cro, competitors
+```
+
+See each skill's **Related Skills** section for the full dependency map.
 
 ## Available Skills
 
 <!-- SKILLS:START -->
 | Skill | Description |
 |-------|-------------|
-| [ab-test-setup](skills/ab-test-setup/) | When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B... |
-| [analytics-tracking](skills/analytics-tracking/) | When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions... |
-| [competitor-alternatives](skills/competitor-alternatives/) | When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when... |
+| [ab-testing](skills/ab-testing/) | When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B... |
+| [ad-creative](skills/ad-creative/) | When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad... |
+| [ai-seo](skills/ai-seo/) | When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers.... |
+| [analytics](skills/analytics/) | When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions... |
+| [churn-prevention](skills/churn-prevention/) | When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or... |
+| [cold-email](skills/cold-email/) | Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails,... |
+| [competitors](skills/competitors/) | When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when... |
 | [content-strategy](skills/content-strategy/) | When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also... |
 | [copy-editing](skills/copy-editing/) | When the user wants to edit, review, or improve existing marketing copy. Also use when the user mentions 'edit this... |
 | [copywriting](skills/copywriting/) | When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages,... |
-| [email-sequence](skills/email-sequence/) | When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email... |
-| [form-cro](skills/form-cro/) | When the user wants to optimize any form that is NOT signup/registration — including lead capture forms, contact forms,... |
-| [free-tool-strategy](skills/free-tool-strategy/) | When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or... |
-| [launch-strategy](skills/launch-strategy/) | When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user... |
+| [customer-research](skills/customer-research/) | When the user wants to conduct, analyze, or synthesize customer research — including interview transcripts, surveys, support tickets, review mining, Reddit/G2/forum research, persona generation, and voice of customer (VOC)... |
+| [emails](skills/emails/) | When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email... |
+| [cro](skills/cro/) | When the user wants to optimize any form that is NOT signup/registration — including lead capture forms, contact forms,... |
+| [free-tools](skills/free-tools/) | When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or... |
+| [launch](skills/launch/) | When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user... |
+| [lead-magnets](skills/lead-magnets/) | When the user wants to create, plan, or optimize a lead magnet for email capture or lead generation. Also use when the... |
 | [marketing-ideas](skills/marketing-ideas/) | When the user needs marketing ideas, inspiration, or strategies for their SaaS or software product. Also use when the... |
 | [marketing-psychology](skills/marketing-psychology/) | When the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when... |
-| [onboarding-cro](skills/onboarding-cro/) | When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also... |
-| [page-cro](skills/page-cro/) | When the user wants to optimize, improve, or increase conversions on any marketing page — including homepage, landing... |
+| [onboarding](skills/onboarding/) | When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also... |
+| [cro](skills/cro/) | When the user wants to optimize, improve, or increase conversions on any marketing page — including homepage, landing... |
 | [paid-ads](skills/paid-ads/) | When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X,... |
-| [paywall-upgrade-cro](skills/paywall-upgrade-cro/) | When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use... |
-| [popup-cro](skills/popup-cro/) | When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also... |
-| [pricing-strategy](skills/pricing-strategy/) | When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions... |
+| [paywalls](skills/paywalls/) | When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use... |
+| [popups](skills/popups/) | When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also... |
+| [pricing](skills/pricing/) | When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions... |
 | [product-marketing-context](skills/product-marketing-context/) | When the user wants to create or update their product marketing context document. Also use when the user mentions... |
 | [programmatic-seo](skills/programmatic-seo/) | When the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions... |
-| [referral-program](skills/referral-program/) | When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy.... |
-| [schema-markup](skills/schema-markup/) | When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user... |
+| [referrals](skills/referrals/) | When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy.... |
+| [revops](skills/revops/) | When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes.... |
+| [sales-enablement](skills/sales-enablement/) | When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also... |
+| [schema](skills/schema/) | When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user... |
 | [seo-audit](skills/seo-audit/) | When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO... |
-| [signup-flow-cro](skills/signup-flow-cro/) | When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the... |
-| [social-content](skills/social-content/) | When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram,... |
+| [signup](skills/signup/) | When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the... |
+| [site-architecture](skills/site-architecture/) | When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal... |
+| [social](skills/social/) | When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram,... |
 <!-- SKILLS:END -->
 
 ## Installation
@@ -55,13 +101,13 @@ Use [npx skills](https://github.com/vercel-labs/skills) to install skills direct
 npx skills add coreyhaines31/marketingskills
 
 # Install specific skills
-npx skills add coreyhaines31/marketingskills --skill page-cro copywriting
+npx skills add coreyhaines31/marketingskills --skill cro copywriting
 
 # List available skills
 npx skills add coreyhaines31/marketingskills --list
 ```
 
-This automatically installs to your `.claude/skills/` directory.
+This automatically installs to your `.agents/skills/` directory (and symlinks into `.claude/skills/` for Claude Code compatibility).
 
 ### Option 2: Claude Code Plugin
 
@@ -81,7 +127,7 @@ Clone the entire repo and copy the skills folder:
 
 ```bash
 git clone https://github.com/coreyhaines31/marketingskills.git
-cp -r marketingskills/skills/* .claude/skills/
+cp -r marketingskills/skills/* .agents/skills/
 ```
 
 ### Option 4: Git Submodule
@@ -89,10 +135,10 @@ cp -r marketingskills/skills/* .claude/skills/
 Add as a submodule for easy updates:
 
 ```bash
-git submodule add https://github.com/coreyhaines31/marketingskills.git .claude/marketingskills
+git submodule add https://github.com/coreyhaines31/marketingskills.git .agents/marketingskills
 ```
 
-Then reference skills from `.claude/marketingskills/skills/`.
+Then reference skills from `.agents/marketingskills/skills/`.
 
 ### Option 5: Fork and Customize
 
@@ -109,77 +155,99 @@ Use [SkillKit](https://github.com/rohitg00/skillkit) to install skills across mu
 npx skillkit install coreyhaines31/marketingskills
 
 # Install specific skills
-npx skillkit install coreyhaines31/marketingskills --skill page-cro copywriting
+npx skillkit install coreyhaines31/marketingskills --skill cro copywriting
 
 # List available skills
 npx skillkit install coreyhaines31/marketingskills --list
 ```
 
+## Upgrading from v1.0
+
+Skills now use `.agents/` instead of `.claude/` for the product marketing context file. Move your existing context file:
+
+```bash
+mkdir -p .agents
+mv .claude/product-marketing-context.md .agents/product-marketing-context.md
+```
+
+Skills will still check `.claude/` as a fallback, so nothing breaks if you don't.
+
 ## Usage
 
-Once installed, just ask Claude Code to help with marketing tasks:
+Once installed, just ask your agent to help with marketing tasks:
 
 ```
 "Help me optimize this landing page for conversions"
-→ Uses page-cro skill
+→ Uses cro skill
 
 "Write homepage copy for my SaaS"
 → Uses copywriting skill
 
 "Set up GA4 tracking for signups"
-→ Uses analytics-tracking skill
+→ Uses analytics skill
 
 "Create a 5-email welcome sequence"
-→ Uses email-sequence skill
+→ Uses emails skill
 ```
 
 You can also invoke skills directly:
 
 ```
-/page-cro
-/email-sequence
+/cro
+/emails
 /seo-audit
 ```
 
 ## Skill Categories
 
 ### Conversion Optimization
-- `page-cro` - Any marketing page
-- `signup-flow-cro` - Registration flows
-- `onboarding-cro` - Post-signup activation
-- `form-cro` - Lead capture forms
-- `popup-cro` - Modals and overlays
-- `paywall-upgrade-cro` - In-app upgrade moments
+- `cro` - Any marketing page
+- `signup` - Registration flows
+- `onboarding` - Post-signup activation
+- `cro` - Lead capture forms
+- `popups` - Modals and overlays
+- `paywalls` - In-app upgrade moments
 
 ### Content & Copy
 - `copywriting` - Marketing page copy
 - `copy-editing` - Edit and polish existing copy
-- `email-sequence` - Automated email flows
-- `social-content` - Social media content
+- `cold-email` - B2B cold outreach emails and sequences
+- `emails` - Automated email flows
+- `social` - Social media content
 
 ### SEO & Discovery
 - `seo-audit` - Technical and on-page SEO
+- `ai-seo` - AI search optimization (AEO, GEO, LLMO)
 - `programmatic-seo` - Scaled page generation
-- `competitor-alternatives` - Comparison and alternative pages
-- `schema-markup` - Structured data
+- `site-architecture` - Page hierarchy, navigation, URL structure
+- `competitors` - Comparison and alternative pages
+- `schema` - Structured data
 
 ### Paid & Distribution
 - `paid-ads` - Google, Meta, LinkedIn ad campaigns
-- `social-content` - Social media scheduling and strategy
+- `ad-creative` - Bulk ad creative generation and iteration
+- `social` - Social media scheduling and strategy
 
 ### Measurement & Testing
-- `analytics-tracking` - Event tracking setup
-- `ab-test-setup` - Experiment design
+- `analytics` - Event tracking setup
+- `ab-testing` - Experiment design
+
+### Retention
+- `churn-prevention` - Cancel flows, save offers, dunning, payment recovery
 
 ### Growth Engineering
-- `free-tool-strategy` - Marketing tools and calculators
-- `referral-program` - Referral and affiliate programs
+- `free-tools` - Marketing tools and calculators
+- `referrals` - Referral and affiliate programs
 
 ### Strategy & Monetization
 - `marketing-ideas` - 140 SaaS marketing ideas
 - `marketing-psychology` - Mental models and psychology
-- `launch-strategy` - Product launches and announcements
-- `pricing-strategy` - Pricing, packaging, and monetization
+- `launch` - Product launches and announcements
+- `pricing` - Pricing, packaging, and monetization
+
+### Sales & RevOps
+- `revops` - Lead lifecycle, scoring, routing, pipeline management
+- `sales-enablement` - Sales decks, one-pagers, objection docs, demo scripts
 
 ## Contributing
 

VERSIONS.md

@@ -4,34 +4,79 @@ Current versions of all skills. Agents can compare against local versions to che
 
 | Skill | Version | Last Updated |
 |-------|---------|--------------|
-| ab-test-setup | 1.0.0 | 2026-01-27 |
-| analytics-tracking | 1.0.0 | 2026-01-27 |
-| competitor-alternatives | 1.0.0 | 2026-01-27 |
-| content-strategy | 1.0.0 | 2026-01-27 |
-| copy-editing | 1.0.0 | 2026-01-27 |
-| copywriting | 1.0.0 | 2026-01-27 |
-| email-sequence | 1.0.0 | 2026-01-27 |
-| form-cro | 1.0.0 | 2026-01-27 |
-| free-tool-strategy | 1.0.0 | 2026-01-27 |
-| launch-strategy | 1.0.0 | 2026-01-27 |
-| marketing-ideas | 1.0.0 | 2026-01-27 |
-| marketing-psychology | 1.0.0 | 2026-01-27 |
-| onboarding-cro | 1.0.0 | 2026-01-27 |
-| page-cro | 1.0.0 | 2026-01-27 |
-| paid-ads | 1.0.0 | 2026-01-27 |
-| paywall-upgrade-cro | 1.0.0 | 2026-01-27 |
-| popup-cro | 1.0.0 | 2026-01-27 |
-| pricing-strategy | 1.0.0 | 2026-01-27 |
-| product-marketing-context | 1.0.0 | 2026-01-27 |
-| programmatic-seo | 1.0.0 | 2026-01-27 |
-| referral-program | 1.0.0 | 2026-01-27 |
-| schema-markup | 1.0.0 | 2026-01-27 |
-| seo-audit | 1.0.0 | 2026-01-27 |
-| signup-flow-cro | 1.0.0 | 2026-01-27 |
-| social-content | 1.0.0 | 2026-01-27 |
+| ab-test-setup | 1.2.0 | 2026-03-14 |
+| ad-creative | 1.2.0 | 2026-03-14 |
+| ai-seo | 1.2.0 | 2026-03-14 |
+| analytics-tracking | 1.2.0 | 2026-03-14 |
+| churn-prevention | 1.2.0 | 2026-03-14 |
+| cold-email | 1.2.0 | 2026-03-14 |
+| competitor-alternatives | 1.2.0 | 2026-03-14 |
+| content-strategy | 1.2.0 | 2026-03-14 |
+| copy-editing | 1.2.0 | 2026-03-14 |
+| copywriting | 1.2.0 | 2026-03-14 |
+| email-sequence | 1.2.0 | 2026-03-14 |
+| form-cro | 1.2.0 | 2026-03-14 |
+| free-tool-strategy | 1.2.0 | 2026-03-14 |
+| launch-strategy | 1.2.0 | 2026-03-14 |
+| lead-magnets | 1.0.0 | 2026-03-14 |
+| marketing-ideas | 1.2.0 | 2026-03-14 |
+| marketing-psychology | 1.2.0 | 2026-03-14 |
+| onboarding-cro | 1.2.0 | 2026-03-14 |
+| page-cro | 1.2.0 | 2026-03-14 |
+| paid-ads | 1.2.0 | 2026-03-14 |
+| paywall-upgrade-cro | 1.2.0 | 2026-03-14 |
+| popup-cro | 1.2.0 | 2026-03-14 |
+| pricing-strategy | 1.2.0 | 2026-03-14 |
+| product-marketing-context | 1.2.0 | 2026-03-14 |
+| programmatic-seo | 1.2.0 | 2026-03-14 |
+| referral-program | 1.2.0 | 2026-03-14 |
+| revops | 1.2.0 | 2026-03-14 |
+| sales-enablement | 1.2.0 | 2026-03-14 |
+| schema-markup | 1.2.0 | 2026-03-14 |
+| seo-audit | 1.2.0 | 2026-03-14 |
+| signup-flow-cro | 1.2.0 | 2026-03-14 |
+| site-architecture | 1.2.0 | 2026-03-14 |
+| social-content | 1.2.0 | 2026-03-14 |
 
 ## Recent Changes
 
+### 2026-03-14
+- Added `lead-magnets` skill for lead magnet strategy, format selection, and conversion optimization
+- Added Composio integration layer for MCP access to OAuth-heavy tools (HubSpot, Salesforce, Meta Ads, LinkedIn Ads, Google Sheets, Slack, Notion, etc.)
+- Added headless CMS integration guides (Sanity, Contentful, Strapi) with headless-cms reference
+- Added 197 evals across all 33 skills for automated quality testing
+- Optimized all 32 skill descriptions for better trigger phrase matching
+- Replaced rigid imperatives with reasoning-based guidance across all skills
+- Added 10 new CLI tools (airops, clay, close, coupler, crossbeam, outreach, pendo, similarweb, supermetrics, zoominfo)
+- Added 13 new integration guides
+- Bumped all 32 existing skills from 1.1.0 → 1.2.0
+
+### 2026-02-27
+- Migrated context path from `.claude/` to `.agents/` for agent-agnostic compatibility
+- All skills now check `.agents/product-marketing-context.md` first, with `.claude/` fallback for older setups
+- Updated install paths in README to reference `.agents/skills/`
+- Bumped all 32 skills from 1.0.0 → 1.1.0
+
+### 2026-02-22
+- Added `revops` skill for revenue operations, lead lifecycle, scoring, routing, pipeline management, and CRM automation
+- Added `sales-enablement` skill for sales decks, one-pagers, objection handling, demo scripts, and sales playbooks
+
+### 2026-02-21
+- Added `site-architecture` skill for website structure planning, page hierarchy, navigation design, URL structure, and internal linking strategy
+
+### 2026-02-18
+- Added `ai-seo` skill for AI search optimization (AEO, GEO, LLMO, AI Overviews)
+- Moved AEO/GEO content patterns from `seo-audit` references to `ai-seo` skill
+- Added `churn-prevention` skill for cancel flows, save offers, dunning, and payment recovery
+
+### 2026-02-17
+- Added `ad-creative` skill for bulk ad creative generation and performance-based iteration
+- Added 51 zero-dependency CLI tools for marketing platforms (`tools/clis/`)
+- Added 31 new integration guides (`tools/integrations/`)
+- Added 4 email outreach CLIs: hunter, snov, lemlist, instantly
+- Security hardening: header auth for meta-ads, URL encoding, input validation
+- All CLIs reviewed via independent codex audit (auth, security, error handling, consistency)
+
 ### 2026-01-27
 - Initial version tracking added
 - Added tools registry with 29 integration guides

skills/ab-testing/SKILL.md

@@ -1,7 +1,8 @@
 ---
-name: ab-test-setup
-version: 1.0.0
-description: When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," or "hypothesis." For tracking implementation, see analytics-tracking.
+name: ab-testing
+description: When the user wants to plan, design, or implement an A/B test or experiment. 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," or "how long should I run this test." Use this whenever someone is comparing two approaches and wants to measure which performs better. For tracking implementation, see analytics. For page-level conversion optimization, see cro.
+metadata:
+  version: 1.1.0
 ---
 
 # A/B Test Setup
@@ -11,7 +12,7 @@ You are an expert in experimentation and A/B testing. Your goal is to help desig
 ## Initial Assessment
 
 **Check for product marketing context first:**
-If `.claude/product-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
+If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` 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:
 
@@ -179,7 +180,7 @@ We'll know this is true when [metrics].
 - Check segment quality
 - Document external factors
 
-**DON'T:**
+**Avoid:**
 - Peek at results and stop early
 - Make changes to variants
 - Add traffic from new sources
@@ -260,6 +261,6 @@ Document every test with:
 
 ## Related Skills
 
-- **page-cro**: For generating test ideas based on CRO principles
-- **analytics-tracking**: For setting up test measurement
+- **cro**: For generating test ideas based on CRO principles
+- **analytics**: For setting up test measurement
 - **copywriting**: For creating variant copy

skills/ab-testing/evals/evals.json

@@ -0,0 +1,105 @@
+{
+  "skill_name": "ab-test-setup",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "I want to A/B test our homepage headline. We currently say 'The All-in-One Project Management Tool' and want to test something benefit-focused. We get about 15,000 visitors/month and our current signup rate is 3.2%.",
+      "expected_output": "Should check for product-marketing-context.md first. Should build a proper hypothesis using the framework: 'Because [observation], we believe [change] will cause [outcome], which we'll measure by [metric].' Should identify this as an A/B test (two variants). Should calculate or reference sample size needs based on 15,000 monthly visitors and 3.2% baseline. Should define primary metric (signup rate), secondary metrics, and guardrail metrics. Should warn about the peeking problem and recommend a fixed test duration. Should provide the test plan in the structured output format.",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Uses the hypothesis framework with observation, belief, outcome, and metric",
+        "Identifies as A/B test type",
+        "Addresses sample size calculation based on traffic and baseline rate",
+        "Defines primary metric (signup rate)",
+        "Defines secondary and guardrail metrics",
+        "Warns about the peeking problem",
+        "Provides structured test plan output"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "we want to test like 4 different CTA button colors on our pricing page. is that a good idea?",
+      "expected_output": "Should trigger on casual phrasing. Should identify this as an A/B/n test (multiple variants). Should caution that testing 4 variants requires significantly more traffic than a simple A/B test. Should reference the sample size quick reference showing traffic multipliers for multiple variants. Should question whether button color alone is likely to produce meaningful lift vs testing CTA copy, placement, or surrounding context. Should recommend either reducing to 2 variants or ensuring sufficient traffic. Should still provide hypothesis framework and test setup if proceeding.",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Identifies as A/B/n test (multiple variants)",
+        "Cautions about increased traffic needs for 4 variants",
+        "References sample size requirements",
+        "Questions whether button color alone is high-impact",
+        "Suggests alternative higher-impact elements to test",
+        "Provides hypothesis framework"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "Our test has been running for 3 days and Variant B is winning with 95% confidence. Should we call it?",
+      "expected_output": "Should immediately address the peeking problem. Should explain that checking results early inflates false positive rates. Should recommend running for the full pre-calculated duration regardless of early results. Should explain why early significance can be misleading (regression to the mean, day-of-week effects, audience mix shifts). Should provide guidance on when it IS appropriate to stop early (sequential testing methods). Should recommend the pre-test commitment to duration.",
+      "assertions": [
+        "Addresses the peeking problem directly",
+        "Explains why early significance is misleading",
+        "Recommends running for full pre-calculated duration",
+        "Mentions day-of-week effects or audience mix shifts",
+        "Explains false positive rate inflation from peeking",
+        "Mentions sequential testing as alternative approach"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "Help me set up a multivariate test on our landing page. I want to test the headline, hero image, and CTA button simultaneously.",
+      "expected_output": "Should identify this as a Multivariate Test (MVT). Should explain that MVT tests combinations of elements and requires much more traffic than A/B tests. Should calculate or reference traffic needs (combinations multiply: e.g., 2 headlines × 2 images × 2 CTAs = 8 combinations). Should recommend MVT only if traffic supports it, otherwise suggest sequential A/B tests. Should build hypotheses for each element being tested. Should define interaction effects to watch for. Should provide structured test plan.",
+      "assertions": [
+        "Identifies as multivariate test (MVT)",
+        "Explains MVT tests combinations of elements",
+        "Addresses dramatically higher traffic requirements",
+        "Calculates number of combinations",
+        "Suggests sequential A/B tests as alternative if traffic insufficient",
+        "Builds hypotheses for each element",
+        "Provides structured test plan"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "What metrics should I track for an A/B test on our trial signup page? We're testing a longer form (adds company size and role fields) against the current short form.",
+      "expected_output": "Should apply the metrics selection framework with three tiers: primary, secondary, and guardrail metrics. Primary: form completion rate (the direct conversion metric). Secondary: lead quality metrics (SQL conversion rate, activation rate post-signup). Guardrail: overall signup volume (ensure longer form doesn't tank total signups below acceptable threshold). Should explain the tradeoff between conversion quantity and lead quality. Should note that this test needs longer observation window to measure downstream metrics.",
+      "assertions": [
+        "Applies three-tier metric framework (primary, secondary, guardrail)",
+        "Identifies form completion rate as primary metric",
+        "Identifies lead quality as secondary metric",
+        "Defines guardrail metrics to protect against negative outcomes",
+        "Explains quantity vs quality tradeoff",
+        "Notes need for longer observation window for downstream metrics"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "Can you help me write copy for our new landing page? We want to test it against the current version.",
+      "expected_output": "Should recognize this is primarily a copywriting task, not a test setup task. Should defer to or cross-reference the copywriting skill for writing the actual copy. May help frame the test hypothesis and setup, but should make clear that copywriting is the right skill for creating the page copy itself.",
+      "assertions": [
+        "Recognizes this as primarily a copywriting task",
+        "References or defers to copywriting skill",
+        "Does not attempt to write full page copy using test setup patterns",
+        "May offer to help with test hypothesis and setup"
+      ],
+      "files": []
+    },
+    {
+      "id": 7,
+      "prompt": "We ran an A/B test on our pricing page for 4 weeks. Control: 2.1% conversion. Variant: 2.4% conversion. 12,000 visitors per variant. Is this statistically significant? Should we ship it?",
+      "expected_output": "Should evaluate the results against statistical significance criteria. Should calculate or estimate whether the sample size is sufficient to detect a 0.3 percentage point lift from a 2.1% baseline (this is a ~14% relative lift). Should reference the 95% confidence threshold. Should discuss practical significance vs statistical significance. Should recommend whether to ship, continue testing, or iterate. Should consider segment analysis if results are borderline.",
+      "assertions": [
+        "Evaluates against statistical significance criteria",
+        "Addresses whether sample size is sufficient for this effect size",
+        "References 95% confidence threshold",
+        "Distinguishes statistical significance from practical significance",
+        "Provides clear recommendation on shipping",
+        "Suggests segment analysis or follow-up if borderline"
+      ],
+      "files": []
+    }
+  ]
+}

skills/ab-testing/references/sample-size-guide.md

@@ -2,6 +2,17 @@
 
 Reference for calculating sample sizes and test duration.
 
+## Contents
+- Sample Size Fundamentals (required inputs, what these mean)
+- Sample Size Quick Reference Tables
+- Duration Calculator (formula, examples, minimum duration rules, maximum duration guidelines)
+- Online Calculators
+- Adjusting for Multiple Variants
+- Common Sample Size Mistakes
+- When Sample Size Requirements Are Too High
+- Sequential Testing
+- Quick Decision Framework
+
 ## Sample Size Fundamentals
 
 ### Required Inputs

skills/ab-testing/references/test-templates.md

@@ -2,6 +2,15 @@
 
 Templates for planning, documenting, and analyzing experiments.
 
+## Contents
+- Test Plan Template
+- Results Documentation Template
+- Test Repository Entry Template
+- Quick Test Brief Template
+- Stakeholder Update Template
+- Experiment Prioritization Scorecard
+- Hypothesis Bank Template
+
 ## Test Plan Template
 
 ```markdown

skills/ad-creative/SKILL.md

@@ -0,0 +1,362 @@
+---
+name: ad-creative
+description: "When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform. Also use when the user mentions 'ad copy variations,' 'ad creative,' 'generate headlines,' 'RSA headlines,' 'bulk ad copy,' 'ad iterations,' 'creative testing,' 'ad performance optimization,' 'write me some ads,' 'Facebook ad copy,' 'Google ad headlines,' 'LinkedIn ad text,' or 'I need more ad variations.' Use this whenever someone needs to produce ad copy at scale or iterate on existing ads. For campaign strategy and targeting, see paid-ads. For landing page copy, see copywriting."
+metadata:
+  version: 1.1.0
+---
+
+# Ad Creative
+
+You are an expert performance creative strategist. Your goal is to generate high-performing ad creative at scale — headlines, descriptions, and primary text that drive clicks and conversions — and iterate based on real performance data.
+
+## Before Starting
+
+**Check for product marketing context first:**
+If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
+
+Gather this context (ask if not provided):
+
+### 1. Platform & Format
+- What platform? (Google Ads, Meta, LinkedIn, TikTok, Twitter/X)
+- What ad format? (Search RSAs, display, social feed, stories, video)
+- Are there existing ads to iterate on, or starting from scratch?
+
+### 2. Product & Offer
+- What are you promoting? (Product, feature, free trial, demo, lead magnet)
+- What's the core value proposition?
+- What makes this different from competitors?
+
+### 3. Audience & Intent
+- Who is the target audience?
+- What stage of awareness? (Problem-aware, solution-aware, product-aware)
+- What pain points or desires drive them?
+
+### 4. Performance Data (if iterating)
+- What creative is currently running?
+- Which headlines/descriptions are performing best? (CTR, conversion rate, ROAS)
+- Which are underperforming?
+- What angles or themes have been tested?
+
+### 5. Constraints
+- Brand voice guidelines or words to avoid?
+- Compliance requirements? (Industry regulations, platform policies)
+- Any mandatory elements? (Brand name, trademark symbols, disclaimers)
+
+---
+
+## How This Skill Works
+
+This skill supports two modes:
+
+### Mode 1: Generate from Scratch
+When starting fresh, you generate a full set of ad creative based on product context, audience insights, and platform best practices.
+
+### Mode 2: Iterate from Performance Data
+When the user provides performance data (CSV, paste, or API output), you analyze what's working, identify patterns in top performers, and generate new variations that build on winning themes while exploring new angles.
+
+The core loop:
+
+```
+Pull performance data → Identify winning patterns → Generate new variations → Validate specs → Deliver
+```
+
+---
+
+## Platform Specs
+
+Platforms reject or truncate creative that exceeds these limits, so verify every piece of copy fits before delivering.
+
+### Google Ads (Responsive Search Ads)
+
+| Element | Limit | Quantity |
+|---------|-------|----------|
+| Headline | 30 characters | Up to 15 |
+| Description | 90 characters | Up to 4 |
+| Display URL path | 15 characters each | 2 paths |
+
+**RSA rules:**
+- Headlines must make sense independently and in any combination
+- Pin headlines to positions only when necessary (reduces optimization)
+- Include at least one keyword-focused headline
+- Include at least one benefit-focused headline
+- Include at least one CTA headline
+
+### Meta Ads (Facebook/Instagram)
+
+| Element | Limit | Notes |
+|---------|-------|-------|
+| Primary text | 125 chars visible (up to 2,200) | Front-load the hook |
+| Headline | 40 characters recommended | Below the image |
+| Description | 30 characters recommended | Below headline |
+| URL display link | 40 characters | Optional |
+
+### LinkedIn Ads
+
+| Element | Limit | Notes |
+|---------|-------|-------|
+| Intro text | 150 chars recommended (600 max) | Above the image |
+| Headline | 70 chars recommended (200 max) | Below the image |
+| Description | 100 chars recommended (300 max) | Appears in some placements |
+
+### TikTok Ads
+
+| Element | Limit | Notes |
+|---------|-------|-------|
+| Ad text | 80 chars recommended (100 max) | Above the video |
+| Display name | 40 characters | Brand name |
+
+### Twitter/X Ads
+
+| Element | Limit | Notes |
+|---------|-------|-------|
+| Tweet text | 280 characters | The ad copy |
+| Headline | 70 characters | Card headline |
+| Description | 200 characters | Card description |
+
+For detailed specs and format variations, see [references/platform-specs.md](references/platform-specs.md).
+
+---
+
+## Generating Ad Visuals
+
+For image and video ad creative, use generative AI tools and code-based video rendering. See [references/generative-tools.md](references/generative-tools.md) for the complete guide covering:
+
+- **Image generation** — Nano Banana Pro (Gemini), Flux, Ideogram for static ad images
+- **Video generation** — Veo, Kling, Runway, Sora, Seedance, Higgsfield for video ads
+- **Voice & audio** — ElevenLabs, OpenAI TTS, Cartesia for voiceovers, cloning, multilingual
+- **Code-based video** — Remotion for templated, data-driven video at scale
+- **Platform image specs** — Correct dimensions for every ad placement
+- **Cost comparison** — Pricing for 100+ ad variations across tools
+
+**Recommended workflow for scaled production:**
+1. Generate hero creative with AI tools (exploratory, high-quality)
+2. Build Remotion templates based on winning patterns
+3. Batch produce variations with Remotion using data feeds
+4. Iterate — AI for new angles, Remotion for scale
+
+---
+
+## Generating Ad Copy
+
+### Step 1: Define Your Angles
+
+Before writing individual headlines, establish 3-5 distinct **angles** — different reasons someone would click. Each angle should tap into a different motivation.
+
+**Common angle categories:**
+
+| Category | Example Angle |
+|----------|---------------|
+| Pain point | "Stop wasting time on X" |
+| Outcome | "Achieve Y in Z days" |
+| Social proof | "Join 10,000+ teams who..." |
+| Curiosity | "The X secret top companies use" |
+| Comparison | "Unlike X, we do Y" |
+| Urgency | "Limited time: get X free" |
+| Identity | "Built for [specific role/type]" |
+| Contrarian | "Why [common practice] doesn't work" |
+
+### Step 2: Generate Variations per Angle
+
+For each angle, generate multiple variations. Vary:
+- **Word choice** — synonyms, active vs. passive
+- **Specificity** — numbers vs. general claims
+- **Tone** — direct vs. question vs. command
+- **Structure** — short punch vs. full benefit statement
+
+### Step 3: Validate Against Specs
+
+Before delivering, check every piece of creative against the platform's character limits. Flag anything that's over and provide a trimmed alternative.
+
+### Step 4: Organize for Upload
+
+Present creative in a structured format that maps to the ad platform's upload requirements.
+
+---
+
+## Iterating from Performance Data
+
+When the user provides performance data, follow this process:
+
+### Step 1: Analyze Winners
+
+Look at the top-performing creative (by CTR, conversion rate, or ROAS — ask which metric matters most) and identify:
+
+- **Winning themes** — What topics or pain points appear in top performers?
+- **Winning structures** — Questions? Statements? Commands? Numbers?
+- **Winning word patterns** — Specific words or phrases that recur?
+- **Character utilization** — Are top performers shorter or longer?
+
+### Step 2: Analyze Losers
+
+Look at the worst performers and identify:
+
+- **Themes that fall flat** — What angles aren't resonating?
+- **Common patterns in low performers** — Too generic? Too long? Wrong tone?
+
+### Step 3: Generate New Variations
+
+Create new creative that:
+- **Doubles down** on winning themes with fresh phrasing
+- **Extends** winning angles into new variations
+- **Tests** 1-2 new angles not yet explored
+- **Avoids** patterns found in underperformers
+
+### Step 4: Document the Iteration
+
+Track what was learned and what's being tested:
+
+```
+## Iteration Log
+- Round: [number]
+- Date: [date]
+- Top performers: [list with metrics]
+- Winning patterns: [summary]
+- New variations: [count] headlines, [count] descriptions
+- New angles being tested: [list]
+- Angles retired: [list]
+```
+
+---
+
+## Writing Quality Standards
+
+### Headlines That Click
+
+**Strong headlines:**
+- Specific ("Cut reporting time 75%") over vague ("Save time")
+- Benefits ("Ship code faster") over features ("CI/CD pipeline")
+- Active voice ("Automate your reports") over passive ("Reports are automated")
+- Include numbers when possible ("3x faster," "in 5 minutes," "10,000+ teams")
+
+**Avoid:**
+- Jargon the audience won't recognize
+- Claims without specificity ("Best," "Leading," "Top")
+- All caps or excessive punctuation
+- Clickbait that the landing page can't deliver on
+
+### Descriptions That Convert
+
+Descriptions should complement headlines, not repeat them. Use descriptions to:
+- Add proof points (numbers, testimonials, awards)
+- Handle objections ("No credit card required," "Free forever for small teams")
+- Reinforce CTAs ("Start your free trial today")
+- Add urgency when genuine ("Limited to first 500 signups")
+
+---
+
+## Output Formats
+
+### Standard Output
+
+Organize by angle, with character counts:
+
+```
+## Angle: [Pain Point — Manual Reporting]
+
+### Headlines (30 char max)
+1. "Stop Building Reports by Hand" (29)
+2. "Automate Your Weekly Reports" (28)
+3. "Reports Done in 5 Min, Not 5 Hr" (31) <- OVER LIMIT, trimmed below
+   -> "Reports in 5 Min, Not 5 Hrs" (27)
+
+### Descriptions (90 char max)
+1. "Marketing teams save 10+ hours/week with automated reporting. Start free." (73)
+2. "Connect your data sources once. Get automated reports forever. No code required." (80)
+```
+
+### Bulk CSV Output
+
+When generating at scale (10+ variations), offer CSV format for direct upload:
+
+```csv
+headline_1,headline_2,headline_3,description_1,description_2,platform
+"Stop Manual Reporting","Automate in 5 Minutes","Join 10K+ Teams","Save 10+ hrs/week on reports. Start free.","Connect data sources once. Reports forever.","google_ads"
+```
+
+### Iteration Report
+
+When iterating, include a summary:
+
+```
+## Performance Summary
+- Analyzed: [X] headlines, [Y] descriptions
+- Top performer: "[headline]" — [metric]: [value]
+- Worst performer: "[headline]" — [metric]: [value]
+- Pattern: [observation]
+
+## New Creative
+[organized variations]
+
+## Recommendations
+- [What to pause, what to scale, what to test next]
+```
+
+---
+
+## Batch Generation Workflow
+
+For large-scale creative production (Anthropic's growth team generates 100+ variations per cycle):
+
+### 1. Break into sub-tasks
+- **Headline generation** — Focused on click-through
+- **Description generation** — Focused on conversion
+- **Primary text generation** — Focused on engagement (Meta/LinkedIn)
+
+### 2. Generate in waves
+- Wave 1: Core angles (3-5 angles, 5 variations each)
+- Wave 2: Extended variations on top 2 angles
+- Wave 3: Wild card angles (contrarian, emotional, specific)
+
+### 3. Quality filter
+- Remove anything over character limit
+- Remove duplicates or near-duplicates
+- Flag anything that might violate platform policies
+- Ensure headline/description combinations make sense together
+
+---
+
+## Common Mistakes
+
+- **Writing headlines that only work together** — RSA headlines get combined randomly
+- **Ignoring character limits** — Platforms truncate without warning
+- **All variations sound the same** — Vary angles, not just word choice
+- **No CTA headlines** — RSAs need action-oriented headlines to drive clicks; include at least 2-3
+- **Generic descriptions** — "Learn more about our solution" wastes the slot
+- **Iterating without data** — Gut feelings are less reliable than metrics
+- **Testing too many things at once** — Change one variable per test cycle
+- **Retiring creative too early** — Allow 1,000+ impressions before judging
+
+---
+
+## Tool Integrations
+
+For pulling performance data and managing campaigns, see the [tools registry](../../tools/REGISTRY.md).
+
+| Platform | Pull Performance Data | Manage Campaigns | Guide |
+|----------|:---------------------:|:----------------:|-------|
+| **Google Ads** | `google-ads campaigns list`, `google-ads reports get` | `google-ads campaigns create` | [google-ads.md](../../tools/integrations/google-ads.md) |
+| **Meta Ads** | `meta-ads insights get` | `meta-ads campaigns list` | [meta-ads.md](../../tools/integrations/meta-ads.md) |
+| **LinkedIn Ads** | `linkedin-ads analytics get` | `linkedin-ads campaigns list` | [linkedin-ads.md](../../tools/integrations/linkedin-ads.md) |
+| **TikTok Ads** | `tiktok-ads reports get` | `tiktok-ads campaigns list` | [tiktok-ads.md](../../tools/integrations/tiktok-ads.md) |
+
+### Workflow: Pull Data, Analyze, Generate
+
+```bash
+# 1. Pull recent ad performance
+node tools/clis/google-ads.js reports get --type ad_performance --date-range last_30_days
+
+# 2. Analyze output (identify top/bottom performers)
+# 3. Feed winning patterns into this skill
+# 4. Generate new variations
+# 5. Upload to platform
+```
+
+---
+
+## Related Skills
+
+- **paid-ads**: For campaign strategy, targeting, budgets, and optimization
+- **copywriting**: For landing page copy (where ad traffic lands)
+- **ab-testing**: For structuring creative tests with statistical rigor
+- **marketing-psychology**: For psychological principles behind high-performing creative
+- **copy-editing**: For polishing ad copy before launch

skills/ad-creative/evals/evals.json

@@ -0,0 +1,90 @@
+{
+  "skill_name": "ad-creative",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Generate ad creative for our Meta (Facebook/Instagram) campaign. We sell an AI writing assistant for content marketers. Main value prop: write blog posts 5x faster. Target audience: content marketing managers at B2B SaaS companies. Budget: $5k/month.",
+      "expected_output": "Should check for product-marketing-context.md first. Should generate creative following the angle-based approach: identify 3-5 angles (speed, quality, ROI, pain of blank page, competitive edge). For each angle, should generate primary text (≤125 chars), headline (≤40 chars), and description (≤30 chars) respecting Meta character limits. Should provide multiple variations per angle. Should suggest image/visual direction for each. Should organize output with angle name, hook, body, CTA for each variation. Should recommend which angles to test first.",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Uses angle-based generation approach",
+        "Identifies multiple angles (3-5)",
+        "Respects Meta character limits (125/40/30)",
+        "Generates multiple variations per angle",
+        "Suggests image or visual direction",
+        "Includes hook, body, and CTA for each",
+        "Recommends which angles to test first"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "I need Google Ads copy for our CRM product. We're targeting the keyword 'best CRM for small business'. Need responsive search ads.",
+      "expected_output": "Should generate Google RSA creative respecting character limits: headlines (≤30 chars each, need 10-15 variations) and descriptions (≤90 chars each, need 4+ variations). Should note that pinning should be used sparingly as it reduces optimization. Should include the target keyword in headlines. Should provide multiple angle-based variations. Should suggest ad extensions (sitelinks, callouts, structured snippets). Should follow Google Ads best practices for RSA.",
+      "assertions": [
+        "Respects Google RSA character limits (30 char headlines, 90 char descriptions)",
+        "Generates 10-15 headline variations",
+        "Generates 4+ description variations",
+        "Includes target keyword in headlines",
+        "Notes pinning should be used sparingly per skill guidance",
+        "Suggests ad extensions",
+        "Uses angle-based variation approach"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "Here's our ad performance data: Ad A (pain point angle) - CTR 2.1%, CPC $3.20, Conv rate 4.5%. Ad B (social proof angle) - CTR 1.4%, CPC $4.10, Conv rate 6.2%. Ad C (feature angle) - CTR 0.8%, CPC $5.50, Conv rate 2.1%. Help me iterate on these.",
+      "expected_output": "Should activate the iteration-from-performance mode (not generate-from-scratch). Should analyze the data: Ad A has best CTR, Ad B has best conversion rate (highest efficiency despite lower CTR), Ad C is underperforming on all metrics. Should recommend doubling down on the pain point angle (high CTR) and social proof angle (high conversion), while pausing or reworking the feature angle. Should generate new variations that combine winning elements (pain point hook + social proof). Should suggest specific iterations on Ad A and Ad B.",
+      "assertions": [
+        "Activates iteration mode based on performance data",
+        "Analyzes CTR, CPC, and conversion rate for each ad",
+        "Identifies winning angles from the data",
+        "Recommends pausing or reworking underperforming creative",
+        "Generates new variations combining winning elements",
+        "Provides specific iterations on top performers"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "we need linkedin ads for our enterprise security product. audience is CISOs and IT directors.",
+      "expected_output": "Should trigger on casual phrasing. Should generate LinkedIn ad creative respecting character limits: introductory text (≤150 chars), headline (≤70 chars), description (≤100 chars). Should adapt tone and messaging for enterprise security audience (CISOs, IT directors) — more formal, compliance-focused, risk-reduction language. Should provide multiple angles relevant to security buyers (risk reduction, compliance, incident response time, cost of breaches). Should suggest ad format recommendations for LinkedIn (sponsored content, message ads, etc.).",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Respects LinkedIn character limits (150/70/100)",
+        "Adapts tone for enterprise security audience",
+        "Uses risk-reduction and compliance language",
+        "Provides multiple angles relevant to security buyers",
+        "Suggests LinkedIn ad format recommendations"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "I need to generate a big batch of ad variations for a multi-platform campaign launching next week. We're a meal delivery service targeting busy professionals. Need ads for Google, Meta, and TikTok.",
+      "expected_output": "Should activate the batch generation workflow. Should generate creative for all three platforms respecting each platform's character limits: Google RSA (30/90), Meta (125/40/30), TikTok (80 chars recommended, 100 max). Should identify 3-5 angles that work across platforms (convenience, health, time savings, variety, cost vs eating out). Should generate variations per angle per platform. Should note platform-specific creative considerations (TikTok needs video concepts, not just text). Should organize output clearly by platform.",
+      "assertions": [
+        "Activates batch generation workflow",
+        "Generates for all three platforms",
+        "Respects each platform's character limits",
+        "Identifies angles that work across platforms",
+        "Notes TikTok needs video concepts",
+        "Organizes output by platform",
+        "Generates multiple variations per angle per platform"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "Help me plan our overall paid advertising strategy. We have a $20k monthly budget and want to figure out which platforms to use and how to allocate spend.",
+      "expected_output": "Should recognize this is a paid advertising strategy task, not ad creative generation. Should defer to or cross-reference the paid-ads skill, which handles campaign strategy, platform selection, and budget allocation. May briefly mention creative considerations but should make clear that paid-ads is the right skill for strategy.",
+      "assertions": [
+        "Recognizes this as paid ads strategy, not creative generation",
+        "References or defers to paid-ads skill",
+        "Does not attempt full campaign strategy using creative generation patterns"
+      ],
+      "files": []
+    }
+  ]
+}

skills/ad-creative/references/generative-tools.md

@@ -0,0 +1,637 @@
+# Generative AI Tools for Ad Creative
+
+Reference for using AI image generators, video generators, and code-based video tools to produce ad visuals at scale.
+
+---
+
+## When to Use Generative Tools
+
+| Need | Tool Category | Best Fit |
+|------|---------------|----------|
+| Static ad images (banners, social) | Image generation | Nano Banana Pro, Flux, Ideogram |
+| Ad images with text overlays | Image generation (text-capable) | Ideogram, Nano Banana Pro |
+| Short video ads (6-30 sec) | Video generation | Veo, Kling, Runway, Sora, Seedance |
+| Video ads with voiceover | Video gen + voice | Veo/Sora (native), or Runway + ElevenLabs |
+| Voiceover tracks for ads | Voice generation | ElevenLabs, OpenAI TTS, Cartesia |
+| Multi-language ad versions | Voice generation | ElevenLabs, PlayHT |
+| Brand voice cloning | Voice generation | ElevenLabs, Resemble AI |
+| Product mockups and variations | Image generation + references | Flux (multi-image reference) |
+| Templated video ads at scale | Code-based video | Remotion |
+| Personalized video (name, data) | Code-based video | Remotion |
+| Brand-consistent variations | Image gen + style refs | Flux, Ideogram, Nano Banana Pro |
+
+---
+
+## Image Generation
+
+### Nano Banana Pro (Gemini)
+
+Google DeepMind's image generation model, available through the Gemini API.
+
+**Best for:** High-quality ad images, product visuals, text rendering
+**API:** Gemini API (Google AI Studio, Vertex AI)
+**Pricing:** ~$0.04/image (Gemini 2.5 Flash Image), ~$0.24/4K image (Nano Banana Pro)
+
+**Strengths:**
+- Strong text rendering in images (logos, headlines)
+- Native image editing (modify existing images with prompts)
+- Available through the same Gemini API used for text generation
+- Supports both generation and editing in one model
+
+**Ad creative use cases:**
+- Generate social media ad images from text descriptions
+- Create product mockup variations
+- Edit existing ad images (swap backgrounds, change colors)
+- Generate images with headline text baked in
+
+**API example:**
+```bash
+# Using the Gemini API for image generation
+curl -X POST "https://generativelanguage.googleapis.com/v1beta/models/gemini-2.5-flash-image:generateContent" \
+  -H "Content-Type: application/json" \
+  -H "x-goog-api-key: $GEMINI_API_KEY" \
+  -d '{
+    "contents": [{"parts": [{"text": "Create a clean, modern social media ad image for a project management tool. Show a laptop with a kanban board interface. Bright, professional, 16:9 ratio."}]}],
+    "generationConfig": {"responseModalities": ["TEXT", "IMAGE"]}
+  }'
+```
+
+**Docs:** [Gemini Image Generation](https://ai.google.dev/gemini-api/docs/image-generation)
+
+---
+
+### Flux (Black Forest Labs)
+
+Open-weight image generation models with API access through Replicate and BFL's native API.
+
+**Best for:** Photorealistic images, brand-consistent variations, multi-reference generation
+**API:** Replicate, BFL API, fal.ai
+**Pricing:** ~$0.01-0.06/image depending on model and resolution
+
+**Model variants:**
+| Model | Speed | Quality | Cost | Best For |
+|-------|-------|---------|------|----------|
+| Flux 2 Pro | ~6 sec | Highest | $0.015/MP | Final production assets |
+| Flux 2 Flex | ~22 sec | High + editing | $0.06/MP | Iterative editing |
+| Flux 2 Dev | ~2.5 sec | Good | $0.012/MP | Rapid prototyping |
+| Flux 2 Klein | Fastest | Good | Lowest | High-volume batch generation |
+
+**Strengths:**
+- Multi-image reference (up to 8 images) for consistent identity across ads
+- Product consistency — same product in different contexts
+- Style transfer from reference images
+- Open-weight Dev model for self-hosting
+
+**Ad creative use cases:**
+- Generate 50+ ad variations with consistent product/person identity
+- Create product-in-context images (your SaaS on different devices)
+- Style-match to existing brand assets using reference images
+- Rapid A/B test image variations
+
+**Docs:** [Replicate Flux](https://replicate.com/black-forest-labs/flux-2-pro), [BFL API](https://docs.bfl.ml/)
+
+---
+
+### Ideogram
+
+Specialized in typography and text rendering within images.
+
+**Best for:** Ad banners with text, branded graphics, social ad images with headlines
+**API:** Ideogram API, Runware
+**Pricing:** ~$0.06/image (API), ~$0.009/image (subscription)
+
+**Strengths:**
+- Best-in-class text rendering (~90% accuracy vs ~30% for most tools)
+- Style reference system (upload up to 3 reference images)
+- 4.3 billion style presets for consistent brand aesthetics
+- Strong at logos and branded typography
+
+**Ad creative use cases:**
+- Generate ad banners with headline text directly in the image
+- Create social media graphics with branded text overlays
+- Produce multiple design variations with consistent typography
+- Generate promotional materials without needing a designer for each iteration
+
+**Docs:** [Ideogram API](https://developer.ideogram.ai/), [Ideogram](https://ideogram.ai/)
+
+---
+
+### Other Image Tools
+
+| Tool | Best For | API Status | Notes |
+|------|----------|------------|-------|
+| **DALL-E 3** (OpenAI) | General image generation | Official API | Integrated with ChatGPT, good text rendering |
+| **Midjourney** | Artistic, high-aesthetic images | No official public API | Discord-based; unofficial APIs exist but risk bans |
+| **Stable Diffusion** | Self-hosted, customizable | Open source | Best for teams with GPU infrastructure |
+
+---
+
+## Video Generation
+
+### Google Veo
+
+Google DeepMind's video generation model, available through the Gemini API and Vertex AI.
+
+**Best for:** High-quality video ads with native audio, vertical video for social
+**API:** Gemini API, Vertex AI
+**Pricing:** ~$0.15/sec (Veo 3.1 Fast), ~$0.40/sec (Veo 3.1 Standard)
+
+**Capabilities:**
+- Up to 60 seconds at 1080p
+- Native audio generation (dialogue, sound effects, ambient)
+- Vertical 9:16 output for Stories/Reels/Shorts
+- Upscale to 4K
+- Text-to-video and image-to-video
+
+**Ad creative use cases:**
+- Generate short video ads (15-30 sec) from text descriptions
+- Create vertical video ads for TikTok, Reels, Shorts
+- Produce product demos with voiceover
+- Generate multiple video variations from the same prompt with different styles
+
+**Docs:** [Veo on Vertex AI](https://cloud.google.com/vertex-ai/generative-ai/docs/video/overview)
+
+---
+
+### Kling (Kuaishou)
+
+Video generation with simultaneous audio-visual generation and camera controls.
+
+**Best for:** Cinematic video ads, longer-form content, audio-synced video
+**API:** Kling API, PiAPI, fal.ai
+**Pricing:** ~$0.09/sec (via fal.ai third-party)
+
+**Capabilities:**
+- Up to 3 minutes at 1080p/30-48fps
+- Simultaneous audio-visual generation (Kling 2.6)
+- Text-to-video and image-to-video
+- Motion and camera controls
+
+**Ad creative use cases:**
+- Longer product explainer videos
+- Cinematic brand videos with synchronized audio
+- Animate product images into video ads
+
+**Docs:** [Kling AI Developer](https://klingai.com/global/dev/model/video)
+
+---
+
+### Runway
+
+Video generation and editing platform with strong controllability.
+
+**Best for:** Controlled video generation, style-consistent content, editing existing footage
+**API:** Runway Developer Portal
+
+**Capabilities:**
+- Gen-4: Character/scene consistency across shots
+- Motion brush and camera controls
+- Image-to-video with reference images
+- Video-to-video style transfer
+
+**Ad creative use cases:**
+- Generate video ads with consistent characters/products across scenes
+- Style-transfer existing footage to match brand aesthetics
+- Extend or remix existing video content
+
+**Docs:** [Runway API](https://docs.dev.runwayml.com/)
+
+---
+
+### Sora 2 (OpenAI)
+
+OpenAI's video generation model with synchronized audio.
+
+**Best for:** High-fidelity video with dialogue and sound
+**API:** OpenAI API
+**Pricing:** Free tier available; Pro from $0.10-0.50/sec depending on resolution
+
+**Capabilities:**
+- Up to 60 seconds with synchronized audio
+- Dialogue, sound effects, and ambient audio
+- sora-2 (fast) and sora-2-pro (quality) variants
+- Text-to-video and image-to-video
+
+**Ad creative use cases:**
+- Video testimonials and talking-head style ads
+- Product demo videos with narration
+- Narrative brand videos
+
+**Docs:** [OpenAI Video Generation](https://platform.openai.com/docs/guides/video-generation)
+
+---
+
+### Seedance 2.0 (ByteDance)
+
+ByteDance's video generation model with simultaneous audio-visual generation and multimodal inputs.
+
+**Best for:** Fast, affordable video ads with native audio, multimodal reference inputs
+**API:** BytePlus (official), Replicate, WaveSpeedAI, fal.ai (third-party); OpenAI-compatible API format
+**Pricing:** ~$0.10-0.80/min depending on resolution (estimated 10-100x cheaper than Sora 2 per clip)
+
+**Capabilities:**
+- Up to 20 seconds at up to 2K resolution
+- Simultaneous audio-visual generation (Dual-Branch Diffusion Transformer)
+- Text-to-video and image-to-video
+- Up to 12 reference files for multimodal input
+- OpenAI-compatible API structure
+
+**Ad creative use cases:**
+- High-volume short video ad production at low cost
+- Video ads with synchronized voiceover and sound effects in one pass
+- Multi-reference generation (feed product images, brand assets, style references)
+- Rapid iteration on video ad concepts
+
+**Docs:** [Seedance](https://seed.bytedance.com/en/seedance2_0)
+
+---
+
+### Higgsfield
+
+Full-stack video creation platform with cinematic camera controls.
+
+**Best for:** Social video ads, cinematic style, mobile-first content
+**Platform:** [higgsfield.ai](https://higgsfield.ai/)
+
+**Capabilities:**
+- 50+ professional camera movements (zooms, pans, FPV drone shots)
+- Image-to-video animation
+- Built-in editing, transitions, and keyframing
+- All-in-one workflow: image gen, animation, editing
+
+**Ad creative use cases:**
+- Social media video ads with cinematic feel
+- Animate product images into dynamic video
+- Create multiple video variations with different camera styles
+- Quick-turn video content for social campaigns
+
+---
+
+### Video Tool Comparison
+
+| Tool | Max Length | Audio | Resolution | API | Best For |
+|------|-----------|-------|------------|-----|----------|
+| **Veo 3.1** | 60 sec | Native | 1080p/4K | Gemini | Vertical social video |
+| **Kling 2.6** | 3 min | Native | 1080p | Third-party | Longer cinematic |
+| **Runway Gen-4** | 10 sec | No | 1080p | Official | Controlled, consistent |
+| **Sora 2** | 60 sec | Native | 1080p | Official | Dialogue-heavy |
+| **Seedance 2.0** | 20 sec | Native | 2K | Official + third-party | Affordable high-volume |
+| **Higgsfield** | Varies | Yes | 1080p | Web-based | Social, mobile-first |
+
+---
+
+## Voice & Audio Generation
+
+For layering realistic voiceovers onto video ads, adding narration to product demos, or generating audio for Remotion-rendered videos. These tools turn ad scripts into natural-sounding voice tracks.
+
+### When to Use Voice Tools
+
+Many video generators (Veo, Kling, Sora, Seedance) now include native audio. Use standalone voice tools when you need:
+
+- **Voiceover on silent video** — Runway Gen-4 and Remotion produce silent output
+- **Brand voice consistency** — Clone a specific voice for all ads
+- **Multi-language versions** — Same ad script in 20+ languages
+- **Script iteration** — Re-record voiceover without reshooting video
+- **Precise control** — Exact timing, emotion, and pacing
+
+---
+
+### ElevenLabs
+
+The market leader in realistic voice generation and voice cloning.
+
+**Best for:** Most natural-sounding voiceovers, brand voice cloning, multilingual
+**API:** REST API with streaming support
+**Pricing:** ~$0.12-0.30 per 1,000 characters depending on plan; starts at $5/month
+
+**Capabilities:**
+- 29+ languages with natural accent and intonation
+- Voice cloning from short audio clips (instant) or longer recordings (professional)
+- Emotion and style control
+- Streaming for real-time generation
+- Voice library with hundreds of pre-built voices
+
+**Ad creative use cases:**
+- Generate voiceover tracks for video ads
+- Clone your brand spokesperson's voice for all ad variations
+- Produce the same ad in 10+ languages from one script
+- A/B test different voice styles (authoritative vs. friendly vs. urgent)
+
+**API example:**
+```bash
+curl -X POST "https://api.elevenlabs.io/v1/text-to-speech/{voice_id}" \
+  -H "xi-api-key: $ELEVENLABS_API_KEY" \
+  -H "Content-Type: application/json" \
+  -d '{
+    "text": "Stop wasting hours on manual reporting. Try DataFlow free for 14 days.",
+    "model_id": "eleven_multilingual_v2",
+    "voice_settings": {"stability": 0.5, "similarity_boost": 0.75}
+  }' --output voiceover.mp3
+```
+
+**Docs:** [ElevenLabs API](https://elevenlabs.io/docs/api-reference/text-to-speech)
+
+---
+
+### OpenAI TTS
+
+Simple, affordable text-to-speech built into the OpenAI API.
+
+**Best for:** Quick voiceovers, cost-effective at scale, simple integration
+**API:** OpenAI API (same SDK as GPT/DALL-E)
+**Pricing:** $15/million chars (standard), $30/million chars (HD); ~$0.015/min with gpt-4o-mini-tts
+
+**Capabilities:**
+- 13 built-in voices (no custom cloning)
+- Multiple languages
+- Real-time streaming
+- HD quality option
+- Simple API — same SDK you already use for GPT
+
+**Ad creative use cases:**
+- Fast, cheap voiceover for draft/test ad versions
+- High-volume narration at low cost
+- Prototype ad audio before investing in premium voice
+
+**Docs:** [OpenAI TTS](https://platform.openai.com/docs/guides/text-to-speech)
+
+---
+
+### Cartesia Sonic
+
+Ultra-low latency voice generation built for real-time applications.
+
+**Best for:** Real-time voice, lowest latency, emotional expressiveness
+**API:** REST + WebSocket streaming
+**Pricing:** Starts at $5/month; pay-as-you-go from $0.03/min
+
+**Capabilities:**
+- 40ms time-to-first-audio (fastest in class)
+- 15+ languages
+- Nonverbal expressiveness: laughter, breathing, emotional inflections
+- Sonic Turbo for even lower latency
+- Streaming API for real-time generation
+
+**Ad creative use cases:**
+- Real-time ad preview during creative iteration
+- Interactive demo videos with dynamic narration
+- Ads requiring natural laughter, sighs, or emotional reactions
+
+**Docs:** [Cartesia Sonic](https://docs.cartesia.ai/build-with-cartesia/tts-models/latest)
+
+---
+
+### Voicebox (Open Source)
+
+Free, local-first voice synthesis studio powered by Qwen3-TTS. The open-source alternative to ElevenLabs.
+
+**Best for:** Free voice cloning, local/private generation, zero-cost batch production
+**API:** Local REST API at `http://localhost:8000`
+**Pricing:** Free (MIT license). Runs entirely on your machine.
+**Stack:** Tauri (Rust) + React + FastAPI (Python)
+
+**Capabilities:**
+- Voice cloning from short audio samples via Qwen3-TTS
+- Multi-language support (English, Chinese, more planned)
+- Multi-track timeline editor for composing conversations
+- 4-5x faster inference on Apple Silicon via MLX Metal acceleration
+- Local REST API for programmatic generation
+- No cloud dependency — all processing on-device
+
+**Ad creative use cases:**
+- Free voice cloning for brand spokesperson across all ad variations
+- Batch generate voiceovers without per-character costs
+- Private/local generation when ad content is sensitive or pre-launch
+- Prototype voice variations before committing to a paid service
+
+**API example:**
+```bash
+curl -X POST http://localhost:8000/generate \
+  -H "Content-Type: application/json" \
+  -d '{"text": "Stop wasting hours on manual reporting.", "profile_id": "abc123", "language": "en"}'
+```
+
+**Install:** Desktop apps for macOS and Windows at [voicebox.sh](https://voicebox.sh), or build from source:
+```bash
+git clone https://github.com/jamiepine/voicebox.git
+cd voicebox && make setup && make dev
+```
+
+**Docs:** [GitHub](https://github.com/jamiepine/voicebox)
+
+---
+
+### Other Voice Tools
+
+| Tool | Best For | Differentiator | API |
+|------|----------|---------------|-----|
+| **PlayHT** | Large voice library, low latency | 900+ voices, <300ms latency, ultra-realistic | [play.ht](https://play.ht/) |
+| **Resemble AI** | Enterprise voice cloning | On-premise deployment, real-time speech-to-speech | [resemble.ai](https://www.resemble.ai/) |
+| **WellSaid Labs** | Ethical, commercial-safe voices | Voices from compensated actors, safe for commercial use | [wellsaid.io](https://www.wellsaid.io/) |
+| **Fish Audio** | Budget-friendly, emotion control | ~50-70% cheaper than ElevenLabs, emotion tags | [fish.audio](https://fish.audio/) |
+| **Murf AI** | Non-technical teams | Browser-based studio, 200+ voices | [murf.ai](https://murf.ai/) |
+| **Google Cloud TTS** | Google ecosystem, scale | 220+ voices, 40+ languages, enterprise SLAs | [Google TTS](https://cloud.google.com/text-to-speech) |
+| **Amazon Polly** | AWS ecosystem, cost | Neural voices, SSML control, cheap at volume | [Amazon Polly](https://aws.amazon.com/polly/) |
+
+---
+
+### Voice Tool Comparison
+
+| Tool | Quality | Cloning | Languages | Latency | Price/1K chars |
+|------|---------|---------|-----------|---------|----------------|
+| **ElevenLabs** | Best | Yes (instant + pro) | 29+ | ~200ms | $0.12-0.30 |
+| **OpenAI TTS** | Good | No | 13+ | ~300ms | $0.015-0.030 |
+| **Cartesia Sonic** | Very good | No | 15+ | ~40ms | ~$0.03/min |
+| **PlayHT** | Very good | Yes | 140+ | <300ms | ~$0.10-0.20 |
+| **Fish Audio** | Good | Yes | 13+ | ~200ms | ~$0.05-0.10 |
+| **WellSaid** | Very good | No (actor voices) | English | ~300ms | Custom pricing |
+| **Voicebox** | Good | Yes (local) | 2+ | Local | Free (open source) |
+
+### Choosing a Voice Tool
+
+```
+Need voiceover for ads?
+├── Need to clone a specific brand voice?
+│   ├── Best quality → ElevenLabs
+│   ├── Enterprise/on-premise → Resemble AI
+│   └── Budget-friendly → Fish Audio, PlayHT
+├── Need multilingual (same ad, many languages)?
+│   ├── Most languages → PlayHT (140+)
+│   └── Best quality → ElevenLabs (29+)
+├── Need free / open source / local?
+│   └── Voicebox (MIT, runs on your machine)
+├── Need cheap, fast, good-enough?
+│   └── OpenAI TTS ($0.015/min)
+├── Need commercially-safe licensing?
+│   └── WellSaid Labs (actor-compensated voices)
+└── Need real-time/interactive?
+    └── Cartesia Sonic (40ms TTFA)
+```
+
+### Workflow: Voice + Video
+
+```
+1. Write ad script (use ad-creative skill for copy)
+2. Generate voiceover with ElevenLabs/OpenAI TTS
+3. Generate or render video:
+   a. Silent video from Runway/Remotion → layer voice track
+   b. Or use Veo/Sora/Seedance with native audio (skip separate VO)
+4. Combine with ffmpeg if layering separately:
+   ffmpeg -i video.mp4 -i voiceover.mp3 -c:v copy -c:a aac output.mp4
+5. Generate variations (different scripts, voices, or languages)
+```
+
+---
+
+## Code-Based Video: Remotion
+
+For templated, data-driven video ads at scale, Remotion is the best option. Unlike AI video generators that produce unique video from prompts, Remotion uses React code to render deterministic, brand-perfect video from templates and data.
+
+**Best for:** Templated ad variations, personalized video, brand-consistent production
+**Stack:** React + TypeScript
+**Pricing:** Free for individuals/small teams; commercial license required for 4+ employees
+**Docs:** [remotion.dev](https://www.remotion.dev/)
+
+### Why Remotion for Ads
+
+| AI Video Generators | Remotion |
+|---------------------|----------|
+| Unique output each time | Deterministic, pixel-perfect |
+| Prompt-based, less control | Full code control over every frame |
+| Hard to match brand exactly | Exact brand colors, fonts, spacing |
+| One-at-a-time generation | Batch render hundreds from data |
+| No dynamic data insertion | Personalize with names, prices, stats |
+
+### Ad Creative Use Cases
+
+**1. Dynamic product ads**
+Feed a JSON array of products and render a unique video ad for each:
+```tsx
+// Simplified Remotion component for product ads
+export const ProductAd: React.FC<{
+  productName: string;
+  price: string;
+  imageUrl: string;
+  tagline: string;
+}> = ({productName, price, imageUrl, tagline}) => {
+  return (
+    <AbsoluteFill style={{backgroundColor: '#fff'}}>
+      <Img src={imageUrl} style={{width: 400, height: 400}} />
+      <h1>{productName}</h1>
+      <p>{tagline}</p>
+      <div className="price">{price}</div>
+      <div className="cta">Shop Now</div>
+    </AbsoluteFill>
+  );
+};
+```
+
+**2. A/B test video variations**
+Render the same template with different headlines, CTAs, or color schemes:
+```tsx
+const variations = [
+  {headline: "Save 50% Today", cta: "Get the Deal", theme: "urgent"},
+  {headline: "Join 10K+ Teams", cta: "Start Free", theme: "social-proof"},
+  {headline: "Built for Speed", cta: "Try It Now", theme: "benefit"},
+];
+// Render all variations programmatically
+```
+
+**3. Personalized outreach videos**
+Generate videos addressing prospects by name for cold outreach or sales.
+
+**4. Social ad batch production**
+Render the same content across different aspect ratios:
+- 1:1 for feed
+- 9:16 for Stories/Reels
+- 16:9 for YouTube
+
+### Remotion Workflow for Ad Creative
+
+```
+1. Design template in React (or use AI to generate the component)
+2. Define data schema (products, headlines, CTAs, images)
+3. Feed data array into template
+4. Batch render all variations
+5. Upload to ad platform
+```
+
+### Getting Started
+
+```bash
+# Create a new Remotion project
+npx create-video@latest
+
+# Render a single video
+npx remotion render src/index.ts MyComposition out/video.mp4
+
+# Batch render from data
+npx remotion render src/index.ts MyComposition --props='{"data": [...]}'
+```
+
+---
+
+## Choosing the Right Tool
+
+### Decision Tree
+
+```
+Need video ads?
+├── Templated, data-driven (same structure, different data)
+│   └── Use Remotion
+├── Unique creative from prompts (exploratory)
+│   ├── Need dialogue/voiceover? → Sora 2, Veo 3.1, Kling 2.6, Seedance 2.0
+│   ├── Need consistency across scenes? → Runway Gen-4
+│   ├── Need vertical social video? → Veo 3.1 (native 9:16)
+│   ├── Need high volume at low cost? → Seedance 2.0
+│   └── Need cinematic camera work? → Higgsfield, Kling
+└── Both → Use AI gen for hero creative, Remotion for variations
+
+Need image ads?
+├── Need text/headlines in image? → Ideogram
+├── Need product consistency across variations? → Flux (multi-ref)
+├── Need quick iterations on existing images? → Nano Banana Pro
+├── Need highest visual quality? → Flux Pro, Midjourney
+└── Need high volume at low cost? → Flux Klein, Nano Banana
+```
+
+### Cost Comparison for 100 Ad Variations
+
+| Approach | Tool | Approximate Cost |
+|----------|------|-----------------|
+| 100 static images | Nano Banana Pro | ~$4-24 |
+| 100 static images | Flux Dev | ~$1-2 |
+| 100 static images | Ideogram API | ~$6 |
+| 100 × 15-sec videos | Veo 3.1 Fast | ~$225 |
+| 100 × 15-sec videos | Remotion (templated) | ~$0 (self-hosted render) |
+| 10 hero videos + 90 templated | Veo + Remotion | ~$22 + render time |
+
+### Recommended Workflow for Scaled Ad Production
+
+1. **Generate hero creative** with AI (Nano Banana, Flux, Veo) — high-quality, exploratory
+2. **Build templates** in Remotion based on winning creative patterns
+3. **Batch produce variations** with Remotion using data (products, headlines, CTAs)
+4. **Iterate** — use AI tools for new angles, Remotion for scale
+
+This hybrid approach gives you the creative exploration of AI generators and the consistency and scale of code-based rendering.
+
+---
+
+## Platform-Specific Image Specs
+
+When generating images for ads, request the correct dimensions:
+
+| Platform | Placement | Aspect Ratio | Recommended Size |
+|----------|-----------|-------------|-----------------|
+| Meta Feed | Single image | 1:1 | 1080x1080 |
+| Meta Stories/Reels | Vertical | 9:16 | 1080x1920 |
+| Meta Carousel | Square | 1:1 | 1080x1080 |
+| Google Display | Landscape | 1.91:1 | 1200x628 |
+| Google Display | Square | 1:1 | 1200x1200 |
+| LinkedIn Feed | Landscape | 1.91:1 | 1200x627 |
+| LinkedIn Feed | Square | 1:1 | 1200x1200 |
+| TikTok Feed | Vertical | 9:16 | 1080x1920 |
+| Twitter/X Feed | Landscape | 16:9 | 1200x675 |
+| Twitter/X Card | Landscape | 1.91:1 | 800x418 |
+
+Include these dimensions in your generation prompts to avoid needing to crop or resize.

skills/ad-creative/references/platform-specs.md

@@ -0,0 +1,213 @@
+# Platform Specs Reference
+
+Complete character limits, format requirements, and best practices for each ad platform.
+
+---
+
+## Google Ads
+
+### Responsive Search Ads (RSAs)
+
+| Element | Character Limit | Required | Notes |
+|---------|----------------|----------|-------|
+| Headline | 30 chars | 3 minimum, 15 max | Any 3 may be shown together |
+| Description | 90 chars | 2 minimum, 4 max | Any 2 may be shown together |
+| Display path 1 | 15 chars | Optional | Appears after domain in URL |
+| Display path 2 | 15 chars | Optional | Appears after path 1 |
+| Final URL | No limit | Required | Landing page URL |
+
+**Combination rules:**
+- Google selects up to 3 headlines and 2 descriptions to show
+- Headlines appear separated by " | " or stacked
+- Any headline can appear in any position unless pinned
+- Pinning reduces Google's ability to optimize — use sparingly
+
+**Pinning strategy:**
+- Pin your brand name to position 1 if brand guidelines require it
+- Pin your strongest CTA to position 2 or 3
+- Leave most headlines unpinned for machine learning
+
+**Headline mix recommendation (15 headlines):**
+- 3-4 keyword-focused (match search intent)
+- 3-4 benefit-focused (what they get)
+- 2-3 social proof (numbers, awards, customers)
+- 2-3 CTA-focused (action to take)
+- 1-2 differentiators (why you over competitors)
+- 1 brand name headline
+
+**Description mix recommendation (4 descriptions):**
+- 1 benefit + proof point
+- 1 feature + outcome
+- 1 social proof + CTA
+- 1 urgency/offer + CTA (if applicable)
+
+### Performance Max
+
+| Element | Character Limit | Notes |
+|---------|----------------|-------|
+| Headline | 30 chars (5 required) | Short headlines for various placements |
+| Long headline | 90 chars (5 required) | Used in display, video, discover |
+| Description | 90 chars (1 required, 5 max) | Accompany various ad formats |
+| Business name | 25 chars | Required |
+
+### Display Ads
+
+| Element | Character Limit |
+|---------|----------------|
+| Headline | 30 chars |
+| Long headline | 90 chars |
+| Description | 90 chars |
+| Business name | 25 chars |
+
+---
+
+## Meta Ads (Facebook & Instagram)
+
+### Single Image / Video / Carousel
+
+| Element | Recommended | Maximum | Notes |
+|---------|-------------|---------|-------|
+| Primary text | 125 chars | 2,200 chars | Text above image; truncated after ~125 |
+| Headline | 40 chars | 255 chars | Below image; truncated after ~40 |
+| Description | 30 chars | 255 chars | Below headline; may not show |
+| URL display link | 40 chars | N/A | Optional custom display URL |
+
+**Placement-specific notes:**
+- **Feed**: All elements show; primary text most visible
+- **Stories/Reels**: Primary text overlaid; keep under 72 chars
+- **Right column**: Only headline visible; skip description
+- **Audience Network**: Varies by publisher
+
+**Best practices:**
+- Front-load the hook in primary text (first 125 chars)
+- Use line breaks for readability in longer primary text
+- Emojis: test, but don't overuse — 1-2 per ad max
+- Questions in primary text increase engagement
+- Headline should be a clear CTA or value statement
+
+### Lead Ads (Instant Form)
+
+| Element | Limit |
+|---------|-------|
+| Greeting headline | 60 chars |
+| Greeting description | 360 chars |
+| Privacy policy text | 200 chars |
+
+---
+
+## LinkedIn Ads
+
+### Single Image Ad
+
+| Element | Recommended | Maximum | Notes |
+|---------|-------------|---------|-------|
+| Intro text | 150 chars | 600 chars | Above the image; truncated after ~150 |
+| Headline | 70 chars | 200 chars | Below the image |
+| Description | 100 chars | 300 chars | Only shows on Audience Network |
+
+### Carousel Ad
+
+| Element | Limit |
+|---------|-------|
+| Intro text | 255 chars |
+| Card headline | 45 chars |
+| Card count | 2-10 cards |
+
+### Message Ad (InMail)
+
+| Element | Limit |
+|---------|-------|
+| Subject line | 60 chars |
+| Message body | 1,500 chars |
+| CTA button | 20 chars |
+
+### Text Ad
+
+| Element | Limit |
+|---------|-------|
+| Headline | 25 chars |
+| Description | 75 chars |
+
+**LinkedIn-specific guidelines:**
+- Professional tone, but not boring
+- Use job-specific language the audience recognizes
+- Statistics and data points perform well
+- Avoid consumer-style hype ("Amazing!" "Incredible!")
+- First-person testimonials from peers resonate
+
+---
+
+## TikTok Ads
+
+### In-Feed Ads
+
+| Element | Recommended | Maximum | Notes |
+|---------|-------------|---------|-------|
+| Ad text | 80 chars | 100 chars | Above the video |
+| Display name | N/A | 40 chars | Brand name |
+| CTA button | Platform options | Predefined | Select from TikTok's options |
+
+### Spark Ads (Boosted Organic)
+
+| Element | Notes |
+|---------|-------|
+| Caption | Uses original post caption |
+| CTA button | Added by advertiser |
+| Display name | Original creator's handle |
+
+**TikTok-specific guidelines:**
+- Native content outperforms polished ads
+- First 2 seconds determine if they watch
+- Use trending sounds and formats
+- Text overlay is essential (most watch with sound off)
+- Vertical video only (9:16)
+
+---
+
+## Twitter/X Ads
+
+### Promoted Tweets
+
+| Element | Limit | Notes |
+|---------|-------|-------|
+| Tweet text | 280 chars | Full tweet with image/video |
+| Card headline | 70 chars | Website card |
+| Card description | 200 chars | Website card |
+
+### Website Cards
+
+| Element | Limit |
+|---------|-------|
+| Headline | 70 chars |
+| Description | 200 chars |
+
+**Twitter/X-specific guidelines:**
+- Conversational, casual tone
+- Short sentences work best
+- One clear message per tweet
+- Hashtags: 1-2 max (0 is often better for ads)
+- Threads can work for consideration-stage content
+
+---
+
+## Character Counting Tips
+
+- **Spaces count** as characters on all platforms
+- **Emojis** count as 1-2 characters depending on platform
+- **Special characters** (|, &, etc.) count as 1 character
+- **URLs** in body text count against limits
+- **Dynamic keyword insertion** (`{KeyWord:default}`) can exceed limits — set safe defaults
+- Always verify in the platform's ad preview before launching
+
+---
+
+## Multi-Platform Creative Adaptation
+
+When creating for multiple platforms simultaneously, start with the most restrictive format:
+
+1. **Google Search headlines** (30 chars) — forces the tightest messaging
+2. **Expand to Meta headlines** (40 chars) — add a word or two
+3. **Expand to LinkedIn intro text** (150 chars) — add context and proof
+4. **Expand to Meta primary text** (125+ chars) — full hook and value prop
+
+This cascading approach ensures your core message works everywhere, then gets enriched for platforms that allow more space.

skills/ai-seo/SKILL.md

@@ -0,0 +1,398 @@
+---
+name: ai-seo
+description: "When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for Perplexity,' 'AI citations,' 'AI visibility,' 'zero-click search,' 'how do I show up in AI answers,' 'LLM mentions,' or 'optimize for Claude/Gemini.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional technical and on-page SEO audits, see seo-audit. For structured data implementation, see schema-markup."
+metadata:
+  version: 1.1.0
+---
+
+# AI SEO
+
+You are an expert in AI search optimization — the practice of making content discoverable, extractable, and citable by AI systems including Google AI Overviews, ChatGPT, Perplexity, Claude, Gemini, and Copilot. Your goal is to help users get their content cited as a source in AI-generated answers.
+
+## Before Starting
+
+**Check for product marketing context first:**
+If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
+
+Gather this context (ask if not provided):
+
+### 1. Current AI Visibility
+- Do you know if your brand appears in AI-generated answers today?
+- Have you checked ChatGPT, Perplexity, or Google AI Overviews for your key queries?
+- What queries matter most to your business?
+
+### 2. Content & Domain
+- What type of content do you produce? (Blog, docs, comparisons, product pages)
+- What's your domain authority / traditional SEO strength?
+- Do you have existing structured data (schema markup)?
+
+### 3. Goals
+- Get cited as a source in AI answers?
+- Appear in Google AI Overviews for specific queries?
+- Compete with specific brands already getting cited?
+- Optimize existing content or create new AI-optimized content?
+
+### 4. Competitive Landscape
+- Who are your top competitors in AI search results?
+- Are they being cited where you're not?
+
+---
+
+## How AI Search Works
+
+### The AI Search Landscape
+
+| Platform | How It Works | Source Selection |
+|----------|-------------|----------------|
+| **Google AI Overviews** | Summarizes top-ranking pages | Strong correlation with traditional rankings |
+| **ChatGPT (with search)** | Searches web, cites sources | Draws from wider range, not just top-ranked |
+| **Perplexity** | Always cites sources with links | Favors authoritative, recent, well-structured content |
+| **Gemini** | Google's AI assistant | Pulls from Google index + Knowledge Graph |
+| **Copilot** | Bing-powered AI search | Bing index + authoritative sources |
+| **Claude** | Brave Search (when enabled) | Training data + Brave search results |
+
+For a deep dive on how each platform selects sources and what to optimize per platform, see [references/platform-ranking-factors.md](references/platform-ranking-factors.md).
+
+### Key Difference from Traditional SEO
+
+Traditional SEO gets you ranked. AI SEO gets you **cited**.
+
+In traditional search, you need to rank on page 1. In AI search, a well-structured page can get cited even if it ranks on page 2 or 3 — AI systems select sources based on content quality, structure, and relevance, not just rank position.
+
+**Critical stats:**
+- AI Overviews appear in ~45% of Google searches
+- AI Overviews reduce clicks to websites by up to 58%
+- Brands are 6.5x more likely to be cited via third-party sources than their own domains
+- Optimized content gets cited 3x more often than non-optimized
+- Statistics and citations boost visibility by 40%+ across queries
+
+---
+
+## AI Visibility Audit
+
+Before optimizing, assess your current AI search presence.
+
+### Step 1: Check AI Answers for Your Key Queries
+
+Test 10-20 of your most important queries across platforms:
+
+| Query | Google AI Overview | ChatGPT | Perplexity | You Cited? | Competitors Cited? |
+|-------|:-----------------:|:-------:|:----------:|:----------:|:-----------------:|
+| [query 1] | Yes/No | Yes/No | Yes/No | Yes/No | [who] |
+| [query 2] | Yes/No | Yes/No | Yes/No | Yes/No | [who] |
+
+**Query types to test:**
+- "What is [your product category]?"
+- "Best [product category] for [use case]"
+- "[Your brand] vs [competitor]"
+- "How to [problem your product solves]"
+- "[Your product category] pricing"
+
+### Step 2: Analyze Citation Patterns
+
+When your competitors get cited and you don't, examine:
+- **Content structure** — Is their content more extractable?
+- **Authority signals** — Do they have more citations, stats, expert quotes?
+- **Freshness** — Is their content more recently updated?
+- **Schema markup** — Do they have structured data you're missing?
+- **Third-party presence** — Are they cited via Wikipedia, Reddit, review sites?
+
+### Step 3: Content Extractability Check
+
+For each priority page, verify:
+
+| Check | Pass/Fail |
+|-------|-----------|
+| Clear definition in first paragraph? | |
+| Self-contained answer blocks (work without surrounding context)? | |
+| Statistics with sources cited? | |
+| Comparison tables for "[X] vs [Y]" queries? | |
+| FAQ section with natural-language questions? | |
+| Schema markup (FAQ, HowTo, Article, Product)? | |
+| Expert attribution (author name, credentials)? | |
+| Recently updated (within 6 months)? | |
+| Heading structure matches query patterns? | |
+| AI bots allowed in robots.txt? | |
+
+### Step 4: AI Bot Access Check
+
+Verify your robots.txt allows AI crawlers. Each AI platform has its own bot, and blocking it means that platform can't cite you:
+
+- **GPTBot** and **ChatGPT-User** — OpenAI (ChatGPT)
+- **PerplexityBot** — Perplexity
+- **ClaudeBot** and **anthropic-ai** — Anthropic (Claude)
+- **Google-Extended** — Google Gemini and AI Overviews
+- **Bingbot** — Microsoft Copilot (via Bing)
+
+Check your robots.txt for `Disallow` rules targeting any of these. If you find them blocked, you have a business decision to make: blocking prevents AI training on your content but also prevents citation. One middle ground is blocking training-only crawlers (like **CCBot** from Common Crawl) while allowing the search bots listed above.
+
+See [references/platform-ranking-factors.md](references/platform-ranking-factors.md) for the full robots.txt configuration.
+
+---
+
+## Optimization Strategy
+
+### The Three Pillars
+
+```
+1. Structure (make it extractable)
+2. Authority (make it citable)
+3. Presence (be where AI looks)
+```
+
+### Pillar 1: Structure — Make Content Extractable
+
+AI systems extract passages, not pages. Every key claim should work as a standalone statement.
+
+**Content block patterns:**
+- **Definition blocks** for "What is X?" queries
+- **Step-by-step blocks** for "How to X" queries
+- **Comparison tables** for "X vs Y" queries
+- **Pros/cons blocks** for evaluation queries
+- **FAQ blocks** for common questions
+- **Statistic blocks** with cited sources
+
+For detailed templates for each block type, see [references/content-patterns.md](references/content-patterns.md).
+
+**Structural rules:**
+- Lead every section with a direct answer (don't bury it)
+- Keep key answer passages to 40-60 words (optimal for snippet extraction)
+- Use H2/H3 headings that match how people phrase queries
+- Tables beat prose for comparison content
+- Numbered lists beat paragraphs for process content
+- Each paragraph should convey one clear idea
+
+### Pillar 2: Authority — Make Content Citable
+
+AI systems prefer sources they can trust. Build citation-worthiness.
+
+**The Princeton GEO research** (KDD 2024, studied across Perplexity.ai) ranked 9 optimization methods:
+
+| Method | Visibility Boost | How to Apply |
+|--------|:---------------:|--------------|
+| **Cite sources** | +40% | Add authoritative references with links |
+| **Add statistics** | +37% | Include specific numbers with sources |
+| **Add quotations** | +30% | Expert quotes with name and title |
+| **Authoritative tone** | +25% | Write with demonstrated expertise |
+| **Improve clarity** | +20% | Simplify complex concepts |
+| **Technical terms** | +18% | Use domain-specific terminology |
+| **Unique vocabulary** | +15% | Increase word diversity |
+| **Fluency optimization** | +15-30% | Improve readability and flow |
+| ~~Keyword stuffing~~ | **-10%** | **Actively hurts AI visibility** |
+
+**Best combination:** Fluency + Statistics = maximum boost. Low-ranking sites benefit even more — up to 115% visibility increase with citations.
+
+**Statistics and data** (+37-40% citation boost)
+- Include specific numbers with sources
+- Cite original research, not summaries of research
+- Add dates to all statistics
+- Original data beats aggregated data
+
+**Expert attribution** (+25-30% citation boost)
+- Named authors with credentials
+- Expert quotes with titles and organizations
+- "According to [Source]" framing for claims
+- Author bios with relevant expertise
+
+**Freshness signals**
+- "Last updated: [date]" prominently displayed
+- Regular content refreshes (quarterly minimum for competitive topics)
+- Current year references and recent statistics
+- Remove or update outdated information
+
+**E-E-A-T alignment**
+- First-hand experience demonstrated
+- Specific, detailed information (not generic)
+- Transparent sourcing and methodology
+- Clear author expertise for the topic
+
+### Pillar 3: Presence — Be Where AI Looks
+
+AI systems don't just cite your website — they cite where you appear.
+
+**Third-party sources matter more than your own site:**
+- Wikipedia mentions (7.8% of all ChatGPT citations)
+- Reddit discussions (1.8% of ChatGPT citations)
+- Industry publications and guest posts
+- Review sites (G2, Capterra, TrustRadius for B2B SaaS)
+- YouTube (frequently cited by Google AI Overviews)
+- Quora answers
+
+**Actions:**
+- Ensure your Wikipedia page is accurate and current
+- Participate authentically in Reddit communities
+- Get featured in industry roundups and comparison articles
+- Maintain updated profiles on relevant review platforms
+- Create YouTube content for key how-to queries
+- Answer relevant Quora questions with depth
+
+### Schema Markup for AI
+
+Structured data helps AI systems understand your content. Key schemas:
+
+| Content Type | Schema | Why It Helps |
+|-------------|--------|-------------|
+| Articles/Blog posts | `Article`, `BlogPosting` | Author, date, topic identification |
+| How-to content | `HowTo` | Step extraction for process queries |
+| FAQs | `FAQPage` | Direct Q&A extraction |
+| Products | `Product` | Pricing, features, reviews |
+| Comparisons | `ItemList` | Structured comparison data |
+| Reviews | `Review`, `AggregateRating` | Trust signals |
+| Organization | `Organization` | Entity recognition |
+
+Content with proper schema shows 30-40% higher AI visibility. For implementation, use the **schema-markup** skill.
+
+---
+
+## Content Types That Get Cited Most
+
+Not all content is equally citable. Prioritize these formats:
+
+| Content Type | Citation Share | Why AI Cites It |
+|-------------|:------------:|----------------|
+| **Comparison articles** | ~33% | Structured, balanced, high-intent |
+| **Definitive guides** | ~15% | Comprehensive, authoritative |
+| **Original research/data** | ~12% | Unique, citable statistics |
+| **Best-of/listicles** | ~10% | Clear structure, entity-rich |
+| **Product pages** | ~10% | Specific details AI can extract |
+| **How-to guides** | ~8% | Step-by-step structure |
+| **Opinion/analysis** | ~10% | Expert perspective, quotable |
+
+**Underperformers for AI citation:**
+- Generic blog posts without structure
+- Thin product pages with marketing fluff
+- Gated content (AI can't access it)
+- Content without dates or author attribution
+- PDF-only content (harder for AI to parse)
+
+---
+
+## Monitoring AI Visibility
+
+### What to Track
+
+| Metric | What It Measures | How to Check |
+|--------|-----------------|-------------|
+| AI Overview presence | Do AI Overviews appear for your queries? | Manual check or Semrush/Ahrefs |
+| Brand citation rate | How often you're cited in AI answers | AI visibility tools (see below) |
+| Share of AI voice | Your citations vs. competitors | Peec AI, Otterly, ZipTie |
+| Citation sentiment | How AI describes your brand | Manual review + monitoring tools |
+| Source attribution | Which of your pages get cited | Track referral traffic from AI sources |
+
+### AI Visibility Monitoring Tools
+
+| Tool | Coverage | Best For |
+|------|----------|----------|
+| **Otterly AI** | ChatGPT, Perplexity, Google AI Overviews | Share of AI voice tracking |
+| **Peec AI** | ChatGPT, Gemini, Perplexity, Claude, Copilot+ | Multi-platform monitoring at scale |
+| **ZipTie** | Google AI Overviews, ChatGPT, Perplexity | Brand mention + sentiment tracking |
+| **LLMrefs** | ChatGPT, Perplexity, AI Overviews, Gemini | SEO keyword → AI visibility mapping |
+
+### DIY Monitoring (No Tools)
+
+Monthly manual check:
+1. Pick your top 20 queries
+2. Run each through ChatGPT, Perplexity, and Google
+3. Record: Are you cited? Who is? What page?
+4. Log in a spreadsheet, track month-over-month
+
+---
+
+## AI SEO for Different Content Types
+
+### SaaS Product Pages
+
+**Goal:** Get cited in "What is [category]?" and "Best [category]" queries.
+
+**Optimize:**
+- Clear product description in first paragraph (what it does, who it's for)
+- Feature comparison tables (you vs. category, not just competitors)
+- Specific metrics ("processes 10,000 transactions/sec" not "blazing fast")
+- Customer count or social proof with numbers
+- Pricing transparency (AI cites pages with visible pricing)
+- FAQ section addressing common buyer questions
+
+### Blog Content
+
+**Goal:** Get cited as an authoritative source on topics in your space.
+
+**Optimize:**
+- One clear target query per post (match heading to query)
+- Definition in first paragraph for "What is" queries
+- Original data, research, or expert quotes
+- "Last updated" date visible
+- Author bio with relevant credentials
+- Internal links to related product/feature pages
+
+### Comparison/Alternative Pages
+
+**Goal:** Get cited in "[X] vs [Y]" and "Best [X] alternatives" queries.
+
+**Optimize:**
+- Structured comparison tables (not just prose)
+- Fair and balanced (AI penalizes obviously biased comparisons)
+- Specific criteria with ratings or scores
+- Updated pricing and feature data
+- Cite the competitors skill for building these pages
+
+### Documentation / Help Content
+
+**Goal:** Get cited in "How to [X] with [your product]" queries.
+
+**Optimize:**
+- Step-by-step format with numbered lists
+- Code examples where relevant
+- HowTo schema markup
+- Screenshots with descriptive alt text
+- Clear prerequisites and expected outcomes
+
+---
+
+## Common Mistakes
+
+- **Ignoring AI search entirely** — ~45% of Google searches now show AI Overviews, and ChatGPT/Perplexity are growing fast
+- **Treating AI SEO as separate from SEO** — Good traditional SEO is the foundation; AI SEO adds structure and authority on top
+- **Writing for AI, not humans** — If content reads like it was written to game an algorithm, it won't get cited or convert
+- **No freshness signals** — Undated content loses to dated content because AI systems weight recency heavily. Show when content was last updated
+- **Gating all content** — AI can't access gated content. Keep your most authoritative content open
+- **Ignoring third-party presence** — You may get more AI citations from a Wikipedia mention than from your own blog
+- **No structured data** — Schema markup gives AI systems structured context about your content
+- **Keyword stuffing** — Unlike traditional SEO where it's just ineffective, keyword stuffing actively reduces AI visibility by 10% (Princeton GEO study)
+- **Blocking AI bots** — If GPTBot, PerplexityBot, or ClaudeBot are blocked in robots.txt, those platforms can't cite you
+- **Generic content without data** — "We're the best" won't get cited. "Our customers see 3x improvement in [metric]" will
+- **Forgetting to monitor** — You can't improve what you don't measure. Check AI visibility monthly at minimum
+
+---
+
+## Tool Integrations
+
+For implementation, see the [tools registry](../../tools/REGISTRY.md).
+
+| Tool | Use For |
+|------|---------|
+| `semrush` | AI Overview tracking, keyword research, content gap analysis |
+| `ahrefs` | Backlink analysis, content explorer, AI Overview data |
+| `gsc` | Search Console performance data, query tracking |
+| `ga4` | Referral traffic from AI sources |
+
+---
+
+## Task-Specific Questions
+
+1. What are your top 10-20 most important queries?
+2. Have you checked if AI answers exist for those queries today?
+3. Do you have structured data (schema markup) on your site?
+4. What content types do you publish? (Blog, docs, comparisons, etc.)
+5. Are competitors being cited by AI where you're not?
+6. Do you have a Wikipedia page or presence on review sites?
+
+---
+
+## Related Skills
+
+- **seo-audit**: For traditional technical and on-page SEO audits
+- **schema-markup**: For implementing structured data that helps AI understand your content
+- **content-strategy**: For planning what content to create
+- **competitors**: For building comparison pages that get cited
+- **programmatic-seo**: For building SEO pages at scale
+- **copywriting**: For writing content that's both human-readable and AI-extractable

skills/ai-seo/evals/evals.json

@@ -0,0 +1,90 @@
+{
+  "skill_name": "ai-seo",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "How do I make sure our SaaS product shows up in AI search results? We're a project management tool and we keep getting left out of ChatGPT and Perplexity recommendations when people ask about project management software.",
+      "expected_output": "Should check for product-marketing-context.md first. Should apply the three pillars framework: Structure (make content extractable), Authority (make content citable), Presence (be where AI looks). Should run through the AI Visibility Audit checklist across platforms (Google AI Overviews, ChatGPT, Perplexity, etc.). Should check content extractability (clear definitions, structured comparisons, statistics). Should reference Princeton GEO research findings (citations improve visibility +40%, statistics +37%). Should check AI bot access in robots.txt. Should provide a prioritized action plan.",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Applies three pillars framework (Structure, Authority, Presence)",
+        "Runs AI Visibility Audit across platforms",
+        "Checks content extractability",
+        "References Princeton GEO research findings",
+        "Checks AI bot access in robots.txt",
+        "Provides prioritized action plan"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "Should we block AI crawlers like GPTBot and PerplexityBot in our robots.txt? We're worried about content theft.",
+      "expected_output": "Should address the AI bot access question directly. Should explain the tradeoff: blocking AI bots prevents training on your content but also prevents AI platforms from citing and recommending you. Should reference the specific bots and their purposes (GPTBot, Google-Extended, PerplexityBot, ClaudeBot, etc.). Should provide the recommended robots.txt configuration. Should explain that blocking may hurt AI visibility more than it protects content. Should provide a nuanced recommendation based on business goals.",
+      "assertions": [
+        "Addresses the blocking tradeoff directly",
+        "Explains impact on AI visibility vs content protection",
+        "Lists specific AI bot user agents",
+        "Provides recommended robots.txt configuration",
+        "Gives nuanced recommendation based on business goals",
+        "Explains what each bot does"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "What kind of content gets cited most by AI systems? We want to create content specifically optimized for AI search.",
+      "expected_output": "Should reference the content types that get cited most, including comparisons (~33% of AI citations), definitive guides (~15%), and other high-citation content types. Should explain why these formats work (they provide the structured, extractable, authoritative information AI systems need). Should provide specific recommendations for creating AI-optimized content: clear definitions, structured data, original statistics, comparison tables, expert quotes. Should reference the Princeton GEO research on what increases citation probability.",
+      "assertions": [
+        "References specific content types with citation rates",
+        "Mentions comparisons as highest-cited format",
+        "Explains why these formats work for AI",
+        "Provides specific content creation recommendations",
+        "References Princeton GEO research",
+        "Mentions structured data, statistics, and clear definitions"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "we noticed our competitors are showing up in google AI overviews but we're not. what do we need to change?",
+      "expected_output": "Should trigger on casual phrasing. Should focus specifically on Google AI Overviews visibility. Should explain how AI Overviews selects sources (authoritative, well-structured, directly answers queries). Should run through the Structure pillar checklist: content extractability, heading hierarchy, answer-first format, structured data. Should check Authority signals: domain authority, citations, E-E-A-T. Should recommend specific content structure changes. Should suggest monitoring approach.",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Focuses on Google AI Overviews specifically",
+        "Explains how AI Overviews selects sources",
+        "Checks Structure pillar (extractability, headings, answer-first)",
+        "Checks Authority signals",
+        "Recommends specific content structure changes",
+        "Suggests monitoring approach"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "Can you audit our website for AI search readiness? We want to know how visible we are across ChatGPT, Perplexity, Google AI Overviews, and other AI platforms.",
+      "expected_output": "Should run the full AI Visibility Audit. Should check each platform in the landscape (Google AI Overviews, ChatGPT, Perplexity, Claude, Gemini, Copilot). Should evaluate all three pillars: Structure (content extractability, JSON-LD, clear definitions), Authority (citations, backlinks, E-E-A-T signals), Presence (AI bot access, platform-specific factors). Should provide findings organized by pillar. Should provide a prioritized action plan with specific fixes.",
+      "assertions": [
+        "Runs full AI Visibility Audit",
+        "Checks multiple AI platforms",
+        "Evaluates all three pillars (Structure, Authority, Presence)",
+        "Checks content extractability",
+        "Checks AI bot access",
+        "Provides findings organized by pillar",
+        "Provides prioritized action plan"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "Our organic search traffic has dropped 30% this quarter. Can you do a full SEO audit to figure out what's going on?",
+      "expected_output": "Should recognize this is a traditional SEO audit request, not specifically an AI SEO task. Should defer to or cross-reference the seo-audit skill, which handles comprehensive traditional SEO audits including crawlability, technical foundations, on-page optimization, and content quality. May mention AI search as one factor to investigate but should make clear that seo-audit is the primary skill for this task.",
+      "assertions": [
+        "Recognizes this as a traditional SEO audit request",
+        "References or defers to seo-audit skill",
+        "Does not attempt a full traditional SEO audit using AI SEO patterns",
+        "May mention AI search as one factor to consider"
+      ],
+      "files": []
+    }
+  ]
+}

skills/ai-seo/references/content-patterns.md

@@ -4,6 +4,12 @@ Reusable content block patterns optimized for answer engines and AI citation.
 
 ---
 
+## Contents
+- Answer Engine Optimization (AEO) Patterns (Definition Block, Step-by-Step Block, Comparison Table Block, Pros and Cons Block, FAQ Block, Listicle Block)
+- Generative Engine Optimization (GEO) Patterns (Statistic Citation Block, Expert Quote Block, Authoritative Claim Block, Self-Contained Answer Block, Evidence Sandwich Block)
+- Domain-Specific GEO Tactics (Technology Content, Health/Medical Content, Financial Content, Legal Content, Business/Marketing Content)
+- Voice Search Optimization (Question Formats for Voice, Voice-Optimized Answer Structure)
+
 ## Answer Engine Optimization (AEO) Patterns
 
 These patterns help content appear in featured snippets, AI Overviews, voice search results, and answer boxes.

skills/ai-seo/references/platform-ranking-factors.md

@@ -0,0 +1,152 @@
+# How Each AI Platform Picks Sources
+
+Each AI search platform has its own search index, ranking logic, and content preferences. This guide covers what matters for getting cited on each one.
+
+Sources cited throughout: Princeton GEO study (KDD 2024), SE Ranking domain authority study, ZipTie content-answer fit analysis.
+
+---
+
+## The Fundamentals
+
+Every AI platform shares three baseline requirements:
+
+1. **Your content must be in their index** — Each platform uses a different search backend (Google, Bing, Brave, or their own). If you're not indexed, you can't be cited.
+2. **Your content must be crawlable** — AI bots need access via robots.txt. Block the bot, lose the citation.
+3. **Your content must be extractable** — AI systems pull passages, not pages. Clear structure and self-contained paragraphs win.
+
+Beyond these basics, each platform weights different signals. Here's what matters and where.
+
+---
+
+## Google AI Overviews
+
+Google AI Overviews pull from Google's own index and lean heavily on E-E-A-T signals (Experience, Expertise, Authoritativeness, Trustworthiness). They appear in roughly 45% of Google searches.
+
+**What makes Google AI Overviews different:** They already have your traditional SEO signals — backlinks, page authority, topical relevance. The additional AI layer adds a preference for content with cited sources and structured data. Research shows that including authoritative citations in your content correlates with a 132% visibility boost, and writing with an authoritative (not salesy) tone adds another 89%.
+
+**Importantly, AI Overviews don't just recycle the traditional Top 10.** Only about 15% of AI Overview sources overlap with conventional organic results. Pages that wouldn't crack page 1 in traditional search can still get cited if they have strong structured data and clear, extractable answers.
+
+**What to focus on:**
+- Schema markup is the single biggest lever — Article, FAQPage, HowTo, and Product schemas give AI Overviews structured context to work with (30-40% visibility boost)
+- Build topical authority through content clusters with strong internal linking
+- Include named, sourced citations in your content (not just claims)
+- Author bios with real credentials matter — E-E-A-T is weighted heavily
+- Get into Google's Knowledge Graph where possible (an accurate Wikipedia entry helps)
+- Target "how to" and "what is" query patterns — these trigger AI Overviews most often
+
+---
+
+## ChatGPT
+
+ChatGPT's web search draws from a Bing-based index. It combines this with its training knowledge to generate answers, then cites the web sources it relied on.
+
+**What makes ChatGPT different:** Domain authority matters more here than on other AI platforms. An SE Ranking analysis of 129,000 domains found that authority and credibility signals account for roughly 40% of what determines citation, with content quality at about 35% and platform trust at 25%. Sites with very high referring domain counts (350K+) average 8.4 citations per response, while sites with slightly lower trust scores (91-96 vs 97-100) drop from 8.4 to 6 citations.
+
+**Freshness is a major differentiator.** Content updated within the last 30 days gets cited about 3.2x more often than older content. ChatGPT clearly favors recent information.
+
+**The most important signal is content-answer fit** — a ZipTie analysis of 400,000 pages found that how well your content's style and structure matches ChatGPT's own response format accounts for about 55% of citation likelihood. This is far more important than domain authority (12%) or on-page structure (14%) alone. Write the way ChatGPT would answer the question, and you're more likely to be the source it cites.
+
+**Where ChatGPT looks beyond your site:** Wikipedia accounts for 7.8% of all ChatGPT citations, Reddit for 1.8%, and Forbes for 1.1%. Brand official sites are cited frequently but third-party mentions carry significant weight.
+
+**What to focus on:**
+- Invest in backlinks and domain authority — it's the strongest baseline signal
+- Update competitive content at least monthly
+- Structure your content the way ChatGPT structures its answers (conversational, direct, well-organized)
+- Include verifiable statistics with named sources
+- Clean heading hierarchy (H1 > H2 > H3) with descriptive headings
+
+---
+
+## Perplexity
+
+Perplexity always cites its sources with clickable links, making it the most transparent AI search platform. It combines its own index with Google's and runs results through multiple reranking passes — initial relevance retrieval, then traditional ranking factor scoring, then ML-based quality evaluation that can discard entire result sets if they don't meet quality thresholds.
+
+**What makes Perplexity different:** It's the most "research-oriented" AI search engine, and its citation behavior reflects that. Perplexity maintains curated lists of authoritative domains (Amazon, GitHub, major academic sites) that get inherent ranking boosts. It uses a time-decay algorithm that evaluates new content quickly, giving fresh publishers a real shot at citation.
+
+**Perplexity has unique content preferences:**
+- **FAQ Schema (JSON-LD)** — Pages with FAQ structured data get cited noticeably more often
+- **PDF documents** — Publicly accessible PDFs (whitepapers, research reports) are prioritized. If you have authoritative PDF content gated behind a form, consider making a version public.
+- **Publishing velocity** — How frequently you publish matters more than keyword targeting
+- **Self-contained paragraphs** — Perplexity prefers atomic, semantically complete paragraphs it can extract cleanly
+
+**What to focus on:**
+- Allow PerplexityBot in robots.txt
+- Implement FAQPage schema on any page with Q&A content
+- Host PDF resources publicly (whitepapers, guides, reports)
+- Add Article schema with publication and modification timestamps
+- Write in clear, self-contained paragraphs that work as standalone answers
+- Build deep topical authority in your specific niche
+
+---
+
+## Microsoft Copilot
+
+Copilot is embedded across Microsoft's ecosystem — Edge, Windows, Microsoft 365, and Bing Search. It relies entirely on Bing's index, so if Bing hasn't indexed your content, Copilot can't cite it.
+
+**What makes Copilot different:** The Microsoft ecosystem connection creates unique optimization opportunities. Mentions and content on LinkedIn and GitHub provide ranking boosts that other platforms don't offer. Copilot also puts more weight on page speed — sub-2-second load times are a clear threshold.
+
+**What to focus on:**
+- Submit your site to Bing Webmaster Tools (many sites only submit to Google Search Console)
+- Use IndexNow protocol for faster indexing of new and updated content
+- Optimize page speed to under 2 seconds
+- Write clear entity definitions — when your content defines a term or concept, make the definition explicit and extractable
+- Build presence on LinkedIn (publish articles, maintain company page) and GitHub if relevant
+- Ensure Bingbot has full crawl access
+
+---
+
+## Claude
+
+Claude uses Brave Search as its search backend when web search is enabled — not Google, not Bing. This is a completely different index, which means your Brave Search visibility directly determines whether Claude can find and cite you.
+
+**What makes Claude different:** Claude is extremely selective about what it cites. While it processes enormous amounts of content, its citation rate is very low — it's looking for the most factually accurate, well-sourced content on a given topic. Data-rich content with specific numbers and clear attribution performs significantly better than general-purpose content.
+
+**What to focus on:**
+- Verify your content appears in Brave Search results (search for your brand and key terms at search.brave.com)
+- Allow ClaudeBot and anthropic-ai user agents in robots.txt
+- Maximize factual density — specific numbers, named sources, dated statistics
+- Use clear, extractable structure with descriptive headings
+- Cite authoritative sources within your content
+- Aim to be the most factually accurate source on your topic — Claude rewards precision
+
+---
+
+## Allowing AI Bots in robots.txt
+
+If your robots.txt blocks an AI bot, that platform can't cite your content. Here are the user agents to allow:
+
+```
+User-agent: GPTBot           # OpenAI — powers ChatGPT search
+User-agent: ChatGPT-User     # ChatGPT browsing mode
+User-agent: PerplexityBot    # Perplexity AI search
+User-agent: ClaudeBot        # Anthropic Claude
+User-agent: anthropic-ai     # Anthropic Claude (alternate)
+User-agent: Google-Extended   # Google Gemini and AI Overviews
+User-agent: Bingbot          # Microsoft Copilot (via Bing)
+Allow: /
+```
+
+**Training vs. search:** Some AI bots are used for both model training and search citation. If you want to be cited but don't want your content used for training, your options are limited — GPTBot handles both for OpenAI. However, you can safely block **CCBot** (Common Crawl) without affecting any AI search citations, since it's only used for training dataset collection.
+
+---
+
+## Where to Start
+
+If you're optimizing for AI search for the first time, focus your effort where your audience actually is:
+
+**Start with Google AI Overviews** — They reach the most users (45%+ of Google searches) and you likely already have Google SEO foundations in place. Add schema markup, include cited sources in your content, and strengthen E-E-A-T signals.
+
+**Then address ChatGPT** — It's the most-used standalone AI search tool for tech and business audiences. Focus on freshness (update content monthly), domain authority, and matching your content structure to how ChatGPT formats its responses.
+
+**Then expand to Perplexity** — Especially valuable if your audience includes researchers, early adopters, or tech professionals. Add FAQ schema, publish PDF resources, and write in clear, self-contained paragraphs.
+
+**Copilot and Claude are lower priority** unless your audience skews enterprise/Microsoft (Copilot) or developer/analyst (Claude). But the fundamentals — structured content, cited sources, schema markup — help across all platforms.
+
+**Actions that help everywhere:**
+1. Allow all AI bots in robots.txt
+2. Implement schema markup (FAQPage, Article, Organization at minimum)
+3. Include statistics with named sources in your content
+4. Update content regularly — monthly for competitive topics
+5. Use clear heading structure (H1 > H2 > H3)
+6. Keep page load time under 2 seconds
+7. Add author bios with credentials

skills/analytics/SKILL.md

@@ -1,7 +1,8 @@
 ---
-name: analytics-tracking
-version: 1.0.0
-description: When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," or "tracking plan." For A/B test measurement, see ab-test-setup.
+name: analytics
+description: When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "track conversions," "attribution," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For A/B test measurement, see ab-testing.
+metadata:
+  version: 1.1.0
 ---
 
 # Analytics Tracking
@@ -11,7 +12,7 @@ You are an expert in analytics implementation and measurement. Your goal is to h
 ## Initial Assessment
 
 **Check for product marketing context first:**
-If `.claude/product-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
+If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` 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 implementing tracking, understand:
 
@@ -302,6 +303,7 @@ For implementation, see the [tools registry](../../tools/REGISTRY.md). Key analy
 
 ## Related Skills
 
-- **ab-test-setup**: For experiment tracking
+- **ab-testing**: For experiment tracking
 - **seo-audit**: For organic traffic analysis
-- **page-cro**: For conversion optimization (uses this data)
+- **cro**: For conversion optimization (uses this data)
+- **revops**: For pipeline metrics, CRM tracking, and revenue attribution

skills/analytics/evals/evals.json

@@ -0,0 +1,90 @@
+{
+  "skill_name": "analytics-tracking",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Help me set up analytics tracking for our B2B SaaS product. We use GA4 and GTM. We need to track signups, feature usage, and upgrade events.",
+      "expected_output": "Should check for product-marketing-context.md first. Should apply the 'track for decisions' principle — ask what decisions the tracking will inform. Should use the event naming convention (object_action, lowercase with underscores). Should define essential events for SaaS: signup_completed, trial_started, feature_used, plan_upgraded, etc. Should provide GA4 implementation details with proper event parameters. Should include GTM data layer push examples. Should organize output as a tracking plan with event name, trigger, parameters, and purpose for each event.",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Applies 'track for decisions' principle",
+        "Uses object_action naming convention",
+        "Defines essential SaaS events (signup, feature usage, upgrade)",
+        "Provides GA4 implementation details",
+        "Includes GTM data layer examples",
+        "Output follows tracking plan format"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "What UTM parameters should we use? We run ads on Google, Meta, and LinkedIn, plus send a weekly newsletter and post on LinkedIn organically.",
+      "expected_output": "Should apply the UTM parameter strategy framework. Should define consistent UTM conventions: source (google, meta, linkedin, newsletter), medium (cpc, paid-social, email, organic-social), campaign (naming convention with date or identifier). Should provide specific UTM examples for each channel mentioned. Should warn about common UTM mistakes (inconsistent casing, redundant parameters, missing medium). Should recommend a UTM tracking spreadsheet or naming convention document.",
+      "assertions": [
+        "Applies UTM parameter strategy",
+        "Defines source, medium, and campaign conventions",
+        "Provides specific UTM examples for each channel",
+        "Uses consistent naming conventions (lowercase)",
+        "Warns about common UTM mistakes",
+        "Recommends tracking documentation"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "our tracking seems broken — we're seeing duplicate events and our conversion numbers in GA4 don't match what our database shows. help?",
+      "expected_output": "Should trigger on casual phrasing. Should apply the debugging and validation framework. Should systematically check for common issues: duplicate GTM tags firing, missing event deduplication, incorrect trigger conditions, cross-domain tracking issues, consent mode filtering. Should provide specific debugging steps: use GA4 DebugView, GTM Preview mode, browser developer tools. Should address the GA4 vs database discrepancy (common causes: consent mode, ad blockers, client-side vs server-side tracking, session timeout differences).",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Applies debugging and validation framework",
+        "Checks for duplicate tag firing",
+        "Provides specific debugging tools (GA4 DebugView, GTM Preview)",
+        "Addresses GA4 vs database discrepancy",
+        "Lists common causes of data mismatches",
+        "Provides systematic troubleshooting steps"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "We're launching an e-commerce store and need to set up tracking from scratch. What events do we absolutely need?",
+      "expected_output": "Should reference the essential events by site type, specifically e-commerce. Should define the e-commerce event taxonomy: product_viewed, product_added_to_cart, cart_viewed, checkout_started, checkout_step_completed, purchase_completed, product_removed_from_cart. Should include enhanced e-commerce parameters (item_id, item_name, price, quantity, etc.). Should follow object_action naming convention. Should organize as a tracking plan with priorities (must-have vs nice-to-have).",
+      "assertions": [
+        "References essential events for e-commerce site type",
+        "Defines full e-commerce event taxonomy",
+        "Includes enhanced e-commerce parameters",
+        "Follows object_action naming convention",
+        "Organizes by priority (must-have vs nice-to-have)",
+        "Provides tracking plan format output"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "We need to make sure our tracking is GDPR compliant. We have European users and we're using GA4, Hotjar, and Facebook Pixel.",
+      "expected_output": "Should apply the privacy and compliance framework. Should address GDPR requirements for each tool: consent before tracking, consent management platform (CMP) setup, GA4 consent mode configuration, conditional loading of Hotjar and Facebook Pixel. Should recommend a consent hierarchy (necessary, analytics, marketing). Should provide GTM implementation for consent-based tag firing. Should mention data retention settings in GA4. Should address cookie banner requirements.",
+      "assertions": [
+        "Applies privacy and compliance framework",
+        "Addresses GDPR requirements specifically",
+        "Recommends consent management platform",
+        "Covers GA4 consent mode configuration",
+        "Addresses conditional loading for each tool",
+        "Provides consent hierarchy",
+        "Mentions data retention settings"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "Help me set up tracking for our A/B test. We want to measure which version of our pricing page converts better.",
+      "expected_output": "Should recognize this overlaps with A/B test setup, not just analytics tracking. Should defer to or cross-reference the ab-test-setup skill for the experiment design, hypothesis, and statistical analysis. May help with the tracking implementation (events to fire, parameters to include) but should make clear that ab-test-setup is the right skill for the experiment framework.",
+      "assertions": [
+        "Recognizes overlap with A/B test setup",
+        "References or defers to ab-test-setup skill",
+        "May help with tracking implementation specifics",
+        "Does not attempt to design the full experiment"
+      ],
+      "files": []
+    }
+  ]
+}

skills/analytics/references/event-library.md

@@ -2,6 +2,15 @@
 
 Comprehensive list of events to track by business type and context.
 
+## Contents
+- Marketing Site Events (navigation & engagement, CTA & form interactions, conversion events)
+- Product/App Events (onboarding, core usage, errors & support)
+- Monetization Events (pricing & checkout, subscription management)
+- E-commerce Events (browsing, cart, checkout, post-purchase)
+- B2B / SaaS Specific Events (team & collaboration, integration events, account events)
+- Event Properties (Parameters)
+- Funnel Event Sequences
+
 ## Marketing Site Events
 
 ### Navigation & Engagement

skills/analytics/references/ga4-implementation.md

@@ -2,6 +2,16 @@
 
 Detailed implementation guide for Google Analytics 4.
 
+## Contents
+- Configuration (data streams, enhanced measurement events, recommended events)
+- Custom Events (gtag.js implementation, Google Tag Manager)
+- Conversions Setup (creating conversions, conversion values)
+- Custom Dimensions and Metrics (when to use, setup steps, examples)
+- Audiences (creating audiences, audience examples)
+- Debugging (DebugView, real-time reports, common issues)
+- Data Quality (filters, cross-domain tracking, session settings)
+- Integration with Google Ads (linking, audience export)
+
 ## Configuration
 
 ### Data Streams

skills/analytics/references/gtm-implementation.md

@@ -2,6 +2,16 @@
 
 Detailed guide for implementing tracking via Google Tag Manager.
 
+## Contents
+- Container Structure (tags, triggers, variables)
+- Naming Conventions
+- Data Layer Patterns
+- Common Tag Configurations (GA4 configuration tag, GA4 event tag, Facebook pixel)
+- Preview and Debug
+- Workspaces and Versioning
+- Consent Management
+- Advanced Patterns (tag sequencing, exception handling, custom JavaScript variables)
+
 ## Container Structure
 
 ### Tags

skills/aso-audit/SKILL.md

@@ -0,0 +1,299 @@
+---
+name: aso-audit
+description: >
+  Use when auditing an App Store or Google Play listing for optimization.
+  Triggers: "ASO audit", "app store optimization", "optimize my app listing",
+  "improve app visibility", "app store ranking", "audit my listing", or when
+  user shares an App Store / Google Play URL and wants to improve it. Also
+  triggers on: "why aren't people downloading my app", "improve my app
+  conversion", "keyword optimization for app", "compare my app to competitors".
+metadata:
+  version: 1.0.0
+---
+
+# ASO Audit
+
+Analyze App Store and Google Play listings against ASO best practices. Fetches
+live listing data, scores metadata, visuals, and ratings, then produces a
+prioritized action plan.
+
+## When to Use
+
+- User shares an App Store or Google Play URL
+- User asks to audit or optimize an app listing
+- User wants to compare their app against competitors
+- User asks about app store ranking, visibility, or download conversion
+
+## Before Auditing
+
+**Check for product marketing context first:**
+If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
+
+## Phase 1 — Identify Store & Fetch
+
+### Detect store type from URL
+
+```
+Apple:  apps.apple.com/{country}/app/{name}/id{digits}
+Google: play.google.com/store/apps/details?id={package}
+```
+
+If the user gives an app name instead of a URL, search the web for:
+`site:apps.apple.com "{app name}"` or `site:play.google.com "{app name}"`
+
+### Fetch the listing
+
+Use WebFetch to retrieve the listing page. Extract every available field:
+
+**Apple App Store fields:**
+
+- App name (title) — 30 char limit
+- Subtitle — 30 char limit
+- Description (long) — not indexed for search, but matters for conversion
+- Promotional text — 170 chars, updatable without new release
+- Category (primary + secondary)
+- Screenshots (count, order, caption text)
+- Preview video (presence, duration)
+- Rating (average + count)
+- Recent reviews (visible ones)
+- Price / in-app purchases
+- Developer name
+- Last updated date
+- Version history notes
+- Age rating
+- Size
+- Languages / localizations listed
+- In-app events (if any visible)
+
+**Google Play fields:**
+
+- App name (title) — 30 char limit
+- Short description — 80 char limit
+- Full description — 4,000 char limit, IS indexed for search
+- Category + tags
+- Feature graphic (presence)
+- Screenshots (count, order)
+- Preview video (presence)
+- Rating (average + count)
+- Recent reviews (visible ones)
+- Price / in-app purchases
+- Developer name
+- Last updated date
+- What's new text
+- Downloads range
+- Content rating
+- Data safety section
+- Languages listed
+
+If WebFetch returns incomplete data (stores render client-side), note gaps and
+work with what's available. Ask the user to paste missing fields if critical.
+
+### Visual asset assessment
+
+WebFetch cannot extract screenshot images or caption text. **Always use the
+Playwright browser tool** to get visual data:
+
+1. Navigate to the listing URL with `browser_navigate`
+2. Take a full-page screenshot with `browser_take_screenshot`
+3. Read the screenshot image to assess: icon, screenshot count, caption text,
+   messaging quality, preview video presence, feature graphic (Google Play)
+4. If Playwright is unavailable, ask the user to share a screenshot of the
+   listing page
+
+**Promotional text (Apple):** This 170-char field appears above the description
+but is often indistinguishable from it in scraped HTML. If you cannot confirm
+its presence, note this and recommend the user check App Store Connect.
+
+---
+
+## Phase 1.5 — Assess Brand Maturity
+
+Before scoring, classify the app into one of three tiers. This determines how
+you interpret "textbook ASO" deviations — a deliberate brand choice by a
+household name is not the same as a missed opportunity by an unknown app.
+
+### Tier definitions
+
+| Tier            | Signals                                                                                                                              | Examples                                    |
+| --------------- | ------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------- |
+| **Dominant**    | Household name, 1M+ ratings, top-10 in category, near-universal brand recognition. Users search by brand name, not generic keywords. | Instagram, Uber, Spotify, WhatsApp, Netflix |
+| **Established** | Well-known in their category, 100K+ ratings, strong organic installs, recognized brand but not universally known.                    | Strava, Notion, Duolingo, Cash App, Calm    |
+| **Challenger**  | Building awareness, <100K ratings, needs discovery through keywords and ASO tactics. Most apps fall here.                            | Your app, most indie/startup apps           |
+
+### How tier affects scoring
+
+**Dominant apps** get adjusted scoring in these areas:
+
+- **Title:** Brand-only or brand-first titles are valid (score 8+ if brand is the keyword). These apps don't need generic keyword discovery.
+- **Description:** Score purely on conversion quality, not keyword presence. If the app is a household name, a well-crafted brand description beats a keyword-stuffed one.
+- **Visual Assets:** Lifestyle/brand photography instead of UI demos is a legitimate conversion strategy. No video is acceptable if the product is hard to demo in 30s or brand awareness is near-universal.
+- **What's New:** Generic release notes at weekly+ cadence are acceptable (score 8+). At scale, detailed changelogs have minimal ROI and risk backlash.
+- **In-app events:** Missing events for utility apps with massive install bases (Uber, WhatsApp) is not a penalty. These apps don't need discovery help.
+- **Localization:** Score relative to actual market, not absolute count. A US-only fintech with 2 languages (English + Spanish) is appropriately localized.
+
+**Established apps** get partial adjustment:
+
+- Brand-first titles are fine but should still include 1-2 keywords
+- Strategic description choices get benefit of the doubt
+- Other dimensions scored normally
+
+**Challenger apps** are scored strictly against textbook ASO best practices — every character, screenshot, and keyword matters.
+
+**Key principle:** Before docking points, ask: "Is this a mistake or a deliberate
+choice by a team that has data I don't?" If the app has 1M+ ratings and a
+dedicated ASO team, assume their choices are data-informed unless clearly wrong.
+
+---
+
+## Phase 2 — Score Each Dimension
+
+Score each dimension 0-10 using the criteria in `references/scoring-criteria.md`.
+Apply the brand maturity tier adjustments from Phase 1.5.
+
+Reference files for platform specs and benchmarks:
+
+- `references/apple-specs.md` — Official Apple character limits, screenshot/video specs, CPP/PPO rules, rejection triggers
+- `references/google-play-specs.md` — Official Google Play limits, screenshot specs, Android Vitals thresholds, policies
+- `references/benchmarks.md` — Conversion data, rating impact, video lift, screenshot behavior, CPP/event benchmarks
+
+### Dimensions and Weights
+
+| #   | Dimension            | Weight | What It Covers                                                            |
+| --- | -------------------- | ------ | ------------------------------------------------------------------------- |
+| 1   | Title & Subtitle     | 20%    | Character usage, keyword presence, clarity, brand + keyword balance       |
+| 2   | Description          | 15%    | First 3 lines, keyword density (Google), CTA, structure, promotional text |
+| 3   | Visual Assets        | 25%    | Screenshot count/quality/messaging, video, icon, feature graphic          |
+| 4   | Ratings & Reviews    | 20%    | Average rating, volume, recency, developer responses                      |
+| 5   | Metadata & Freshness | 10%    | Category choice, update recency, localization count, data safety          |
+| 6   | Conversion Signals   | 10%    | Price positioning, IAP transparency, social proof, download range         |
+
+**Final score** = weighted sum, out of 100.
+
+### Score interpretation
+
+| Score  | Grade | Meaning                                                   |
+| ------ | ----- | --------------------------------------------------------- |
+| 85-100 | A     | Well-optimized; focus on A/B testing and iteration        |
+| 70-84  | B     | Good foundation; clear opportunities to improve           |
+| 50-69  | C     | Significant gaps; prioritized fixes will have high impact |
+| 30-49  | D     | Major optimization needed across multiple dimensions      |
+| 0-29   | F     | Listing needs a complete overhaul                         |
+
+---
+
+## Phase 3 — Competitor Comparison (Optional)
+
+If the user provides competitor URLs or asks for comparison:
+
+1. Fetch 2-3 top competitors in the same category
+2. Run the same scoring on each
+3. Build a comparison table highlighting where the user's app is weaker/stronger
+4. Identify keyword gaps — terms competitors rank for that the user's app doesn't target
+
+If no competitors are specified, suggest the user provide 2-3 or offer to search
+for top apps in their category.
+
+---
+
+## Phase 4 — Generate Report
+
+Use the template in `references/report-template.md` to structure the output.
+
+The report must include:
+
+1. **Score card** — table with all 6 dimensions, scores, and grade
+2. **Top 3 quick wins** — changes that take <1 hour and have highest impact
+3. **Detailed findings** — per-dimension breakdown with specific issues and fixes
+4. **Keyword suggestions** — based on title/description analysis and competitor gaps
+5. **Visual asset recommendations** — specific screenshot/video improvements
+6. **Priority action plan** — ordered list of changes by impact vs effort
+
+### Report rules
+
+- Every recommendation must be **specific and actionable** ("Change subtitle from X to Y" not "Improve subtitle")
+- Include character counts for all text recommendations
+- Flag platform-specific differences (Apple vs Google) when relevant
+- Note what CANNOT be assessed without paid tools (search volume, exact rankings)
+- When suggesting keyword changes, explain WHY each keyword matters
+
+---
+
+## Platform-Specific Rules
+
+### Apple App Store — Key Facts
+
+- Title (30 chars) + Subtitle (30 chars) + Keyword field (100 **bytes**, hidden) = indexed text
+- Keywords field is bytes not chars — Arabic/CJK use 2-3 bytes per char
+- Long description is NOT indexed for search — optimize for conversion only
+- Promotional text (170 chars) does NOT affect search (Apple confirmed)
+- Never repeat words across title/subtitle/keyword field (Apple indexes each word once)
+- Keyword field: commas, no spaces ("photo,editor,filter" not "photo, editor, filter")
+- Screenshots: up to 10 per device. First 3 visible in search — 90% never scroll past 3rd
+- Screenshot captions indexed since June 2025 (AI extraction)
+- In-app events: max 10 published at once, max 31 days each. Indexed and appear in search
+- Custom Product Pages (up to 70) in organic search since July 2025. +5.9% avg conversion lift
+- App preview video: up to 3, 15-30s each. Autoplays muted — +20-40% conversion lift
+- SKStoreReviewController: max 3 prompts per 365 days
+- Apple has human editorial curation — quality and design matter more
+- See `references/apple-specs.md` for full specs, dimensions, and rejection triggers
+
+### Google Play — Key Facts
+
+- Title (30 chars) + Short description (80 chars) + Full description (4,000 chars) = indexed text
+- Full description IS indexed — target 2-3% keyword density naturally
+- No hidden keyword field — all keywords must be in visible text
+- Google NLP/semantic understanding — keyword stuffing detected and penalized
+- Prohibited in title: emojis, ALL CAPS, "best"/"#1"/"free", CTAs (enforced since 2021)
+- Screenshots: min 2, **max 8** per device (not 10 like Apple)
+- Feature graphic (1024x500, exact) required for featured placements
+- Video does NOT autoplay — only ~6% of users tap play (low ROI vs iOS)
+- Android Vitals directly affect ranking: crash >1.09% or ANR >0.47% = reduced visibility
+- Promotional Content: submit 14 days early for featuring. Apps see 2x explore acquisitions
+- Custom Store Listings: up to 50 (can target churned users, specific countries, ad campaigns)
+- Store Listing Experiments: test up to 3 variants, run 7+ days, 1 experiment at a time
+- See `references/google-play-specs.md` for full specs and policy details
+
+### What Apple Indexes vs What Google Indexes
+
+| Field                 | Apple Indexed?   | Google Indexed?        |
+| --------------------- | ---------------- | ---------------------- |
+| Title                 | Yes              | Yes (strongest signal) |
+| Subtitle / Short desc | Yes              | Yes                    |
+| Keyword field         | Yes (hidden)     | Does not exist         |
+| Long description      | No               | Yes (heavily)          |
+| Screenshot captions   | Yes (since 2025) | No                     |
+| In-app events         | Yes              | N/A (LiveOps instead)  |
+| Developer name        | No               | Partial                |
+| IAP names             | Yes              | Yes                    |
+
+---
+
+## Common Issues Checklist
+
+Flag these if found. Items marked _(tier-dependent)_ should be evaluated against
+the app's brand maturity tier — they may be deliberate choices for Dominant apps.
+
+**Always flag (all tiers):**
+
+- [ ] Rating below 4.0
+- [ ] Last update > 3 months ago
+- [ ] Google Play description has no keyword strategy (under 1% density)
+- [ ] Google Play missing feature graphic
+- [ ] Apple keyword field likely has repeated words (inferred from title+subtitle)
+- [ ] Category mismatch — app would face less competition in a different category
+- [ ] Fewer than 5 screenshots
+
+**Flag for Challenger/Established only** _(not mistakes for Dominant apps):_
+
+- [ ] Title wastes characters on brand name only (no keywords) _(Dominant: brand IS the keyword)_
+- [ ] Subtitle/short description duplicates title keywords
+- [ ] Description first 3 lines are generic _(Dominant: may be brand-voice choice)_
+- [ ] No preview video _(Dominant: may be rational if product is hard to demo)_
+- [ ] Screenshots are just UI dumps with no messaging/captions _(Dominant: lifestyle/brand shots may convert better)_
+- [ ] Only 1-2 localizations _(score relative to actual market, not absolute count)_
+- [ ] No in-app events or promotional content _(Dominant utility apps may not need discovery help)_
+
+**Flag for all tiers but note context:**
+
+- [ ] No developer responses to negative reviews _(note volume — responding at 10M+ reviews is a different challenge than at 1K)_
+- [ ] Generic "What's New" text _(acceptable at weekly+ release cadence for Established/Dominant)_

skills/aso-audit/references/apple-specs.md

@@ -0,0 +1,107 @@
+# Apple App Store — Official Specs & Guidelines
+
+All data from developer.apple.com as of March 2026.
+
+## Character Limits
+
+| Field                   | Limit            | Indexed for Search?      | Notes                                                    |
+| ----------------------- | ---------------- | ------------------------ | -------------------------------------------------------- |
+| App Name                | 30 chars (min 2) | Yes                      | Must be unique; no trademarks, competitor names, pricing |
+| Subtitle                | 30 chars         | Yes                      | No unverifiable claims                                   |
+| Keywords                | 100 bytes        | Yes (hidden)             | Commas, no spaces between terms                          |
+| Description             | 4,000 chars      | **No**                   | Plain text only, no HTML                                 |
+| Promotional Text        | 170 chars        | **No** (Apple confirmed) | Updatable without new version                            |
+| What's New              | 4,000 chars      | No                       | Required for all versions after first                    |
+| IAP Name                | 35 chars         | Yes                      | Appears in search                                        |
+| IAP Description         | 55 chars         | No                       |                                                          |
+| In-App Event Name       | 30 chars         | Yes                      | Title case required                                      |
+| In-App Event Short Desc | 50 chars         | Yes                      | Sentence case                                            |
+| In-App Event Long Desc  | 120 chars        | No                       | Sentence case                                            |
+
+**Keywords field is 100 bytes, not 100 characters.** Non-Latin scripts (Arabic,
+Chinese, Japanese, Korean) use 2-3 bytes per character, reducing effective
+keyword count significantly.
+
+## Screenshot Specs
+
+| Device           | Required?     | Count | Dimensions (portrait)      |
+| ---------------- | ------------- | ----- | -------------------------- |
+| 6.9" iPhone      | **Required**  | 1-10  | 1260 x 2736                |
+| 13" iPad         | **Required**  | 1-10  | 2064 x 2752                |
+| Mac              | If applicable | 1-10  | Up to 2880 x 1800 (16:10)  |
+| Apple Watch      | If applicable | 1-10  | Varies by model            |
+| Apple TV         | If applicable | 1-10  | 1920 x 1080 or 3840 x 2160 |
+| Apple Vision Pro | If applicable | 1-10  | 3840 x 2160                |
+
+- Formats: JPEG, PNG
+- Apple auto-scales from required base sizes to smaller devices
+
+## App Preview Video Specs
+
+- **Count:** Up to 3 per app
+- **Duration:** 15-30 seconds
+- **Max file size:** 500 MB
+- **Codecs:** H.264 (10-12 Mbps, up to 30fps) or ProRes 422 HQ
+- **Audio:** Stereo, 256 kbps AAC or PCM, 44.1/48 kHz
+- **Formats:** .mov, .m4v, .mp4
+- **Behavior:** Autoplays muted on product page (iOS 11+)
+
+## Custom Product Pages (CPPs)
+
+- **Max:** 70 additional pages (plus 1 default)
+- **Customizable:** Screenshots, promotional text, app previews, deep links (iOS 18+)
+- **Keywords:** Each keyword combo must be unique to a single CPP
+- **Review:** Submitted to App Review independently of app updates
+- **Organic search:** CPPs appear in organic search results since July 2025
+- **Performance:** +2.5 percentage points higher conversion on average vs default
+
+## Product Page Optimization (A/B Testing)
+
+- **Treatments:** Up to 3 vs original
+- **Testable:** App icons, screenshots, app preview videos
+- **NOT testable:** Title, subtitle, description, keywords
+- **Concurrent tests:** 1 per app
+- **Max duration:** 90 days
+- **Icon constraint:** All icon variants must be in the published app binary
+- **Confidence:** Apple recommends 90% threshold (Bayesian method)
+- **Cannot modify** a test once started
+
+## In-App Events
+
+- **Max approved:** 15 in App Store Connect at once
+- **Max published:** 10 on App Store simultaneously
+- **Max duration:** 31 days per event
+- **Pre-event promotion:** Up to 14 days before start
+- **Badge types:** Challenge, Competition, Live Event, Major Update, New Season, Premiere, Special Event
+
+**Event card image:** 16:9, min 1920x1080, max 3840x2160
+**Event details image:** 9:16, min 1080x1920, max 2160x3840
+
+**Not suitable:** Repetitive daily tasks, price promotions without new content, general awareness campaigns.
+
+## Ratings & Reviews
+
+- **SKStoreReviewController:** Max 3 prompts per 365-day period
+- System controls display frequency (may show fewer than 3)
+- Do not use custom buttons to request reviews
+- Developers can respond to all reviews in App Store Connect
+- Summary rating is territory-specific
+
+## Metadata Rejection Triggers (App Review Guidelines)
+
+| Guideline | Rejection Trigger                                                         |
+| --------- | ------------------------------------------------------------------------- |
+| 2.3.1     | Hidden features, misleading marketing, false pricing                      |
+| 2.3.2     | Not disclosing IAPs in description/screenshots                            |
+| 2.3.3     | Screenshots that don't show app in use (only splash/login)                |
+| 2.3.4     | Preview videos using non-app content                                      |
+| 2.3.5     | Wrong category selected                                                   |
+| 2.3.7     | Keyword stuffing: trademarks, competitor names, pricing, irrelevant terms |
+| 2.3.8     | Metadata not appropriate for all audiences (must be 4+ rated)             |
+| 2.3.10    | Other platform names/imagery (Android, etc.) in metadata                  |
+| 2.3.12    | Generic What's New for significant changes                                |
+| 2.3.13    | Inaccurate in-app event metadata                                          |
+
+Sources: developer.apple.com/app-store/product-page/,
+developer.apple.com/app-store/search/,
+developer.apple.com/app-store/review/guidelines/

skills/aso-audit/references/benchmarks.md

@@ -0,0 +1,129 @@
+# ASO Benchmarks & Conversion Data
+
+Industry data from AppTweak, SplitMetrics, Sensor Tower, and others. Updated March 2026.
+
+## Conversion Rate Benchmarks by Category
+
+**Average CVR (page view to install):**
+
+- iOS overall: **25.0%**
+- Google Play overall: **27.3%**
+
+| Category          | iOS CVR        | Google Play CVR |
+| ----------------- | -------------- | --------------- |
+| Navigation        | 115%\*         | --              |
+| Auto & Vehicles   | --             | 70.5%           |
+| Business          | 66.7%          | --              |
+| Music (Games)     | --             | 45.0%           |
+| Utilities & Tools | --             | 36.8%           |
+| Shopping          | --             | 27.7%           |
+| Health & Fitness  | --             | 23.2%           |
+| Finance           | --             | 19.7%           |
+| Food & Drink      | --             | 13.1%           |
+| Games (Board)     | 1.2%           | 7.3%            |
+| Games (overall)   | 3-5% realistic | --              |
+
+\*Above 100% = some users install from search without visiting product page.
+
+Source: AppTweak 2025 Benchmarks Report (H1 2024 data, US market)
+
+## Rating Impact on Conversion
+
+| Rating Change              | Conversion Impact                       |
+| -------------------------- | --------------------------------------- |
+| 3.0 to 4.0 stars           | **+89%**                                |
+| 4.0 to 4.5 stars           | **+20-30%**                             |
+| 4.3 to 4.6 stars           | **+22-28%** (Finance, Health)           |
+| 0.4-star gap vs competitor | **~25% lost installs** from same search |
+| 3-star vs 5-star app       | **50% fewer conversions** for 3-star    |
+
+**Critical thresholds:**
+
+- **4.0 stars** = minimum for Apple featuring, user trust, conversion viability
+- **4.5+ stars** = optimal zone. Sweet spot: 4.1-4.9
+- **5.0 stars** can look suspicious to users
+- **Below 3.5** = sharp visibility drop on both stores
+- **79% of users** check ratings before downloading
+- **50% reject** apps below 3 stars
+
+Sources: AppFollow, MobileAction, Sensor Tower, Troof.ai
+
+## Preview Video Impact
+
+**iOS:** +20-40% conversion lift (video autoplays on product page)
+**Google Play:** Minimal lift (only ~6% of visitors tap to play)
+
+- Autoplay introduced in iOS 11 caused **+47% conversion jump**
+- Users who watch video are **2x more likely to install**
+- Average watch time: **4-6.5 seconds** (first 5 seconds are critical)
+- 50%+ of viewers watch to the end
+
+**Takeaway:** Video is high-ROI on iOS, low-ROI on Google Play.
+
+Sources: StoreMaven, SplitMetrics, Leanplum
+
+## Screenshot Impact
+
+- **90% of users** do not scroll past the 3rd screenshot
+- Average scroll rate: only **17%**
+- Users spend **6-10 seconds** scanning before deciding
+- **First screenshot decides everything**
+- Well-designed screenshots lift conversion **20-35%**
+- A/B test winners see **10-25% improvement**
+- **Optimal count:** 4-5 for utility apps, 5-6 for complex apps
+- More than 6: diminishing returns, can cause decision paralysis
+- Top 200 apps update screenshots **2-4 times/year**
+- Top Google Play games update visuals **up to 8x/year**
+- **57% of top games** A/B tested screenshots at least 2x in 2024
+
+Sources: AppTweak, ASOMobile, Sensor Tower
+
+## Custom Product Pages (Apple CPPs)
+
+- Average conversion lift: **+5.9% for apps**, **+3.5% for games**
+- Best cases: up to **+8.6%**
+- Organic referral: **+2.5 percentage points** (156% lift vs 1.6% baseline)
+- Apple Ads CPP CVR: **55.8% in 2024** (up from 42.1% in 2023)
+- **Only 31% of apps** and **26% of games** use CPPs (low adoption = opportunity)
+- Screenshot reordering alone produced **+16.6% installs** in one case
+
+Sources: AppTweak, SplitMetrics, MobileAction
+
+## Custom Store Listings (Google Play CSLs)
+
+- Up to **50 custom versions** per app
+- Case study (Lockwood/Avakin Life): **+57% CVR** over 2 months
+- Can target inactive/churned users (28+ days no activity)
+
+Source: Phiture, MobileAction
+
+## In-App Events (Apple)
+
+- **55% of top 200 apps** use them regularly
+- +**15-20% more impressions** from editorial/browse placements
+- One case: **+124% surge** in total impressions
+- One case: **+50% impressions AND first-time downloads**
+- Search CVR uptick: **+10.3%**
+- Re-downloads increase: **+15.5%**
+- **Boost is short-lived** -- KPIs drop to baseline when event ends
+- Optimal: **2-4 active events per month**
+
+Sources: Phiture, AppTweak, Appalize
+
+## Promotional Content (Google Play)
+
+- Apps with featuring see **2x explore acquisitions** (official Google)
+- +2% 28-day active users and +4% revenue on average
+
+Source: Google Play Console documentation
+
+## A/B Test Impact Thresholds
+
+| Improvement | Classification                     |
+| ----------- | ---------------------------------- |
+| >10%        | Strong winner -- apply immediately |
+| 5-10%       | Meaningful winner                  |
+| 2-5%        | Marginal winner                    |
+| <2%         | Noise -- not significant           |
+
+Source: SplitMetrics, MobileAction

skills/aso-audit/references/google-play-specs.md

@@ -0,0 +1,131 @@
+# Google Play Store — Official Specs & Guidelines
+
+All data from support.google.com and developer.android.com as of March 2026.
+
+## Character Limits
+
+| Field             | Limit       | Indexed?               | Notes                                 |
+| ----------------- | ----------- | ---------------------- | ------------------------------------- |
+| App Title         | 30 chars    | Yes (strongest signal) | Reduced from 50 in Sept 2021          |
+| Short Description | 80 chars    | Yes                    | Visible without expanding             |
+| Full Description  | 4,000 chars | **Yes (heavily)**      | Google NLP indexes entire text        |
+| Developer Name    | 64 chars    | Partial                | Same emoji/caps restrictions as title |
+
+## Prohibited in Metadata (enforced since Sept 2021)
+
+**Title, Icon, Developer Name:**
+
+- Emojis, emoticons, repeated special characters
+- ALL CAPS (unless registered brand)
+- Performance claims: "top," "best," "#1," "free," "no ads"
+- Misleading store performance or endorsement
+- Calls-to-action: "update now," "download now"
+
+**Short Description:**
+
+- Same performance claims as title
+- Calls-to-action
+- Unattributed testimonials
+
+**Screenshots, Feature Graphic, Video:**
+
+- Time-sensitive taglines
+- Calls-to-action ("Download now," "Play now")
+- Must authentically showcase app functionality
+
+## Screenshot Specs
+
+| Device     | Min   | Max   | Aspect Ratio | Min Resolution | Max Long Edge |
+| ---------- | ----- | ----- | ------------ | -------------- | ------------- |
+| Phone      | **2** | **8** | 9:16 or 16:9 | 320px any side | 3,840px       |
+| 7" Tablet  | 4     | 8     | 9:16 or 16:9 | 1,080px short  | 7,680px       |
+| 10" Tablet | 4     | 8     | 9:16 or 16:9 | 1,080px short  | 7,680px       |
+| Chromebook | 4     | 8     | 9:16 or 16:9 | 1,080px short  | 7,680px       |
+| Wear OS    | 1     | 8     | **1:1**      | 384x384        | 3,840px       |
+| Android TV | 1     | 8     | **16:9**     | 1,920x1,080    | 3,840px       |
+
+- **Recommended phone size:** 1080x1920 (portrait)
+- **Format:** JPEG or 24-bit PNG (no alpha)
+- **Max file size:** 8 MB each
+
+**Note:** Google Play max is 8 screenshots per device, not 10 like Apple.
+
+## Feature Graphic
+
+- **Dimensions:** 1024 x 500 px (exact, required)
+- **Format:** JPEG or 24-bit PNG (no alpha)
+- Displayed at top of listing and in featured placements
+
+## App Icon
+
+- **Dimensions:** 512 x 512 px
+- **Format:** 32-bit PNG (with alpha)
+- **Max file size:** 1,024 KB
+- **Shape:** Full square (Google applies 30% corner radius automatically)
+- **Prohibited:** Ranking claims, download counts, deal text, emoji
+
+## Preview Video
+
+- **Format:** YouTube URL (public or unlisted)
+- **Duration:** 30 seconds to 2 minutes recommended
+- No ads, no monetization, must be embeddable, not age-restricted
+- **Does NOT autoplay** (only ~6% of visitors tap to play)
+
+## Store Listing Experiments (A/B Testing)
+
+- **Variants:** Up to 3 per experiment (plus control)
+- **Testable:** Icon, feature graphic, screenshots, video, short description, full description
+- **Concurrent:** Cannot run more than 1 default graphics experiment simultaneously
+- **Audience:** Signed-in Google Play users only
+- **Metrics:** First-time installers + retained first-time installers (1-day retention)
+- **Duration:** Run at least 7 days (weekday/weekend variance)
+- **Localized:** Test across up to 5 languages simultaneously
+
+## Custom Store Listings
+
+- **Max:** 50 per app (100 for Play partners)
+- **Customizable:** Title, short/full description, icon, screenshots, feature graphic, video
+- **Targeting:** Country/region, pre-registration, install state, Google Ads campaigns, inactive/churned users (28+ days)
+- **2025 addition:** Gemini AI auto-generates text for CSLs in Play Console
+
+## Promotional Content (LiveOps)
+
+| Type              | Description                    | Duration             |
+| ----------------- | ------------------------------ | -------------------- |
+| Offers            | Discounts, free items, bundles | Up to 28 days        |
+| Events            | Time-limited in-app events     | Must have time limit |
+| Major Update      | Significant new features       | Max 1 week           |
+| Crossover (games) | Cross-game/IP collaboration    | Varies               |
+
+- Submit **4+ days** before start (standard review)
+- Submit **14+ days** before for featuring requests
+- **Impact:** "Over twice as many explore acquisitions during featuring" (official Google)
+
+## Android Vitals — Ranking Thresholds
+
+Apps exceeding these thresholds get **reduced visibility** in search and recommendations.
+
+| Metric                       | Overall Threshold | Per-Device Threshold |
+| ---------------------------- | ----------------- | -------------------- |
+| User-Perceived Crash Rate    | **1.09%**         | 8%                   |
+| User-Perceived ANR Rate      | **0.47%**         | 8%                   |
+| Excessive Partial Wake Locks | 5%                | N/A                  |
+
+**Consequences:** Reduced search visibility, warning labels on listing, quality alerts to users before install.
+**Recovery:** Google checks daily using 28-day rolling average.
+
+## Search Ranking — Official Factors
+
+Google confirms these affect ranking:
+
+1. **Metadata relevance** — Title carries most weight. NLP scans title + short desc + full desc.
+2. **App quality** — Android Vitals (crash/ANR rates)
+3. **Ratings and reviews** — Star rating + review text. 85% of featured apps have 4.0+
+4. **Install volume and velocity** — Total installs + daily/weekly frequency
+5. **Engagement and retention** — Session frequency, duration, retention rates
+6. **Update frequency** — Regular updates signal active maintenance
+7. **Localization** — Regional keyword/visual adaptation. 59% of US apps localize titles.
+
+Sources: support.google.com/googleplay/android-developer/answer/4448378,
+support.google.com/googleplay/android-developer/answer/9898842,
+developer.android.com/topic/performance/vitals

skills/aso-audit/references/report-template.md

@@ -0,0 +1,213 @@
+# ASO Audit Report Template
+
+Use this structure for all ASO audit reports.
+
+---
+
+## Header
+
+```
+# ASO Audit: {App Name}
+**Store:** {Apple App Store / Google Play}
+**URL:** {listing URL}
+**Audit date:** {date}
+**Brand tier:** {Dominant / Established / Challenger} — {one-line justification}
+**Overall Score:** {score}/100 (Grade: {A/B/C/D/F})
+```
+
+---
+
+## Score Card
+
+```
+| Dimension | Score | Grade | Key Issue |
+|-----------|-------|-------|-----------|
+| Title & Subtitle | X/10 | {grade} | {one-line summary} |
+| Description | X/10 | {grade} | {one-line summary} |
+| Visual Assets | X/10 | {grade} | {one-line summary} |
+| Ratings & Reviews | X/10 | {grade} | {one-line summary} |
+| Metadata & Freshness | X/10 | {grade} | {one-line summary} |
+| Conversion Signals | X/10 | {grade} | {one-line summary} |
+| **OVERALL** | **{weighted}/100** | **{grade}** | |
+```
+
+Grade scale per dimension: 9-10 = A, 7-8 = B, 5-6 = C, 3-4 = D, 1-2 = F
+
+---
+
+## Top 3 Quick Wins
+
+Highest-impact changes that take under 1 hour:
+
+```
+### 1. {Action verb} — {specific change}
+**Impact:** {High/Medium} | **Effort:** {<15 min / <30 min / <1 hour}
+**Current:** {what it is now}
+**Recommended:** {exact replacement, with character count}
+**Why:** {one sentence explaining the impact}
+
+### 2. ...
+### 3. ...
+```
+
+---
+
+## Detailed Findings
+
+### Title & Subtitle Analysis
+
+```
+**Current title:** "{title}" ({X}/30 chars used)
+**Current subtitle/short desc:** "{subtitle}" ({X}/30 or /80 chars used)
+
+**Issues found:**
+- {issue 1}
+- {issue 2}
+
+**Recommended title:** "{new title}" ({X}/30 chars) — {rationale}
+**Recommended subtitle:** "{new subtitle}" ({X}/30 or /80 chars) — {rationale}
+```
+
+### Description Analysis
+
+```
+**First 3 lines (above fold):**
+> {quoted text}
+
+**Issues found:**
+- {issue 1}
+- {issue 2}
+
+**Keyword density (Google Play only):** {X}% — target: 2-3%
+**Top keywords found:** {keyword1} (Xn), {keyword2} (Xn), ...
+**Missing high-value keywords:** {keyword1}, {keyword2}, ...
+
+**Recommended first 3 lines:**
+> {rewritten text}
+```
+
+### Visual Assets Analysis
+
+```
+**Screenshots:** {count} ({store} shows first {3/all} in search)
+**Preview video:** {Yes/No}
+**Icon assessment:** {description}
+**Feature graphic (Google Play):** {Yes/No}
+
+**Screenshot audit:**
+1. {screenshot 1 description} — {pass/issue}
+2. {screenshot 2 description} — {pass/issue}
+...
+
+**Recommendations:**
+- {specific visual change 1}
+- {specific visual change 2}
+```
+
+### Ratings & Reviews Analysis
+
+```
+**Average rating:** {X.X} stars ({count} ratings)
+**Recent review sentiment:** {Positive/Mixed/Negative}
+**Common complaints:** {theme1}, {theme2}
+**Developer responses:** {Yes, active / Sporadic / None}
+
+**Recommendations:**
+- {specific action 1}
+- {specific action 2}
+```
+
+### Metadata & Freshness
+
+```
+**Last updated:** {date} ({X days/months ago})
+**Localizations:** {count} languages
+**Category:** {current category}
+**In-app events/LiveOps:** {Yes/No}
+
+**Recommendations:**
+- {specific action 1}
+- {specific action 2}
+```
+
+### Conversion Signals
+
+```
+**Price model:** {Free / Freemium / Paid}
+**IAP count:** {count}
+**Downloads (Google Play):** {range}
+**Social proof visible:** {awards, press, badges — or "none"}
+
+**Recommendations:**
+- {specific action 1}
+- {specific action 2}
+```
+
+---
+
+## Keyword Suggestions
+
+```
+| Keyword | Rationale | Where to Place | Priority |
+|---------|-----------|----------------|----------|
+| {keyword} | {why this keyword} | {title/subtitle/description/keyword field} | {High/Med/Low} |
+| ... | ... | ... | ... |
+```
+
+Note: Without paid ASO tools, exact search volume is unavailable. These
+suggestions are based on category analysis, competitor metadata, and semantic
+relevance. Validate with AppTweak, Sensor Tower, or MobileAction for volume data.
+
+---
+
+## Competitor Comparison (if applicable)
+
+```
+| Metric | {Your App} | {Competitor 1} | {Competitor 2} |
+|--------|-----------|----------------|----------------|
+| Title keywords | ... | ... | ... |
+| Rating | ... | ... | ... |
+| Screenshots | ... | ... | ... |
+| Video | ... | ... | ... |
+| Description keywords | ... | ... | ... |
+| Last updated | ... | ... | ... |
+| Overall ASO score | ... | ... | ... |
+```
+
+---
+
+## Priority Action Plan
+
+Ordered by impact (high to low), grouped by effort:
+
+```
+### Do This Week (Quick Wins)
+1. {action} — {expected impact}
+2. {action} — {expected impact}
+
+### Do This Month (Medium Effort)
+3. {action} — {expected impact}
+4. {action} — {expected impact}
+
+### Plan for Next Quarter (High Effort)
+5. {action} — {expected impact}
+6. {action} — {expected impact}
+```
+
+---
+
+## Limitations
+
+Always include this section:
+
+> **What this audit cannot measure without paid ASO tools:**
+>
+> - Exact keyword search volume and difficulty scores
+> - Historical keyword ranking positions
+> - Download and revenue estimates
+> - Apple keyword field contents (hidden from public view)
+> - Install conversion rate data (only available to app owner in console)
+> - A/B test results from previous experiments
+>
+> For these data points, consider using AppTweak ($69/mo), Sensor Tower, or
+> MobileAction ($69/mo).

skills/aso-audit/references/scoring-criteria.md

@@ -0,0 +1,213 @@
+# ASO Scoring Criteria
+
+Score each dimension 0-10 using the rubrics below.
+**Apply brand maturity tier adjustments** from Phase 1.5 of the main skill.
+
+---
+
+## Brand Maturity Adjustments (apply to all dimensions)
+
+Before scoring, determine the app's tier: **Dominant**, **Established**, or **Challenger**.
+
+**Dominant apps (Instagram, Uber, Spotify, WhatsApp, Netflix):**
+
+- Brand-only titles score 8+ (the brand IS the keyword)
+- Lifestyle/brand screenshots score same as captioned UI screenshots
+- Generic What's New at weekly+ cadence scores 8+
+- Missing in-app events for utility apps is not a penalty
+- Description scored on conversion quality only, not keyword presence
+- Localization scored relative to actual market footprint
+- Missing preview video is acceptable if brand awareness is near-universal
+
+**Established apps (Duolingo, Strava, Notion, Calm, Cash App):**
+
+- Brand-first titles with 1-2 keywords score normally
+- Strategic description/visual choices get benefit of the doubt
+- All other dimensions scored normally
+
+**Challenger apps (most apps):**
+
+- Scored strictly against textbook ASO — every character and feature matters
+
+**Key principle:** Before docking points, ask: "Is this a mistake or a data-informed
+choice by a team with more information than I have?"
+
+---
+
+## 1. Title & Subtitle (Weight: 20%)
+
+**Challenger rubric:**
+
+| Score | Criteria                                                                                                                                                                |
+| ----- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| 9-10  | Brand + high-value keyword in title, complementary keywords in subtitle, no word repetition across fields, near max character usage, instantly communicates app purpose |
+| 7-8   | Good keyword presence, minor character waste (5+ unused chars), clear purpose                                                                                           |
+| 5-6   | Has keywords but poor placement, some repetition between fields, purpose somewhat clear                                                                                 |
+| 3-4   | Title is brand-only or generic, subtitle missing or weak, poor character usage                                                                                          |
+| 1-2   | No keyword strategy, title doesn't communicate purpose, major character waste                                                                                           |
+| 0     | Cannot assess (data unavailable)                                                                                                                                        |
+
+**Dominant/Established adjustment:** Brand-only titles (e.g., "Instagram") are
+valid if the brand has high search volume. Score 8+ for Dominant apps where
+brand recognition eliminates the need for generic keywords. Evaluate whether
+unused characters represent waste or intentional simplicity.
+
+**Check for:**
+
+- Characters used vs limit (title: 30, subtitle/short desc: 30/80). "Near max" = within 3 chars of the limit (27+/30, 77+/80)
+- Primary keyword in title
+- Keyword duplication between title and subtitle
+- Whether app purpose is immediately clear
+- Unnecessary words (articles, prepositions) consuming space
+- Special characters or claims ("#1", "best") that risk rejection (Apple)
+
+---
+
+## 2. Description (Weight: 15%)
+
+### Apple App Store
+
+| Score | Criteria                                                                                                                                               |
+| ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| 9-10  | First 3 lines hook with clear value prop, structured with features/benefits/social proof/CTA, promotional text actively used, compelling and scannable |
+| 7-8   | Good opening, decent structure, could improve scannability or CTA                                                                                      |
+| 5-6   | Generic opening ("Welcome to..."), some structure, missing CTA or social proof                                                                         |
+| 3-4   | Wall of text, no clear value prop above fold, no promotional text                                                                                      |
+| 1-2   | Minimal or boilerplate description, no effort                                                                                                          |
+| 0     | Cannot assess                                                                                                                                          |
+
+### Google Play
+
+| Score | Criteria                                                                                                                                     |
+| ----- | -------------------------------------------------------------------------------------------------------------------------------------------- |
+| 9-10  | Keywords in first 3 sentences, 2-3% natural density throughout, HTML formatting used, structured sections, strong CTA, keywords feel natural |
+| 7-8   | Good keyword presence, some structure, density slightly off (1-2% or 3-4%)                                                                   |
+| 5-6   | Keywords present but sparse (<1%) or stuffed (>5%), weak structure                                                                           |
+| 3-4   | No keyword strategy visible, poor formatting, wall of text                                                                                   |
+| 1-2   | Minimal description, no keywords, no structure                                                                                               |
+| 0     | Cannot assess                                                                                                                                |
+
+**Check for:**
+
+- First 3 lines quality (visible before "Read More")
+- Feature-benefit framing (not just feature lists)
+- Social proof (downloads, awards, press mentions)
+- Call to action
+- Keyword density (Google Play only - count target keywords / total words)
+- HTML formatting usage (Google Play)
+- Promotional text presence and quality (Apple)
+
+---
+
+## 3. Visual Assets (Weight: 25%)
+
+| Score | Criteria                                                                                                                                                                      |
+| ----- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| 9-10  | 8-10 screenshots with clear messaging/captions, preview video present, screenshots tell a story in sequence, each communicates one benefit, icon is distinctive and memorable |
+| 7-8   | 6-7 screenshots with captions, good icon, no video OR good video but some screenshot messaging unclear                                                                        |
+| 5-6   | 5+ screenshots but weak/no captions, basic icon, no video, screenshots are UI dumps                                                                                           |
+| 3-4   | 3-4 screenshots, no captions, generic icon, no storytelling                                                                                                                   |
+| 1-2   | Fewer than 3 screenshots, or screenshots are raw unedited UI, poor icon                                                                                                       |
+| 0     | Cannot assess                                                                                                                                                                 |
+
+**Check for:**
+
+- Screenshot count (minimum 5, ideal 8-10)
+- Caption/overlay text on screenshots (one message per screen, 5-7 words max)
+- First 3 screenshots (highest conversion impact on Apple)
+- Preview video presence and quality
+- Icon distinctiveness (no text in icon, bold shapes, stands out)
+- Feature graphic presence (Google Play - mandatory for featured placements)
+- Screenshot storytelling flow (do they tell a coherent story?)
+- Localized visual assets (for non-English markets)
+- Caption keywords (Apple - indexed since June 2025)
+
+---
+
+## 4. Ratings & Reviews (Weight: 20%)
+
+| Score | Criteria                                                                                               |
+| ----- | ------------------------------------------------------------------------------------------------------ |
+| 9-10  | 4.5+ stars, 10K+ ratings, recent reviews positive, developer responds to negatives, steady review flow |
+| 7-8   | 4.0-4.4 stars, 1K+ ratings, mostly positive recent reviews, some developer responses                   |
+| 5-6   | 3.5-3.9 stars, 500+ ratings, mixed recent reviews, no developer responses                              |
+| 3-4   | 3.0-3.4 stars, <500 ratings, negative themes in recent reviews                                         |
+| 1-2   | Below 3.0 stars, few ratings, no developer engagement, visible complaints                              |
+| 0     | No ratings yet or cannot assess                                                                        |
+
+**Check for:**
+
+- Average rating (target: 4.0+ minimum, 4.5+ ideal)
+- Total rating count
+- Recent review sentiment (last 5-10 visible reviews)
+- Common complaint themes (bugs, crashes, pricing, UX)
+- Developer response presence and quality
+- Rating trend (improving or declining, if visible)
+- Review recency (fresh reviews signal active user base)
+
+---
+
+## 5. Metadata & Freshness (Weight: 10%)
+
+| Score | Criteria                                                                                                                  |
+| ----- | ------------------------------------------------------------------------------------------------------------------------- |
+| 9-10  | Updated within last month, 10+ localizations, optimal category choice, in-app events/LiveOps active, data safety complete |
+| 7-8   | Updated within 2 months, 5+ localizations, good category, data safety present                                             |
+| 5-6   | Updated within 3 months, 2-4 localizations, acceptable category                                                           |
+| 3-4   | Updated 3-6 months ago, 1-2 localizations, possibly wrong category                                                        |
+| 1-2   | Not updated in 6+ months, single language, poor category choice                                                           |
+| 0     | Cannot assess                                                                                                             |
+
+**Check for:**
+
+- Last update date and recency
+- Number of supported languages/localizations
+- Category selection (is it the best fit? less competitive alternative?)
+- In-app events (Apple) or promotional content (Google) presence
+- Data safety / privacy nutrition label completeness
+- Age rating appropriateness
+- Version history quality (do release notes communicate value?)
+- What's New text quality
+
+---
+
+## 6. Conversion Signals (Weight: 10%)
+
+| Score | Criteria                                                                                                                                                          |
+| ----- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| 9-10  | Clear value before download, transparent pricing/IAP, social proof visible (press, awards), download range suggests strong traction, developer credibility strong |
+| 7-8   | Good value communication, pricing clear, some social proof                                                                                                        |
+| 5-6   | Value prop exists but weak, pricing unclear or IAP heavy, limited social proof                                                                                    |
+| 3-4   | Unclear what user gets, confusing pricing, no social proof, low downloads visible                                                                                 |
+| 1-2   | No value communication, suspicious pricing, app looks abandoned                                                                                                   |
+| 0     | Cannot assess                                                                                                                                                     |
+
+**Check for:**
+
+- Price transparency (free, freemium, paid - is it clear?)
+- In-app purchase list quality (do IAP names communicate value?)
+- Download range (Google Play - 10K+, 100K+, 1M+ signals trust)
+- Developer name/brand recognition
+- "Editors' Choice" or featured badges
+- Press mentions or awards in description
+- Related apps from same developer (portfolio trust signal)
+- Privacy practices transparency
+
+---
+
+## Calculating Final Score
+
+```
+Final Score = (Title * 0.20) + (Description * 0.15) + (Visuals * 0.25)
+            + (Ratings * 0.20) + (Metadata * 0.10) + (Conversion * 0.10)
+
+Scale to 100: Final Score * 10
+```
+
+**Example:** Title: 7, Description: 6, Visuals: 8, Ratings: 9, Metadata: 5, Conversion: 7
+
+```
+(7 * 0.20) + (6 * 0.15) + (8 * 0.25) + (9 * 0.20) + (5 * 0.10) + (7 * 0.10)
+= 1.4 + 0.9 + 2.0 + 1.8 + 0.5 + 0.7
+= 7.3 → 73/100 → Grade: B
+```

skills/churn-prevention/SKILL.md

@@ -0,0 +1,424 @@
+---
+name: churn-prevention
+description: "When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers or wants to build systems to prevent it. For post-cancel win-back email sequences, see emails. For in-app upgrade paywalls, see paywalls."
+metadata:
+  version: 1.1.0
+---
+
+# Churn Prevention
+
+You are an expert in SaaS retention and churn prevention. Your goal is to help reduce both voluntary churn (customers choosing to cancel) and involuntary churn (failed payments) through well-designed cancel flows, dynamic save offers, proactive retention, and dunning strategies.
+
+## Before Starting
+
+**Check for product marketing context first:**
+If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
+
+Gather this context (ask if not provided):
+
+### 1. Current Churn Situation
+- What's your monthly churn rate? (Voluntary vs. involuntary if known)
+- How many active subscribers?
+- What's the average MRR per customer?
+- Do you have a cancel flow today, or does cancel happen instantly?
+
+### 2. Billing & Platform
+- What billing provider? (Stripe, Chargebee, Paddle, Recurly, Braintree)
+- Monthly, annual, or both billing intervals?
+- Do you support plan pausing or downgrades?
+- Any existing retention tooling? (Churnkey, ProsperStack, Raaft)
+
+### 3. Product & Usage Data
+- Do you track feature usage per user?
+- Can you identify engagement drop-offs?
+- Do you have cancellation reason data from past churns?
+- What's your activation metric? (What do retained users do that churned users don't?)
+
+### 4. Constraints
+- B2B or B2C? (Affects flow design)
+- Self-serve cancellation required? (Some regulations mandate easy cancel)
+- Brand tone for offboarding? (Empathetic, direct, playful)
+
+---
+
+## How This Skill Works
+
+Churn has two types requiring different strategies:
+
+| Type | Cause | Solution |
+|------|-------|----------|
+| **Voluntary** | Customer chooses to cancel | Cancel flows, save offers, exit surveys |
+| **Involuntary** | Payment fails | Dunning emails, smart retries, card updaters |
+
+Voluntary churn is typically 50-70% of total churn. Involuntary churn is 30-50% but is often easier to fix.
+
+This skill supports three modes:
+
+1. **Build a cancel flow** — Design from scratch with survey, save offers, and confirmation
+2. **Optimize an existing flow** — Analyze cancel data and improve save rates
+3. **Set up dunning** — Failed payment recovery with retries and email sequences
+
+---
+
+## Cancel Flow Design
+
+### The Cancel Flow Structure
+
+Every cancel flow follows this sequence:
+
+```
+Trigger → Survey → Dynamic Offer → Confirmation → Post-Cancel
+```
+
+**Step 1: Trigger**
+Customer clicks "Cancel subscription" in account settings.
+
+**Step 2: Exit Survey**
+Ask why they're cancelling. This determines which save offer to show.
+
+**Step 3: Dynamic Save Offer**
+Present a targeted offer based on their reason (discount, pause, downgrade, etc.)
+
+**Step 4: Confirmation**
+If they still want to cancel, confirm clearly with end-of-billing-period messaging.
+
+**Step 5: Post-Cancel**
+Set expectations, offer easy reactivation path, trigger win-back sequence.
+
+### Exit Survey Design
+
+The exit survey is the foundation. Good reason categories:
+
+| Reason | What It Tells You |
+|--------|-------------------|
+| Too expensive | Price sensitivity, may respond to discount or downgrade |
+| Not using it enough | Low engagement, may respond to pause or onboarding help |
+| Missing a feature | Product gap, show roadmap or workaround |
+| Switching to competitor | Competitive pressure, understand what they offer |
+| Technical issues / bugs | Product quality, escalate to support |
+| Temporary / seasonal need | Usage pattern, offer pause |
+| Business closed / changed | Unavoidable, learn and let go gracefully |
+| Other | Catch-all, include free text field |
+
+**Survey best practices:**
+- 1 question, single-select with optional free text
+- 5-8 reason options max (avoid decision fatigue)
+- Put most common reasons first (review data quarterly)
+- Don't make it feel like a guilt trip
+- "Help us improve" framing works better than "Why are you leaving?"
+
+### Dynamic Save Offers
+
+The key insight: **match the offer to the reason.** A discount won't save someone who isn't using the product. A feature roadmap won't save someone who can't afford it.
+
+**Offer-to-reason mapping:**
+
+| Cancel Reason | Primary Offer | Fallback Offer |
+|---------------|---------------|----------------|
+| Too expensive | Discount (20-30% for 2-3 months) | Downgrade to lower plan |
+| Not using it enough | Pause (1-3 months) | Free onboarding session |
+| Missing feature | Roadmap preview + timeline | Workaround guide |
+| Switching to competitor | Competitive comparison + discount | Feedback session |
+| Technical issues | Escalate to support immediately | Credit + priority fix |
+| Temporary / seasonal | Pause subscription | Downgrade temporarily |
+| Business closed | Skip offer (respect the situation) | — |
+
+### Save Offer Types
+
+**Discount**
+- 20-30% off for 2-3 months is the sweet spot
+- Avoid 50%+ discounts (trains customers to cancel for deals)
+- Time-limit the offer ("This offer expires when you leave this page")
+- Show the dollar amount saved, not just the percentage
+
+**Pause subscription**
+- 1-3 month pause maximum (longer pauses rarely reactivate)
+- 60-80% of pausers eventually return to active
+- Auto-reactivation with advance notice email
+- Keep their data and settings intact
+
+**Plan downgrade**
+- Offer a lower tier instead of full cancellation
+- Show what they keep vs. what they lose
+- Position as "right-size your plan" not "downgrade"
+- Easy path back up when ready
+
+**Feature unlock / extension**
+- Unlock a premium feature they haven't tried
+- Extend trial of a higher tier
+- Works best for "not getting enough value" reasons
+
+**Personal outreach**
+- For high-value accounts (top 10-20% by MRR)
+- Route to customer success for a call
+- Personal email from founder for smaller companies
+
+### Cancel Flow UI Patterns
+
+```
+┌─────────────────────────────────────┐
+│  We're sorry to see you go          │
+│                                     │
+│  What's the main reason you're      │
+│  cancelling?                        │
+│                                     │
+│  ○ Too expensive                    │
+│  ○ Not using it enough              │
+│  ○ Missing a feature I need         │
+│  ○ Switching to another tool        │
+│  ○ Technical issues                 │
+│  ○ Temporary / don't need right now │
+│  ○ Other: [____________]            │
+│                                     │
+│  [Continue]                         │
+│  [Never mind, keep my subscription] │
+└─────────────────────────────────────┘
+         ↓ (selects "Too expensive")
+┌─────────────────────────────────────┐
+│  What if we could help?             │
+│                                     │
+│  We'd love to keep you. Here's a    │
+│  special offer:                     │
+│                                     │
+│  ┌───────────────────────────────┐  │
+│  │  25% off for the next 3 months│  │
+│  │  Save $XX/month               │  │
+│  │                               │  │
+│  │  [Accept Offer]               │  │
+│  └───────────────────────────────┘  │
+│                                     │
+│  Or switch to [Basic Plan] at       │
+│  $X/month →                         │
+│                                     │
+│  [No thanks, continue cancelling]   │
+└─────────────────────────────────────┘
+```
+
+**UI principles:**
+- Keep the "continue cancelling" option visible (no dark patterns)
+- One primary offer + one fallback, not a wall of options
+- Show specific dollar savings, not abstract percentages
+- Use the customer's name and account data when possible
+- Mobile-friendly (many cancellations happen on mobile)
+
+For detailed cancel flow patterns by industry and billing provider, see [references/cancel-flow-patterns.md](references/cancel-flow-patterns.md).
+
+---
+
+## Churn Prediction & Proactive Retention
+
+The best save happens before the customer ever clicks "Cancel."
+
+### Risk Signals
+
+Track these leading indicators of churn:
+
+| Signal | Risk Level | Timeframe |
+|--------|-----------|-----------|
+| Login frequency drops 50%+ | High | 2-4 weeks before cancel |
+| Key feature usage stops | High | 1-3 weeks before cancel |
+| Support tickets spike then stop | High | 1-2 weeks before cancel |
+| Email open rates decline | Medium | 2-6 weeks before cancel |
+| Billing page visits increase | High | Days before cancel |
+| Team seats removed | High | 1-2 weeks before cancel |
+| Data export initiated | Critical | Days before cancel |
+| NPS score drops below 6 | Medium | 1-3 months before cancel |
+
+### Health Score Model
+
+Build a simple health score (0-100) from weighted signals:
+
+```
+Health Score = (
+  Login frequency score × 0.30 +
+  Feature usage score   × 0.25 +
+  Support sentiment     × 0.15 +
+  Billing health        × 0.15 +
+  Engagement score      × 0.15
+)
+```
+
+| Score | Status | Action |
+|-------|--------|--------|
+| 80-100 | Healthy | Upsell opportunities |
+| 60-79 | Needs attention | Proactive check-in |
+| 40-59 | At risk | Intervention campaign |
+| 0-39 | Critical | Personal outreach |
+
+### Proactive Interventions
+
+**Before they think about cancelling:**
+
+| Trigger | Intervention |
+|---------|-------------|
+| Usage drop >50% for 2 weeks | "We noticed you haven't used [feature]. Need help?" email |
+| Approaching plan limit | Upgrade nudge (not a wall — paywalls handles this) |
+| No login for 14 days | Re-engagement email with recent product updates |
+| NPS detractor (0-6) | Personal follow-up within 24 hours |
+| Support ticket unresolved >48h | Escalation + proactive status update |
+| Annual renewal in 30 days | Value recap email + renewal confirmation |
+
+---
+
+## Involuntary Churn: Payment Recovery
+
+Failed payments cause 30-50% of all churn but are the most recoverable.
+
+### The Dunning Stack
+
+```
+Pre-dunning → Smart retry → Dunning emails → Grace period → Hard cancel
+```
+
+### Pre-Dunning (Prevent Failures)
+
+- **Card expiry alerts**: Email 30, 15, and 7 days before card expires
+- **Backup payment method**: Prompt for a second payment method at signup
+- **Card updater services**: Visa/Mastercard auto-update programs (reduces hard declines 30-50%)
+- **Pre-billing notification**: Email 3-5 days before charge for annual plans
+
+### Smart Retry Logic
+
+Not all failures are the same. Retry strategy by decline type:
+
+| Decline Type | Examples | Retry Strategy |
+|-------------|----------|----------------|
+| Soft decline (temporary) | Insufficient funds, processor timeout | Retry 3-5 times over 7-10 days |
+| Hard decline (permanent) | Card stolen, account closed | Don't retry — ask for new card |
+| Authentication required | 3D Secure, SCA | Send customer to update payment |
+
+**Retry timing best practices:**
+- Retry 1: 24 hours after failure
+- Retry 2: 3 days after failure
+- Retry 3: 5 days after failure
+- Retry 4: 7 days after failure (with dunning email escalation)
+- After 4 retries: Hard cancel with reactivation path
+
+**Smart retry tip:** Retry on the day of the month the payment originally succeeded (if Day 1 worked before, retry on Day 1). Stripe Smart Retries handles this automatically.
+
+### Dunning Email Sequence
+
+| Email | Timing | Tone | Content |
+|-------|--------|------|---------|
+| 1 | Day 0 (failure) | Friendly alert | "Your payment didn't go through. Update your card." |
+| 2 | Day 3 | Helpful reminder | "Quick reminder — update your payment to keep access." |
+| 3 | Day 7 | Urgency | "Your account will be paused in 3 days. Update now." |
+| 4 | Day 10 | Final warning | "Last chance to keep your account active." |
+
+**Dunning email best practices:**
+- Direct link to payment update page (no login required if possible)
+- Show what they'll lose (their data, their team's access)
+- Don't blame ("your payment failed" not "you failed to pay")
+- Include support contact for help
+- Plain text performs better than designed emails for dunning
+
+### Recovery Benchmarks
+
+| Metric | Poor | Average | Good |
+|--------|------|---------|------|
+| Soft decline recovery | <40% | 50-60% | 70%+ |
+| Hard decline recovery | <10% | 20-30% | 40%+ |
+| Overall payment recovery | <30% | 40-50% | 60%+ |
+| Pre-dunning prevention | None | 10-15% | 20-30% |
+
+For the complete dunning playbook with provider-specific setup, see [references/dunning-playbook.md](references/dunning-playbook.md).
+
+---
+
+## Metrics & Measurement
+
+### Key Churn Metrics
+
+| Metric | Formula | Target |
+|--------|---------|--------|
+| Monthly churn rate | Churned customers / Start-of-month customers | <5% B2C, <2% B2B |
+| Revenue churn (net) | (Lost MRR - Expansion MRR) / Start MRR | Negative (net expansion) |
+| Cancel flow save rate | Saved / Total cancel sessions | 25-35% |
+| Offer acceptance rate | Accepted offers / Shown offers | 15-25% |
+| Pause reactivation rate | Reactivated / Total paused | 60-80% |
+| Dunning recovery rate | Recovered / Total failed payments | 50-60% |
+| Time to cancel | Days from first churn signal to cancel | Track trend |
+
+### Cohort Analysis
+
+Segment churn by:
+- **Acquisition channel** — Which channels bring stickier customers?
+- **Plan type** — Which plans churn most?
+- **Tenure** — When do most cancellations happen? (30, 60, 90 days?)
+- **Cancel reason** — Which reasons are growing?
+- **Save offer type** — Which offers work best for which segments?
+
+### Cancel Flow A/B Tests
+
+Test one variable at a time:
+
+| Test | Hypothesis | Metric |
+|------|-----------|--------|
+| Discount % (20% vs 30%) | Higher discount saves more | Save rate, LTV impact |
+| Pause duration (1 vs 3 months) | Longer pause increases return rate | Reactivation rate |
+| Survey placement (before vs after offer) | Survey-first personalizes offers | Save rate |
+| Offer presentation (modal vs full page) | Full page gets more attention | Save rate |
+| Copy tone (empathetic vs direct) | Empathetic reduces friction | Save rate |
+
+**How to run cancel flow experiments:** Use the **ab-testing** skill to design statistically rigorous tests. PostHog is a good fit for cancel flow experiments — its feature flags can split users into different flows server-side, and its funnel analytics track each step of the cancel flow (survey → offer → accept/decline → confirm). See the [PostHog integration guide](../../tools/integrations/posthog.md) for setup.
+
+---
+
+## Common Mistakes
+
+- **No cancel flow at all** — Instant cancel leaves money on the table. Even a simple survey + one offer saves 10-15%
+- **Making cancellation hard to find** — Hidden cancel buttons breed resentment and bad reviews. Many jurisdictions require easy cancellation (FTC Click-to-Cancel rule)
+- **Same offer for every reason** — A blanket discount doesn't address "missing feature" or "not using it"
+- **Discounts too deep** — 50%+ discounts train customers to cancel-and-return for deals
+- **Ignoring involuntary churn** — Often 30-50% of total churn and the easiest to fix
+- **No dunning emails** — Letting payment failures silently cancel accounts
+- **Guilt-trip copy** — "Are you sure you want to abandon us?" damages brand trust
+- **Not tracking save offer LTV** — A "saved" customer who churns 30 days later wasn't really saved
+- **Pausing too long** — Pauses beyond 3 months rarely reactivate. Set limits.
+- **No post-cancel path** — Make reactivation easy and trigger win-back emails, because some churned users will want to come back
+
+---
+
+## Tool Integrations
+
+For implementation, see the [tools registry](../../tools/REGISTRY.md).
+
+### Retention Platforms
+
+| Tool | Best For | Key Feature |
+|------|----------|-------------|
+| **Churnkey** | Full cancel flow + dunning | AI-powered adaptive offers, 34% avg save rate |
+| **ProsperStack** | Cancel flows with analytics | Advanced rules engine, Stripe/Chargebee integration |
+| **Raaft** | Simple cancel flow builder | Easy setup, good for early-stage |
+| **Chargebee Retention** | Chargebee customers | Native integration, was Brightback |
+
+### Billing Providers (Dunning)
+
+| Provider | Smart Retries | Dunning Emails | Card Updater |
+|----------|:------------:|:--------------:|:------------:|
+| **Stripe** | Built-in (Smart Retries) | Built-in | Automatic |
+| **Chargebee** | Built-in | Built-in | Via gateway |
+| **Paddle** | Built-in | Built-in | Managed |
+| **Recurly** | Built-in | Built-in | Built-in |
+| **Braintree** | Manual config | Manual | Via gateway |
+
+### Related CLI Tools
+
+| Tool | Use For |
+|------|---------|
+| `stripe` | Subscription management, dunning config, payment retries |
+| `customer-io` | Dunning email sequences, retention campaigns |
+| `posthog` | Cancel flow A/B tests via feature flags, funnel analytics |
+| `mixpanel` / `ga4` | Usage tracking, churn signal analysis |
+| `segment` | Event routing for health scoring |
+
+---
+
+## Related Skills
+
+- **emails**: For win-back email sequences after cancellation
+- **paywalls**: For in-app upgrade moments and trial expiration
+- **pricing**: For plan structure and annual discount strategy
+- **onboarding**: For activation to prevent early churn
+- **analytics**: For setting up churn signal events
+- **ab-testing**: For testing cancel flow variations with statistical rigor

skills/churn-prevention/evals/evals.json

@@ -0,0 +1,93 @@
+{
+  "skill_name": "churn-prevention",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Our SaaS product has a 7% monthly churn rate and we need to bring it down. We're a $49/month project management tool with about 2,000 paying customers. Can you help us design a churn prevention strategy?",
+      "expected_output": "Should check for product-marketing-context.md first. Should address both voluntary and involuntary churn. Should design a cancel flow following the framework: trigger → exit survey → dynamic save offer → confirmation → post-cancel nurture. Should include the 7 exit survey categories and recommend dynamic save offers mapped to each cancellation reason. Should address dunning for involuntary churn (pre-dunning, smart retry, email sequence, grace period). Should recommend a health score model. Should provide prioritized implementation plan.",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Addresses both voluntary and involuntary churn",
+        "Designs cancel flow with proper stages",
+        "Includes exit survey with multiple categories",
+        "Maps save offers to cancellation reasons",
+        "Addresses dunning stack for payment recovery",
+        "Recommends health score model",
+        "Provides prioritized implementation plan"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "We keep losing customers because their credit cards expire. About 15% of our churn is from failed payments. How do we fix this?",
+      "expected_output": "Should identify this as involuntary churn / payment recovery. Should apply the dunning stack framework: pre-dunning (card expiration reminders before failure), smart retry (retry logic based on failure reason), dunning email sequence (escalating urgency), grace period, and eventual cancellation. Should provide specific timing for each stage. Should recommend payment recovery tools and strategies (card updater services, backup payment methods). Should include recovery rate benchmarks.",
+      "assertions": [
+        "Identifies as involuntary churn / payment recovery",
+        "Applies dunning stack framework",
+        "Includes pre-dunning card expiration reminders",
+        "Includes smart retry logic",
+        "Provides dunning email sequence with escalating urgency",
+        "Recommends grace period before cancellation",
+        "Mentions card updater services or backup payment methods",
+        "Includes recovery benchmarks"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "what should we show users when they click the cancel button? right now they just go straight to cancellation with no attempt to save them",
+      "expected_output": "Should trigger on casual phrasing. Should design the cancel flow: cancel button → exit survey → dynamic save offer → confirmation → post-cancel. Should detail the exit survey categories (too expensive, missing feature, switched to competitor, not using enough, technical issues, bad support, other). Should provide dynamic save offers matched to each reason (e.g., too expensive → discount offer, missing feature → roadmap update, not using enough → onboarding help). Should include copy recommendations for each screen. Should warn against dark patterns (making it impossible to cancel).",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Designs multi-step cancel flow",
+        "Includes exit survey with 7 categories",
+        "Provides dynamic save offers mapped to reasons",
+        "Includes copy recommendations",
+        "Warns against dark patterns",
+        "Includes confirmation and post-cancel steps"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "How do we identify which customers are at risk of churning before they actually cancel? We want to be proactive.",
+      "expected_output": "Should apply the health score model framework. Should define health score components: product usage signals (login frequency, feature adoption, key action completion), engagement signals (support tickets, NPS responses, email engagement), and account signals (contract type, company growth, stakeholder changes). Should recommend scoring methodology (0-100 scale). Should define risk tiers and recommended interventions for each tier. Should suggest data sources and implementation approach.",
+      "assertions": [
+        "Applies health score model framework",
+        "Defines usage-based health signals",
+        "Defines engagement-based health signals",
+        "Defines account-based health signals",
+        "Recommends scoring methodology",
+        "Defines risk tiers with interventions",
+        "Suggests data sources and implementation"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "Our exit survey shows that 40% of cancellations say 'too expensive' as the reason. What save offers should we try?",
+      "expected_output": "Should reference the dynamic save offers mapped to the 'too expensive' reason. Should suggest multiple offer types: temporary discount, downgrade to cheaper plan, annual billing discount, pause instead of cancel, extended trial of current plan. Should recommend testing different offers to find what works best. Should also dig deeper — 'too expensive' often masks other issues (not seeing value, not using enough features). Should suggest follow-up questions in the exit survey to get more specific.",
+      "assertions": [
+        "References save offers for 'too expensive' reason",
+        "Suggests multiple offer types (discount, downgrade, pause)",
+        "Recommends testing different offers",
+        "Notes that 'too expensive' often masks other issues",
+        "Suggests deeper follow-up questions",
+        "Provides specific save offer copy or structure"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "We want to set up a win-back email sequence for customers who already cancelled. Can you help write those emails?",
+      "expected_output": "Should recognize this overlaps with email sequence work. Should defer to or cross-reference the email-sequence skill for writing the actual email sequence. May provide churn-specific context (timing post-cancel, re-engagement hooks, win-back offer strategy) but should make clear that email-sequence is the right skill for designing and writing the full email sequence.",
+      "assertions": [
+        "Recognizes overlap with email sequence work",
+        "References or defers to email-sequence skill",
+        "May provide churn-specific context for the sequence",
+        "Does not attempt to write a full email sequence"
+      ],
+      "files": []
+    }
+  ]
+}

skills/churn-prevention/references/cancel-flow-patterns.md

@@ -0,0 +1,316 @@
+# Cancel Flow Patterns
+
+Detailed cancel flow patterns by business type, billing provider, and industry.
+
+---
+
+## Cancel Flow by Business Type
+
+### B2C / Self-Serve SaaS
+
+High volume, low touch. The flow must work without human intervention.
+
+**Flow structure:**
+```
+Cancel button → Exit survey (1 question) → Dynamic offer → Confirm → Post-cancel
+```
+
+**Characteristics:**
+- Fully automated, no human in the loop
+- Quick — 2-3 screens maximum
+- One offer + one fallback, not a menu of options
+- Mobile-optimized (significant cancellations on mobile)
+- Clear "continue cancelling" at every step
+
+**Typical save rate:** 20-30%
+
+**Example flow for a $29/mo productivity app:**
+1. "What's the main reason?" → 6 options
+2. Selected "Too expensive" → "Get 25% off for 3 months (save $21.75)"
+3. Declined → "Or switch to our Starter plan at $12/mo"
+4. Declined → "We're sorry to see you go. Your access continues until [date]."
+
+---
+
+### B2B / Team Plans
+
+Lower volume, higher stakes. Personal outreach is worth the cost.
+
+**Flow structure:**
+```
+Cancel button → Exit survey → Offer (or route to CS) → Confirm → Post-cancel
+```
+
+**Characteristics:**
+- Route accounts above MRR threshold to customer success
+- Show team impact ("Your 8 team members will lose access")
+- Offer admin-to-admin call for enterprise accounts
+- Longer consideration — allow "schedule a call" as a save option
+- Require admin/owner role to cancel (not any team member)
+
+**Typical save rate:** 30-45% (higher because of personal touch)
+
+**MRR-based routing:**
+
+| Account MRR | Cancel Flow |
+|-------------|-------------|
+| <$100/mo | Automated flow with offers |
+| $100-$500/mo | Automated + flag for CS follow-up |
+| $500-$2,000/mo | Route to CS before cancel completes |
+| $2,000+/mo | Block self-serve cancel, require CS call |
+
+---
+
+### Freemium / Free-to-Paid
+
+Users cancelling paid to return to free tier. Different psychology — they're not leaving, they're downgrading.
+
+**Flow structure:**
+```
+Cancel button → "Switch to Free?" prompt → Exit survey (if still cancelling) → Offer → Confirm
+```
+
+**Characteristics:**
+- Lead with the free tier as the first option (not a save offer)
+- Show what they keep on free vs. what they lose
+- The "save" is keeping them on free, not losing them entirely
+- Track free-tier users for future re-upgrade campaigns
+
+---
+
+## Cancel Flow by Billing Interval
+
+### Monthly Subscribers
+
+- More price-sensitive, shorter commitment
+- Discount offers work well (20-30% for 2-3 months)
+- Pause is effective (1-2 months)
+- Suggest annual plan at a discount as an alternative
+
+**Offer priority:**
+1. Discount (if reason = price)
+2. Pause (if reason = not using / temporary)
+3. Annual plan switch (if engaged but price-sensitive)
+
+### Annual Subscribers
+
+- Higher commitment, often cancelling for stronger reasons
+- Prorate refund expectations matter
+- Longer save window (they've already paid)
+- Personal outreach more justified (higher LTV at stake)
+
+**Offer priority:**
+1. Pause remainder of term (if temporary)
+2. Plan adjustment + credit for next renewal
+3. Personal outreach from CS
+4. Partial refund + downgrade (better than full refund + cancel)
+
+**Refund handling:**
+- Offer prorated refund if significant time remaining
+- "Pause until renewal" if less than 3 months left
+- Be generous — bad refund experiences create vocal detractors
+
+---
+
+## Save Offer Patterns
+
+### The Discount Ladder
+
+Don't lead with your biggest discount. Escalate:
+
+```
+Cancel click → 15% off → Still cancelling → 25% off → Still cancelling → Let them go
+```
+
+**Rules:**
+- Maximum 2 discount offers per cancel session
+- Never exceed 30% (higher trains cancel-for-discount behavior)
+- Time-limit discounts (2-3 months, then full price resumes)
+- Track discount accepters — if they cancel again at full price, don't re-offer
+
+### The Pause Playbook
+
+Pause is often better than a discount because it doesn't devalue your product.
+
+**Implementation:**
+
+| Setting | Recommendation |
+|---------|---------------|
+| Pause duration options | 1 month, 2 months, 3 months |
+| Default selection | 1 month (shortest) |
+| Maximum pause | 3 months (longer pauses rarely return) |
+| During pause | Keep data, remove access |
+| Reactivation | Auto-reactivate with 7-day advance email |
+| Repeat pauses | Allow 1 pause per 12-month period |
+
+**Pause reactivation sequence:**
+- Day -7: "Your pause ends in 7 days. We've been busy — here's what's new."
+- Day -1: "Welcome back tomorrow! Here's what's waiting for you."
+- Day 0: "You're back! Here's a quick tour of what's new."
+
+### The Downgrade Path
+
+For multi-plan products, downgrade is the strongest save:
+
+```
+┌─────────────────────────────────────────┐
+│  Before you go, what about right-sizing │
+│  your plan?                             │
+│                                         │
+│  Current: Pro ($49/mo)                  │
+│                                         │
+│  ┌─────────────────────────────────┐    │
+│  │ Switch to Starter ($19/mo)      │    │
+│  │                                 │    │
+│  │ ✓ Keep: Projects, integrations  │    │
+│  │ ✗ Lose: Advanced analytics,     │    │
+│  │         team features           │    │
+│  │                                 │    │
+│  │ [Switch to Starter]             │    │
+│  └─────────────────────────────────┘    │
+│                                         │
+│  [No thanks, continue cancelling]       │
+└─────────────────────────────────────────┘
+```
+
+**Downgrade best practices:**
+- Show exactly what they keep and what they lose
+- Use checkmarks and X marks for scanability
+- Preserve their data even on the lower plan
+- If they downgrade, don't show upgrade prompts for at least 30 days
+
+### The Competitor Switch Handler
+
+When the cancel reason is "switching to competitor":
+
+1. **Ask which competitor** (optional, don't force it)
+2. **Show a comparison** if you have one (see competitors skill)
+3. **Offer a migration credit** ("We'll match their price for 3 months")
+4. **Request a feedback call** ("15 minutes to understand what we're missing")
+
+This data is gold for product and marketing teams.
+
+---
+
+## Post-Cancel Experience
+
+What happens after cancel matters for:
+- Win-back potential
+- Word of mouth
+- Review sentiment
+
+### Confirmation Page
+
+```
+Your subscription has been cancelled.
+
+What happens next:
+• Your access continues until [billing period end date]
+• Your data will be preserved for 90 days
+• You can reactivate anytime from your account settings
+
+[Reactivate My Account]
+
+We'd love to have you back. We'll keep improving based on feedback
+from customers like you.
+```
+
+### Post-Cancel Sequence
+
+| Timing | Action |
+|--------|--------|
+| Immediately | Confirmation email with access end date |
+| Day 1 | (Nothing — don't be desperate) |
+| Day 7 | NPS/satisfaction survey about overall experience |
+| Day 30 | "What's new" email with recent improvements |
+| Day 60 | Address their specific cancel reason if resolved |
+| Day 90 | Final win-back with special offer |
+
+**For detailed win-back email sequences**: See the emails skill.
+
+---
+
+## Segmentation Rules
+
+The most effective cancel flows use segmentation to show different offers to different customers.
+
+### Segmentation Dimensions
+
+| Dimension | Why It Matters |
+|-----------|---------------|
+| Plan / MRR | Higher-value customers get personal outreach |
+| Tenure | Long-term customers get more generous offers |
+| Usage level | High-usage customers get different messaging than dormant ones |
+| Billing interval | Monthly vs. annual need different approaches |
+| Previous saves | Don't re-offer the same discount to a repeat canceller |
+| Cancel reason | Drives which offer to show (core mapping) |
+
+### Segment-Specific Flows
+
+**New customer (< 30 days):**
+- They haven't activated. The save is onboarding, not discounts.
+- Offer: Free onboarding call, setup help, extended trial
+- Ask: "What were you hoping to accomplish?" (learn what's missing)
+
+**Engaged customer cancelling on price:**
+- They love the product but can't justify the cost.
+- Offer: Discount, annual plan switch, downgrade
+- High save potential
+
+**Dormant customer (no login 30+ days):**
+- They forgot about you. A discount won't bring them back.
+- Offer: Pause subscription, "what changed?" conversation
+- Low save potential — focus on learning why
+
+**Power user switching to competitor:**
+- They're actively choosing something else.
+- Offer: Competitive match, feedback call, roadmap preview
+- Medium save potential — depends on reason
+
+---
+
+## Implementation Checklist
+
+### Phase 1: Foundation (Week 1)
+- [ ] Add cancel flow (survey + 1 offer + confirmation)
+- [ ] Set up exit survey with 5-7 reason categories
+- [ ] Map one offer per reason (simple 1:1 mapping)
+- [ ] Track cancel reasons and save rate in analytics
+- [ ] Enable pre-dunning card expiry emails
+
+### Phase 2: Optimization (Weeks 2-4)
+- [ ] Add fallback offers (primary + secondary per reason)
+- [ ] Implement pause subscription option
+- [ ] Set up dunning email sequence (4 emails over 10 days)
+- [ ] Enable smart retries (Stripe Smart Retries or equivalent)
+- [ ] Add MRR-based routing for high-value accounts
+
+### Phase 3: Advanced (Month 2+)
+- [ ] Build health score from usage signals
+- [ ] Set up proactive intervention triggers
+- [ ] A/B test discount amounts and offer types
+- [ ] Segment flows by plan, tenure, and usage
+- [ ] Post-cancel win-back sequence (coordinate with emails skill)
+- [ ] Cohort analysis: churn by channel, plan, tenure
+
+---
+
+## Compliance Notes
+
+### FTC Click-to-Cancel Rule (US)
+- Cancellation must be as easy as signup
+- Cannot require a phone call to cancel if signup was online
+- Cannot add excessive steps to discourage cancellation
+- Save offers are allowed but "continue cancelling" must be clear
+
+### GDPR / Data Retention (EU)
+- Inform users about data retention period post-cancel
+- Offer data export before account deletion
+- Honor deletion requests within 30 days
+- Don't use post-cancel data for marketing without consent
+
+### General Best Practices
+- Always show a clear path to complete cancellation
+- Never hide the cancel button (dark pattern)
+- Process cancellation even if save flow has errors
+- Confirm cancellation with email receipt

skills/churn-prevention/references/dunning-playbook.md

@@ -0,0 +1,408 @@
+# Dunning Playbook
+
+Complete guide to recovering failed payments and reducing involuntary churn.
+
+---
+
+## Why Dunning Matters
+
+- Failed payments cause 30-50% of all subscription churn
+- Most failed payments are recoverable with the right strategy
+- Subscription businesses lose an estimated $129 billion annually to involuntary churn
+- Effective dunning recovers 50-60% of failed payments
+
+---
+
+## The Dunning Timeline
+
+```
+Day -30 to -7: Pre-dunning (prevent failures)
+Day 0:         Payment fails → Smart retry #1 + Email #1
+Day 1-3:       Smart retry #2 + Email #2
+Day 3-5:       Smart retry #3
+Day 5-7:       Smart retry #4 + Email #3
+Day 7-10:      Final retry + Email #4 (final warning)
+Day 10-14:     Grace period ends → Account paused/cancelled
+Day 14+:       Win-back sequence begins
+```
+
+---
+
+## Pre-Dunning: Prevent Failures Before They Happen
+
+### Card Expiry Management
+
+| Timing | Action |
+|--------|--------|
+| 30 days before expiry | Email: "Your card ending in 4242 expires next month" |
+| 15 days before expiry | Email: "Update your payment method to avoid interruption" |
+| 7 days before expiry | Email: "Your card expires in 7 days — update now" |
+| 3 days before expiry | In-app banner: "Payment method expiring soon" |
+
+**Email template — Card expiring:**
+```
+Subject: Your card ending in 4242 expires soon
+
+Hi [Name],
+
+The card on file for your [Product] subscription expires on [date].
+
+Update your payment method now to avoid any interruption:
+
+[Update Payment Method →]
+
+This takes less than 30 seconds.
+
+— [Product] Team
+```
+
+### Card Updater Services
+
+Major card networks offer automatic card update programs:
+
+| Service | Network | What It Does |
+|---------|---------|--------------|
+| Visa Account Updater (VAU) | Visa | Auto-updates stored card numbers and expiry dates |
+| Mastercard Automatic Billing Updater (ABU) | Mastercard | Same for Mastercard |
+| Amex Cardrefresher | American Express | Same for Amex |
+
+**Impact:** Reduces hard declines from expired/replaced cards by 30-50%.
+
+**How to enable:**
+- **Stripe**: Automatic — enabled by default
+- **Chargebee**: Enabled through gateway settings
+- **Recurly**: Built-in, enabled by default
+- **Braintree**: Contact processor to enable
+
+### Backup Payment Methods
+
+Prompt for a second payment method:
+- During signup: "Add a backup payment method" (low conversion)
+- After first successful payment: "Protect your account with a backup card" (better timing)
+- After a failed payment is recovered: "Add a backup to prevent future interruptions" (best timing — they felt the pain)
+
+### Pre-Billing Notifications
+
+For annual plans or high-value subscriptions:
+- Email 7 days before renewal with amount and date
+- Include link to update payment method
+- Show what's included in the renewal
+- Required by some regulations for auto-renewals
+
+---
+
+## Smart Retry Strategy
+
+### Decline Type Classification
+
+| Code | Type | Meaning | Retry? |
+|------|------|---------|--------|
+| `insufficient_funds` | Soft | Temporarily low balance | Yes — retry in 2-3 days |
+| `card_declined` (generic) | Soft | Various temporary reasons | Yes — retry 3-4 times |
+| `processing_error` | Soft | Gateway/network issue | Yes — retry within 24h |
+| `expired_card` | Hard | Card is expired | No — request new card |
+| `stolen_card` | Hard | Card reported stolen | No — request new card |
+| `do_not_honor` | Soft/Hard | Bank refused (ambiguous) | Try once more, then ask for new card |
+| `authentication_required` | Auth | SCA/3DS needed | Send customer to authenticate |
+
+### Retry Schedule by Provider
+
+**Stripe (Smart Retries — recommended):**
+- Enable "Smart Retries" in Stripe Dashboard → Billing → Settings
+- Stripe's ML model picks optimal retry timing based on billions of transactions
+- Typically 4-8 retry attempts over 3-4 weeks
+- Recovers ~15% more than fixed-schedule retries
+
+**Manual retry schedule (if no smart retries):**
+
+| Retry | Timing | Best Day/Time |
+|-------|--------|--------------|
+| 1 | Day 1 (24h after failure) | Morning, same day of week as original |
+| 2 | Day 3 | Try a different time of day |
+| 3 | Day 5 | After typical payday (1st, 15th) |
+| 4 | Day 7 | Morning of the next business day |
+| 5 (final) | Day 10 | Last attempt before grace period ends |
+
+**Retry timing insights:**
+- Retry on the same day of month the original payment succeeded
+- Retry after common paydays (1st and 15th of the month)
+- Avoid retrying on weekends (lower approval rates)
+- Morning retries (8-10am local time) perform slightly better
+
+---
+
+## Dunning Email Sequence
+
+### Email 1: Payment Failed (Day 0)
+
+**Tone:** Friendly, matter-of-fact. No alarm.
+
+```
+Subject: Action needed — your payment didn't go through
+
+Hi [Name],
+
+We tried to charge your [card type] ending in [last 4] for your
+[Product] subscription ($[amount]), but it didn't go through.
+
+This happens sometimes — usually a quick card update fixes it.
+
+[Update Payment Method →]
+
+Your access isn't affected yet. We'll retry automatically, but
+updating your card is the fastest fix.
+
+Need help? Just reply to this email.
+
+— [Product] Team
+```
+
+### Email 2: Reminder (Day 3)
+
+**Tone:** Helpful, slightly more urgent.
+
+```
+Subject: Quick reminder — update your payment for [Product]
+
+Hi [Name],
+
+Just a heads-up — we still haven't been able to process your
+$[amount] payment for [Product].
+
+[Update Payment Method →]
+
+Takes less than 30 seconds. Your [data/projects/team access]
+is safe, but we'll need a valid payment method to keep your
+account active.
+
+Questions? Reply here and we'll help.
+
+— [Product] Team
+```
+
+### Email 3: Urgency (Day 7)
+
+**Tone:** Direct, clear consequences.
+
+```
+Subject: Your [Product] account will be paused in 3 days
+
+Hi [Name],
+
+We've tried to process your payment several times, but your
+[card type] ending in [last 4] keeps getting declined.
+
+If we don't receive payment by [date], your account will be
+paused and you'll lose access to:
+
+• [Key feature/data they use]
+• [Their projects/workspace]
+• [Team access for X members]
+
+[Update Payment Method Now →]
+
+Your data won't be deleted — you can reactivate anytime by
+updating your payment method.
+
+— [Product] Team
+```
+
+### Email 4: Final Warning (Day 10)
+
+**Tone:** Final, clear, no guilt.
+
+```
+Subject: Last chance to keep your [Product] account active
+
+Hi [Name],
+
+This is our last reminder. Your payment of $[amount] is past
+due, and your account will be paused tomorrow ([date]).
+
+[Update Payment Method →]
+
+After pausing:
+• Your data is saved for [90 days]
+• You can reactivate anytime
+• Just update your card to restore access
+
+If you intended to cancel, no action needed — your account
+will be paused automatically.
+
+— [Product] Team
+```
+
+---
+
+## Grace Period Management
+
+### What Happens During Grace Period
+
+| Setting | Recommendation |
+|---------|---------------|
+| Duration | 7-14 days after final retry |
+| Access | Degraded (read-only) or full access |
+| Visibility | In-app banner: "Payment past due — update to continue" |
+| Retry | Continue background retries during grace |
+| Communication | Dunning emails continue |
+
+### Access Degradation Options
+
+**Option A: Full access during grace (recommended for B2B)**
+- Lower friction, customer feels respected
+- Higher recovery rate (they still see value)
+- Risk: some customers exploit the grace period
+
+**Option B: Read-only access (recommended for B2C)**
+- Can view but not create/edit
+- Creates urgency without data loss fear
+- Clear message: "Update payment to resume full access"
+
+**Option C: Immediate lockout (not recommended)**
+- Aggressive, damages relationship
+- Lower recovery rate
+- Only appropriate for very low-cost plans
+
+### Post-Grace Period
+
+| Timing | Action |
+|--------|--------|
+| Grace period ends | Pause account (not delete) |
+| Day 1 post-pause | "Your account has been paused" email |
+| Day 7 post-pause | "Your data is still here" reminder |
+| Day 30 post-pause | Win-back attempt with new offer |
+| Day 60 post-pause | Final win-back |
+| Day 90 post-pause | Data deletion warning (if applicable) |
+
+---
+
+## Provider-Specific Setup
+
+### Stripe
+
+**Enable Smart Retries:**
+1. Dashboard → Settings → Billing → Subscriptions and emails
+2. Enable "Smart Retries" under retry rules
+3. Set failed payment emails in Dashboard → Settings → Emails
+
+**Custom retry rules (if not using Smart Retries):**
+```
+Retry 1: 3 days after failure
+Retry 2: 5 days after failure
+Retry 3: 7 days after failure
+Final:   Mark subscription as unpaid after last retry
+```
+
+**Webhook events to handle:**
+- `invoice.payment_failed` — trigger dunning
+- `invoice.paid` — cancel dunning, restore access
+- `customer.subscription.updated` — status changes
+- `customer.subscription.deleted` — final cancellation
+
+### Chargebee
+
+**Built-in dunning:**
+1. Settings → Configure Chargebee → Retry Settings
+2. Configure retry attempts and intervals
+3. Settings → Configure Chargebee → Email Notifications → Dunning
+
+**Dunning options:**
+- Automatic retries with configurable schedule
+- Built-in dunning emails (customizable templates)
+- Grace period configuration per plan
+
+### Paddle
+
+**Managed dunning:**
+- Paddle handles retries and dunning automatically
+- Limited customization (Paddle manages the relationship)
+- Webhook: `subscription.payment_failed`, `subscription.cancelled`
+- Best for hands-off approach
+
+### Recurly
+
+**Revenue Recovery:**
+1. Configuration → Dunning Management
+2. Set retry schedule per plan
+3. Configure grace period and final action (pause vs cancel)
+
+**Advanced features:**
+- Machine-learning retry optimization
+- Per-plan dunning schedules
+- Built-in Account Updater
+
+---
+
+## In-App Dunning
+
+Don't rely on email alone. Show payment failures in the app:
+
+### Banner Pattern
+```
+┌──────────────────────────────────────────────────────┐
+│ ⚠ Your payment of $29 failed. Update your card to    │
+│ avoid losing access. [Update Payment →]  [Dismiss]   │
+└──────────────────────────────────────────────────────┘
+```
+
+**Rules:**
+- Show on every page load during dunning period
+- Allow dismiss (but show again next session)
+- Direct link to payment update (fewest clicks possible)
+- Don't block the product — let them continue using it
+
+### Modal Pattern (for final warning)
+```
+┌─────────────────────────────────────┐
+│                                     │
+│  Your account will be paused        │
+│  on [date]                          │
+│                                     │
+│  Update your payment method to      │
+│  keep access to your [X] projects   │
+│  and [Y] team members.              │
+│                                     │
+│  [Update Payment Method]            │
+│  [Remind Me Later]                  │
+│                                     │
+└─────────────────────────────────────┘
+```
+
+---
+
+## Measuring Dunning Performance
+
+### Key Metrics
+
+| Metric | How to Calculate | Target |
+|--------|-----------------|--------|
+| Recovery rate | Recovered payments / Total failed | 50-60% |
+| Recovery rate by decline type | Recovered / Failed per type | Soft: 70%+, Hard: 40%+ |
+| Time to recovery | Days from failure to successful payment | <5 days |
+| Pre-dunning prevention rate | Prevented failures / Expected failures | 20-30% |
+| Dunning email open rate | Opens / Sent per email | 60%+ |
+| Dunning email click rate | Clicks / Opens per email | 30%+ |
+| Revenue recovered (monthly) | Sum of recovered payment amounts | Track trend |
+| Revenue lost to involuntary churn | Sum of failed + unrecovered amounts | Track trend |
+
+### Benchmarking
+
+**By company stage:**
+
+| Stage | Typical Involuntary Churn | Target After Optimization |
+|-------|--------------------------|--------------------------|
+| Early (< $1M ARR) | 3-5% of MRR/month | 1-2% |
+| Growth ($1-10M ARR) | 2-4% of MRR/month | 0.5-1.5% |
+| Scale ($10M+ ARR) | 1-3% of MRR/month | 0.3-0.8% |
+
+### ROI Calculation
+
+```
+Monthly failed payment MRR:        $10,000
+Current recovery rate:              30% ($3,000 recovered)
+Target recovery rate:               60% ($6,000 recovered)
+Monthly improvement:                $3,000/month
+Annual improvement:                 $36,000/year
+Cost of dunning optimization:       ~$200-500/month (tooling)
+ROI:                                6-15x
+```

skills/cold-email/SKILL.md

@@ -0,0 +1,158 @@
+---
+name: cold-email
+description: Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions "cold outreach," "prospecting email," "outbound email," "email to leads," "reach out to prospects," "sales email," "follow-up email sequence," "nobody's replying to my emails," or "how do I write a cold email." Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences. For warm/lifecycle email sequences, see emails. For sales collateral beyond emails, see sales-enablement.
+metadata:
+  version: 1.1.0
+---
+
+# Cold Email Writing
+
+You are an expert cold email writer. Your goal is to write emails that sound like they came from a sharp, thoughtful human — not a sales machine following a template.
+
+## Before Writing
+
+**Check for product marketing context first:**
+If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
+
+Understand the situation (ask if not provided):
+
+1. **Who are you writing to?** — Role, company, why them specifically
+2. **What do you want?** — The outcome (meeting, reply, intro, demo)
+3. **What's the value?** — The specific problem you solve for people like them
+4. **What's your proof?** — A result, case study, or credibility signal
+5. **Any research signals?** — Funding, hiring, LinkedIn posts, company news, tech stack changes
+
+Work with whatever the user gives you. If they have a strong signal and a clear value prop, that's enough to write. Don't block on missing inputs — use what you have and note what would make it stronger.
+
+---
+
+## Writing Principles
+
+### Write like a peer, not a vendor
+
+The email should read like it came from someone who understands their world — not someone trying to sell them something. Use contractions. Read it aloud. If it sounds like marketing copy, rewrite it.
+
+### Every sentence must earn its place
+
+Cold email is ruthlessly short. If a sentence doesn't move the reader toward replying, cut it. The best cold emails feel like they could have been shorter, not longer.
+
+### Personalization must connect to the problem
+
+If you remove the personalized opening and the email still makes sense, the personalization isn't working. The observation should naturally lead into why you're reaching out.
+
+See [personalization.md](references/personalization.md) for the 4-level system and research signals.
+
+### Lead with their world, not yours
+
+The reader should see their own situation reflected back. "You/your" should dominate over "I/we." Don't open with who you are or what your company does.
+
+### One ask, low friction
+
+Interest-based CTAs ("Worth exploring?" / "Would this be useful?") beat meeting requests. One CTA per email. Make it easy to say yes with a one-line reply.
+
+---
+
+## Voice & Tone
+
+**The target voice:** A smart colleague who noticed something relevant and is sharing it. Conversational but not sloppy. Confident but not pushy.
+
+**Calibrate to the audience:**
+
+- C-suite: ultra-brief, peer-level, understated
+- Mid-level: more specific value, slightly more detail
+- Technical: precise, no fluff, respect their intelligence
+
+**What it should NOT sound like:**
+
+- A template with fields swapped in
+- A pitch deck compressed into paragraph form
+- A LinkedIn DM from someone you've never met
+- An AI-generated email (avoid the telltale patterns: "I hope this email finds you well," "I came across your profile," "leverage," "synergy," "best-in-class")
+
+---
+
+## Structure
+
+There's no single right structure. Choose a framework that fits the situation, or write freeform if the email flows naturally without one.
+
+**Common shapes that work:**
+
+- **Observation → Problem → Proof → Ask** — You noticed X, which usually means Y challenge. We helped Z with that. Interested?
+- **Question → Value → Ask** — Struggling with X? We do Y. Company Z saw [result]. Worth a look?
+- **Trigger → Insight → Ask** — Congrats on X. That usually creates Y challenge. We've helped similar companies with that. Curious?
+- **Story → Bridge → Ask** — [Similar company] had [problem]. They [solved it this way]. Relevant to you?
+
+For the full catalog of frameworks with examples, see [frameworks.md](references/frameworks.md).
+
+---
+
+## Subject Lines
+
+Short, boring, internal-looking. The subject line's only job is to get the email opened — not to sell.
+
+- 2-4 words, lowercase, no punctuation tricks
+- Should look like it came from a colleague ("reply rates," "hiring ops," "Q2 forecast")
+- No product pitches, no urgency, no emojis, no prospect's first name
+
+See [subject-lines.md](references/subject-lines.md) for the full data.
+
+---
+
+## Follow-Up Sequences
+
+Each follow-up should add something new — a different angle, fresh proof, a useful resource. "Just checking in" gives the reader no reason to respond.
+
+- 3-5 total emails, increasing gaps between them
+- Each email should stand alone (they may not have read the previous ones)
+- The breakup email is your last touch — honor it
+
+See [follow-up-sequences.md](references/follow-up-sequences.md) for cadence, angle rotation, and breakup email templates.
+
+---
+
+## Quality Check
+
+Before presenting, gut-check:
+
+- Does it sound like a human wrote it? (Read it aloud)
+- Would YOU reply to this if you received it?
+- Does every sentence serve the reader, not the sender?
+- Is the personalization connected to the problem?
+- Is there one clear, low-friction ask?
+
+---
+
+## What to Avoid
+
+- Opening with "I hope this email finds you well" or "My name is X and I work at Y"
+- Jargon: "synergy," "leverage," "circle back," "best-in-class," "leading provider"
+- Feature dumps — one proof point beats ten features
+- HTML, images, or multiple links
+- Fake "Re:" or "Fwd:" subject lines
+- Identical templates with only {{FirstName}} swapped
+- Asking for 30-minute calls in first touch
+- "Just checking in" follow-ups
+
+---
+
+## Data & Benchmarks
+
+The references contain performance data if you need to make informed choices:
+
+- [benchmarks.md](references/benchmarks.md) — Reply rates, conversion funnels, expert methods, common mistakes
+- [personalization.md](references/personalization.md) — 4-level personalization system, research signals
+- [subject-lines.md](references/subject-lines.md) — Subject line data and optimization
+- [follow-up-sequences.md](references/follow-up-sequences.md) — Cadence, angles, breakup emails
+- [frameworks.md](references/frameworks.md) — All copywriting frameworks with examples
+
+Use this data to inform your writing — not as a checklist to satisfy.
+
+---
+
+## Related Skills
+
+- **copywriting**: For landing pages and web copy
+- **emails**: For lifecycle/nurture email sequences (not cold outreach)
+- **social**: For LinkedIn and social posts
+- **product-marketing-context**: For establishing foundational positioning
+- **revops**: For lead scoring, routing, and pipeline management

skills/cold-email/evals/evals.json

@@ -0,0 +1,94 @@
+{
+  "skill_name": "cold-email",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Write a cold email to VP of Marketing at mid-size B2B SaaS companies. We sell a content analytics platform that shows which blog posts actually drive pipeline. Our main proof point: customers see 3x increase in content-attributed revenue within 90 days.",
+      "expected_output": "Should check for product-marketing-context.md first. Should write like a peer, not a vendor. Should use one of the structure frameworks (observation→problem→proof→ask or similar). Subject line should be 2-4 words, lowercase, internal-looking. Every sentence should earn its place. Personalization should connect to the prospect's problem, not just their name. Should use the 3x revenue proof point as social proof, not a feature claim. CTA should be low-friction (not 'book a demo'). Should provide 2-3 variations. Should include a quality check against the guidelines.",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Writes like a peer, not a vendor",
+        "Uses a structure framework from the skill",
+        "Subject line is short, lowercase, internal-looking",
+        "Every sentence earns its place (concise)",
+        "Personalization connects to prospect's problem",
+        "Uses proof point as social proof",
+        "CTA is low-friction",
+        "Provides 2-3 variations"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "Help me write a cold email to CTOs at enterprise companies. I sell cybersecurity training. My current email has a 2% open rate and 0% reply rate.",
+      "expected_output": "Should diagnose the current email's likely problems based on 2% open rate (subject line issue) and 0% reply rate (body/relevance issue). Should apply voice calibration for CTO audience (respect their time, technical credibility, executive-level language). Should provide a completely new email following structure frameworks. Subject line should be 2-4 words, look internal. Should adapt tone for enterprise CTOs — more formal than startup audience but still peer-like. Should provide the email plus analysis of why each element works.",
+      "assertions": [
+        "Diagnoses problems from the performance data",
+        "Identifies subject line as likely open rate issue",
+        "Applies voice calibration for CTO audience",
+        "Subject line is short, lowercase, internal-looking",
+        "Adapts tone for enterprise audience",
+        "Uses structure framework from the skill",
+        "Explains why each element works"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "write me a follow-up sequence. prospect didn't reply to my first email about our HR software. how many should I send and how far apart?",
+      "expected_output": "Should trigger on casual phrasing. Should apply the follow-up sequence guidance: 3-5 follow-ups recommended. Each follow-up should add something new (new angle, new proof point, new value) — not just 'bumping' or 'checking in.' Should provide timing recommendations between emails. Should provide actual follow-up email copy for each touch, with different angles. Should include a breakup email at the end. Should note that each follow-up should be shorter than the previous.",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Recommends 3-5 follow-up emails",
+        "Each follow-up adds something new",
+        "Does not use 'just bumping' or 'checking in' language",
+        "Provides timing between emails",
+        "Provides actual copy for each follow-up",
+        "Includes a breakup email",
+        "Follow-ups get progressively shorter"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "Review this cold email and tell me what's wrong: 'Dear Sir/Madam, I hope this email finds you well. I wanted to reach out to introduce our innovative cloud-based platform that leverages AI to streamline your business operations. We have helped over 500 companies transform their workflows. I would love to schedule a 30-minute call to discuss how we can help your organization. Best regards, John'",
+      "expected_output": "Should apply the quality check framework. Should identify multiple problems: 'Dear Sir/Madam' (no personalization), 'I hope this email finds you well' (filler), 'innovative cloud-based platform' (jargon/buzzwords), 'leverages AI to streamline' (vague vendor language), 'transform their workflows' (means nothing), '30-minute call' (too much ask for cold email), entire email is about the sender not the prospect. Should rewrite following the principles: peer tone, observation→problem→proof→ask structure, every sentence earns its place, personalization connected to their problem, low-friction CTA.",
+      "assertions": [
+        "Identifies lack of personalization",
+        "Identifies filler phrases",
+        "Identifies jargon and buzzwords",
+        "Identifies vendor language vs peer language",
+        "Identifies CTA as too high-friction",
+        "Notes email is sender-focused not prospect-focused",
+        "Provides a rewritten version",
+        "Rewrite follows cold email principles"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "What are the best subject lines for cold emails? I want to maximize open rates.",
+      "expected_output": "Should apply the subject line guidelines: short (2-4 words), lowercase or sentence case, internal-looking (should look like it came from a colleague, not a vendor). Should provide examples following these principles. Should explain why these work (bypass promotional filters, trigger curiosity, don't look like marketing). Should warn against common bad subject lines (ALL CAPS, emojis, clickbait, long subjects). Should note that subject line gets them to open but body gets them to reply.",
+      "assertions": [
+        "Applies subject line guidelines (2-4 words, lowercase, internal-looking)",
+        "Provides specific examples",
+        "Explains why the format works",
+        "Warns against common bad subject line patterns",
+        "Notes distinction between open rate and reply rate"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "Can you help me set up an automated email drip campaign for leads who download our whitepaper?",
+      "expected_output": "Should recognize this is a lifecycle/nurture email sequence, not cold outreach. Should defer to or cross-reference the email-sequence skill, which handles drip campaigns, lead nurture sequences, and lifecycle emails. Cold email is specifically for unsolicited outbound outreach to prospects who haven't opted in. Should make this distinction clear.",
+      "assertions": [
+        "Recognizes this as lifecycle/nurture email, not cold outreach",
+        "References or defers to email-sequence skill",
+        "Explains the distinction between cold email and lifecycle email",
+        "Does not attempt to design a nurture sequence using cold email patterns"
+      ],
+      "files": []
+    }
+  ]
+}

skills/cold-email/references/benchmarks.md

@@ -0,0 +1,83 @@
+# Benchmarks, Data & Expert Methods
+
+## Core Performance Metrics (2024–2025)
+
+| Metric                     | Average | Good   | Excellent | Source                   |
+| -------------------------- | ------- | ------ | --------- | ------------------------ |
+| Open rate                  | 27.7%   | 40–45% | 50%+      | Belkins, Snov.io         |
+| Reply rate                 | 4–5.8%  | 5–10%  | 10–15%    | Belkins, Reachoutly      |
+| Reply rate (best-in-class) | —       | —      | 15–25%+   | Digital Bloom, Instantly |
+| Positive reply %           | ~48%    | 55–60% | 62–65%    | Digital Bloom            |
+| Meeting booking rate       | 0.5–1%  | 1–2%   | 2.3%+     | Reachoutly               |
+| Bounce rate                | 7.5%    | <4%    | <2%       | Belkins                  |
+
+## Realistic Funnel Model
+
+500 emails → 100 opens (20%) → 25 replies (5%) → 8 positive replies (30%) → 4 meetings (50%) → 1 client (25% close). ~**0.2% end-to-end conversion** for average performers.
+
+## Performance Levers (ranked by impact)
+
+1. **Hook type** — Timeline hooks outperform problem hooks by 3.4x in meetings
+2. **Personalization depth** — Up to 250% more replies
+3. **Brevity** — 25–75 words optimal, 83% more replies under 75 words
+4. **Targeting precision** — ≤50 contacts per campaign = 2.76x higher reply rates
+5. **Follow-up strategy** — First follow-up adds 49% more replies
+6. **Reading level** — 3rd–5th grade = 67% more replies
+7. **Send timing** — Thursday peaks at 6.87% reply rate
+
+## Declining Effectiveness Trend
+
+Reply rates dropped from 7–8% (2020–2022) to 4–5.8% (2024–2025), ~15% YoY decline. Drivers: inbox saturation (10+ cold emails/week, 20% say none relevant), stricter anti-spam (Google's threshold: 0.1% complaints), AI email flood (more volume, less quality signal). Writing craft matters more, not less — gap between average and excellent is widening.
+
+## Response Rates by Seniority
+
+- **Entry-level:** Highest engagement at 8% reply, 50% open
+- **C-level:** 23% more likely to respond than non-C-suite when they engage (6.4% vs 5.2%)
+- **CTOs/VP Tech:** 7.68% reply
+- **CEOs/Founders:** 7.63% reply
+- **Heads of Sales:** 6.60% (most targeted role, highest saturation)
+
+## Industry Variation
+
+**Highest responding:** Nonprofits (16.5%+), legal (10%), EdTech (7.8%), chemical (7.3%), manufacturing (6.1%).
+**Lowest responding:** SaaS (3.5%), financial services (3.4%), IT services (3.5%).
+
+## Top 15 Mistakes (ranked by impact)
+
+1. **Too long** — 70% of emails above 10th-grade level. Under 75 words = 83% more replies
+2. **Too self-focused** — "We are a leading..." signals sales pitch. Count I/We sentences
+3. **No clear value prop** — 71% of decision-makers ignore irrelevant emails
+4. **Generic templates** — {{FirstName}} isn't personalization. Recipients detect instantly
+5. **Feature dumping** — "Great reps lead with problems" (Lavender). One proof point beats ten features
+6. **False personalization** — "Loved your post!" without specifics is transparent
+7. **Asking too much too soon** — 30-min call in first email = "proposing on first date"
+8. **Pushy language** — "Act Now" stacking increases spam flagging by 67%
+9. **No CTA** — Without a clear next step, momentum dies
+10. **"Just checking in" follow-ups** — "I never heard back" = 12% drop in bookings
+11. **Wrong tone for audience** — Founder ≠ RevOps lead ≠ sales leader
+12. **Jargon/buzzwords** — "Leverage synergistic platform" → "We help you book more meetings"
+13. **Unsubstantiated claims** — "300% more leads" without proof triggers skepticism
+14. **Too many contacts per company** — 1–2 people = 7.8% reply; 10+ = 3.8%
+15. **Fake urgency** — Fake "Re:" / "Fwd:" / countdown timers destroy trust
+
+## Cultural Calibration
+
+| Factor       | US              | UK                       | Germany/DACH         | Scandinavia             |
+| ------------ | --------------- | ------------------------ | -------------------- | ----------------------- |
+| Tone         | Direct, casual  | Polite, professional     | Precise, data-driven | Fact-based, egalitarian |
+| Length       | Shorter, blunt  | Longer, insight-led      | Detail-oriented      | Concise but substantive |
+| Social proof | Outcome numbers | Research-led credibility | Technical precision  | Shared values           |
+
+North America: 4.1% response. Europe: 3.1%. Asia-Pacific: 2.8%. Shorter, more direct sequences work better in US. UK needs more insight/personality. GDPR affects European tone.
+
+## Expert Quick Reference
+
+| Expert         | Core Method                                                     | Best For                                        |
+| -------------- | --------------------------------------------------------------- | ----------------------------------------------- |
+| Alex Berman    | 3C's: Compliment → Case Study → CTA                             | High-ticket B2B services, agencies              |
+| Josh Braun     | "Poke the Bear" — neutral questions exposing invisible problems | Empathy-driven consultative selling             |
+| Kyle Coleman   | Systematic research + AI personalization at scale               | Bridging mass outreach and deep personalization |
+| Becc Holland   | Psychographic personalization, Premise Buckets                  | Combining personalization with relevance        |
+| Will Allred    | Data-driven coaching, Mouse Trap, Vanilla Ice Cream             | Any context; universal frameworks               |
+| Justin Michael | 1–3 sentence hyper-brevity, quote their own words               | High-velocity SDR teams at scale                |
+| Sam Nelson     | Agoge Sequence — Triple on Day 1 (email + LinkedIn + call)      | Multi-channel, tiered personalization           |

skills/cold-email/references/follow-up-sequences.md

@@ -0,0 +1,81 @@
+# Follow-Up Sequences
+
+55% of replies come from follow-ups, not the initial email. Yet 48% of salespeople never follow up even once.
+
+## How Many: 3–5 Total Emails
+
+- Highest single-email reply rate: **8.4%** (Belkins).
+- 4–7 email campaigns achieve **27% reply rates** vs 9% for 1–3 emails (Woodpecker, 20M emails).
+- By 4th follow-up, response rates drop **55%** and spam complaints **triple**.
+- Resolution: longer sequences catch different timing windows. Cap at 4 follow-ups (5 total emails). Each must add genuinely new value.
+
+## Optimal Cadence
+
+Increase the gap between each touch:
+
+| Touch         | Day   | Notes                                          |
+| ------------- | ----- | ---------------------------------------------- |
+| Initial email | 0     | Maximum personalization investment             |
+| Follow-up 1   | 3     | Waiting 3 days increases response by up to 31% |
+| Follow-up 2   | 7–8   | Different angle                                |
+| Follow-up 3   | 14    | New value piece                                |
+| Follow-up 4   | 21–28 | Breakup email                                  |
+
+**Best days:** Tuesday–Thursday (Thursday peaks at 6.87% reply rate).
+**Best times:** 9–11 AM or 1–3 PM in prospect's local time.
+**Avoid:** Monday mornings (inbox overload), Friday afternoons (checked out).
+
+## Angle Rotation
+
+Each follow-up must stand alone while building toward the goal. Never just "bump this up."
+
+| Email       | Angle                                                      | Purpose                    |
+| ----------- | ---------------------------------------------------------- | -------------------------- |
+| Initial     | Personalized hook + core value prop + soft CTA             | Introduce problem/solution |
+| Follow-up 1 | Different angle, new value piece (stat, insight, resource) | Show additional benefit    |
+| Follow-up 2 | Social proof / case study from similar company             | Build credibility          |
+| Follow-up 3 | New insight, industry trend, or relevant resource          | Demonstrate expertise      |
+| Follow-up 4 | Breakup — acknowledge silence, leave door open             | Trigger loss aversion      |
+
+Add only **one new value proposition per email** (SalesBread). This naturally forces different angles.
+
+## The Breakup Email
+
+Leverages loss aversion — removing pressure while creating scarcity through withdrawal. Close.com reports **10–15% response rates** from breakup emails with cold prospects.
+
+**Structure:**
+
+1. Acknowledge you've reached out multiple times
+2. Validate their potential lack of interest
+3. State this is your final email for now
+4. Leave the door open
+
+**Example:**
+
+> I haven't heard back, so I'll assume now isn't the right time. Before I close the loop: [1-sentence insight or resource]. If that changes things, feel free to reply. Otherwise, no hard feelings — good luck with [their goal].
+
+**1-2-3 Format** (reduces friction to near zero):
+
+> Since I haven't heard back, I'll keep it simple. Reply with a number:
+>
+> 1 — Interested, let's talk
+> 2 — Not now, check back in 3 months
+> 3 — Not interested, please stop
+
+**Critical rule:** If you send a breakup email, honor it. Do not contact the prospect again.
+
+## Phrases That Kill Response Rates
+
+- "I never heard back" → **12% drop** in meeting booking rate (Gong)
+- "Just checking in" → Zero value, signals laziness
+- "Bumping this to the top of your inbox" → Presumptuous
+- "Did you see my last email?" → Guilt-tripping
+- "Following up on my previous message" → Generic, adds nothing
+
+## CTA Adjustment by Seniority
+
+**Executives/founders:** Ultra-low-effort, curiosity-driven. "Curious?" or "Worth 2 min?"
+
+**Mid-level managers:** More specific value. "Want me to walk through how [Company] saved 15 hours/week?"
+
+Higher in the org chart = less friction you can ask for.

skills/cold-email/references/frameworks.md

@@ -0,0 +1,90 @@
+# Cold Email Copywriting Frameworks
+
+Frameworks beat templates — they teach thinking patterns, not copy-paste shortcuts.
+
+## PAS — Problem, Agitate, Solution (default)
+
+**Structure:** Identify pain → Amplify consequences → Present solution + soft CTA.
+**Best for:** Problem-aware but not solution-aware prospects. The workhorse framework.
+
+> Most VP Sales at companies your size spend 5+ hours/week on manual CRM reporting. That's 250+ hours/year not spent coaching reps — and often means inaccurate forecasts reaching leadership. We built a tool that auto-generates CRM reports in real time. Teams like Datadog reduced reporting time by 80%. Would it make sense to see how?
+
+## BAB — Before, After, Bridge
+
+**Structure:** Current painful situation → Ideal future → Your product as the bridge.
+**Best for:** Transformation-driven offers with clear before/after. Emotional decision-makers.
+
+> Right now, your team is likely spending hours manually sourcing leads — feast or famine each quarter. Imagine qualified leads arriving daily on autopilot, reps spending 100% of their time selling. That's what our platform does. Companies like HubSpot saw a 40% pipeline increase within 90 days. Can I show you how?
+
+## QVC — Question, Value, CTA
+
+**Structure:** Targeted pain question → Brief value → Direct next step.
+**Best for:** C-suite prospects who prefer brevity. Qualify interest immediately.
+
+> Are your SDRs spending more time researching than selling? We help sales teams automate prospect research so reps focus on conversations. Clients see 3x more meetings per rep per week. Worth a 10-minute demo?
+
+## AIDA — Attention, Interest, Desire, Action
+
+**Structure:** Hook/stat → Address specific challenge → Social proof/outcome → Clear CTA.
+**Best for:** Data-driven prospects, high-ticket pitches with strong stats.
+
+> Companies in pharma lose 30% of leads due to manual outreach. Given {{Company}}'s growth this quarter, pipeline velocity is likely top of mind. Customers like Pfizer use our platform to automate lead qualification — cutting time-to-contact by 60%. Worth a 15-minute call?
+
+## PPP — Praise, Picture, Push
+
+**Structure:** Genuine compliment → How things could be better → Gentle push to action.
+**Best for:** Senior prospects who respond to relationship-building. Requires genuine trigger.
+
+> Your keynote on scaling SDR teams was spot-on — especially on ramp time as the hidden cost. What if you could cut that in half? Our in-inbox coach helps new reps write effective emails from day one with real-time scoring. Open to a quick chat about how this could support your growth?
+
+## Star-Story-Solution
+
+**Structure:** Introduce character (customer) → Tell challenge narrative → Reveal results.
+**Best for:** Strong customer success stories. Humanizes the pitch.
+
+> Last year, Sarah — VP Sales at a Series B startup — had 5 SDRs competing against a rival with 20. Her team was getting crushed on volume. They adopted our AI prospecting tool and sent hyper-personalized emails at 3x pace without losing quality. Within 90 days, they booked more meetings than their competitor's entire team. Happy to share how this could work for {{Company}}.
+
+## SCQ — Situation, Complication, Question
+
+**Structure:** Current reality → Complicating challenge → Question that speaks to need → Optional answer.
+**Best for:** Consultative selling. Mirrors how professionals present to leadership.
+
+> Your team doubled this year. That usually means onboarding is eating into selling time. How are you handling ramp for new hires?
+
+## ACCA — Awareness, Comprehension, Conviction, Action
+
+**Structure:** Contrarian hook → Explain benefit simply → Provide proof → Strong CTA.
+**Best for:** Analytical buyers who need evidence (engineers, CFOs, ops leaders).
+
+> Most sales teams measure rep activity. The top 5% measure rep efficiency instead. When Acme switched, they booked 40% more meetings with fewer emails. Worth seeing how?
+
+## 3C's (Alex Berman)
+
+**Structure:** Compliment → Case Study → CTA.
+**Best for:** Agency/services cold outreach. Case study does the heavy lifting.
+
+> Big fan of [Company]. We just built an app for [Competitor] that does XYZ. I have a few more ideas. Interested?
+
+## Mouse Trap (Lavender/Will Allred)
+
+**Structure:** Observation + Binary value-prop question. 1–2 sentences total.
+**Best for:** Maximum brevity. Impulsive reply based on curiosity.
+
+> Looks like you're hiring reps. Would it be helpful to get a more granular look at how they're ramping on email?
+
+## Justin Michael Method
+
+**Structure:** Trigger/Pain → Solution hint → Binary CTA. 1–3 sentences, no intro.
+**Best for:** High-velocity SDR teams. Mobile-optimized. Deliberately polarizing.
+
+Spend max 1 minute on personalization. Use industry/persona-level signals. For top-tier prospects, quote their own words from interviews — they almost always respond.
+
+## Vanilla Ice Cream (Lavender)
+
+**Structure:** Observation → Problem/Insight → Credibility → Solution → Call-to-Conversation.
+**Best for:** Universal "base" framework that works everywhere. Five parts.
+
+## PASTOR (Ray Edwards)
+
+**Structure:** Problem → Amplify → Story → Testimony → Offer → Response.
+**Best for:** Longer-form or multi-email sequences. Consulting, education, complex B2B services. Each element can be developed across separate touches.

skills/cold-email/references/personalization.md

@@ -0,0 +1,79 @@
+# Personalization at Scale
+
+Personalization drives **50–250% more replies** (Lavender). The key insight: **if your personalization has nothing to do with the problem you solve, it's just an attention hack** (Clay).
+
+## Four Levels of Personalization
+
+### Level 1 — Basic (merge tags)
+
+First name, company name, job title. Table stakes, no longer differentiating. ~5% lift.
+
+### Level 2 — Industry/segment
+
+Industry-specific pain points, trends, regulatory challenges. Scalable via micro-segmentation.
+
+> Most {{industry}} teams struggle with {{lead gen problem}}, which often leads to wasted effort.
+
+### Level 3 — Role-level
+
+Challenges specific to their role and seniority.
+
+> As Head of Sales, keeping pipeline steady is probably your biggest headache. Your RevOps team is small, so you're likely wearing multiple hats during scaling.
+
+### Level 4 — Individual (gold standard)
+
+Specific, timely observations about that person connected to the problem you solve.
+
+> Noticed you're hiring 3 SDRs — sounds like you're scaling outbound fast. Most teams hit follow-up fatigue during onboarding.
+
+## Research Signal Stack
+
+| Signal            | Where to find it                   | How to use it                                                                |
+| ----------------- | ---------------------------------- | ---------------------------------------------------------------------------- |
+| Recent funding    | Crunchbase, LinkedIn, press        | "Congrats on Series B — scaling teams fast usually creates X challenge"      |
+| Job postings      | LinkedIn Jobs, careers page        | "Noticed you're hiring 3 SDRs — sounds like you're scaling outbound"         |
+| Tech stack        | BuiltWith, Wappalyzer, HG Insights | "I see you're using HubSpot — most teams at your stage hit a ceiling with X" |
+| LinkedIn activity | Posts, comments, job changes       | "Really enjoyed your post about X"                                           |
+| Company news      | Google News, press releases        | "Congrats on acquiring X — integrating teams usually creates Y challenge"    |
+| Podcast/talks     | Google, YouTube, podcasts          | "Caught your talk at SaaStr on X — really insightful"                        |
+| Website changes   | Manual review                      | "Your new pricing page caught my eye — curious how it's converting"          |
+
+## The 3-Minute Personalization System
+
+From "30 Minutes to President's Club":
+
+**Step 1:** Build a research stack of top 10 buying signals — 5 company triggers, 5 person triggers. Stack-rank by relevance.
+
+**Step 2:** Build a 3x3 template: (1) personalization attached to a problem, (2) problem you solve, (3) one-sentence solution + low-friction CTA.
+
+**Step 3:** Create 5 "trigger templates" — pre-written personalization paragraphs for each trigger, with a smooth segue into the problem.
+
+The personalization must logically connect to the problem. This creates 5 reusable triggers with the rest of the email constant. A top SDR writes a personalized email in **under 3 minutes**.
+
+## The Four -Graphic Principles (Becc Holland)
+
+- **Demographic** — Age, profession, background
+- **Technographic** — Tech stack, tools used
+- **Firmographic** — Company size, funding, industry, growth stage
+- **Psychographic** — Values, passions, beliefs (highest-impact dimension)
+
+Tapping into what prospects are passionate about drives significantly higher response rates.
+
+## Observation-Based Openers (highest performing)
+
+**Trigger-event:** "Congrats on the recent funding round — scaling the team from here is exciting, and I imagine [challenge] is top of mind."
+
+**Observation:** "Your recent post about [topic] resonated — especially the part about [detail]. Got me thinking about how that applies to [challenge]."
+
+**Industry insight:** "Most [role titles] I talk to spend [X hours/week] on [problem] — curious if that matches your experience at [Company]."
+
+## What Feels Fake (avoid)
+
+- AI-generated emails with similar phrasing ("I hope this email finds you well")
+- Generic attention hacks disconnected from problem ("Cool that you went to UCLA!" → pitch)
+- Over-personalizing to creepiness
+- "I saw your LinkedIn profile and wanted to reach out" — signals mass automation
+
+## The "So What?" Test
+
+After writing any opening line, read from prospect's perspective: "So what? Why would I care?" If the answer is nothing, rewrite.

skills/cold-email/references/subject-lines.md

@@ -0,0 +1,53 @@
+# Subject Line Optimization
+
+The subject line determines whether the email gets read. The data is counterintuitive: **short, boring, internal-looking subject lines win decisively.**
+
+## Length: 2–4 words
+
+- 2-word subject lines get **60% more opens** than 5-word (Lavender).
+- Going from 2 to 4 words reduces replies by **17.5%**.
+- 2–4 words yield **46% open rates** vs 34% for 10 words (Belkins, 5.5M emails).
+- Mobile truncates at 30–35 characters — brevity is practical necessity.
+
+## Internal Camouflage Principle
+
+Subject lines that look like they came from a colleague, not a vendor, double open rates (Gong). Buyers mentally categorize before opening — if it looks like sales, it's filtered.
+
+**High-performing examples:** "reply rates" · "trial delays" · "hiring ops" · "employee turnover" · "Q2 forecast" · "new patients" · "personalization issue" · "second page"
+
+## Capitalization: lowercase wins
+
+All-lowercase has highest open rates (Gong, 85M+ emails). Lowercase looks more personal/internal. For cold outreach specifically, lowercase beats title case.
+
+## Personalization: context over name
+
+Personalized subject lines boost opens **26–50%**, but type matters:
+
+- **First name in subject line → 12% fewer replies.** Signals automation.
+- **Contextual personalization works:** pain points, competitors, trigger events, industry challenges.
+- Use {{painPoint}}, {{competitor}}, {{commonGround}} — not {{firstName}}.
+
+## Questions: only when highly specific
+
+Data conflicts: Belkins says questions perform well (46% open rate). Lavender says questions lower opens by **56%**. Resolution: **specific pain questions work** ("Need help with {{challenge}}?"), **generic questions fail** ("Quick question?" / "Have 15 minutes?"). Default to statements.
+
+## What to Avoid
+
+| Anti-pattern                                   | Impact                      |
+| ---------------------------------------------- | --------------------------- |
+| Salesy language ("increase," "boost," "ROI")   | -17.9% opens                |
+| Urgency words ("ASAP," "urgent")               | Below 36% opens             |
+| Excessive punctuation ("!!!" or "??")          | -36% opens                  |
+| Numbers and percentages                        | -46% opens                  |
+| Emojis                                         | Hurt B2B professionalism    |
+| Pitching product in subject                    | -57% replies                |
+| Empty/no subject line                          | +30% opens but -12% replies |
+| Spam triggers ("free," "guarantee," "act now") | Deliverability risk         |
+
+## C-Suite Subject Lines
+
+Executives receive 300–400 emails daily, decide in seconds. They respond **23% more often** than non-C-suite when emails pass their filter (6.4% reply rate).
+
+What works: ultra-concise, human, understated. "{{companyInitiative}}" · "thank you" · "an update" · "a question" · reference to a specific project or trigger event.
+
+Anything "salesy" is immediately rejected.

skills/community-marketing/SKILL.md

@@ -0,0 +1,143 @@
+---
+name: community-marketing
+description: Build and leverage online communities to drive product growth and brand loyalty. Use when the user wants to create a community strategy, grow a Discord or Slack community, manage a forum or subreddit, build brand advocates, increase word-of-mouth, drive community-led growth, engage users post-signup, or turn customers into evangelists. Trigger phrases: "build a community," "community strategy," "Discord community," "Slack community," "community-led growth," "brand advocates," "user community," "forum strategy," "community engagement," "grow our community," "ambassador program," "community flywheel."
+metadata:
+  version: 1.0.0
+---
+
+# Community Marketing
+
+You are an expert community builder and community-led growth strategist. Your goal is to help the user design, launch, and grow a community that creates genuine value for members while driving measurable business outcomes.
+
+## Before You Start
+
+**Check for product marketing context first:**
+If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered.
+
+Understand the situation (ask if not provided):
+
+1. **What is the product or brand?** — What problem does it solve, who uses it
+2. **What community platform(s) are in play?** — Discord, Slack, Circle, Reddit, Facebook Groups, forum, etc.
+3. **What stage is the community at?** — Pre-launch, 0–100 members, 100–1k, scaling, or established
+4. **What is the primary community goal?** — Retention, activation, word-of-mouth, support deflection, product feedback, revenue
+5. **Who is the ideal community member?** — Role, motivation, what they hope to get from joining
+
+Work with whatever context is available. If key details are missing, make reasonable assumptions and flag them.
+
+---
+
+## Community Strategy Principles
+
+### Build around a shared identity, not just a product
+
+The strongest communities are built around who members *are* or aspire to be — not around your product. Members join because of the product but stay because of the people and identity.
+
+Examples:
+- Indie hackers (identity: bootstrapped founders)
+- r/homelab (identity: tinkerers who self-host)
+- Figma community (identity: designers who care about craft)
+
+Always define: **What identity does this community reinforce for its members?**
+
+### Value must flow to members first
+
+Every community touchpoint should answer: *What does the member get from this?*
+
+- Exclusive knowledge or early access
+- Peer connections they can't get elsewhere
+- Recognition and status within a group they respect
+- Direct influence on the product roadmap
+- Career opportunities, visibility, or credibility
+
+### The Community Flywheel
+
+Healthy communities compound over time:
+
+```
+Members join → get value → engage → create content/help others
+    ↑                                          ↓
+    ←←←←← new members discover the community ←←
+```
+
+Design for the flywheel from day one. Every decision should ask: *Does this accelerate the loop or slow it down?*
+
+---
+
+## Playbooks by Goal
+
+### Launching a Community from Zero
+
+1. **Recruit 20–50 founding members manually** — DM your most engaged users, beta testers, or fans. Don't open publicly until there is baseline activity.
+2. **Set the culture explicitly** — Write community guidelines that describe the *vibe*, not just the rules. What does great participation look like here?
+3. **Seed conversations before launch** — Pre-populate channels with 5–10 posts that model the behavior you want. Questions, wins, resources.
+4. **Do things that don't scale at first** — Reply to every post. Welcome every new member by name. Host a weekly call. You are buying social proof.
+5. **Define your core loop** — What action do you want members to take weekly? Make it easy and reward it publicly.
+
+### Growing an Existing Community
+
+1. **Audit where members drop off** — Are people joining but not posting? Posting once and disappearing? Identify the leaky stage.
+2. **Create a new member journey** — A pinned welcome post, a #introduce-yourself channel, a DM or email from a community manager, a clear "start here" path.
+3. **Surface member wins publicly** — Showcase user projects, testimonials, milestones. This reinforces identity and signals that participation has rewards.
+4. **Run recurring community rituals** — Weekly threads (e.g., "What are you working on?"), monthly AMAs, seasonal challenges. Rituals create habit.
+5. **Identify and invest in power users** — 1% of members generate 90% of value. Give them recognition, early access, moderator roles, or direct product input.
+
+### Building a Brand Ambassador / Advocate Program
+
+1. **Identify candidates** — Look for people who already recommend you unprompted. Check reviews, social mentions, community posts.
+2. **Make the ask personal** — Don't send a generic form. Reach out 1:1 and explain why you chose them specifically.
+3. **Offer meaningful benefits** — Exclusive access, swag, revenue share, or public recognition — not just "early access to features."
+4. **Give them tools and content** — Referral links, shareable assets, key talking points, a private Slack channel.
+5. **Measure and iterate** — Track referral traffic, signups, and engagement driven by advocates. Double down on what works.
+
+### Community-Led Support (Deflection + Retention)
+
+1. **Create a searchable knowledge base** from top community questions
+2. **Recognize members who help others** — "Community Expert" badges, leaderboards, shoutouts
+3. **Close the loop with product** — When community feedback drives a change, announce it publicly and credit the members who raised it
+4. **Monitor sentiment weekly** — Look for patterns in complaints or confusion before they become churn signals
+
+---
+
+## Platform Selection Guide
+
+| Platform | Best For | Watch Out For |
+|----------|----------|---------------|
+| Discord | Developer, gaming, creator communities; real-time chat | High noise, hard to search, onboarding friction |
+| Slack | B2B / professional communities; familiar to SaaS buyers | Free tier limits history; feels like work |
+| Circle | Creator or course-based communities; clean UX | Less organic discovery; requires driving traffic |
+| Reddit | High-volume public communities; SEO benefit | You don't own it; moderation is hard |
+| Facebook Groups | Consumer brands; older demographics | Declining organic reach; algorithm dependent |
+| Forum (Discourse) | Long-form technical communities; SEO-rich | Slower velocity; higher effort to post |
+
+---
+
+## Community Health Metrics
+
+Track these signals weekly:
+
+- **DAU/MAU ratio** — Stickiness. Above 20% is healthy for most communities.
+- **New member post rate** — % of new members who post within 7 days of joining
+- **Thread reply rate** — % of posts that receive at least one reply
+- **Churn / lurker ratio** — Members who joined but haven't posted in 30+ days
+- **Content created by non-staff** — % of posts not written by the company team
+
+**Warning signs:**
+- Most posts are from the company team, not members
+- Questions go unanswered for >24 hours
+- The same 5 people account for 80%+ of engagement
+- New members stop posting after their intro message
+
+---
+
+## Output Formats
+
+Depending on what the user needs, produce one of:
+
+- **Community Strategy Doc** — Platform choice, identity definition, core loop, 90-day launch plan
+- **Channel Architecture** — Recommended channels/categories with purpose and posting guidelines for each
+- **New Member Journey** — Welcome sequence: pinned post, DM template, first-week prompts
+- **Community Ritual Calendar** — Weekly/monthly recurring events and threads
+- **Ambassador Program Brief** — Criteria, benefits, outreach template, tracking plan
+- **Health Audit Report** — Current metrics, diagnosis, top 3 priorities to fix
+
+Always be specific. Generic advice ("be consistent," "provide value") is not useful. Give the user something they can act on today.

skills/competitors/SKILL.md

@@ -1,7 +1,8 @@
 ---
-name: competitor-alternatives
-version: 1.0.0
-description: "When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' or 'competitive landing pages.' Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Emphasizes deep research, modular content architecture, and varied section types beyond feature tables."
+name: competitors
+description: "When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'battle card,' or 'competitor teardown.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For sales-specific competitor docs, see sales-enablement."
+metadata:
+  version: 1.1.0
 ---
 
 # Competitor & Alternative Pages
@@ -11,7 +12,7 @@ You are an expert in creating competitor comparison and alternative pages. Your
 ## Initial Assessment
 
 **Check for product marketing context first:**
-If `.claude/product-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
+If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` 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 creating competitor pages, understand:
 
@@ -252,3 +253,4 @@ Recommended pages to create with priority order based on search volume.
 - **copywriting**: For writing compelling comparison copy
 - **seo-audit**: For optimizing competitor pages
 - **schema-markup**: For FAQ and comparison schema
+- **sales-enablement**: For internal sales collateral, decks, and objection docs

skills/competitors/evals/evals.json

@@ -0,0 +1,93 @@
+{
+  "skill_name": "competitor-alternatives",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Create a 'Best Asana Alternatives' page for our project management tool. We compete mainly on price (we're $8/user vs their $24/user) and simplicity (they've become bloated). Target audience is small teams (5-20 people).",
+      "expected_output": "Should check for product-marketing-context.md first. Should identify this as the plural alternatives format ([Competitor] Alternatives). Should include the essential sections: TL;DR comparison, brief paragraphs on each alternative (including the user's product positioned first or prominently), feature comparison table, pricing comparison, who each alternative is best for. Should use the modular content architecture approach. Should address SEO considerations for the target keyword 'Asana alternatives.' Should position the user's product with the stated differentiators (price, simplicity).",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Identifies as plural alternatives format",
+        "Includes TL;DR comparison section",
+        "Includes feature comparison table",
+        "Includes pricing comparison",
+        "Includes 'who it's best for' per alternative",
+        "Positions user's product prominently with differentiators",
+        "Addresses SEO for target keyword"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "Write a 'HubSpot vs Salesforce' comparison page. We're HubSpot and want to show why we're the better choice for SMBs.",
+      "expected_output": "Should identify this as the 'you vs competitor' format. Should include structured comparison sections: overview of both, feature-by-feature comparison, pricing comparison, pros/cons of each, who each is best for, and migration path. Should be factually accurate about the competitor while strategically positioning the user's product. Should include a TL;DR at the top. Should address the SMB angle throughout. Should use the centralized competitor data architecture pattern.",
+      "assertions": [
+        "Identifies as 'you vs competitor' format",
+        "Includes structured comparison sections",
+        "Includes feature-by-feature comparison",
+        "Includes pricing comparison",
+        "Includes TL;DR at the top",
+        "Factually accurate about competitor",
+        "Strategically positions user's product for SMBs",
+        "Includes migration path or switching section"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "we need a page targeting 'mailchimp alternative' (singular). we're an email marketing platform focused on e-commerce brands.",
+      "expected_output": "Should trigger on casual phrasing. Should identify this as the singular alternative format ([Competitor] Alternative — positioning your product as THE alternative). Should focus the entire page on why the user's product is the best Mailchimp alternative for e-commerce. Should include: why people switch from Mailchimp, what the user's product does better (e-commerce specific features), feature comparison, pricing comparison, migration guide, customer testimonials. Should optimize for the singular keyword 'Mailchimp alternative.'",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Identifies as singular alternative format",
+        "Focuses on user's product as THE alternative",
+        "Includes why people switch from Mailchimp",
+        "Highlights e-commerce-specific advantages",
+        "Includes feature and pricing comparison",
+        "Includes migration guide",
+        "Optimizes for singular keyword"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "Can you create a comparison page for 'Notion vs Coda'? We're a third-party review site, not affiliated with either product.",
+      "expected_output": "Should identify this as the 'competitor vs competitor' format (third-party perspective). Should maintain objectivity since the user isn't either product. Should include balanced comparison: overview of both, feature comparison, pricing, pros/cons, use case recommendations. Should use the essential page sections from the skill. Should suggest how to monetize the page (affiliate links, CTA to the user's own product if relevant). Should address SEO for the 'Notion vs Coda' keyword.",
+      "assertions": [
+        "Identifies as 'competitor vs competitor' format",
+        "Maintains objectivity (third-party perspective)",
+        "Includes balanced feature comparison",
+        "Includes pricing comparison",
+        "Includes use case recommendations",
+        "Addresses SEO considerations",
+        "Suggests monetization approach"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "We want to build a whole competitor comparison hub. We have 5 main competitors and want to create alternative pages for each, plus head-to-head comparisons. How should we structure this?",
+      "expected_output": "Should apply the centralized competitor data architecture. Should recommend a hub structure with: individual alternative pages for each competitor (5 singular pages), a 'best alternatives' roundup page, head-to-head comparison pages for key matchups. Should address internal linking strategy between these pages. Should recommend the research process for gathering competitive data. Should address URL structure and site architecture for the hub.",
+      "assertions": [
+        "Applies centralized competitor data architecture",
+        "Recommends hub structure with multiple page types",
+        "Suggests individual and roundup alternative pages",
+        "Addresses internal linking between comparison pages",
+        "Recommends research process for competitive data",
+        "Addresses URL structure"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "I need to create a battle card for our sales team comparing us to Zendesk. It should help reps handle competitive objections during sales calls.",
+      "expected_output": "Should recognize this as internal sales enablement material, not a public comparison page. Should defer to or cross-reference the sales-enablement skill, which handles battle cards, objection handling docs, and internal competitive collateral. May provide some competitive positioning advice but should make clear that sales-enablement is the right skill for internal sales materials.",
+      "assertions": [
+        "Recognizes this as internal sales enablement material",
+        "References or defers to sales-enablement skill",
+        "Does not attempt to create internal battle card using public comparison page patterns"
+      ],
+      "files": []
+    }
+  ]
+}

skills/competitors/references/content-architecture.md

@@ -2,6 +2,14 @@
 
 How to structure and maintain competitor data for scalable comparison pages.
 
+## Contents
+- Centralized Competitor Data
+- Competitor Data Template
+- Your Product Data
+- Page Generation
+- Index Page Structure (alternatives index, vs comparisons index, index page best practices)
+- Footer Navigation
+
 ## Centralized Competitor Data
 
 Create a single source of truth for each competitor:

skills/competitors/references/templates.md

@@ -2,6 +2,17 @@
 
 Ready-to-use templates for each section of competitor comparison pages.
 
+## Contents
+- TL;DR Summary
+- Paragraph Comparison (Not Just Tables)
+- Feature Comparison Section
+- Pricing Comparison Section
+- Service & Support Comparison
+- Who It's For Section
+- Migration Section
+- Social Proof Section
+- Comparison Table Best Practices (beyond checkmarks, organize by category, include ratings where useful)
+
 ## TL;DR Summary
 
 Start every page with a quick summary for scanners:

skills/content-strategy/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: content-strategy
-version: 1.0.0
-description: When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," or "content planning." For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit.
+description: When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "what content should I create," "blog topics," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce, not just writing it. For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media content specifically, see social.
+metadata:
+  version: 1.1.0
 ---
 
 # Content Strategy
@@ -11,7 +12,7 @@ You are a content strategist. Your goal is to help plan content that drives traf
 ## Before Planning
 
 **Check for product marketing context first:**
-If `.claude/product-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
+If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
 
 Gather this context (ask if not provided):
 
@@ -347,10 +348,18 @@ Visual or structured representation of how content interconnects.
 
 ---
 
+## References
+
+- **[Headless CMS Guide](references/headless-cms.md)**: CMS selection, content modeling for marketing, editorial workflows, platform comparison (Sanity, Contentful, Strapi)
+
+---
+
 ## Related Skills
 
 - **copywriting**: For writing individual content pieces
 - **seo-audit**: For technical SEO and on-page optimization
+- **ai-seo**: For optimizing content for AI search engines and getting cited by LLMs
 - **programmatic-seo**: For scaled content generation
-- **email-sequence**: For email-based content
-- **social-content**: For social media content
+- **site-architecture**: For page hierarchy, navigation design, and URL structure
+- **emails**: For email-based content
+- **social**: For social media content

skills/content-strategy/evals/evals.json

@@ -0,0 +1,90 @@
+{
+  "skill_name": "content-strategy",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Help me build a content strategy for our B2B SaaS product. We sell expense management software to finance teams at companies with 50-500 employees. We currently have no blog and want to start from scratch.",
+      "expected_output": "Should check for product-marketing-context.md first. Should establish content pillars (3-5 core topic areas). Should map content types by buyer stage (awareness → consideration → decision → implementation). Should identify keyword research opportunities by buyer stage. Should recommend a mix of searchable (SEO-driven) and shareable (thought leadership, data) content. Should use the prioritization scoring framework (customer impact 40%, content-market fit 30%, search potential 20%, resources 10%). Should provide an initial content calendar or publishing cadence. Should recommend content types appropriate for starting from scratch.",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Establishes 3-5 content pillars",
+        "Maps content by buyer stage (awareness through implementation)",
+        "Includes keyword research by buyer stage",
+        "Recommends mix of searchable and shareable content",
+        "Uses prioritization scoring framework",
+        "Provides publishing cadence or calendar",
+        "Recommends appropriate starting content types"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "We have 200+ blog posts but traffic has been flat for a year. Our content feels random — no clear strategy. How do we fix this?",
+      "expected_output": "Should diagnose the 'random content' problem. Should recommend a content audit process to evaluate existing posts. Should introduce content pillars and topical clustering to organize the existing library. Should identify hub-and-spoke opportunities from existing content. Should recommend which posts to update, consolidate, or retire. Should use the prioritization framework to plan next steps. Should address topical authority building through clusters.",
+      "assertions": [
+        "Diagnoses the 'random content' problem",
+        "Recommends content audit for existing posts",
+        "Introduces content pillars and topical clustering",
+        "Identifies hub-and-spoke opportunities",
+        "Recommends update, consolidate, or retire decisions",
+        "Uses prioritization framework",
+        "Addresses topical authority building"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "what kind of content should we be creating? we're a developer tool (API testing platform) and our audience is backend developers and QA engineers",
+      "expected_output": "Should trigger on casual phrasing. Should recommend content types appropriate for a developer audience: technical tutorials, documentation-style guides, use-case content, template/example libraries, data-driven benchmarks. Should note that developer audiences prefer depth, accuracy, and practical value over marketing fluff. Should suggest content pillars aligned with developer interests. Should use the ideation sources framework (keyword data, community forums like Stack Overflow/Reddit, competitor gaps).",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Recommends content types for developer audience",
+        "Emphasizes technical depth and practical value",
+        "Notes developers prefer substance over marketing",
+        "Suggests content pillars for developer tool",
+        "Uses ideation sources framework",
+        "Mentions developer community channels"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "How should we prioritize which content to create first? We have a list of 50 blog post ideas but limited resources — one content marketer writing 2 posts per week.",
+      "expected_output": "Should apply the prioritization scoring framework: customer impact (40%), content-market fit (30%), search potential (20%), resources required (10%). Should help score or rank the content ideas using this framework. Should recommend focusing on high-impact, lower-effort content first. Should consider the buyer stage distribution (don't write only top-of-funnel). Should provide a practical workflow for the single content marketer to use going forward.",
+      "assertions": [
+        "Applies prioritization scoring framework with weights",
+        "Explains each scoring dimension",
+        "Recommends focusing on high-impact, lower-effort first",
+        "Considers buyer stage distribution",
+        "Provides practical workflow for limited resources"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "We want to build topical authority in 'employee engagement.' What does a content cluster look like for this topic?",
+      "expected_output": "Should apply the hub-and-spoke content cluster model. Should design a pillar page for 'employee engagement' (comprehensive, 3000+ word guide). Should identify 8-15 supporting spoke articles targeting long-tail keywords related to employee engagement. Should map the internal linking structure between hub and spokes. Should address keyword research for the cluster. Should recommend content types for each piece (guide, how-to, template, data-driven, etc.).",
+      "assertions": [
+        "Applies hub-and-spoke content cluster model",
+        "Designs a pillar page for the core topic",
+        "Identifies 8-15 supporting spoke articles",
+        "Maps internal linking between hub and spokes",
+        "Addresses keyword research for the cluster",
+        "Recommends content types for each piece"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "Can you write a blog post about remote work best practices for our HR software blog?",
+      "expected_output": "Should recognize this is a copywriting/content creation task, not a content strategy task. Should defer to or cross-reference the copywriting skill for writing individual pieces of content. May provide strategic context (where this fits in the content strategy, keyword targeting, audience) but should make clear that copywriting is the right skill for writing the actual content.",
+      "assertions": [
+        "Recognizes this as content creation, not strategy",
+        "References or defers to copywriting skill",
+        "Does not attempt to write the full blog post",
+        "May provide strategic context for the piece"
+      ],
+      "files": []
+    }
+  ]
+}

skills/content-strategy/references/headless-cms.md

@@ -0,0 +1,194 @@
+# Headless CMS Guide
+
+Reference for choosing, modeling, and implementing a headless CMS for marketing content.
+
+## When to Use This Reference
+
+Use this when selecting a CMS for a new project, designing content models for marketing sites, setting up editorial workflows, or connecting CMS content to programmatic pages.
+
+---
+
+## Headless vs Traditional CMS
+
+A headless CMS separates content management from presentation. Content is stored in a structured backend and delivered via API to any frontend.
+
+### When Headless Makes Sense
+
+- Multiple frontends consume the same content (web, mobile, email)
+- Developers want full control over the frontend stack
+- Content needs to be reused across channels
+- You're building with a modern framework (Next.js, Remix, Astro)
+- Marketing needs structured, reusable content blocks
+
+### When Traditional Works Better
+
+- Small team with no dedicated developers
+- Simple blog or brochure site
+- WYSIWYG editing is a hard requirement
+- Budget is tight and WordPress/Webflow does the job
+
+### Decision Checklist
+
+| Factor | Headless | Traditional |
+|--------|----------|-------------|
+| Multi-channel delivery | Yes | Limited |
+| Developer control | Full | Constrained |
+| Non-technical editing | Requires setup | Built-in |
+| Time to launch | Longer | Faster |
+| Content reuse | Native | Manual |
+| Hosting flexibility | Any frontend | Platform-dependent |
+
+---
+
+## Content Modeling for Marketing
+
+### Core Principles
+
+1. **Think in types, not pages.** A "Landing Page" is a content type with fields — not an HTML file. This lets you reuse components across pages.
+2. **Separate content from presentation.** Store the headline text, not the styled headline. Presentation belongs in the frontend.
+3. **Design for reuse.** If testimonials appear on 5 pages, create a Testimonial type and reference it — don't duplicate.
+4. **Keep models flat.** Deeply nested structures are hard to query and maintain. Prefer references over nesting.
+
+### Common Marketing Content Types
+
+| Type | Key Fields | Notes |
+|------|-----------|-------|
+| **Landing Page** | title, slug, hero, sections[], seo | Modular sections for flexibility |
+| **Blog Post** | title, slug, body, author, category, tags, publishedAt, seo | Rich text or Portable Text body |
+| **Case Study** | title, customer, challenge, solution, results, metrics[], logo | Link to related products/features |
+| **Testimonial** | quote, author, role, company, avatar, rating | Reference from landing pages |
+| **FAQ** | question, answer, category | Group by category for programmatic pages |
+| **Author** | name, bio, avatar, social links | Reference from blog posts |
+| **CTA Block** | heading, body, buttonText, buttonUrl, variant | Reusable across pages |
+
+### SEO Fields Checklist
+
+Every page-level content type needs:
+
+- `metaTitle` — 50-60 characters
+- `metaDescription` — 150-160 characters
+- `ogImage` — 1200x630px social preview
+- `slug` — URL path segment
+- `canonicalUrl` — optional override
+- `noIndex` — boolean for excluding from search
+- `structuredData` — optional JSON-LD override
+
+---
+
+## Editorial Workflows
+
+### Draft → Review → Publish Cycle
+
+1. **Draft** — Author creates or edits content
+2. **Review** — Editor reviews for accuracy, brand voice, SEO
+3. **Approve** — Stakeholder signs off
+4. **Schedule** — Set publish date/time
+5. **Publish** — Content goes live via API
+
+### Preview APIs
+
+All major headless CMS platforms support draft previews:
+
+- **Sanity**: Real-time preview with `useLiveQuery` or Presentation tool
+- **Contentful**: Preview API (`preview.contentful.com`) with separate access token
+- **Strapi**: Draft & Publish system with `status=draft` query parameter (v5; replaces v4's `publicationState`)
+
+Set up a preview route in your frontend (e.g., `/api/preview`) that authenticates and renders draft content.
+
+### Roles and Permissions
+
+| Role | Can Create | Can Edit | Can Publish | Can Delete |
+|------|:----------:|:--------:|:-----------:|:----------:|
+| Author | Yes | Own | No | Own drafts |
+| Editor | Yes | All | Yes | Drafts |
+| Admin | Yes | All | Yes | All |
+
+Exact permission models vary by platform. Sanity uses role-based access. Contentful has space-level roles. Strapi has granular RBAC.
+
+---
+
+## Platform Comparison
+
+| Feature | Sanity | Contentful | Strapi |
+|---------|--------|------------|--------|
+| Hosting | Cloud (managed) | Cloud (managed) | Self-hosted or Cloud |
+| Query Language | GROQ | REST / GraphQL | REST / GraphQL |
+| Free Tier | Generous | Limited | Open source (free) |
+| Real-time Collab | Yes (built-in) | Limited | No |
+| Best For | Developer flexibility | Enterprise multi-locale | Budget / self-hosted |
+| Content Modeling | Schema-as-code | Web UI | Web UI or code |
+| Media Handling | Built-in DAM | Built-in | Plugin-based |
+
+### Sanity
+
+**Strengths**: GROQ query language is powerful and flexible. Schema defined in code (version-controlled). Real-time collaborative editing. Portable Text for rich content. Generous free tier.
+
+**Considerations**: Steeper learning curve for non-developers. Studio customization requires React knowledge. Vendor lock-in on GROQ queries.
+
+**Marketing fit**: Best when developers and marketers collaborate closely. Strong for content-heavy sites with complex models.
+
+### Contentful
+
+**Strengths**: Mature enterprise platform. Excellent multi-locale support. Strong ecosystem of integrations. Composable content with Studio. Well-documented APIs.
+
+**Considerations**: Pricing scales with content types and locales. Two separate APIs (Delivery and Management). Rate limits can be tight on lower plans.
+
+**Marketing fit**: Best for enterprises with multi-market content needs. Good when you need established vendor reliability.
+
+### Strapi
+
+**Strengths**: Open source, self-hosted option. Full control over data. No per-seat pricing. Customizable admin panel. Plugin ecosystem. REST by default, GraphQL via plugin.
+
+**Considerations**: Self-hosting means you handle infrastructure. Smaller ecosystem than Sanity/Contentful. V5 migration can be significant from V4.
+
+**Marketing fit**: Best for teams with DevOps capability who want full control and no vendor lock-in. Good for budget-conscious projects.
+
+### Others Worth Knowing
+
+- **Hygraph** — GraphQL-native, strong for federation and multi-source content
+- **Keystatic** — Git-based, good for developer-content hybrid workflows
+- **Payload** — TypeScript-first, self-hosted, code-configured like Sanity
+- **Builder.io** — Visual editor with headless backend, good for non-technical marketers
+- **Prismic** — Slice-based content modeling, strong Next.js integration
+
+---
+
+## Integration with Marketing Skills
+
+### Programmatic SEO
+
+Use CMS as the data source for programmatic pages. Store structured data (FAQs, comparisons, city pages) as content types and generate pages from queries. See **programmatic-seo** skill.
+
+### Copywriting
+
+CMS content models enforce consistent structure. Define fields that match your copy frameworks (headline, subheadline, social proof, CTA). See **copywriting** skill.
+
+### Site Architecture
+
+URL structure, navigation hierarchy, and internal linking all depend on how content is organized in the CMS. Plan your content model and site architecture together. See **site-architecture** skill.
+
+### Email Sequences
+
+Pull CMS content into email templates for consistent messaging across web and email. Case studies, testimonials, and blog posts can feed email nurture sequences. See **emails** skill.
+
+---
+
+## Implementation Checklist
+
+- [ ] Define content types based on page types and reusable blocks
+- [ ] Add SEO fields to every page-level content type
+- [ ] Set up preview/draft mode in your frontend
+- [ ] Configure roles and permissions for your team
+- [ ] Create sample content for each type before building frontend
+- [ ] Set up webhook notifications for content changes (rebuild triggers)
+- [ ] Document content guidelines for editors (field descriptions, character limits)
+- [ ] Test content delivery performance (CDN, caching, ISR)
+- [ ] Plan migration strategy if moving from existing CMS
+
+---
+
+## Relevant Integration Guides
+
+- [Sanity](../../../tools/integrations/sanity.md) — GROQ queries, mutations, CLI
+- [Contentful](../../../tools/integrations/contentful.md) — Delivery/Management APIs, publishing
+- [Strapi](../../../tools/integrations/strapi.md) — REST CRUD, filters, document API

skills/copy-editing/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: copy-editing
-version: 1.0.0
-description: "When the user wants to edit, review, or improve existing marketing copy. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' or 'copy sweep.' This skill provides a systematic approach to editing marketing copy through multiple focused passes."
+description: "When the user wants to edit, review, or improve existing marketing copy. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' 'copy sweep,' 'tighten this up,' 'this reads awkwardly,' 'clean up this text,' 'too wordy,' or 'sharpen the messaging.' Use this when the user already has copy and wants it improved rather than rewritten from scratch. For writing new copy, see copywriting."
+metadata:
+  version: 1.1.0
 ---
 
 # Copy Editing
@@ -11,7 +12,7 @@ You are an expert copy editor specializing in marketing and conversion copy. You
 ## Core Philosophy
 
 **Check for product marketing context first:**
-If `.claude/product-marketing-context.md` exists, read it before editing. Use brand voice and customer language from that context to guide your edits.
+If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before editing. Use brand voice and customer language from that context to guide your edits.
 
 Good copy editing isn't about rewriting—it's about enhancing. Each pass focuses on one dimension, catching issues that get missed when you try to fix everything at once.
 
@@ -430,9 +431,9 @@ This iterative process ensures each edit doesn't create new problems while respe
 ## Related Skills
 
 - **copywriting**: For writing new copy from scratch (use this skill to edit after your first draft is complete)
-- **page-cro**: For broader page optimization beyond copy
+- **cro**: For broader page optimization beyond copy
 - **marketing-psychology**: For understanding why certain edits improve conversion
-- **ab-test-setup**: For testing copy variations
+- **ab-testing**: For testing copy variations
 
 ---
 
@@ -443,4 +444,4 @@ This iterative process ensures each edit doesn't create new problems while respe
 | Writing new page copy from scratch | copywriting |
 | Reviewing and improving existing copy | copy-editing (this skill) |
 | Editing copy you just wrote | copy-editing (this skill) |
-| Structural or strategic page changes | page-cro |
+| Structural or strategic page changes | cro |

skills/copy-editing/evals/evals.json

@@ -0,0 +1,89 @@
+{
+  "skill_name": "copy-editing",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Edit this homepage copy for us: 'Welcome to CloudSync! We are very excited to offer you an innovative, cutting-edge platform that seamlessly integrates with your existing tools. Our powerful solution helps businesses of all sizes optimize their workflows and drive meaningful results. Get started today and experience the difference!'",
+      "expected_output": "Should check for product-marketing-context.md first. Should apply the Seven Sweeps Framework systematically. Sweep 1 (Clarity): identify vague language ('optimize workflows,' 'drive meaningful results,' 'experience the difference'). Sweep 2 (Voice & Tone): flag 'Welcome to' as weak opening, 'we are very excited' as company-focused. Sweep 3 (So What): question what specific value is being offered. Sweep 4 (Prove It): note no proof points, stats, or evidence. Sweep 5 (Specificity): flag 'businesses of all sizes,' 'existing tools,' 'powerful solution' as generic. Sweep 6 (Heightened Emotion): assess emotional impact. Sweep 7 (Zero Risk): check for trust signals. Should provide a rewritten version addressing all issues.",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Applies Seven Sweeps Framework",
+        "Identifies vague language (Clarity sweep)",
+        "Flags weak opening and company-focused language (Voice & Tone sweep)",
+        "Questions missing value proposition (So What sweep)",
+        "Notes missing proof points (Prove It sweep)",
+        "Flags generic terms (Specificity sweep)",
+        "Provides a rewritten version"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "Quick edit on this CTA section: 'Ready to take your business to the next level? Our team of dedicated professionals is standing by to help you achieve your goals. Click here to learn more about how we can help you succeed.'",
+      "expected_output": "Should apply the quick-pass editing checks. Should identify: 'take your business to the next level' (cliché), 'team of dedicated professionals' (filler), 'standing by' (passive), 'click here' (weak CTA), 'learn more' (vague action), 'help you succeed' (generic). Should apply word-level, sentence-level, and paragraph-level checks. Should rewrite with specific value prop, active voice, and strong action-oriented CTA. Should be concise since this was requested as a 'quick edit.'",
+      "assertions": [
+        "Identifies clichés and filler phrases",
+        "Flags 'click here' and 'learn more' as weak",
+        "Applies word-level and sentence-level checks",
+        "Rewrites with specific value and strong CTA",
+        "Uses active voice in rewrite",
+        "Keeps response concise for a quick edit"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "edit this product description, it feels too long and wordy: 'Our comprehensive project management solution provides teams with a robust set of tools that enable them to efficiently plan, execute, and monitor their projects from start to finish. With our intuitive interface, powerful analytics dashboard, and seamless integration capabilities, you can ensure that every aspect of your project is managed with precision and care. Whether you're a small startup or a large enterprise, our platform scales to meet your unique needs and requirements, helping you deliver projects on time and within budget every single time.'",
+      "expected_output": "Should trigger on casual phrasing. Should apply the Clarity and Specificity sweeps primarily. Should identify: redundancy ('plan, execute, and monitor' overlaps with 'from start to finish'), filler words ('comprehensive,' 'robust,' 'efficiently,' 'seamless,' 'unique'), hedge phrases ('ensuring every aspect,' 'with precision and care'), and generic claims ('scales to meet your needs,' 'on time and within budget every single time'). Should cut the copy significantly (probably by 50%+). Should provide a tighter rewrite that says the same thing in fewer, more specific words.",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Identifies redundancy in the copy",
+        "Identifies filler words and hedge phrases",
+        "Identifies generic claims",
+        "Cuts copy significantly (50%+ reduction)",
+        "Provides tighter rewrite with specific language"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "Review this testimonial section and improve it: 'CloudSync is great! It really helped our company. The team was very responsive and the product works well. We would recommend it to anyone looking for a solution. - John S., CEO'",
+      "expected_output": "Should apply the Prove It and Specificity sweeps. Should identify the testimonial as too vague to be persuasive ('great,' 'really helped,' 'works well,' 'anyone looking for a solution'). Should recommend replacing with specific results ('reduced project delivery time by 30%'), specific context ('team of 45 engineers'), and specific outcomes. Should suggest questions to ask the customer for a better testimonial. Should not fabricate specific numbers but should provide a template showing what a strong testimonial looks like.",
+      "assertions": [
+        "Applies Prove It and Specificity sweeps",
+        "Identifies testimonial as too vague",
+        "Recommends specific results and context",
+        "Suggests questions to get better testimonial",
+        "Does not fabricate specific numbers",
+        "Provides template for strong testimonial"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "I need you to apply the 'So What' and 'Zero Risk' sweeps to this pricing page copy: 'Our Pro plan includes unlimited projects, advanced reporting, priority support, and custom integrations. Starting at $99/month.'",
+      "expected_output": "Should apply specifically the So What and Zero Risk sweeps as requested. So What: for each feature, ask 'so what does this mean for the customer?' — unlimited projects (what does that enable?), advanced reporting (what decisions can they make?), priority support (what does that mean in practice? response time?), custom integrations (which ones? what workflow does it enable?). Zero Risk: identify missing trust signals — no guarantee, no trial mention, no social proof near pricing, no 'cancel anytime' assurance. Should provide rewritten copy addressing both sweeps.",
+      "assertions": [
+        "Applies So What sweep to each feature",
+        "Translates features to customer benefits",
+        "Applies Zero Risk sweep",
+        "Identifies missing trust signals",
+        "Suggests guarantee, trial, or cancel-anytime language",
+        "Provides rewritten copy addressing both sweeps"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "Write fresh homepage copy for our new product. We're launching a CRM for real estate agents.",
+      "expected_output": "Should recognize this is a copywriting-from-scratch task, not copy editing. Should defer to or cross-reference the copywriting skill, which handles writing new copy from scratch. Copy-editing is specifically for improving existing copy. Should make this distinction clear.",
+      "assertions": [
+        "Recognizes this as writing new copy, not editing existing copy",
+        "References or defers to copywriting skill",
+        "Explains that copy-editing is for improving existing copy",
+        "Does not attempt to write full page copy from scratch"
+      ],
+      "files": []
+    }
+  ]
+}

skills/copy-editing/references/plain-english-alternatives.md

@@ -6,6 +6,24 @@ Source: Plain English Campaign A-Z of Alternative Words (2001), Australian Gover
 
 ---
 
+## Contents
+- A
+- B
+- C
+- D
+- E
+- F
+- G-H
+- I
+- L-M
+- N-O
+- P
+- R
+- S
+- T-U
+- V-Z
+- Phrases to Remove Entirely
+
 ## A
 
 | Complex | Plain Alternative |

skills/copywriting/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: copywriting
-version: 1.0.0
-description: When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," or "CTA copy." For email copy, see email-sequence. For popup copy, see popup-cro.
+description: When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," "CTA copy," "value proposition," "tagline," "subheadline," "hero section copy," "above the fold," "this copy is weak," "make this more compelling," or "help me describe my product." Use this whenever someone is working on website text that needs to persuade or convert. For email copy, see emails. For popup copy, see popups. For editing existing copy, see copy-editing.
+metadata:
+  version: 1.1.0
 ---
 
 # Copywriting
@@ -11,7 +12,7 @@ You are an expert conversion copywriter. Your goal is to write marketing copy th
 ## Before Writing
 
 **Check for product marketing context first:**
-If `.claude/product-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
+If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
 
 Gather this context (ask if not provided):
 
@@ -66,7 +67,7 @@ Each section should advance one argument. Build a logical flow down the page.
 3. **Active over passive** — "We generate reports" not "Reports are generated"
 4. **Confident over qualified** — Remove "almost," "very," "really"
 5. **Show over tell** — Describe the outcome instead of using adverbs
-6. **Honest over sensational** — Never fabricate statistics or testimonials
+6. **Honest over sensational** — Fabricated statistics or testimonials erode trust and create legal liability
 
 ### Quick Quality Check
 
@@ -245,7 +246,7 @@ For headlines and CTAs, provide 2-3 options:
 ## Related Skills
 
 - **copy-editing**: For polishing existing copy (use after your draft)
-- **page-cro**: If page structure/strategy needs work, not just copy
-- **email-sequence**: For email copywriting
-- **popup-cro**: For popup and modal copy
-- **ab-test-setup**: To test copy variations
+- **cro**: If page structure/strategy needs work, not just copy
+- **emails**: For email copywriting
+- **popups**: For popup and modal copy
+- **ab-testing**: To test copy variations

skills/copywriting/evals/evals.json

@@ -0,0 +1,111 @@
+{
+  "skill_name": "copywriting",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Write homepage copy for a SaaS tool that automates employee onboarding. Target audience is HR directors at mid-size companies (200-2000 employees). Main differentiator is that it integrates with all major HRIS systems and cuts onboarding time from 2 weeks to 2 days.",
+      "expected_output": "Should check for product-marketing-context.md first. Should write full page copy organized by section: Headline, Subheadline, CTA (above the fold), then Social Proof, Problem/Pain, Solution/Benefits, How It Works, Objection Handling, and Final CTA. Should follow copywriting principles: clarity over cleverness, benefits over features, specificity (use the '2 weeks to 2 days' stat), customer language. Headline should communicate core value proposition. CTAs should be action-oriented ('Start Free Trial' not 'Submit'). Should provide 2-3 headline alternatives with rationale. Should include annotations explaining key copy choices. Should include meta content (SEO page title and meta description).",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Writes full page copy organized by section",
+        "Includes Headline, Subheadline, and CTA above the fold",
+        "Includes Social Proof, Problem/Pain, Solution/Benefits, How It Works sections",
+        "Uses the '2 weeks to 2 days' specificity in copy",
+        "CTAs are action-oriented, not generic",
+        "Provides 2-3 headline alternatives with rationale",
+        "Includes annotations explaining copy choices",
+        "Includes meta content (SEO title and meta description)"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "Rewrite this headline: 'An Innovative AI-Powered Platform for Streamlined Business Operations' — it's for a B2B SaaS tool that helps small businesses manage invoicing and payments.",
+      "expected_output": "Should identify problems: jargon ('innovative,' 'AI-powered,' 'streamlined,' 'business operations'), too vague, company language not customer language. Should apply copywriting principles — specificity over vagueness, benefits over features, customer language over company language. Should provide 2-3 alternative headlines using formulas like '{Achieve outcome} without {pain point}' or 'The {category} for {audience}'. Each alternative should include rationale. Should also suggest a subheadline that adds specificity.",
+      "assertions": [
+        "Identifies jargon in original headline",
+        "Identifies vagueness as a problem",
+        "Identifies company language vs customer language issue",
+        "Provides 2-3 alternative headlines",
+        "Alternatives use headline formulas from the skill",
+        "Each alternative includes rationale",
+        "Suggests a subheadline"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "i need copy for my pricing page. we have three plans: starter ($29/mo), pro ($79/mo), business ($199/mo). it's a social media scheduling tool for marketers",
+      "expected_output": "Should trigger on the casual phrasing. Should ask or infer audience context. Should apply Pricing Page guidance: help visitors choose the right plan, address 'which is right for me?' anxiety, make recommended plan obvious. Should write plan names, descriptions, feature lists with benefit-oriented copy (not just feature names). Should include a page headline that addresses the pricing decision. CTAs should be specific per plan. Should handle objection handling (FAQ copy). Should provide alternatives for key elements.",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Applies Pricing Page guidance",
+        "Addresses 'which plan is right for me' anxiety",
+        "Makes recommended plan obvious",
+        "Writes benefit-oriented feature copy, not just feature names",
+        "Includes page headline",
+        "CTAs are specific per plan",
+        "Includes FAQ or objection handling copy",
+        "Provides alternatives for key elements"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "Write copy for our About page. We're a 3-person startup that built a developer tool for database migrations. Founded because we kept losing data during migrations at our last jobs. Tone should be professional but human.",
+      "expected_output": "Should apply About Page guidance: tell the story of why you exist, connect mission to customer benefit, still include a CTA. Should adapt voice and tone to 'professional but human' as specified. Should tell the founder origin story authentically. Should connect the personal pain to the customer's pain. Should include a CTA even on the About page. Copy should follow style rules: active voice, confident, specific. Should NOT be overly corporate or generic.",
+      "assertions": [
+        "Applies About Page guidance",
+        "Tells the story of why the company exists",
+        "Connects mission to customer benefit",
+        "Includes a CTA",
+        "Adapts tone to professional but human",
+        "Uses the founder origin story",
+        "Connects personal pain to customer pain",
+        "Uses active voice",
+        "Avoids corporate jargon"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "Can you improve this CTA? We currently have 'Learn More' on our feature page for our analytics dashboard product.",
+      "expected_output": "Should immediately identify 'Learn More' as a weak CTA per the guidelines. Should apply the CTA formula: [Action Verb] + [What They Get] + [Qualifier]. Should provide 2-3 strong alternatives like 'See the Dashboard in Action,' 'Start Your Free Trial,' or 'Explore Analytics Features.' Each alternative should include rationale and context for when it works best. Should also consider CTA hierarchy — whether this is a primary or secondary CTA, and suggest complementary CTAs if relevant.",
+      "assertions": [
+        "Identifies 'Learn More' as a weak CTA",
+        "Applies the CTA formula from the skill",
+        "Provides 2-3 strong alternatives",
+        "Each alternative includes rationale",
+        "Considers CTA hierarchy (primary vs secondary)",
+        "Suggests complementary CTAs"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "Write me a 5-email welcome sequence for new trial users of our project management tool.",
+      "expected_output": "Should recognize this is an email copywriting task, not page copywriting. Should defer to or cross-reference the email-sequence skill, which specifically handles email sequences, drip campaigns, and lifecycle emails. May provide brief general guidance but should make clear that email-sequence is the right skill for this task.",
+      "assertions": [
+        "Recognizes this as email sequence work",
+        "References or defers to email-sequence skill",
+        "Does not attempt to write a full email sequence using page copywriting patterns"
+      ],
+      "files": []
+    },
+    {
+      "id": 7,
+      "prompt": "Review this copy and tell me what's wrong: 'We are extremely excited to announce our revolutionary, cutting-edge platform that will totally transform how businesses optimize their workflows! Sign up now!!'",
+      "expected_output": "Should apply the Quick Quality Check. Should identify: exclamation points (remove them), marketing buzzwords without substance ('revolutionary,' 'cutting-edge,' 'totally transform,' 'optimize'), passive/weak constructions ('we are excited to announce'), vague language ('workflows'). Should apply writing style rules: simple over complex, specific over vague, confident over qualified, show over tell. Should rewrite the copy following these principles. Should provide 2-3 alternatives.",
+      "assertions": [
+        "Identifies exclamation point overuse",
+        "Identifies marketing buzzwords without substance",
+        "Identifies vague language",
+        "Applies writing style rules",
+        "Rewrites the copy following principles",
+        "Provides alternatives",
+        "Result is specific, clear, and jargon-free"
+      ],
+      "files": []
+    }
+  ]
+}

skills/copywriting/references/copy-frameworks.md

@@ -2,6 +2,12 @@
 
 Headline formulas, page section types, and structural templates.
 
+## Contents
+- Headline Formulas (outcome-focused, problem-focused, audience-focused, differentiation-focused, proof-focused, additional formulas)
+- Landing Page Section Types (core sections, supporting sections)
+- Page Structure Templates (feature-heavy page, varied engaging page, compact landing page, enterprise/B2B landing page, product launch page)
+- Section Writing Tips (problem section, benefits section, how it works section, testimonial selection)
+
 ## Headline Formulas
 
 ### Outcome-Focused

skills/copywriting/references/natural-transitions.md

@@ -6,6 +6,26 @@ Adapted from: University of Manchester Academic Phrasebank (2023), Plain English
 
 ---
 
+## Contents
+- Previewing Content Structure
+- Introducing a New Topic
+- Referring Back
+- Moving Between Sections
+- Indicating Addition
+- Indicating Contrast
+- Indicating Similarity
+- Indicating Cause and Effect
+- Giving Examples
+- Emphasising Key Points
+- Providing Evidence (neutral attribution, expert quotes, supporting claims)
+- Summarising Sections
+- Concluding Content
+- Question-Based Transitions
+- List Introductions
+- Hedging Language
+- Best Practice Guidelines
+- Transitions to Avoid (AI Tells)
+
 ## Previewing Content Structure
 
 Use to orient readers and set expectations:

skills/cro/SKILL.md

@@ -1,29 +1,36 @@
 ---
-name: page-cro
-version: 1.0.0
-description: When the user wants to optimize, improve, or increase conversions on any marketing page — including homepage, landing pages, pricing pages, feature pages, or blog posts. Also use when the user says "CRO," "conversion rate optimization," "this page isn't converting," "improve conversions," or "why isn't this page working." For signup/registration flows, see signup-flow-cro. For post-signup activation, see onboarding-cro. For forms outside of signup, see form-cro. For popups/modals, see popup-cro.
+name: cro
+description: "When the user wants to optimize, improve, or increase conversions on any marketing page or form. Also use when the user says 'CRO,' 'conversion rate optimization,' 'this page isn't converting,' 'improve conversions,' 'why isn't this page working,' 'my landing page sucks,' 'nobody's converting,' 'low conversion rate,' 'bounce rate is too high,' 'form optimization,' 'lead form conversions,' 'form friction,' 'nobody fills out our form,' 'form abandonment,' or 'too many fields.' Use this for any conversion optimization on pages or forms. For signup/registration flows, see signup. For post-signup activation, see onboarding. For popups/modals, see popups. For paywalls, see paywalls."
+metadata:
+  version: 1.0.0
 ---
 
-# Page Conversion Rate Optimization (CRO)
+# Conversion Rate Optimization (CRO)
 
-You are a conversion rate optimization expert. Your goal is to analyze marketing pages and provide actionable recommendations to improve conversion rates.
+You are a conversion rate optimization expert. Your goal is to analyze marketing pages and forms, then provide actionable recommendations to improve conversion rates.
 
 ## Initial Assessment
 
 **Check for product marketing context first:**
-If `.claude/product-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
+If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` 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 providing recommendations, identify:
 
-1. **Page Type**: Homepage, landing page, pricing, feature, blog, about, other
-2. **Primary Conversion Goal**: Sign up, request demo, purchase, subscribe, download, contact sales
-3. **Traffic Context**: Where are visitors coming from? (organic, paid, email, social)
+1. **What needs optimization?** — A page, a form, or both
+2. **Page Type** (if page): Homepage, landing page, pricing, feature, blog, about
+3. **Form Type** (if form): Lead capture, contact, demo request, application, survey, checkout
+4. **Primary Conversion Goal**: Sign up, request demo, purchase, subscribe, download, contact sales
+5. **Traffic Context**: Where are visitors coming from? (organic, paid, email, social)
+
+**For page optimization**: See [references/page.md](references/page.md)
+
+**For form optimization**: See [references/form.md](references/form.md)
 
 ---
 
 ## CRO Analysis Framework
 
-Analyze the page across these dimensions, in order of impact:
+Analyze across these dimensions, in order of impact:
 
 ### 1. Value Proposition Clarity (Highest Impact)
 
@@ -169,13 +176,14 @@ When recommending experiments, consider tests for:
 3. What does your signup/purchase flow look like after this page?
 4. Do you have user research, heatmaps, or session recordings?
 5. What have you already tried?
+6. What type of form are you optimizing (if applicable)?
 
 ---
 
 ## Related Skills
 
-- **signup-flow-cro**: If the issue is in the signup process itself
-- **form-cro**: If forms on the page need optimization
-- **popup-cro**: If considering popups as part of the strategy
+- **signup**: If the issue is in the signup process itself
+- **popups**: If considering popups as part of the strategy
+- **paywalls**: For in-app upgrade moments and trial expiration
 - **copywriting**: If the page needs a complete copy rewrite
-- **ab-test-setup**: To properly test recommended changes
+- **ab-testing**: To properly test recommended changes

skills/cro/references/experiments.md

@@ -2,6 +2,15 @@
 
 Comprehensive list of A/B tests and experiments organized by page type.
 
+## Contents
+- Homepage Experiments (Hero Section, Trust & Social Proof, Features & Content, Navigation & UX)
+- Pricing Page Experiments (Price Presentation, Pricing UX, Objection Handling, Trust Signals)
+- Demo Request Page Experiments (Form Optimization, Page Content, CTA & Routing)
+- Resource/Blog Page Experiments (Content CTAs, Resource Section)
+- Landing Page Experiments (Message Match, Conversion Focus, Page Length)
+- Feature Page Experiments (Feature Presentation, Conversion Path)
+- Cross-Page Experiments (Site-Wide Tests, Navigation Tests)
+
 ## Homepage Experiments
 
 ### Hero Section

skills/cro/references/form.md

@@ -1,17 +1,11 @@
----
-name: form-cro
-version: 1.0.0
-description: When the user wants to optimize any form that is NOT signup/registration — including lead capture forms, contact forms, demo request forms, application forms, survey forms, or checkout forms. Also use when the user mentions "form optimization," "lead form conversions," "form friction," "form fields," "form completion rate," or "contact form." For signup/registration forms, see signup-flow-cro. For popups containing forms, see popup-cro.
----
+# Form CRO Reference
 
-# Form CRO
-
-You are an expert in form optimization. Your goal is to maximize form completion rates while capturing the data that matters.
+Detailed form optimization guidance. Use alongside the main CRO skill.
 
 ## Initial Assessment
 
 **Check for product marketing context first:**
-If `.claude/product-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
+If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` 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 providing recommendations, identify:
 
@@ -119,7 +113,7 @@ For each field, ask:
 4. Logical grouping if many fields
 
 ### Labels and Placeholders
-- Labels: Always visible (not just placeholder)
+- Labels: Keep visible (not just placeholder) — placeholders disappear when typing, leaving users unsure what they're filling in
 - Placeholders: Examples, not labels
 - Help text: Only when genuinely helpful
 
@@ -422,7 +416,6 @@ Ideas to A/B test with expected outcomes
 
 ## Related Skills
 
-- **signup-flow-cro**: For account creation forms
-- **popup-cro**: For forms inside popups/modals
-- **page-cro**: For the page containing the form
-- **ab-test-setup**: For testing form changes
+- **signup**: For account creation forms
+- **popups**: For forms inside popups/modals
+- **ab-testing**: For testing form changes

skills/cro/references/page.md

@@ -0,0 +1,68 @@
+# Page CRO Reference
+
+Detailed page-level conversion optimization guidance. Use alongside the main CRO skill.
+
+## Page Type Audit Checklists
+
+### Homepage
+
+- [ ] Hero clearly communicates what you do and for whom
+- [ ] Primary CTA visible above the fold
+- [ ] Social proof within first viewport
+- [ ] Clear navigation to key pages (pricing, features, use cases)
+- [ ] Both "ready to buy" and "still researching" paths available
+- [ ] Mobile experience tested and optimized
+
+### Landing Page
+
+- [ ] Message matches the traffic source (ad, email, social post)
+- [ ] Single conversion goal — no competing CTAs
+- [ ] Navigation removed or minimized
+- [ ] Complete argument made on one page (no required clicks)
+- [ ] Form or CTA repeated after key sections
+- [ ] Page speed under 3 seconds
+
+### Pricing Page
+
+- [ ] Plans are easy to compare at a glance
+- [ ] Recommended plan is visually highlighted
+- [ ] Feature comparison table included
+- [ ] Annual vs monthly toggle with savings shown
+- [ ] FAQ addresses common pricing objections
+- [ ] Free trial or money-back guarantee prominent
+- [ ] Enterprise/contact option for larger buyers
+
+### Feature Page
+
+- [ ] Feature connected to a clear business benefit
+- [ ] Real use cases or examples shown
+- [ ] Screenshot or demo of the feature in action
+- [ ] CTA to try the feature (not just "learn more")
+- [ ] Related features cross-linked
+
+### Blog Post
+
+- [ ] Contextual CTA matching the content topic
+- [ ] Inline CTA at a natural stopping point (not just end)
+- [ ] Content upgrade or lead magnet related to the topic
+- [ ] Author bio with credibility signals
+- [ ] Related posts suggested
+
+## Above-the-Fold Priorities
+
+The first viewport should answer three questions:
+
+1. **What is this?** — Clear headline with the core value proposition
+2. **Why should I care?** — Subheadline connecting to the visitor's problem or desire
+3. **What do I do next?** — Visible primary CTA
+
+If a visitor can't answer all three within 5 seconds, the above-the-fold content needs work.
+
+## Mobile CRO Considerations
+
+- Thumb-friendly CTA buttons (min 44x44px)
+- Sticky CTA bar for long pages
+- Simplified forms (consider progressive disclosure)
+- Test with real devices, not just browser resize
+- Prioritize speed — mobile users are less patient
+- Consider mobile-specific CTAs (click-to-call, app deep links)

skills/customer-research/SKILL.md

@@ -0,0 +1,269 @@
+---
+name: customer-research
+description: When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," or "find out why customers churn/convert/buy." Use for both analyzing existing research assets AND gathering new research from online sources. For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.
+metadata:
+  version: 1.0.0
+---
+
+# Customer Research
+
+You are an expert customer researcher. Your goal is to help uncover what customers actually think, feel, say, and struggle with — so that everything from positioning to product to copy is grounded in reality rather than assumption.
+
+## Before Starting
+
+**Check for product marketing context first:**
+If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context to skip questions already answered.
+
+---
+
+## Two Modes of Research
+
+### Mode 1: Analyze Existing Assets
+You have raw research material (transcripts, surveys, reviews, tickets). Your job is to extract signal.
+
+### Mode 2: Go Find Research
+You need to gather intel from online sources (Reddit, G2, forums, communities, review sites). Your job is to know where to look and what to extract.
+
+Most engagements combine both. Establish which mode applies before proceeding.
+
+---
+
+## Mode 1: Analyzing Existing Research Assets
+
+### Asset Types
+
+**Customer interview / sales call transcripts**
+- Extract: pains, triggers, desired outcomes, language used, objections, alternatives considered
+- Look for: the moment they decided to look for a solution, what they tried before, what success looks like to them
+
+**Survey results**
+- Segment responses by customer tier, use case, or tenure before drawing conclusions
+- Flag: what open-ended answers say vs. what multiple-choice answers say (they often conflict)
+- Identify: the 20% of responses that contain the most useful signal
+
+**Customer support conversations**
+- Mine for: recurring complaints, confusion points, feature requests, and "I wish it could…" language
+- Categorize tickets before analyzing — don't treat all tickets as equal signal
+- Separate bugs from confusion from missing features from expectation mismatches
+
+**Win/loss interviews and churned customer notes**
+- Wins: what tipped the decision? What almost made them choose a competitor?
+- Losses and churn: was it price, features, fit, timing, or something else?
+- Segment by reason — don't average across different churn causes
+
+**NPS responses**
+- Passives and detractors are higher signal than promoters for improvement work
+- Pair scores with verbatims — a 9 with a specific complaint beats a 10 with no comment
+
+### Extraction Framework
+
+For each asset, extract:
+
+1. **Jobs to Be Done** — what outcome is the customer trying to achieve?
+   - Functional job: the task itself
+   - Emotional job: how they want to feel
+   - Social job: how they want to be perceived
+
+2. **Pain Points** — what's frustrating, broken, or inadequate about their current situation?
+   - Prioritize pains mentioned unprompted and with emotional language
+
+3. **Trigger Events** — what changed that made them seek a solution?
+   - Common triggers: team growth, new hire, missed target, embarrassing incident, competitor doing something
+
+4. **Desired Outcomes** — what does success look like in their words?
+   - Capture exact quotes, not paraphrases
+
+5. **Language and Vocabulary** — exact words and phrases customers use
+   - This is gold for copy. "We were drowning in spreadsheets" > "manual process inefficiency"
+
+6. **Alternatives Considered** — what else did they look at or try?
+   - Includes doing nothing, hiring someone, or building internally
+
+### Synthesis Steps
+
+After extracting from individual assets:
+
+1. **Cluster by theme** — group similar pains, outcomes, and triggers across assets
+2. **Frequency + intensity scoring** — how often does a theme appear, and how strongly is it felt?
+3. **Segment by customer profile** — do patterns differ by company size, role, use case, or tenure?
+4. **Identify the "money quotes"** — 5-10 verbatim quotes that best represent each theme
+5. **Flag contradictions** — where do customers say one thing but do another?
+
+### Research Quality Guardrails
+
+Label every insight with a confidence level before presenting it:
+
+| Confidence | Criteria |
+|------------|----------|
+| **High** | Theme appears in 3+ independent sources; mentioned unprompted; consistent across segments |
+| **Medium** | Theme appears in 2 sources, or only prompted, or limited to one segment |
+| **Low** | Single source; could be an outlier; needs validation |
+
+**Recency window**: Weight sources from the last 12 months more heavily. Markets shift — a 3-year-old transcript may reflect a different product and buyer.
+
+**Sample bias checks**:
+- Online reviewers skew toward power users and people with strong opinions
+- Support tickets skew toward problems, not value
+- Reddit skews technical and skeptical vs. mainstream buyers
+- Factor this in when drawing conclusions about "all customers"
+
+**Minimum viable sample**: Don't build personas or draw messaging conclusions from fewer than 5 independent data points per segment.
+
+---
+
+## Mode 2: Digital Watering Hole Research
+
+Online communities are where customers speak without a filter. The goal is to find authentic, unmoderated language about the problem space.
+
+### Where to Look
+
+Choose sources based on your ICP type — then read `references/source-guides.md` for detailed playbooks, search operators, and per-platform extraction tips.
+
+| ICP Type | Primary Sources |
+|----------|----------------|
+| B2B SaaS / technical buyers | Reddit (role-specific subs), G2/Capterra, Hacker News, LinkedIn, Indie Hackers |
+| SMB / founders | Reddit (r/entrepreneur, r/smallbusiness), Indie Hackers, Product Hunt, Facebook Groups |
+| Developer / DevOps | r/devops, r/programming, Hacker News, Stack Overflow, Discord servers |
+| B2C / consumer | App store reviews (1-3 star), Reddit hobby/lifestyle subs, YouTube comments, TikTok/Instagram comments |
+| Enterprise | LinkedIn, industry analyst reports, G2 Enterprise filter, job postings |
+
+**Quick decision guide:**
+- Have a product category? → Start with G2/Capterra reviews (yours + competitors)
+- Need raw language? → Reddit and YouTube comments
+- Need trigger events? → LinkedIn posts, job postings, Hacker News "Ask HN" threads
+- Need competitive intel? → Competitor 4-star reviews on G2; Product Hunt discussions
+
+### What to Extract from Each Source
+
+For every piece of content you find:
+
+| Field | What to Capture |
+|-------|----------------|
+| Source | Platform, thread URL, date |
+| Verbatim quote | Exact words — don't paraphrase |
+| Context | What prompted the comment? |
+| Sentiment | Positive / negative / neutral / frustrated |
+| Theme tag | Pain / trigger / outcome / alternative / language |
+| Customer profile signals | Role, company size, industry hints from the post |
+
+### Research Synthesis Template
+
+After gathering from multiple sources, synthesize into:
+
+```
+## Top Themes (ranked by frequency × intensity)
+
+### Theme 1: [Name]
+**Summary**: [1-2 sentences]
+**Frequency**: Appeared in X of Y sources
+**Intensity**: High / Medium / Low (based on emotional language used)
+**Representative quotes**:
+- "[exact quote]" — [source, date]
+- "[exact quote]" — [source, date]
+**Implications**: What this means for messaging / product / positioning
+
+### Theme 2: ...
+```
+
+---
+
+## Persona Generation
+
+Personas should be built from research, not invented. Don't create a persona until you have at least 5-10 data points (interviews, reviews, or community posts) from a consistent segment.
+
+### Persona Structure
+
+```
+## [Persona Name] — [Role/Title]
+
+**Profile**
+- Title range: [e.g., "Marketing Manager to VP of Marketing"]
+- Company size: [e.g., "50–500 employees, Series A–C SaaS"]
+- Industry: [if narrow]
+- Reports to: [who]
+- Team size managed: [if relevant]
+
+**Primary Job to Be Done**
+[One sentence: what outcome are they trying to achieve in their role?]
+
+**Trigger Events**
+What causes them to start looking for a solution like yours?
+- [trigger 1]
+- [trigger 2]
+
+**Top Pains**
+1. [Pain — in their words if possible]
+2. [Pain]
+3. [Pain]
+
+**Desired Outcomes**
+- [What success looks like to them]
+- [How they measure it]
+- [How it makes them look to their boss/team]
+
+**Objections and Fears**
+- [What makes them hesitate to buy or switch]
+
+**Alternatives They Consider**
+- [Competitor, DIY, do nothing, hire someone]
+
+**Key Vocabulary**
+Words and phrases they actually use (sourced from research):
+- "[phrase]"
+- "[phrase]"
+
+**How to Reach Them**
+- Channels: [where they spend time]
+- Content they consume: [formats, topics]
+- Influencers/communities they trust: [specific names if known]
+```
+
+### Persona Anti-Patterns
+
+- **Don't name them cutely** ("Marketing Mary") unless your team finds it helpful — it's often a distraction
+- **Don't average across segments** — a persona that represents everyone represents no one
+- **Don't invent details** — if you don't have data on something, leave it blank rather than filling it in
+- **Revisit quarterly** — personas decay as your market and product evolve
+
+---
+
+## Deliverable Formats
+
+Depending on what the user needs, offer:
+
+1. **Research synthesis report** — themes, quotes, patterns, and implications
+2. **VOC quote bank** — organized verbatim quotes by theme, for use in copy
+3. **Persona document** — 1-3 personas built from the research
+4. **Jobs-to-be-done map** — functional, emotional, and social jobs by segment
+5. **Competitive intelligence summary** — what customers say about competitors vs. you
+6. **Research gap analysis** — what you still don't know and how to find it
+
+Ask the user which deliverable(s) they need before generating output.
+
+---
+
+## Questions to Ask Before Proceeding
+
+If context is unclear:
+
+1. **What's the goal?** Improve messaging? Build personas? Find product gaps? Understand churn?
+2. **What do you already have?** (transcripts, surveys, tickets, G2 reviews, nothing)
+3. **Who is the target segment?** (all customers, a specific tier, churned users, prospects who didn't buy)
+4. **What's your product?** (if not in the product marketing context file)
+5. **What do you want delivered?** (synthesis report, persona, quote bank, competitive intel)
+
+Don't ask all five at once — lead with #1 and #2, then follow up as needed.
+
+---
+
+## Related Skills
+
+| When to hand off | Skill |
+|-----------------|-------|
+| Writing copy informed by the research | `copywriting` |
+| Optimizing a page using VOC insights | `cro` |
+| Building a competitor comparison page | `competitors` |
+| Creating a churn prevention strategy from churn research | `churn-prevention` |
+| Planning paid ads informed by research | `paid-ads` |
+| Writing cold email using research on pain/trigger | `cold-email` |
+| Planning content based on discovered topics | `content-strategy` |

skills/customer-research/evals/evals.json

@@ -0,0 +1,162 @@
+{
+  "skill_name": "customer-research",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "I have 20 customer interview transcripts. Help me analyze them.",
+      "expected_output": "Should check for product-marketing-context.md first. Should ask about the goal before analyzing (improve messaging, build personas, find product gaps, etc.). Should apply the extraction framework: jobs to be done, pain points, trigger events, desired outcomes, language/vocabulary, alternatives considered. Should recommend clustering by theme, frequency + intensity scoring, and identifying money quotes. Should ask which deliverable is needed.",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Asks about the goal before diving in (improve messaging, build personas, find gaps, etc.)",
+        "Mentions extracting jobs to be done, pain points, and desired outcomes",
+        "Suggests organizing quotes by theme",
+        "References frequency and intensity scoring",
+        "Asks which deliverable is needed"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "I want to do ICP research but I don't have any customer interviews yet.",
+      "expected_output": "Should check for product-marketing-context.md first. Should recommend digital watering hole research as a starting point. Should mention Reddit, G2, Capterra, forums, or niche communities as sources. Should offer to plan a research approach and explain what to extract from online sources. Should note this is Mode 2 and ask what product/category to research.",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Recommends digital watering hole research as an alternative",
+        "Mentions Reddit, G2, or review sites as starting points",
+        "Asks what product or category to research",
+        "Offers to help extract insights from online sources"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "Mine Reddit and G2 to understand what people hate about project management software.",
+      "expected_output": "Should check for product-marketing-context.md first. Should identify relevant subreddits (r/projectmanagement, r/productivity, r/agile) and search strategies. Should recommend reading 3-star and 1-star G2 reviews and competitor 4-star reviews. Should plan to extract verbatim quotes, pain themes, and switching triggers. Should apply the extraction table (source, quote, context, sentiment, theme tag, profile signals).",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Identifies relevant subreddits or search strategies for project management",
+        "Suggests reading 3-star and 1-star G2 reviews",
+        "Recommends competitor 4-star reviews for buried complaints",
+        "Plans to extract verbatim quotes and pain themes",
+        "Mentions what to look for: complaints, workarounds, switching triggers"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "Build me a customer persona for a marketing manager at a B2B SaaS company.",
+      "expected_output": "Should check for product-marketing-context.md first. Should ask if there is existing research to build from before generating a persona. Should warn against inventing details without data. Should use the persona structure: profile, primary JTBD, trigger events, top pains, desired outcomes, objections, alternatives, key vocabulary, how to reach them. Should note that personas should be built from at least 5-10 data points.",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Asks if there is existing research to build from before inventing details",
+        "Warns against creating personas without data",
+        "Includes jobs to be done, pains, triggers, and desired outcomes in persona structure",
+        "Mentions the need to capture actual customer vocabulary",
+        "Notes minimum data threshold (5-10 data points)"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "I have 6 months of customer support tickets. What insights can I pull from them?",
+      "expected_output": "Should check for product-marketing-context.md first. Should recommend categorizing tickets before analyzing (bugs vs. confusion vs. feature requests vs. expectation mismatches). Should warn against treating all tickets as equal signal. Should suggest extracting recurring language, patterns, and 'I wish it could…' phrases. Should ask about the goal — product improvement, messaging, reducing support load, or something else.",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Recommends categorizing tickets before analyzing (bugs vs confusion vs feature requests)",
+        "Warns against treating all tickets as equal signal",
+        "Mentions extracting recurring language and patterns",
+        "Asks about the goal — product improvement, messaging, or something else"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "What are customers saying about my competitors on review sites?",
+      "expected_output": "Should check for product-marketing-context.md first. Should ask which competitors to research. Should recommend G2 and Capterra as primary sources. Should specifically call out reading competitor 4-star reviews for buried complaints. Should describe what to extract: what they love (battlecard intel), what frustrates them (opportunities), unmet needs. Should use the review mining template.",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Recommends reading competitor 4-star reviews specifically for buried complaints",
+        "Mentions G2 or Capterra as sources",
+        "Describes what to extract: what they love, what frustrates them, unmet needs",
+        "Frames as competitive intelligence input"
+      ],
+      "files": []
+    },
+    {
+      "id": 7,
+      "prompt": "Help me do voice of customer research for a new SaaS in the HR space.",
+      "expected_output": "Should check for product-marketing-context.md first. Should ask about the specific ICP segment within HR (recruiter, HR generalist, CHRO, etc.). Should suggest relevant digital watering holes: r/humanresources, r/recruiting, HR Slack communities, G2 HR category, LinkedIn. Should plan to extract verbatim language for copy use. Should offer to produce a VOC quote bank as a deliverable.",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Asks about target ICP segment within HR",
+        "Suggests relevant digital watering holes (subreddits, G2 categories, communities)",
+        "Plans to extract verbatim language for copy use",
+        "Mentions organizing findings into a VOC quote bank"
+      ],
+      "files": []
+    },
+    {
+      "id": 8,
+      "prompt": "I want to understand why customers churn. I have exit survey results.",
+      "expected_output": "Should check for product-marketing-context.md first. Should recommend segmenting churn reasons before analyzing — do not average across different causes. Should suggest pairing open-ended responses with quantitative data. Should ask if win/loss interview data or support tickets are also available. Should apply confidence labels (high/med/low) based on sample size and source consistency.",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Recommends segmenting churn reasons before analyzing",
+        "Warns against averaging across different churn causes",
+        "Suggests pairing open-ended responses with quantitative data",
+        "Asks if win/loss interview data is also available"
+      ],
+      "files": []
+    },
+    {
+      "id": 9,
+      "prompt": "Find the digital watering holes where DevOps engineers talk shop.",
+      "expected_output": "Should check for product-marketing-context.md first. Should identify specific relevant communities: r/devops, r/sysadmin, Hacker News, DevOps-focused Discord/Slack groups, LinkedIn, Stack Overflow. Should suggest what to search for in those communities. Should describe what signal to extract from each source type and reference source-guides.md for detailed playbooks.",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Mentions specific relevant communities (r/devops, Hacker News, LinkedIn, Discord)",
+        "Suggests what to search for in those communities",
+        "Describes what signal to extract from each source type"
+      ],
+      "files": []
+    },
+    {
+      "id": 10,
+      "prompt": "Turn my customer research into messaging I can use on my homepage.",
+      "expected_output": "Should check for product-marketing-context.md first. Should extract VOC language and top themes before moving to copy. Should identify the highest-signal quotes and language patterns. Should produce a VOC summary or quote bank, then hand off to the copywriting skill for the actual copy writing step rather than writing homepage copy directly.",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Extracts the VOC language and themes first before jumping to copy",
+        "Identifies the highest-signal quotes for messaging",
+        "References the copywriting skill for the actual copy writing step"
+      ],
+      "files": []
+    },
+    {
+      "id": 11,
+      "prompt": "I run a mobile fitness app and want to understand why users drop off after week 2.",
+      "expected_output": "Should check for product-marketing-context.md first. Should recognize this as a B2C research scenario. Should suggest B2C-appropriate sources: app store reviews (1-3 star), Reddit fitness communities, YouTube comment sections on fitness apps, TikTok/Instagram comments. Should also recommend in-app surveys and analyzing support tickets/reviews. Should frame around activation and habit formation research.",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Recognizes this as a B2C research scenario",
+        "Suggests app store reviews as a primary source",
+        "Mentions Reddit or community sources relevant to fitness/consumer apps",
+        "Frames around understanding drop-off triggers and desired outcomes"
+      ],
+      "files": []
+    },
+    {
+      "id": 12,
+      "prompt": "I have no existing research and don't know who my best customers are yet.",
+      "expected_output": "Should check for product-marketing-context.md first. Should treat this as a bootstrap research scenario. Should recommend starting with hypothesis formation before gathering data. Should suggest a minimum viable research plan: 5-10 customer interviews + digital watering hole scan. Should provide interview recruiting tips and what questions to ask. Should warn against building personas before collecting any data.",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Recognizes this as a zero-research bootstrap scenario",
+        "Recommends forming hypotheses before gathering data",
+        "Suggests a minimum viable research plan (interviews + online sources)",
+        "Warns against building personas without any data"
+      ],
+      "files": []
+    }
+  ]
+}

skills/customer-research/references/source-guides.md

@@ -0,0 +1,345 @@
+# Customer Research — Source Guides
+
+Detailed, source-by-source playbooks for gathering customer intelligence from online watering holes.
+
+---
+
+## Reddit Research
+
+### Finding the Right Subreddits
+
+Start by identifying where your ICP spends time, not where your product is discussed.
+
+**Discovery methods:**
+- Search `site:reddit.com "[job title] tools"` or `site:reddit.com "[problem category] software"`
+- Use [subreddit search tools](https://www.reddit.com/subreddits/search) with problem-space keywords
+- Look at what subreddits show up in Google results when you search ICP problems
+- Check what subreddits competitors' customers mention in reviews
+
+**Common high-value subreddits by category:**
+- B2B SaaS: r/sales, r/marketing, r/entrepreneur, r/startups, r/smallbusiness
+- Dev tools: r/programming, r/devops, r/webdev, r/cscareerquestions
+- Analytics/data: r/analytics, r/dataengineering, r/BusinessIntelligence
+- Marketing: r/PPC, r/SEO, r/emailmarketing, r/content_marketing
+- HR/recruiting: r/recruiting, r/humanresources, r/jobs
+- Finance/ops: r/accounting, r/financialplanning, r/projectmanagement
+
+### Search Operators
+
+```
+site:reddit.com/r/[subreddit] "[keyword]"
+site:reddit.com "[problem]" "recommend" OR "suggestion" OR "alternative"
+site:reddit.com "[competitor name]" "vs" OR "alternative" OR "switched"
+```
+
+### What to Look For
+
+**High-signal post types:**
+- "What tools do you use for X?" → reveals alternatives and vocab
+- "Frustrated with [competitor], looking for alternatives" → reveals pain and switching triggers
+- "How do you handle X?" → reveals workflow and workarounds
+- "Is [your category] worth it?" → reveals objections and evaluation criteria
+- Complaint threads about competitors → reveals gaps you might fill
+
+**What to extract:**
+- The exact problem described in the post
+- Top-voted solutions (what do practitioners actually recommend?)
+- Complaints about existing solutions in comments
+- The language used — note specific words and phrases
+- Upvote patterns — consensus vs. controversy
+
+### Tools
+- Reddit's native search (limited but fast)
+- Google: `site:reddit.com [query]` (better results)
+- Pullpush.io — search archived Reddit posts (good for older threads)
+
+---
+
+## G2 and Review Site Mining
+
+### Your Own Product Reviews
+
+Read in this order for maximum signal:
+
+1. **3-star reviews** — these are the most honest. Customer liked it enough to stay but felt something was missing.
+2. **1-star reviews** — understand the failure modes. Separate product issues from support/onboarding issues.
+3. **5-star reviews** — extract the "what they love" language. These are your proof points.
+4. **4-star reviews** — often contain "the only thing I wish…" buried in praise.
+
+**What to extract:**
+- What they say they use it *for* (the job to be done)
+- What they say is hardest or most frustrating
+- What they compare it to ("coming from [X]", "better than [Y]")
+- Industry and role signals in reviewer profiles
+
+### Competitor Reviews on G2
+
+The 4-star competitor reviews are gold — customers who like the product but still have complaints.
+
+**G2 structure to exploit:**
+- "What do you like best?" → their strengths (your battlecard intel)
+- "What do you dislike?" → their weaknesses (your opportunities)
+- "What problems are you solving?" → the job to be done
+
+**Capterra** has similar structure. **Trustpilot** skews B2C. **AppSumo** reviews are useful for SMB/prosumer SaaS.
+
+### Review Mining Template
+
+For each competitor's 4-star reviews, extract:
+
+| Category | Notes |
+|----------|-------|
+| Job to be done | Why do they use the product? |
+| Top praise | What do they love (and might be hard for you to match)? |
+| Top complaint | What frustrates them? |
+| Switching context | Did they mention switching from something else? |
+| Unmet need | "I wish it could…" or "It would be better if…" |
+
+---
+
+## Indie Hackers and Product Hunt
+
+### Indie Hackers
+
+Strong signal for founder/builder/SMB ICP.
+
+**Where to look:**
+- "Ask IH" posts: questions about problems your product solves
+- Milestone posts: when founders describe their stack, they reveal tool preferences and pain
+- Comment threads on product launches in your category
+
+**Search:** `site:indiehackers.com "[problem]"` or use IH's native search.
+
+### Product Hunt
+
+**Discussion tabs** on competing products are a research goldmine:
+- Questions asked = pre-sales concerns = objections
+- Comments = early adopter reactions = leading indicators of reception
+- "Alternatives to X" collections reveal the competitive landscape as users see it
+
+---
+
+## Hacker News
+
+Strong signal for technical/developer ICP. Skews toward builders and skeptics.
+
+**High-value searches:**
+- `site:news.ycombinator.com "[competitor or category]"`
+- HN "Ask HN: best tools for X" threads
+- "Show HN" posts for competitors — read the skeptical comments
+
+**What's different about HN:**
+- Users are more likely to critique underlying architecture and business model
+- Strong opinions about pricing models (especially anything subscription-based)
+- First principles objections you might not hear elsewhere
+
+---
+
+## LinkedIn Research
+
+### Posts and Comments
+
+Search for posts by practitioners describing their workflows:
+- "[Role] at [company size]" + problem keyword
+- "We used to [old way] but now we [new way]" stories
+- Posts asking for tool recommendations get comments from active buyers
+
+### Job Postings
+
+A job posting is a company's admission of a pain point.
+
+**What to look for:**
+- What tools are listed as "nice to have" vs. "required"? (reveals stack and adjacent tools)
+- What metrics and outcomes are mentioned in the role description?
+- What does the role spend most of its time doing? (reveals the job to be done)
+
+**Search:** `site:linkedin.com/jobs "[role title]" "[relevant tool or category]"`
+
+---
+
+## YouTube Comments
+
+### Finding High-Signal Videos
+
+- Tutorial videos for problems your product solves
+- "Best tools for X in [year]" roundup videos
+- Competitor product demos and walkthroughs
+
+**What to look for in comments:**
+- "Does this work for [specific use case]?" → edge cases and unmet needs
+- "I tried this but…" → failure points
+- "What about [competitor]?" → active evaluation
+- Timestamps with questions → confusion points in the workflow
+
+---
+
+## Twitter / X Research
+
+### Search Operators
+
+```
+"[competitor]" -filter:replies min_faves:10
+"[problem keyword]" "anyone know" OR "recommend" OR "alternative"
+"[category] is broken" OR "frustrated with [category]"
+```
+
+### What to Find
+
+- Real-time complaints about competitors
+- Practitioners discussing their stack
+- Influencers/thought leaders your ICP follows (useful for distribution)
+
+---
+
+## Blog Post and Forum Research
+
+### Comparison Content
+
+Google: `"[competitor 1] vs [competitor 2]"` or `"best [category] software [year]"`
+
+Read the comments on these posts — people who find comparison content are actively evaluating. Their comments are questions your sales process should answer.
+
+### Niche Communities
+
+- **Slack communities**: Many industries have public or semi-public Slack groups. Search "[industry] Slack community".
+- **Discord servers**: Growing for developer and creator communities.
+- **Facebook Groups**: Still strong for SMB, e-commerce, agency, and coach/consultant ICP.
+- **Circle/Mighty Networks communities**: Check if there are paid communities in your ICP's space.
+
+---
+
+## B2C and Consumer App Research
+
+B2C research requires different sources than B2B SaaS. Consumer buyers don't congregate on LinkedIn or G2 — they leave traces in app stores, social media, and communities built around the activity your product serves.
+
+### App Store Reviews (iOS App Store / Google Play)
+
+One of the richest unfiltered sources for mobile/consumer products.
+
+**Read in this order:**
+1. **1-2 star reviews** — failure modes, unmet expectations, frustration peaks
+2. **3-star reviews** — honest tradeoffs and "it's good but…" feedback
+3. **5-star reviews** — what they love in their own words (proof points and positioning)
+
+**What to extract:**
+- What job they hired the app to do ("I use this to…")
+- The moment it stopped working for them
+- What they compared it to or switched from
+- Emotional language — "I love how…", "I'm so frustrated that…"
+
+**Search tip:** Sort by "Most Recent" to get fresh signal, then "Most Critical" for pain themes.
+
+### Amazon Reviews (for physical products or software with Amazon presence)
+
+Same priority order as app stores: 3-star reviews first.
+
+**G2 analog for consumer SaaS**: Trustpilot, Sitejabber, and product-specific review aggregators.
+
+### Reddit Consumer Communities
+
+B2C Reddit is highly vertical — go to the hobby/lifestyle subreddit, not the general ones.
+
+**Examples by product type:**
+- Fitness apps: r/running, r/loseit, r/fitness, r/MyFitnessPal
+- Personal finance: r/personalfinance, r/financialindependence, r/ynab
+- Productivity/notes: r/productivity, r/Notion, r/ObsidianMD
+- Travel: r/travel, r/solotravel, r/digitalnomad
+- Parenting: r/Parenting, r/beyondthebump, r/daddit
+
+**Search pattern:** `site:reddit.com/r/[community] "[app name OR problem]"`
+
+### TikTok and Instagram Comments
+
+High-signal for consumer products with visual/lifestyle appeal.
+
+**How to find signal:**
+- Search TikTok for "[product name] review" or "is [product] worth it"
+- Watch the top 5-10 videos; read ALL comments — not just likes
+- On Instagram, check tagged posts from real users (not brand posts)
+
+**What to extract:**
+- Questions in comments = unmet needs or unclear positioning
+- "Does this work for…?" = jobs they want to hire it for
+- "I switched from X" comments = switching triggers
+- Complaints about price, missing features, or broken promises
+
+### YouTube Comments (Consumer)
+
+Same approach as B2B but different video types:
+
+- "X app honest review" or "X app after 6 months"
+- "Best [category] apps [year]" comparison videos
+- Unboxing or "setup" videos for hardware/physical products
+
+Comments on review videos are especially valuable — these are people actively in the consideration phase.
+
+### Consumer Community Platforms
+
+- **Facebook Groups**: Still dominant for many consumer verticals (parenting, fitness, local services, hobbies)
+- **Discord servers**: Growing for gaming, creator tools, productivity, crypto, lifestyle communities
+- **Nextdoor**: Useful for local service businesses
+- **Quora**: Long-form questions reveal decision anxiety and evaluation criteria
+
+---
+
+## Organizing Your Research
+
+Use a simple tagging system across all sources:
+
+| Tag | Meaning |
+|-----|---------|
+| `#pain` | A problem or frustration |
+| `#trigger` | An event that prompted the search |
+| `#outcome` | What success looks like |
+| `#language` | Exact phrases worth using in copy |
+| `#alternative` | Another solution they considered or use |
+| `#objection` | Reason to hesitate or not buy |
+| `#competitor` | Anything about a competing product |
+
+Keep a running doc with columns: Source | Date | Quote | Tags | Notes
+
+After 20-30 entries, patterns will emerge. Look for quotes that appear in multiple unrelated sources — those are your highest-confidence insights.
+
+---
+
+## Source Reliability and Confidence Scoring
+
+Not all sources carry equal weight. Use this guide when assigning confidence labels.
+
+### Source Weighting
+
+| Source | Signal Strength | Bias to Note |
+|--------|----------------|--------------|
+| Customer interviews (unprompted) | Very high | Small sample; selection bias toward engaged customers |
+| Win/loss interviews | High | Recent memory only; rationalization common |
+| App store / G2 reviews | High | Skews toward strong opinions (love or hate) |
+| Reddit / community posts | Medium-high | Skews technical, skeptical, vocal minorities |
+| Support tickets | Medium | Skews toward problems; silent majority not represented |
+| Survey (open-ended) | Medium | Primed by question framing |
+| Survey (multiple choice) | Low-medium | Artifacts of the options you provided |
+| NPS verbatims | Medium | Correlates with score; prompted by the survey moment |
+| YouTube/TikTok comments | Medium | Skews toward engaged viewers; social performance |
+| Job postings | Low-medium | Aspirational, not necessarily reflective of current pain |
+
+### Confidence Labels in Practice
+
+When presenting insights, lead with confidence:
+
+```
+[HIGH CONFIDENCE] Customers feel overwhelmed by manual reporting — appears in 12 of 20 interviews,
+4 Reddit threads, and is the #1 complaint in 3-star G2 reviews. Consistent across SMB and mid-market.
+
+[MEDIUM CONFIDENCE] Customers compare us to spreadsheets more than to direct competitors —
+mentioned in 6 interviews and 3 Reddit threads, but not yet seen in review data.
+
+[LOW CONFIDENCE] Enterprise buyers may have procurement concerns — mentioned by 2 interviewees
+from companies 500+. Needs more signal before acting on it.
+```
+
+### Recency Window
+
+- **Use as primary source**: Data from the last 12 months
+- **Use with caution**: 12-24 months (product and market may have shifted)
+- **Use only for baseline context**: 2+ years old
+
+When a theme appears consistently across old and new data, that's a durable signal worth acting on.

skills/emails/SKILL.md

@@ -1,7 +1,8 @@
 ---
-name: email-sequence
-version: 1.0.0
-description: When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," or "lifecycle emails." For in-app onboarding, see onboarding-cro.
+name: emails
+description: When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding.
+metadata:
+  version: 1.1.0
 ---
 
 # Email Sequence Design
@@ -11,7 +12,7 @@ You are an expert in email marketing and automation. Your goal is to create emai
 ## Initial Assessment
 
 **Check for product marketing context first:**
-If `.claude/product-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
+If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` 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 creating a sequence, understand:
 
@@ -292,6 +293,7 @@ For implementation, see the [tools registry](../../tools/REGISTRY.md). Key email
 |------|----------|:---:|-------|
 | **Customer.io** | Behavior-based automation | - | [customer-io.md](../../tools/integrations/customer-io.md) |
 | **Mailchimp** | SMB email marketing | ✓ | [mailchimp.md](../../tools/integrations/mailchimp.md) |
+| **Nitrosend** | AI-native email (sequences via prompts) | ✓ | [nitrosend.md](../../tools/integrations/nitrosend.md) |
 | **Resend** | Developer-friendly transactional | ✓ | [resend.md](../../tools/integrations/resend.md) |
 | **SendGrid** | Transactional email at scale | - | [sendgrid.md](../../tools/integrations/sendgrid.md) |
 | **Kit** | Creator/newsletter focused | - | [kit.md](../../tools/integrations/kit.md) |
@@ -300,7 +302,10 @@ For implementation, see the [tools registry](../../tools/REGISTRY.md). Key email
 
 ## Related Skills
 
-- **onboarding-cro**: For in-app onboarding (email supports this)
+- **lead-magnets**: For planning lead magnets that feed into nurture sequences
+- **churn-prevention**: For cancel flows, save offers, and dunning strategy (email supports this)
+- **onboarding**: For in-app onboarding (email supports this)
 - **copywriting**: For landing pages emails link to
-- **ab-test-setup**: For testing email elements
-- **popup-cro**: For email capture popups
+- **ab-testing**: For testing email elements
+- **popups**: For email capture popups
+- **revops**: For lifecycle stages that trigger email sequences

skills/emails/evals/evals.json

@@ -0,0 +1,93 @@
+{
+  "skill_name": "email-sequence",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Create a welcome email sequence for new users who sign up for our project management tool's free trial. The trial is 14 days. We want to get them to their aha moment (creating their first project and inviting a team member).",
+      "expected_output": "Should check for product-marketing-context.md first. Should create a welcome sequence (5-7 emails) following the core principles: one email one job, value before ask. Should map each email to a specific goal in the 14-day trial journey. Should include timing/delays between emails. Each email should follow the email copy structure: hook → context → value → CTA → sign-off. Should include subject lines following the subject line strategy. Should align sequence with the aha moment (first project + team invite). Output should follow the structured format with sequence overview and per-email specs.",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Creates 5-7 email welcome sequence",
+        "Follows one email one job principle",
+        "Maps emails to trial timeline (14 days)",
+        "Includes timing between emails",
+        "Each email has hook, context, value, CTA",
+        "Includes subject lines for each email",
+        "Aligns with stated aha moment",
+        "Output follows structured per-email format"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "We need a lead nurture sequence for people who download our 'State of DevOps 2024' report. Goal is to get them to book a demo of our CI/CD platform.",
+      "expected_output": "Should create a lead nurture sequence (6-8 emails). Should follow value before ask — first emails should provide related value, not immediately push for demo. Should map the sequence from awareness (report download) through consideration (related content, case studies) to decision (demo request). Should include timing between emails. Each email should have clear subject line, hook, single CTA. Should gradually increase commitment asks across the sequence.",
+      "assertions": [
+        "Creates 6-8 email lead nurture sequence",
+        "Follows value before ask principle",
+        "Maps from awareness through consideration to decision",
+        "Includes timing between emails",
+        "Each email has clear subject line and single CTA",
+        "Gradually increases commitment asks",
+        "Connects to original download topic"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "our email open rates have tanked. used to be 35% now we're at 18%. what's going on and how do we fix our subject lines?",
+      "expected_output": "Should trigger on casual phrasing. Should diagnose potential causes of declining open rates: sender reputation, list hygiene, subject line quality, sending frequency, deliverability issues. Should apply the subject line strategy from the skill: test curiosity vs benefit vs urgency patterns, personalization, optimal length. Should recommend a re-engagement campaign to clean the list. Should provide specific subject line formulas and examples. Should suggest testing framework for subject lines.",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Diagnoses potential causes beyond just subject lines",
+        "Addresses sender reputation and deliverability",
+        "Recommends list hygiene or re-engagement",
+        "Applies subject line strategy with specific patterns",
+        "Provides subject line formulas and examples",
+        "Suggests testing framework"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "Build a re-engagement sequence for subscribers who haven't opened any emails in 90 days. We have about 5,000 inactive subscribers.",
+      "expected_output": "Should create a re-engagement sequence (3-4 emails). Should follow the re-engagement pattern: first email acknowledges absence and offers value, middle emails escalate with compelling reasons to re-engage, final email is a clear 'last chance' before removal. Should recommend aggressive subject lines to break through. Should include a sunset policy (remove non-responders after sequence completes). Should address the impact on deliverability of keeping inactive subscribers.",
+      "assertions": [
+        "Creates 3-4 email re-engagement sequence",
+        "Acknowledges absence in first email",
+        "Escalates through the sequence",
+        "Includes 'last chance' final email",
+        "Recommends sunset policy for non-responders",
+        "Addresses deliverability impact of inactive subscribers",
+        "Uses compelling subject lines"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "What's the ideal timing for our onboarding email sequence? We send the first email immediately after signup, but we're not sure about the rest.",
+      "expected_output": "Should provide timing guidance for onboarding sequences. Should reference the timing and delays framework: immediate first email (welcome/confirmation), then suggest data-driven timing based on user behavior triggers vs fixed time delays. Should recommend behavior-triggered emails when possible (user completed action → next email) with time-based fallbacks. Should provide typical timing patterns for SaaS onboarding (day 0, day 1, day 3, day 5, day 7, etc.). Should note that optimal timing depends on product complexity and trial length.",
+      "assertions": [
+        "Provides timing guidance for onboarding sequences",
+        "Recommends immediate first email",
+        "Discusses behavior-triggered vs time-based timing",
+        "Provides typical timing patterns",
+        "Notes timing depends on product and trial length",
+        "Recommends behavior triggers with time-based fallbacks"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "Help me optimize our post-signup onboarding experience. Users sign up but 60% never complete setup.",
+      "expected_output": "Should recognize this is an in-app onboarding optimization task, not an email sequence task. Should defer to or cross-reference the onboarding-cro skill, which handles in-app onboarding flows, checklists, and activation optimization. May offer to help with the email component of onboarding but should make clear that onboarding-cro is the primary skill for this task.",
+      "assertions": [
+        "Recognizes this as in-app onboarding optimization",
+        "References or defers to onboarding-cro skill",
+        "Does not attempt full onboarding redesign using email patterns",
+        "May offer email component support"
+      ],
+      "files": []
+    }
+  ]
+}

skills/emails/references/copy-guidelines.md

@@ -1,5 +1,15 @@
 # Email Copy Guidelines
 
+## Contents
+- Structure
+- Formatting
+- Tone
+- Length
+- CTA Buttons vs. Links
+- Personalization (merge fields, dynamic content, triggered emails)
+- Segmentation Strategies (by behavior, by stage, by profile)
+- Testing and Optimization (what to test, how to test, metrics to track)
+
 ## Structure
 
 1. **Hook**: First line grabs attention

skills/emails/references/email-types.md

@@ -2,6 +2,15 @@
 
 A comprehensive guide to lifecycle and campaign emails. Use this as an audit checklist and implementation reference.
 
+## Contents
+- Onboarding Emails (new users series, new customers series, key onboarding step reminder, new user invite)
+- Retention Emails (upgrade to paid, upgrade to higher plan, ask for review, offer support proactively, product usage report, NPS survey, referral program)
+- Billing Emails (switch to annual, failed payment recovery, cancellation survey, upcoming renewal reminder)
+- Usage Emails (daily/weekly/monthly summary, key event or milestone notifications)
+- Win-Back Emails (expired trials, cancelled customers)
+- Campaign Emails (monthly roundup/newsletter, seasonal promotions, product updates, industry news roundup, pricing update)
+- Email Audit Checklist (onboarding, retention, billing, usage, win-back, campaigns)
+
 ## Onboarding Emails
 
 ### New Users Series

skills/emails/references/sequence-templates.md

@@ -2,6 +2,12 @@
 
 Detailed templates for common email sequences.
 
+## Contents
+- Welcome Sequence (Post-Signup)
+- Lead Nurture Sequence (Pre-Sale)
+- Re-Engagement Sequence
+- Onboarding Sequence (Product Users)
+
 ## Welcome Sequence (Post-Signup)
 
 **Email 1: Welcome (Immediate)**

skills/free-tools/SKILL.md

@@ -1,7 +1,8 @@
 ---
-name: free-tool-strategy
-version: 1.0.0
-description: When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or brand awareness. Also use when the user mentions "engineering as marketing," "free tool," "marketing tool," "calculator," "generator," "interactive tool," "lead gen tool," "build a tool for leads," or "free resource." This skill bridges engineering and marketing — useful for founders and technical marketers.
+name: free-tools
+description: When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or brand awareness. Also use when the user mentions "engineering as marketing," "free tool," "marketing tool," "calculator," "generator," "interactive tool," "lead gen tool," "build a tool for leads," "free resource," "ROI calculator," "grader tool," "audit tool," "should I build a free tool," or "tools for lead gen." Use this whenever someone wants to build something useful and give it away to attract leads or earn links. For downloadable content lead magnets (ebooks, checklists, templates), see lead-magnets.
+metadata:
+  version: 1.1.0
 ---
 
 # Free Tool Strategy (Engineering as Marketing)
@@ -11,7 +12,7 @@ You are an expert in engineering-as-marketing strategy. Your goal is to help pla
 ## Initial Assessment
 
 **Check for product marketing context first:**
-If `.claude/product-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
+If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` 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 tool strategy, understand:
 
@@ -171,7 +172,8 @@ Rate each factor 1-5:
 
 ## Related Skills
 
-- **page-cro**: For optimizing the tool's landing page
+- **lead-magnets**: For downloadable content lead magnets (ebooks, checklists, templates)
+- **cro**: For optimizing the tool's landing page
 - **seo-audit**: For SEO-optimizing the tool
-- **analytics-tracking**: For measuring tool usage
-- **email-sequence**: For nurturing leads from the tool
+- **analytics**: For measuring tool usage
+- **emails**: For nurturing leads from the tool

skills/free-tools/evals/evals.json

@@ -0,0 +1,90 @@
+{
+  "skill_name": "free-tool-strategy",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "We want to build a free tool to drive leads for our SEO software. We're thinking about an SEO audit tool or a keyword research tool. Which would be better and how should we approach it?",
+      "expected_output": "Should check for product-marketing-context.md first. Should apply the evaluation scorecard to compare both tool ideas across dimensions (audience alignment, lead quality, build effort, SEO value, maintenance burden, competitive differentiation). Should reference the tool types from the skill (analyzers, testers). Should recommend the stronger option with rationale. Should discuss lead capture gating strategy (what's free vs what requires email). Should address MVP scope — what's the minimum valuable version. Should provide implementation recommendations.",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Applies evaluation scorecard to compare options",
+        "References tool types from the skill",
+        "Recommends one option with clear rationale",
+        "Discusses lead capture gating strategy",
+        "Addresses MVP scope",
+        "Provides implementation recommendations"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "I want to build a free ROI calculator for our HR software. Users input their company size and current processes, and it shows how much time and money they'd save.",
+      "expected_output": "Should identify this as a calculator tool type. Should apply the ideation framework to validate the concept. Should discuss lead capture strategy: should the basic result be free and detailed report gated? Should address the build vs buy decision. Should recommend MVP scope (what inputs, what outputs, what formula). Should discuss SEO considerations for the tool page. Should reference the evaluation scorecard to score the idea.",
+      "assertions": [
+        "Identifies as calculator tool type",
+        "Applies ideation framework to validate",
+        "Discusses lead capture gating strategy",
+        "Addresses build vs buy decision",
+        "Recommends MVP scope (inputs, outputs, formula)",
+        "Discusses SEO considerations",
+        "References evaluation scorecard"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "give me some ideas for free tools we could build. we sell email marketing software for e-commerce brands.",
+      "expected_output": "Should trigger on casual phrasing. Should apply the ideation framework to generate tool ideas relevant to email marketing + e-commerce. Should provide 5-8 ideas across different tool types (calculators, generators, analyzers, testers). Examples: email subject line tester, email deliverability checker, email ROI calculator, email template generator, spam score checker. Should briefly score each against the evaluation dimensions. Should recommend top 2-3 to pursue.",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Applies ideation framework",
+        "Generates ideas across multiple tool types",
+        "Ideas are relevant to email marketing + e-commerce",
+        "Provides 5-8 ideas",
+        "Briefly evaluates each idea",
+        "Recommends top 2-3 to pursue"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "We built a free website speed test tool 6 months ago but it's barely getting any traffic. What went wrong and how do we fix it?",
+      "expected_output": "Should diagnose why the tool isn't getting traffic. Should investigate: SEO strategy for the tool page (target keywords, on-page optimization), distribution strategy (was it launched and forgotten?), competitive landscape (are there dominant free tools already?), tool quality and UX (does it provide unique value?). Should apply the engineering as marketing principles. Should recommend a recovery plan: SEO improvements, content marketing around the tool, product improvements for differentiation.",
+      "assertions": [
+        "Diagnoses potential traffic issues",
+        "Investigates SEO strategy for the tool",
+        "Assesses competitive landscape",
+        "Questions unique value proposition",
+        "Applies engineering as marketing principles",
+        "Recommends recovery plan with specific actions"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "Should we gate our free tool behind an email capture or make it completely free? We want leads but don't want to kill usage.",
+      "expected_output": "Should apply the lead capture gating strategy framework. Should present the spectrum: fully ungated → partial gating (basic results free, detailed report gated) → fully gated. Should recommend partial gating as the typical best approach — give enough value to demonstrate the tool's worth, gate the detailed/actionable output. Should discuss tradeoffs: ungated = more SEO value and usage, gated = more leads but fewer users. Should provide specific gating recommendations based on tool type.",
+      "assertions": [
+        "Applies lead capture gating strategy",
+        "Presents gating spectrum (ungated to fully gated)",
+        "Recommends partial gating approach",
+        "Discusses tradeoffs of each approach",
+        "Provides specific gating recommendations",
+        "Addresses SEO impact of gating decisions"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "How do I optimize the landing page for our free tool to get more signups? The tool itself is great but nobody finds it.",
+      "expected_output": "Should recognize this is a landing page conversion optimization task, not a free tool strategy task. Should defer to or cross-reference the cro skill for optimizing the tool's landing page conversion rate. May provide free-tool-specific context (gating strategy, value demonstration) but should make clear that cro is the right skill for page conversion optimization.",
+      "assertions": [
+        "Recognizes this as page CRO, not free tool strategy",
+        "References or defers to cro skill",
+        "May provide free-tool-specific context",
+        "Does not attempt full page CRO using free tool strategy patterns"
+      ],
+      "files": []
+    }
+  ]
+}

skills/free-tools/references/tool-types.md

@@ -2,6 +2,15 @@
 
 Detailed guide to each type of marketing tool you can build.
 
+## Contents
+- Calculators
+- Generators
+- Analyzers/Auditors
+- Testers/Validators
+- Libraries/Resources
+- Interactive Educational
+- Tool Concept Examples by Industry (SaaS product, agency/services, e-commerce, developer tools, finance)
+
 ## Calculators
 
 **Best for**: Decisions involving numbers, comparisons, estimates

skills/launch/SKILL.md

@@ -1,7 +1,8 @@
 ---
-name: launch-strategy
-version: 1.0.0
-description: "When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' or 'product update.' This skill covers phased launches, channel strategy, and ongoing launch momentum."
+name: launch
+description: "When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update,' 'how do I launch this,' 'launch checklist,' 'GTM plan,' or 'we're about to ship.' Use this whenever someone is preparing to release something publicly. For ongoing marketing after launch, see marketing-ideas."
+metadata:
+  version: 1.1.0
 ---
 
 # Launch Strategy
@@ -11,7 +12,7 @@ You are an expert in SaaS product launches and feature announcements. Your goal
 ## Before Starting
 
 **Check for product marketing context first:**
-If `.claude/product-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
+If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
 
 ---
 
@@ -92,7 +93,7 @@ Tap into someone else's audience to shortcut the hardest part—getting noticed.
 1. List industry leaders your audience follows
 2. Pitch win-win collaborations
 3. Use tools like SparkToro or Listen Notes to find audience overlap
-4. Set up affiliate/referral incentives
+4. Set up affiliate/referral incentives (for channel partner launches, use [Introw](../../tools/integrations/introw.md) to manage deal registration and commissions)
 
 **Example - TRMNL:**
 Sent a free e-ink display to YouTuber Snazzy Labs—not a paid sponsorship, just hoping he'd like it. He created an in-depth review that racked up 500K+ views and drove $500K+ in sales. They also set up an affiliate program for ongoing promotion.
@@ -345,7 +346,8 @@ Even small changelog updates remind customers your product is evolving. This bui
 ## Related Skills
 
 - **marketing-ideas**: For additional launch tactics (#22 Product Hunt, #23 Early Access Referrals)
-- **email-sequence**: For launch and onboarding email sequences
-- **page-cro**: For optimizing launch landing pages
+- **emails**: For launch and onboarding email sequences
+- **cro**: For optimizing launch landing pages
 - **marketing-psychology**: For psychology behind waitlists and exclusivity
 - **programmatic-seo**: For comparison pages mentioned in post-launch
+- **sales-enablement**: For launch sales collateral and enablement materials

skills/launch/evals/evals.json

@@ -0,0 +1,91 @@
+{
+  "skill_name": "launch-strategy",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "We're launching a new B2B SaaS product for design teams in 6 weeks. It's a design review tool. We have a small audience (500 email subscribers, 2k Twitter followers). Help us plan the launch.",
+      "expected_output": "Should check for product-marketing-context.md first. Should apply the ORB Framework (Owned, Rented, Borrowed channels) with the user's specific resources. Owned: email list (500 subscribers), website. Rented: Twitter (2k followers). Borrowed: partnerships, communities, Product Hunt. Should recommend the five-phase launch approach with a timeline mapped to the 6-week window: Internal prep, Alpha (existing network), Beta (expanded), Early Access, Full Launch. Should provide specific tactics for each phase. Should recommend building up the audience before launch day. Should include a launch day checklist.",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Applies ORB Framework (Owned, Rented, Borrowed)",
+        "Maps to user's specific channels and audience sizes",
+        "Recommends five-phase launch approach",
+        "Provides timeline mapped to 6-week window",
+        "Provides specific tactics for each phase",
+        "Recommends audience building before launch",
+        "Includes launch day checklist"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "We want to launch on Product Hunt. Any tips? We've never done it before.",
+      "expected_output": "Should apply the Product Hunt strategy section. Should cover: choosing the right day and time, preparing assets (logo, gallery images, maker video), crafting the tagline and description, building a hunter network, activating supporters on launch day, engaging with comments, and post-launch follow-up. Should recommend preparation timeline (start 2-4 weeks before). Should mention common mistakes to avoid. Should set realistic expectations about outcomes.",
+      "assertions": [
+        "Applies Product Hunt strategy section",
+        "Covers timing (day and time selection)",
+        "Covers asset preparation",
+        "Addresses hunter network and supporter activation",
+        "Recommends preparation timeline",
+        "Mentions common mistakes to avoid",
+        "Sets realistic expectations"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "we just shipped a major feature update. how should we announce it? it's not a full product launch, just a big new feature.",
+      "expected_output": "Should trigger on casual phrasing. Should apply the ongoing launch strategy section, specifically the major/medium/minor update matrix. Should identify this as a major feature update. Should recommend appropriate channels and tactics for a feature launch (less than a full product launch but more than a changelog entry). Should include: announcement email, blog post, social media push, in-app notification, and possibly a mini Product Hunt launch. Should provide a feature announcement framework.",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Applies ongoing launch strategy / update matrix",
+        "Identifies as major feature update",
+        "Scales tactics appropriately (not full launch)",
+        "Recommends announcement channels",
+        "Includes email, blog, social, and in-app notification",
+        "Provides feature announcement framework"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "Our launch flopped. We launched 3 weeks ago and only got 50 signups. We expected at least 500. What went wrong and what can we do now?",
+      "expected_output": "Should apply the post-launch product marketing section. Should diagnose potential failure causes: insufficient audience building pre-launch, wrong channels, weak value proposition messaging, poor launch execution, targeting the wrong audience. Should recommend post-launch recovery tactics: iterate on messaging, identify which channels produced the 50 signups and double down, try new distribution channels, leverage early users for testimonials. Should provide a specific 30-day recovery plan.",
+      "assertions": [
+        "Applies post-launch product marketing guidance",
+        "Diagnoses potential failure causes",
+        "Addresses pre-launch audience building gap",
+        "Recommends post-launch recovery tactics",
+        "Suggests analyzing which channels produced signups",
+        "Provides specific recovery plan"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "How do we leverage partnerships and borrowed audiences for our launch? We don't have a big audience of our own.",
+      "expected_output": "Should focus on the Borrowed channel from the ORB Framework. Should provide specific borrowed audience tactics: podcast guest appearances, co-marketing with complementary tools, influencer partnerships, community engagement (relevant Slack groups, Discord servers, Reddit), guest posts, cross-promotions. Should recommend how to identify and approach potential partners. Should note that borrowed audience strategies take time to build and should start well before launch day.",
+      "assertions": [
+        "Focuses on Borrowed channel from ORB Framework",
+        "Provides specific borrowed audience tactics",
+        "Mentions partnerships, communities, guest content",
+        "Recommends how to identify and approach partners",
+        "Notes borrowed strategies take time to build",
+        "Suggests starting well before launch day"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "Give me some creative marketing ideas to promote our product. We're bootstrapped and don't have a big budget.",
+      "expected_output": "Should recognize this is a broader marketing ideas request, not specifically a launch strategy task. Should defer to or cross-reference the marketing-ideas skill, which provides 139 marketing ideas organized by category and filtered by budget. May provide some launch-related tactical ideas but should make clear that marketing-ideas is the right skill for a broader brainstorming session.",
+      "assertions": [
+        "Recognizes this as broader marketing ideas request",
+        "References or defers to marketing-ideas skill",
+        "Does not attempt full marketing brainstorm using launch strategy patterns",
+        "May provide some launch-related tactical ideas"
+      ],
+      "files": []
+    }
+  ]
+}

skills/lead-magnets/SKILL.md

@@ -0,0 +1,310 @@
+---
+name: lead-magnets
+description: When the user wants to create, plan, or optimize a lead magnet for email capture or lead generation. Also use when the user mentions "lead magnet," "gated content," "content upgrade," "downloadable," "ebook," "cheat sheet," "checklist," "template download," "opt-in," "freebie," "PDF download," "resource library," "content offer," "email capture content," "Notion template," "spreadsheet template," or "what should I give away for emails." Use this for planning what to create and how to distribute it. For interactive tools as lead magnets, see free-tools. For writing the actual content, see copywriting. For the email sequence after capture, see emails.
+metadata:
+  version: 1.0.0
+---
+
+# Lead Magnets
+
+You are an expert in lead magnet strategy. Your goal is to help plan lead magnets that capture emails, generate qualified leads, and naturally lead to product adoption.
+
+## Before Planning
+
+**Check for product marketing context first:**
+If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
+
+Gather this context (ask if not provided):
+
+### 1. Business Context
+- What does the company do?
+- Who is the ideal customer?
+- What problems does your product solve?
+
+### 2. Current Lead Generation
+- How do you currently capture leads?
+- What lead magnets or offers do you have?
+- What's your current conversion rate on email capture?
+
+### 3. Content Assets
+- What existing content could be repurposed? (blog posts, guides, data)
+- What expertise can you package?
+- What templates or tools do you use internally?
+
+### 4. Goals
+- Primary goal: email list growth, lead quality, product education?
+- Target audience stage: awareness, consideration, or decision?
+- Timeline and resource constraints?
+
+---
+
+## Lead Magnet Principles
+
+### 1. Solve a Specific Problem
+- Address one clear pain point, not a broad topic
+- "How to write cold emails that get replies" > "Marketing guide"
+
+### 2. Match the Buyer Stage
+- Awareness leads need education
+- Consideration leads need comparison and evaluation
+- Decision leads need implementation help
+
+### 3. High Perceived Value, Low Time Investment
+- Should look like it's worth paying for
+- Consumable in under 30 minutes (ideally under 10)
+- Immediate, actionable takeaway
+
+### 4. Natural Path to Product
+- Solves a problem your product also solves
+- Creates awareness of a gap your product fills
+- Demonstrates your expertise in the space
+
+### 5. Easy to Consume
+- One clear format (don't mix ebook + video + spreadsheet)
+- Works on mobile
+- No special software required
+
+---
+
+## Lead Magnet Types
+
+| Type | Best For | Effort | Time to Create |
+|------|----------|--------|----------------|
+| Checklist | Quick wins, process steps | Low | 1-2 hours |
+| Cheat sheet | Reference material, shortcuts | Low | 2-4 hours |
+| Template (doc/spreadsheet/Notion) | Repeatable processes, workflows | Low-Med | 2-8 hours |
+| Swipe file | Inspiration, examples | Medium | 4-8 hours |
+| Ebook/guide | Deep education, authority | High | 1-3 weeks |
+| Mini-course (email) | Education + nurture | Medium | 1-2 weeks |
+| Mini-course (video) | Education + personality | High | 2-4 weeks |
+| Quiz/assessment | Segmentation, engagement | Medium | 1-2 weeks |
+| Webinar | Authority, live engagement | Medium | 1 week prep |
+| Resource library | Ongoing value, return visits | High | Ongoing |
+| Free trial/community access | Product experience | Varies | Varies |
+
+**For detailed creation guidance per format**: See [references/format-guide.md](references/format-guide.md)
+
+---
+
+## Matching Lead Magnets to Buyer Stage
+
+### Awareness Stage
+Goal: Educate on the problem. Attract people who don't know you yet.
+
+| Format | Example |
+|--------|---------|
+| Checklist | "10-Point Website Audit Checklist" |
+| Cheat sheet | "SEO Cheat Sheet for Beginners" |
+| Ebook/guide | "The Complete Guide to Email Marketing" |
+| Quiz | "What Type of Marketer Are You?" |
+
+### Consideration Stage
+Goal: Help evaluate solutions. Build trust and demonstrate expertise.
+
+| Format | Example |
+|--------|---------|
+| Comparison template | "CRM Comparison Spreadsheet" |
+| Assessment | "Marketing Maturity Assessment" |
+| Case study collection | "5 Companies That 3x'd Their Pipeline" |
+| Webinar | "How to Choose the Right Analytics Tool" |
+
+### Decision Stage
+Goal: Help implement. Remove friction to purchase.
+
+| Format | Example |
+|--------|---------|
+| Template | "Ready-to-Use Sales Email Templates" |
+| Free trial | "14-Day Free Trial" |
+| Implementation guide | "Migration Checklist: Switch in 30 Minutes" |
+| ROI calculator | "Calculate Your Savings" (→ see **free-tools**) |
+
+---
+
+## Gating Strategy
+
+### Gating Options
+
+| Approach | When to Use | Trade-off |
+|----------|-------------|-----------|
+| **Full gate** | High-value content, bottom-funnel | Max capture, lower reach |
+| **Partial gate** | Preview + full version | Balance of reach and capture |
+| **Ungated + optional** | Top-funnel education | Max reach, lower capture |
+| **Content upgrade** | Blog post + bonus | Contextual, high-intent |
+
+### What to Ask For
+
+- **Email only** — highest conversion, lowest friction
+- **Email + name** — enables personalization, slight friction increase
+- **Email + company/role** — better lead qualification, more friction
+- **Multi-field** — only for high-value offers (webinars, demos)
+
+Rule of thumb: Ask for the minimum needed. Every extra field reduces conversion by 5-10%.
+
+### How to Frame the Exchange
+
+- Make the value obvious: "Get the full 25-page guide free"
+- Show a preview: table of contents, first page, sample results
+- Add social proof: "Downloaded by 5,000+ marketers"
+- Reduce risk: "No spam. Unsubscribe anytime."
+
+**For form optimization**: See **cro** skill
+**For popup implementation**: See **popups** skill
+
+---
+
+## Landing Page & Delivery
+
+### Landing Page Structure
+
+1. **Headline** — Clear benefit: what they'll get and why it matters
+2. **Preview/mockup** — Visual of the lead magnet (cover, screenshot, sample page)
+3. **What's inside** — 3-5 bullet points of key takeaways
+4. **Social proof** — Download count, testimonials, logos
+5. **Form** — Minimal fields, clear CTA button
+6. **FAQ** — Address hesitations (Is it really free? What format?)
+
+**For landing page optimization**: See **cro** skill
+
+### Delivery Methods
+
+| Method | Pros | Cons |
+|--------|------|------|
+| **Instant download** | Immediate gratification | No email verification |
+| **Email delivery** | Verifies email, starts relationship | Slight delay |
+| **Thank you page + email** | Best of both—instant access + email copy | Slightly more complex |
+| **Drip delivery** | Builds habit, multiple touchpoints | Only for courses/series |
+
+### Thank You Page Optimization
+
+Don't waste the thank you page. After they've converted:
+- Confirm delivery ("Check your inbox")
+- Offer a next step (book a demo, start trial, join community)
+- Share on social (pre-written tweet/post)
+- Recommend related content
+
+---
+
+## Promotion & Distribution
+
+### Blog CTAs & Content Upgrades
+
+- Add relevant CTAs within blog posts (inline, end-of-post)
+- Create post-specific content upgrades (bonus checklist for a how-to post)
+- Content upgrades convert 2-5x better than generic sidebar CTAs
+
+### Exit-Intent & Popups
+
+- Trigger on exit intent or scroll depth
+- Match the popup offer to the page content
+- **See popups** for implementation
+
+### Social Media
+
+- Share snippets and teasers from the lead magnet
+- Create carousel posts from key points
+- Use the lead magnet as the CTA in your bio/profile
+- **See social** for social strategy
+
+### Paid Promotion
+
+- Facebook/Instagram lead ads for top-funnel lead magnets
+- Google Ads for high-intent lead magnets (templates, tools)
+- LinkedIn for B2B lead magnets
+- Retarget blog visitors with lead magnet ads
+- **See paid-ads** for campaign strategy
+
+### Partner Co-Promotion
+
+- Cross-promote with complementary brands
+- Guest webinars with partner audiences
+- Include in partner newsletters
+- Bundle in resource collections
+
+---
+
+## Measuring Success
+
+### Key Metrics
+
+| Metric | What It Tells You | Benchmark |
+|--------|-------------------|-----------|
+| **Landing page conversion rate** | Offer attractiveness | 20-40% (warm traffic), 5-15% (cold) |
+| **Cost per lead** | Acquisition efficiency | Varies by channel and industry |
+| **Lead-to-customer rate** | Lead quality | 1-5% (B2B), varies widely |
+| **Email engagement** | Content relevance | 30-50% open, 2-5% click |
+| **Time to conversion** | Nurture effectiveness | Track by lead magnet source |
+
+**For detailed benchmarks by format and industry**: See [references/benchmarks.md](references/benchmarks.md)
+
+### A/B Testing Ideas
+
+- **Headline**: Benefit-focused vs. curiosity-driven
+- **Format**: Checklist vs. guide on same topic
+- **Gate level**: Full gate vs. partial preview
+- **Form fields**: Email-only vs. email + name
+- **CTA copy**: "Download Free Guide" vs. "Get Your Copy"
+- **Delivery**: Instant download vs. email delivery
+
+### Lead Quality Signals
+
+Good lead magnet attracted quality leads if:
+- Higher-than-average email engagement
+- Leads progress to trial/demo at expected rates
+- Low unsubscribe rate after delivery
+- Leads match ICP demographics
+
+---
+
+## Output Format
+
+When creating a lead magnet strategy, provide:
+
+### 1. Lead Magnet Recommendation
+- Format and topic
+- Target buyer stage
+- Why this format for this audience
+- Estimated creation effort
+
+### 2. Content Outline
+- Key sections/components
+- Length and scope
+- What makes it unique or valuable
+
+### 3. Gating & Capture Plan
+- What to gate and how
+- Form fields
+- Landing page structure
+
+### 4. Distribution Plan
+- Promotion channels
+- Content upgrade opportunities
+- Paid amplification (if applicable)
+
+### 5. Measurement Plan
+- KPIs and targets
+- What to A/B test first
+
+---
+
+## Task-Specific Questions
+
+1. What existing content or expertise could you turn into a lead magnet?
+2. Where does your audience spend time online?
+3. What's the most common question prospects ask before buying?
+4. Do you have an email nurture sequence set up for new leads?
+5. What's your budget for design and promotion?
+
+---
+
+## Related Skills
+
+- **free-tools**: For interactive tools as lead magnets (calculators, graders, quizzes)
+- **copywriting**: For writing the lead magnet content itself
+- **emails**: For nurture sequences after lead capture
+- **cro**: For optimizing lead magnet landing pages
+- **popups**: For popup-based lead capture
+- **cro**: For optimizing capture forms
+- **content-strategy**: For content planning and topic selection
+- **analytics**: For measuring lead magnet performance
+- **paid-ads**: For paid promotion of lead magnets
+- **social**: For social media promotion

skills/lead-magnets/references/benchmarks.md

@@ -0,0 +1,129 @@
+# Lead Magnet Benchmarks
+
+Reference data for planning and evaluating lead magnet performance.
+
+---
+
+## Conversion Rate Benchmarks
+
+### By Format Type
+
+| Format | Landing Page Conversion | Notes |
+|--------|------------------------|-------|
+| Checklist | 30-50% | High because low commitment |
+| Cheat sheet | 25-40% | Quick reference appeal |
+| Template | 25-45% | Immediate utility drives conversion |
+| Ebook/guide | 20-35% | Higher commitment, lower rate |
+| Quiz | 30-50% | Engagement drives completion |
+| Webinar | 20-40% (registration) | 30-50% attendance rate of registrants |
+| Mini-course | 15-30% | Higher commitment, higher quality leads |
+| Free trial | 5-15% | High intent but high friction |
+
+### By Traffic Source
+
+| Source | Expected Conversion | Why |
+|--------|-------------------|-----|
+| Blog content upgrade | 3-8% of post readers | Contextually relevant |
+| Dedicated landing page (organic) | 20-40% | High intent |
+| Dedicated landing page (paid) | 10-25% | Cold traffic |
+| Exit-intent popup | 2-5% of visitors | Interruption-based |
+| Sidebar/banner CTA | 0.5-2% | Low engagement |
+| Social media link | 10-20% | Warm but browsing |
+
+### By Industry (Landing Page)
+
+| Industry | Average Conversion |
+|----------|-------------------|
+| SaaS/Tech | 15-25% |
+| Marketing/Agency | 20-35% |
+| Finance | 10-20% |
+| E-commerce | 10-20% |
+| Education | 20-35% |
+| Health/Wellness | 15-25% |
+
+---
+
+## Lead Quality Indicators
+
+### Signals of High-Quality Leads
+- Open first 3 emails at 40%+ rate
+- Click through to content or product pages
+- Return to site within 30 days
+- Match ICP demographics (role, company size, industry)
+- Progress to trial, demo, or purchase within 90 days
+
+### Signals of Low-Quality Leads
+- Unsubscribe within first 3 emails
+- Never open beyond delivery email
+- Use disposable email addresses
+- Don't match target customer profile
+- Downloaded for the content, no product interest
+
+### Quality vs. Quantity by Format
+
+| Format | Lead Volume | Lead Quality | Net Value |
+|--------|-------------|-------------|-----------|
+| Generic ebook | High | Low-Medium | Medium |
+| Specific template | Medium | High | High |
+| Industry report | Medium | Medium-High | High |
+| Quiz/assessment | High | Medium (segmentable) | High |
+| Webinar | Low-Medium | High | High |
+| Checklist | High | Low-Medium | Medium |
+| Free trial | Low | Very High | Very High |
+
+---
+
+## Cost Benchmarks
+
+### Cost Per Lead by Channel
+
+| Channel | Typical CPL | Notes |
+|---------|-------------|-------|
+| Organic search | $0-5 | Lowest, but slow to build |
+| Blog content upgrade | $0-2 | Nearly free if you have traffic |
+| Facebook/Instagram Ads | $3-15 | B2C lower, B2B higher |
+| Google Ads | $10-50 | High intent, higher cost |
+| LinkedIn Ads | $25-75 | B2B, expensive but qualified |
+| Partner co-promotion | $0-5 | Depends on relationship |
+
+### Creation Cost by Format
+
+| Format | DIY Cost | With Designer/Freelancer |
+|--------|----------|-------------------------|
+| Checklist | Free | $100-300 |
+| Cheat sheet | Free | $200-500 |
+| Template | Free | $100-500 |
+| Ebook (10-25 pages) | Free | $500-2,000 |
+| Quiz | $0-100/mo (tool) | $500-2,000 |
+| Webinar | Free (Zoom) | $500-1,500 (production) |
+| Mini-course (email) | Free | $500-1,500 (copywriting) |
+| Video course | $0-200 (gear) | $2,000-5,000 |
+
+---
+
+## Timeline Expectations
+
+### Time to Create
+
+| Format | Solo Creator | With Team |
+|--------|-------------|-----------|
+| Checklist | 1-2 hours | Same day |
+| Cheat sheet | 2-4 hours | Same day |
+| Template | 2-8 hours | 1-2 days |
+| Swipe file | 4-8 hours | 1-2 days |
+| Ebook | 1-3 weeks | 1-2 weeks |
+| Quiz | 1-2 weeks | 1 week |
+| Webinar prep | 1 week | 3-5 days |
+| Mini-course | 1-2 weeks | 1 week |
+
+### Time to See Results
+
+| Phase | Timeline |
+|-------|----------|
+| First leads | Immediately with existing traffic or paid |
+| Organic traffic growth | 2-6 months (SEO) |
+| Meaningful lead volume | 1-3 months |
+| Measurable impact on pipeline | 3-6 months |
+| Full ROI assessment | 6-12 months |
+
+**Note**: These benchmarks are general guidelines. Your actual results depend on audience, niche, traffic volume, and offer quality. Start measuring from day one and build your own benchmarks.

skills/lead-magnets/references/format-guide.md

@@ -0,0 +1,196 @@
+# Lead Magnet Format Guide
+
+Detailed creation guidance for each lead magnet format.
+
+## Contents
+- Ebooks & Guides
+- Checklists
+- Cheat Sheets
+- Templates & Spreadsheets
+- Swipe Files
+- Mini-Courses
+- Quizzes & Assessments
+- Webinars & Workshops
+
+---
+
+## Ebooks & Guides
+
+**Best for**: Building authority, deep education, awareness-stage leads
+
+**Structure**:
+1. Title page with professional design
+2. Table of contents
+3. Introduction — frame the problem, set expectations
+4. 3-7 chapters — one key concept per chapter
+5. Summary — recap key takeaways
+6. CTA — next step toward your product
+
+**Guidelines**:
+- Ideal length: 10-25 pages (shorter is fine if valuable)
+- Include visuals: charts, diagrams, screenshots
+- Use callout boxes for key stats or quotes
+- End each chapter with a quick takeaway
+- Don't pad — density beats length
+
+**Tools**: Canva, Google Docs → PDF, Notion export, Designrr, Beacon.by
+
+---
+
+## Checklists
+
+**Best for**: Process-oriented tasks, quick wins, implementation help
+
+**Structure**:
+- Title: "[Number]-Point [Topic] Checklist"
+- Numbered or checkbox items
+- Group into logical sections if 10+ items
+- Brief explanation per item (1-2 sentences)
+
+**Guidelines**:
+- Keep to 1-2 pages
+- Use actionable language ("Verify X", "Set up Y", "Remove Z")
+- Order by workflow sequence or priority
+- Make it printable — clean layout, generous spacing
+- Include a "done" checkbox for each item
+
+**What works**: Step-by-step processes, audit criteria, launch checklists, setup guides
+
+---
+
+## Cheat Sheets
+
+**Best for**: Reference material, shortcuts, quick-lookup information
+
+**Structure**:
+- One page (two pages max)
+- Organized by category or workflow
+- Dense but scannable
+- Visual hierarchy with headers and grouping
+
+**Guidelines**:
+- Optimize for quick reference, not reading
+- Use tables, grids, or columns
+- Include formulas, shortcuts, or code snippets
+- Design for printing or saving as desktop reference
+- Bold the most important items
+
+**What works**: Keyboard shortcuts, formula references, terminology glossaries, decision matrices
+
+---
+
+## Templates & Spreadsheets
+
+**Best for**: Repeatable processes, planning, tracking
+
+### Spreadsheet Templates (Google Sheets / Excel)
+- Include a "How to Use" tab with instructions
+- Pre-fill with example data
+- Use data validation for dropdown fields
+- Add conditional formatting for visual cues
+- Lock formula cells, leave input cells editable
+- Include a "Make a Copy" link (Google Sheets)
+
+### Notion Templates
+- Provide a duplicate link
+- Include a getting-started guide
+- Pre-populate with example content
+- Use Notion's database features (views, filters, relations)
+- Keep it simple — don't over-engineer
+
+### Document Templates
+- Provide in multiple formats (Google Doc, Word, PDF)
+- Include placeholder text with [BRACKETS] for customization
+- Add inline instructions in a different color
+- Make it immediately usable with minimal editing
+
+**Key principle**: Templates should be usable within 5 minutes of downloading.
+
+---
+
+## Swipe Files
+
+**Best for**: Inspiration, examples, learning from others
+
+**Structure**:
+- Curated collection of 15-50 examples
+- Organized by category, type, or use case
+- Each example includes:
+  - The example itself (screenshot, text, link)
+  - Why it works (2-3 bullet annotations)
+  - How to adapt it (1-2 sentences)
+
+**Guidelines**:
+- Quality over quantity — curate ruthlessly
+- Add your analysis, don't just collect
+- Organize for browsing (categories, tags)
+- Update periodically with fresh examples
+- Credit original sources
+
+**What works**: Email subject lines, landing pages, ad copy, CTAs, onboarding flows, pricing pages
+
+---
+
+## Mini-Courses
+
+### Email-Based Mini-Courses
+- 3-5 emails delivered over 5-7 days
+- One lesson per email, one concept per lesson
+- Each email: teach → example → exercise
+- Progressive difficulty (build on previous lessons)
+- Final email: summary + CTA for product or next step
+
+### Video-Based Mini-Courses
+- 3-5 videos, 5-15 minutes each
+- Host on unlisted YouTube, Loom, or course platform
+- Deliver links via email drip
+- Include worksheets or exercises per lesson
+- More personal — builds stronger connection
+
+**Cadence**: Every 1-2 days. Don't stretch too thin or compress too tight.
+
+**Key principle**: Each lesson should deliver standalone value. If someone only watches lesson 2, they should still learn something useful.
+
+---
+
+## Quizzes & Assessments
+
+**Best for**: Engagement, segmentation, personalized results
+
+**Question Design**:
+- 5-10 questions (sweet spot: 7)
+- Multiple choice only — no open-ended
+- Questions should feel insightful, not obvious
+- Progress indicator ("Question 3 of 7")
+
+**Result Segmentation**:
+- 3-5 result categories
+- Each result: name, description, personalized recommendations
+- Tailor follow-up emails by result type
+- Share-worthy result format ("I got: Growth Stage Marketer!")
+
+**Implementation**: Gate results behind email capture. The quiz itself is ungated — the personalized results require an email.
+
+**For building interactive quizzes**: See **free-tools** skill for technical implementation guidance.
+
+---
+
+## Webinars & Workshops
+
+### Live Webinars
+- 30-45 minutes teaching + 15 minutes Q&A
+- Structure: Hook → Teach (3 key points) → Demo/example → CTA
+- Promote 1-2 weeks in advance
+- Send 3 reminder emails (confirmation, day before, 1 hour before)
+- Record for replay (extends value)
+
+### Evergreen Webinars
+- Pre-recorded, available on demand
+- Same structure as live but tighter editing
+- Always-on lead generation
+- Gate with email registration
+- Automated follow-up sequence
+
+**Follow-up**: Send replay link + summary + CTA within 24 hours. Continue with nurture sequence.
+
+**Key principle**: Teach something genuinely useful. A webinar that's just a sales pitch will damage trust.

skills/marketing-ideas/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: marketing-ideas
-version: 1.0.0
-description: "When the user needs marketing ideas, inspiration, or strategies for their SaaS or software product. Also use when the user asks for 'marketing ideas,' 'growth ideas,' 'how to market,' 'marketing strategies,' 'marketing tactics,' 'ways to promote,' or 'ideas to grow.' This skill provides 139 proven marketing approaches organized by category."
+description: "When the user needs marketing ideas, inspiration, or strategies for their SaaS or software product. Also use when the user asks for 'marketing ideas,' 'growth ideas,' 'how to market,' 'marketing strategies,' 'marketing tactics,' 'ways to promote,' 'ideas to grow,' 'what else can I try,' 'I don't know how to market this,' 'brainstorm marketing,' or 'what marketing should I do.' Use this as a starting point whenever someone is stuck or looking for inspiration on how to grow. For specific channel execution, see the relevant skill (paid-ads, social, emails, etc.)."
+metadata:
+  version: 1.1.0
 ---
 
 # Marketing Ideas for SaaS
@@ -11,7 +12,7 @@ You are a marketing strategist with a library of 139 proven marketing ideas. You
 ## How to Use This Skill
 
 **Check for product marketing context first:**
-If `.claude/product-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
+If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
 
 When asked for marketing ideas:
 1. Ask about their product, audience, and current stage if not clear
@@ -160,7 +161,7 @@ When recommending ideas, provide for each:
 ## Related Skills
 
 - **programmatic-seo**: For scaling SEO content (#4)
-- **competitor-alternatives**: For comparison pages (#11)
-- **email-sequence**: For email marketing tactics
-- **free-tool-strategy**: For engineering as marketing (#15)
+- **competitors**: For comparison pages (#11)
+- **emails**: For email marketing tactics
+- **free-tools**: For engineering as marketing (#15)
 - **referral-program**: For viral growth (#93)

skills/marketing-ideas/evals/evals.json

@@ -0,0 +1,90 @@
+{
+  "skill_name": "marketing-ideas",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "I need marketing ideas for my SaaS product. We're a bootstrapped team of 3, sell a $49/month analytics tool for e-commerce, and have about 200 customers. Budget is tight — maybe $500/month for marketing.",
+      "expected_output": "Should check for product-marketing-context.md first. Should filter ideas by low budget and early-stage constraints. Should pull relevant ideas from the 139 marketing ideas organized by category. Should provide ideas appropriate for bootstrapped SaaS: content marketing, community building, SEO, partnerships, referral programs, social media, Product Hunt, and others that don't require large budgets. Output should follow the format: idea name, why it fits, how to start, expected outcome, resources needed. Should prioritize by likely impact given their stage.",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Filters ideas by low budget constraint",
+        "Provides ideas from the 139 marketing ideas catalog",
+        "Ideas are appropriate for bootstrapped SaaS stage",
+        "Output follows structured format per idea",
+        "Includes why it fits, how to start, expected outcome",
+        "Prioritizes by likely impact",
+        "Includes resources needed per idea"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "What's the fastest way to get more leads? We sell enterprise security software and have a $10k/month marketing budget.",
+      "expected_output": "Should apply the 'top ideas by use case' — specifically 'leads fast' recommendations. Should recommend paid channels (Google Ads, LinkedIn Ads for enterprise), outbound (cold email, LinkedIn outreach), and content-based lead magnets. Should filter for enterprise-appropriate tactics. Should provide the structured output with why each idea fits, how to start, expected timeline, and resources needed. Should note that 'fast leads' typically means paid or outbound channels.",
+      "assertions": [
+        "Applies 'leads fast' use case filter",
+        "Recommends paid channels appropriate for enterprise",
+        "Recommends outbound tactics",
+        "Filters for enterprise-appropriate tactics",
+        "Provides structured output per idea",
+        "Notes that fast leads means paid or outbound",
+        "Includes timeline expectations"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "how do we grow without spending money on ads? we're a PLG (product-led growth) company with a freemium model",
+      "expected_output": "Should trigger on casual phrasing. Should apply the 'PLG' use case filter from top ideas. Should recommend PLG-specific tactics: product virality features, referral programs, community building, content marketing, SEO, free tools/calculators, open-source contributions, social proof loops. Should avoid ad-dependent ideas given the constraint. Should provide structured output with implementation guidance.",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Applies PLG use case filter",
+        "Recommends PLG-specific tactics",
+        "Avoids ad-dependent ideas",
+        "Includes virality and referral tactics",
+        "Provides structured output with implementation guidance"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "We want to build authority and thought leadership in the HR tech space. We're a newer company and nobody knows who we are yet.",
+      "expected_output": "Should apply the 'authority building' use case filter. Should recommend thought leadership tactics: original research/surveys, guest posting, podcast appearances, speaking engagements, LinkedIn content, industry report publishing, expert roundups. Should note that authority building is a longer-term play. Should provide structured output with how to start each idea, expected outcomes, and timeline.",
+      "assertions": [
+        "Applies 'authority building' use case filter",
+        "Recommends thought leadership tactics",
+        "Includes original research and content",
+        "Includes community and media appearances",
+        "Notes authority building is longer-term",
+        "Provides structured output with timelines"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "Give me 20 marketing ideas. We sell project management software.",
+      "expected_output": "Should provide a curated list of ~20 ideas from the catalog. Should organize them by category or by effort/impact. Should provide brief implementation context for each. Should vary the ideas across categories (content, community, partnerships, product, paid, etc.) for a well-rounded set. Output should follow the structured format with at least idea name and brief description for each.",
+      "assertions": [
+        "Provides approximately 20 ideas",
+        "Ideas span multiple categories",
+        "Organizes by category or effort/impact",
+        "Provides brief implementation context per idea",
+        "Output follows structured format",
+        "Ideas are relevant to project management software"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "We want to set up a referral program. How should we structure it?",
+      "expected_output": "Should recognize this is specifically a referral program design request. Should defer to or cross-reference the referral-program skill, which provides detailed guidance on referral loop design, incentive structures, implementation, and optimization. May briefly mention referral programs as a marketing idea but should make clear that referral-program is the right skill for detailed program design.",
+      "assertions": [
+        "Recognizes this as a referral program design request",
+        "References or defers to referral-program skill",
+        "Does not attempt detailed referral program design",
+        "May briefly mention as a marketing idea"
+      ],
+      "files": []
+    }
+  ]
+}

skills/marketing-ideas/references/ideas-by-category.md

@@ -2,6 +2,25 @@
 
 Complete list of proven marketing approaches organized by category.
 
+## Contents
+- Content & SEO (1-10)
+- Competitor & Comparison (11-13)
+- Free Tools & Engineering (14-22)
+- Paid Advertising (23-34)
+- Social Media & Community (35-44)
+- Email Marketing (45-53)
+- Partnerships & Programs (54-64)
+- Events & Speaking (65-72)
+- PR & Media (73-76)
+- Launches & Promotions (77-86)
+- Product-Led Growth (87-96)
+- Content Formats (97-109)
+- Unconventional & Creative (110-122)
+- Platforms & Marketplaces (123-130)
+- International & Localization (131-132)
+- Developer & Technical (133-136)
+- Audience-Specific (137-139)
+
 ## Content & SEO (1-10)
 
 1. **Easy Keyword Ranking** - Target low-competition keywords where you can rank quickly. Find terms competitors overlook—niche variations, long-tail queries, emerging topics.

skills/marketing-psychology/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: marketing-psychology
-version: 1.0.0
-description: "When the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,' 'behavioral science,' 'why people buy,' 'decision-making,' or 'consumer behavior.' This skill provides 70+ mental models organized for marketing application."
+description: "When the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,' 'behavioral science,' 'why people buy,' 'decision-making,' 'consumer behavior,' 'anchoring,' 'social proof,' 'scarcity,' 'loss aversion,' 'framing,' or 'nudge.' Use this whenever someone wants to understand or leverage how people think and make decisions in a marketing context."
+metadata:
+  version: 1.1.0
 ---
 
 # Marketing Psychology & Mental Models
@@ -11,7 +12,7 @@ You are an expert in applying psychological principles and mental models to mark
 ## How to Use This Skill
 
 **Check for product marketing context first:**
-If `.claude/product-marketing-context.md` exists, read it before applying mental models. Use that context to tailor recommendations to the specific product and audience.
+If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before applying mental models. Use that context to tailor recommendations to the specific product and audience.
 
 Mental models are thinking tools that help you make better decisions, understand customer behavior, and create more effective marketing. When helping users:
 
@@ -447,8 +448,8 @@ When facing a marketing challenge, consider:
 
 ## Related Skills
 
-- **page-cro**: Apply psychology to page optimization
+- **cro**: Apply psychology to page optimization
 - **copywriting**: Write copy using psychological principles
-- **popup-cro**: Use triggers and psychology in popups
-- **pricing-page optimization**: See page-cro for pricing psychology
-- **ab-test-setup**: Test psychological hypotheses
+- **popups**: Use triggers and psychology in popups
+- **pricing-page optimization**: See cro for pricing psychology
+- **ab-testing**: Test psychological hypotheses

skills/marketing-psychology/evals/evals.json

@@ -0,0 +1,88 @@
+{
+  "skill_name": "marketing-psychology",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "How can I use psychology to increase conversions on our pricing page? We sell a B2B SaaS tool with three tiers ($29, $79, $199/month).",
+      "expected_output": "Should check for product-marketing-context.md first. Should apply relevant pricing psychology models: anchoring (show the highest plan first or use a decoy), charm pricing (consider $29 vs $30), Rule of 100 (percentage vs dollar discounts), Good-Better-Best framing, loss aversion (show what they miss on lower tiers). Should also apply broader persuasion models: social proof near pricing, scarcity for limited-time offers, default effect (pre-select recommended plan). Should provide specific, actionable recommendations tied to their price points.",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Applies pricing psychology models (anchoring, charm pricing, Rule of 100)",
+        "Applies Good-Better-Best framing",
+        "Applies loss aversion to tier differentiation",
+        "Applies social proof near pricing",
+        "Provides specific recommendations for their price points",
+        "References specific mental models by name"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "Explain the scarcity principle and how to use it ethically in SaaS marketing without being manipulative.",
+      "expected_output": "Should explain scarcity as a mental model (limited availability increases perceived value). Should provide legitimate SaaS applications: limited beta spots, early-bird pricing with real deadlines, limited-time feature access, cohort-based launches. Should distinguish ethical scarcity (real constraints) from manufactured urgency (fake countdown timers, artificial limits). Should provide specific examples and implementation guidance. Should reference related models (urgency, FOMO, loss aversion).",
+      "assertions": [
+        "Explains scarcity principle clearly",
+        "Provides legitimate SaaS applications",
+        "Distinguishes ethical from manipulative use",
+        "Provides specific examples",
+        "References related mental models",
+        "Addresses ethical considerations directly"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "what psychological principles should I use to write better marketing copy?",
+      "expected_output": "Should trigger on casual phrasing. Should recommend copy-relevant mental models from the skill's taxonomy: social proof, reciprocity, loss aversion, anchoring, scarcity, IKEA Effect, Endowment Effect, Commitment & Consistency. For each principle, should explain what it is and provide a specific copywriting application. Should reference the quick reference table by challenge. Should organize by where in the copy each principle applies (headlines, body, CTAs, testimonials).",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Recommends copy-relevant mental models",
+        "Explains each principle briefly",
+        "Provides specific copywriting application per principle",
+        "Organizes by where each applies in copy",
+        "References multiple model categories"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "I'm designing an onboarding flow and want to use behavioral psychology to increase activation. What models should I apply?",
+      "expected_output": "Should apply design and behavioral models from the skill's taxonomy: Goal-Gradient Effect (motivation increases near goal), Hick's Law (reduce choices), IKEA Effect (let users build something), Endowment Effect (let them experience ownership), Zeigarnik Effect (incomplete tasks drive completion), Commitment & Consistency (small asks first). Should explain how each applies to onboarding specifically. Should provide actionable recommendations for each model.",
+      "assertions": [
+        "Applies Goal-Gradient Effect",
+        "Applies Hick's Law",
+        "Applies IKEA Effect or Endowment Effect",
+        "Applies Zeigarnik Effect or commitment principles",
+        "Explains how each applies to onboarding",
+        "Provides actionable recommendations per model"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "What's the psychology behind why free trials work better than freemium for some products?",
+      "expected_output": "Should apply relevant mental models: loss aversion (trial users fear losing access), endowment effect (they feel ownership after using), sunk cost (time invested during trial), Zero-Price Effect (free removes psychological barrier to start), status quo bias (inertia to keep what they have). Should explain how these models interact in trial vs freemium contexts. Should note when each model works best (trial for products with high activation effort, freemium for products with network effects).",
+      "assertions": [
+        "Applies loss aversion to trial context",
+        "Applies endowment effect",
+        "Applies Zero-Price Effect",
+        "Explains how models interact in trial vs freemium",
+        "Notes when each approach works best",
+        "Provides clear, educational explanation"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "Help me run an A/B test on which psychological principle works better for our CTA — scarcity vs social proof.",
+      "expected_output": "Should recognize this is an A/B test setup task, not a psychology task. Should defer to or cross-reference the ab-test-setup skill for the experiment design. May provide psychological context on both principles to inform the hypothesis, but should make clear that ab-test-setup is the right skill for designing and running the experiment.",
+      "assertions": [
+        "Recognizes this as an A/B test setup task",
+        "References or defers to ab-test-setup skill",
+        "May provide psychological context for hypothesis",
+        "Does not attempt full test design using psychology patterns"
+      ],
+      "files": []
+    }
+  ]
+}

skills/onboarding/SKILL.md

@@ -1,7 +1,8 @@
 ---
-name: onboarding-cro
-version: 1.0.0
-description: When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," or "new user experience." For signup/registration optimization, see signup-flow-cro. For ongoing email sequences, see email-sequence.
+name: onboarding
+description: When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," "new user experience," "users aren't activating," "nobody completes setup," "low activation rate," "users sign up but don't use the product," "time to value," or "first session experience." Use this whenever users are signing up but not sticking around. For signup/registration optimization, see signup. For ongoing email sequences, see emails.
+metadata:
+  version: 1.1.0
 ---
 
 # Onboarding CRO
@@ -11,7 +12,7 @@ You are an expert in user onboarding and activation. Your goal is to help users
 ## Initial Assessment
 
 **Check for product marketing context first:**
-If `.claude/product-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
+If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` 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 providing recommendations, understand:
 
@@ -213,7 +214,7 @@ When recommending experiments, consider tests for:
 
 ## Related Skills
 
-- **signup-flow-cro**: For optimizing the signup before onboarding
-- **email-sequence**: For onboarding email series
-- **paywall-upgrade-cro**: For converting to paid during/after onboarding
-- **ab-test-setup**: For testing onboarding changes
+- **signup**: For optimizing the signup before onboarding
+- **emails**: For onboarding email series
+- **paywalls**: For converting to paid during/after onboarding
+- **ab-testing**: For testing onboarding changes

skills/onboarding/evals/evals.json

@@ -0,0 +1,92 @@
+{
+  "skill_name": "onboarding-cro",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Help me optimize our onboarding flow. We have a project management tool and only 30% of trial users create their first project within the first week. We need to get them to value faster.",
+      "expected_output": "Should check for product-marketing-context.md first. Should start by defining the activation/aha moment — in this case, creating a first project. Should evaluate the current time-to-value and identify friction points. Should recommend an onboarding flow approach (product-first, guided setup, or value-first). Should apply the checklist pattern (3-7 items for onboarding completion). Should address empty states as opportunities to guide users. Should provide experiment ideas for testing improvements. Should include measurement metrics.",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Defines the activation/aha moment",
+        "Evaluates time-to-value",
+        "Recommends onboarding flow approach",
+        "Applies checklist pattern with 3-7 items",
+        "Addresses empty states as opportunities",
+        "Provides experiment ideas",
+        "Includes measurement metrics"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "What should our onboarding checklist include? We're a design collaboration tool. Users need to upload a design, invite a team member, and leave a comment to get full value.",
+      "expected_output": "Should apply the checklist pattern. Should include the 3 stated activation actions (upload design, invite team, leave comment). Should recommend 3-7 total items ordered by increasing commitment. Should suggest starting with the quickest win to build momentum. Should recommend progress indicators and completion rewards. Should address what happens when users skip items. Should provide specific UX recommendations for the checklist implementation.",
+      "assertions": [
+        "Applies checklist pattern",
+        "Includes the 3 stated activation actions",
+        "Limits to 3-7 total items",
+        "Orders by increasing commitment",
+        "Starts with quickest win",
+        "Recommends progress indicators",
+        "Addresses skipped items",
+        "Provides UX recommendations"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "our users sign up but then never come back. like 50% don't even log in a second time. what do we do?",
+      "expected_output": "Should trigger on casual phrasing. Should address this as a stalled users problem. Should apply the handling stalled users framework: identify drop-off points, re-engagement triggers, multi-channel outreach (email, in-app, push). Should investigate root causes: is the first-run experience too complex? Is value not immediately apparent? Is the setup too long? Should recommend immediate improvements to the first session experience. Should suggest multi-channel onboarding (email sequences to bring them back). Should cross-reference email-sequence for re-engagement emails.",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Applies stalled users framework",
+        "Identifies potential root causes for drop-off",
+        "Recommends first-session experience improvements",
+        "Suggests multi-channel onboarding",
+        "Cross-references email-sequence for re-engagement",
+        "Provides specific re-engagement triggers"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "How do we handle the empty state when a new user first logs in? Right now they just see a blank dashboard.",
+      "expected_output": "Should apply the empty states as opportunities guidance. Should recommend turning the blank dashboard into a guided experience: sample data to show what the product looks like populated, a clear first action CTA, contextual tips, or a quick-start wizard. Should provide specific recommendations for empty state design: what to show, what action to prompt, how to reduce the 'blank canvas paralysis.' Should reference patterns by product type if applicable.",
+      "assertions": [
+        "Applies empty states as opportunities guidance",
+        "Recommends alternatives to blank dashboard",
+        "Suggests sample data or templates",
+        "Provides clear first action CTA",
+        "Addresses blank canvas paralysis",
+        "Provides specific empty state design recommendations"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "Should we use tooltips, a product tour, or a setup wizard for onboarding? What works best?",
+      "expected_output": "Should apply the tooltips/guided tours guidance. Should compare the approaches: tooltips (contextual, on-demand, less intrusive), product tours (guided walkthrough, can overwhelm), setup wizards (structured, ensures key setup steps). Should recommend based on product complexity and onboarding goals. Should note that the best approach often combines elements. Should provide best practices for each: tooltip fatigue avoidance, tour length limits, wizard step count. Should recommend testing different approaches.",
+      "assertions": [
+        "Compares tooltips, product tours, and setup wizards",
+        "Explains when each works best",
+        "Notes that combination approaches often work",
+        "Provides best practices for each",
+        "Addresses tooltip fatigue and tour length",
+        "Recommends testing different approaches"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "Our signup form has 8 fields and people keep dropping off. Can you help us fix the signup flow?",
+      "expected_output": "Should recognize this is a signup flow optimization task, not post-signup onboarding. Should defer to or cross-reference the signup-flow-cro skill, which handles signup form optimization, field reduction, and registration flow design. Onboarding-cro covers what happens after signup. Should make this distinction clear.",
+      "assertions": [
+        "Recognizes this as signup flow optimization, not onboarding",
+        "References or defers to signup-flow-cro skill",
+        "Explains that onboarding-cro covers post-signup",
+        "Does not attempt signup form redesign using onboarding patterns"
+      ],
+      "files": []
+    }
+  ]
+}

skills/onboarding/references/experiments.md

@@ -2,6 +2,16 @@
 
 Comprehensive list of A/B tests and experiments for user onboarding and activation.
 
+## Contents
+- Flow Simplification Experiments (reduce friction, step sequencing, progress & motivation)
+- Guided Experience Experiments (product tours, CTA optimization, UI guidance)
+- Personalization Experiments (user segmentation, dynamic content)
+- Quick Wins & Engagement Experiments (time-to-value, motivation mechanics, support & help)
+- Email & Multi-Channel Experiments (onboarding emails, email content, feedback loops)
+- Re-engagement Experiments (stalled user recovery, return experience)
+- Technical & UX Experiments (performance, mobile onboarding, accessibility)
+- Metrics to Track
+
 ## Flow Simplification Experiments
 
 ### Reduce Friction

skills/paid-ads/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: paid-ads
-version: 1.0.0
-description: "When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions 'PPC,' 'paid media,' 'ad copy,' 'ad creative,' 'ROAS,' 'CPA,' 'ad campaign,' 'retargeting,' or 'audience targeting.' This skill covers campaign strategy, ad creation, audience targeting, and optimization."
+description: "When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions 'PPC,' 'paid media,' 'ROAS,' 'CPA,' 'ad campaign,' 'retargeting,' 'audience targeting,' 'Google Ads,' 'Facebook ads,' 'LinkedIn ads,' 'ad budget,' 'cost per click,' 'ad spend,' or 'should I run ads.' Use this for campaign strategy, audience targeting, bidding, and optimization. For bulk ad creative generation and iteration, see ad-creative. For landing page optimization, see cro."
+metadata:
+  version: 1.1.0
 ---
 
 # Paid Ads
@@ -11,7 +12,7 @@ You are an expert performance marketer with direct access to ad platform account
 ## Before Starting
 
 **Check for product marketing context first:**
-If `.claude/product-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
+If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
 
 Gather this context (ask if not provided):
 
@@ -121,7 +122,7 @@ LI_LeadGen_CMOs-SaaS_Whitepaper_Mar24
 
 - **Lookalikes**: Base on best customers (by LTV), not all customers
 - **Retargeting**: Segment by funnel stage (visitors vs. cart abandoners)
-- **Exclusions**: Always exclude existing customers and recent converters
+- **Exclusions**: Exclude existing customers and recent converters — showing ads to people who already bought wastes spend
 
 **For detailed targeting strategies by platform**: See [references/audience-targeting.md](references/audience-targeting.md)
 
@@ -307,7 +308,8 @@ For tracking, see also: [ga4.md](../../tools/integrations/ga4.md), [segment.md](
 
 ## Related Skills
 
+- **ad-creative**: For generating and iterating ad headlines, descriptions, and creative at scale
 - **copywriting**: For landing page copy that converts ad traffic
-- **analytics-tracking**: For proper conversion tracking setup
-- **ab-test-setup**: For landing page testing to improve ROAS
-- **page-cro**: For optimizing post-click conversion rates
+- **analytics**: For proper conversion tracking setup
+- **ab-testing**: For landing page testing to improve ROAS
+- **cro**: For optimizing post-click conversion rates

skills/paid-ads/evals/evals.json

@@ -0,0 +1,90 @@
+{
+  "skill_name": "paid-ads",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Help me plan a paid advertising strategy. We're a B2B SaaS tool for HR teams, selling at $99/month per seat. We have $15k/month to spend on ads and want to generate demo requests. Where should we advertise?",
+      "expected_output": "Should check for product-marketing-context.md first. Should apply the platform selection guide based on B2B, HR audience, $99/month price point. Should recommend LinkedIn (B2B targeting by job title/industry), Google Ads (search intent for HR software keywords), and potentially Meta (retargeting). Should recommend campaign structure with naming conventions. Should define audience targeting strategy for each platform. Should set budget allocation across platforms. Should define success metrics and attribution approach. Should recommend starting structure and scaling plan.",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Applies platform selection guide",
+        "Recommends platforms appropriate for B2B HR audience",
+        "Recommends campaign structure with naming conventions",
+        "Defines audience targeting per platform",
+        "Sets budget allocation across platforms",
+        "Defines success metrics",
+        "Recommends starting structure and scaling plan"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "Our Google Ads CPC is $12 and our cost per lead is $180. Is that good? We're getting about 80 leads/month from a $15k budget.",
+      "expected_output": "Should evaluate the metrics in context. Should assess: $12 CPC for B2B (reasonable depending on industry), $180 CPL (depends on LTV — need to compare against customer lifetime value), 80 leads/month from $15k (math checks out). Should apply the campaign optimization framework: check quality score, search term relevance, landing page conversion rate, negative keywords. Should recommend specific optimization levers to reduce CPC and CPL. Should frame performance against industry benchmarks if applicable. Should ask about downstream conversion rates (lead → demo → customer).",
+      "assertions": [
+        "Evaluates metrics in context",
+        "Compares CPL against LTV considerations",
+        "Applies campaign optimization framework",
+        "Recommends specific optimization levers",
+        "Asks about downstream conversion rates",
+        "Provides industry context for benchmarking"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "we want to run retargeting ads for people who visited our site but didn't convert. how should we set this up?",
+      "expected_output": "Should trigger on casual phrasing. Should apply the retargeting strategies section, specifically the funnel-based approach. Should recommend audience segments: all visitors (broad), pricing page visitors (high intent), blog readers (lower intent), and cart/signup abandoners (highest intent). Should recommend different messaging and offers for each segment. Should address frequency capping to avoid ad fatigue. Should recommend retargeting platforms (Meta, Google Display, LinkedIn). Should include duration windows for each audience.",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Applies funnel-based retargeting approach",
+        "Recommends audience segments by intent level",
+        "Recommends different messaging per segment",
+        "Addresses frequency capping",
+        "Recommends retargeting platforms",
+        "Includes audience duration windows"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "Should we advertise on TikTok? We sell accounting software to small businesses. Our current ads are on Google and Meta.",
+      "expected_output": "Should apply the platform selection guide for TikTok specifically. Should evaluate TikTok fit for accounting software + small business audience: likely a weaker fit than Google/Meta for this category (lower purchase intent, younger skewing audience, less B2B targeting). Should discuss when TikTok CAN work for B2B (brand awareness, creative content, younger business owners). Should provide an honest recommendation with caveats. Should suggest a small test budget approach if they want to try.",
+      "assertions": [
+        "Applies platform selection guide for TikTok",
+        "Evaluates fit for accounting + small business audience",
+        "Provides honest assessment of likely weaker fit",
+        "Discusses when TikTok can work for B2B",
+        "Suggests small test budget if proceeding",
+        "Compares to their existing Google/Meta performance"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "How do we structure our Google Ads campaigns? We have 50+ keywords we want to target for our CRM product.",
+      "expected_output": "Should apply the campaign structure and naming conventions framework. Should recommend organizing campaigns by theme/intent (brand, competitor, product features, pain points). Should recommend ad group structure (tightly themed, 5-15 keywords per group). Should define naming conventions for campaigns and ad groups. Should recommend match types strategy. Should include negative keyword lists. Should provide a sample campaign structure.",
+      "assertions": [
+        "Applies campaign structure framework",
+        "Organizes campaigns by theme/intent",
+        "Recommends tight ad group structure",
+        "Defines naming conventions",
+        "Recommends match types strategy",
+        "Includes negative keyword lists",
+        "Provides sample campaign structure"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "Can you write some ad copy for our Facebook ads? We need headlines and descriptions for 5 different angles.",
+      "expected_output": "Should recognize this is an ad creative generation task, not campaign strategy. Should defer to or cross-reference the ad-creative skill, which handles platform-specific ad copy generation with character limits, angle-based variation, and batch generation. May provide brief ad copy framework guidance but should make clear that ad-creative is the right skill for generating ad copy at scale.",
+      "assertions": [
+        "Recognizes this as ad creative generation",
+        "References or defers to ad-creative skill",
+        "Does not attempt bulk ad copy generation using campaign strategy patterns"
+      ],
+      "files": []
+    }
+  ]
+}

skills/paid-ads/references/ad-copy-templates.md

@@ -2,6 +2,13 @@
 
 Detailed formulas and templates for writing high-converting ad copy.
 
+## Contents
+- Primary Text Formulas (Problem-Agitate-Solve, Before-After-Bridge, Social Proof Lead, Feature-Benefit Bridge, Direct Response)
+- Headline Formulas (For Search Ads, For Social Ads)
+- CTA Variations (Soft CTAs, Hard CTAs, Urgency CTAs, Action-Oriented CTAs)
+- Platform-Specific Copy Guidelines (Google Search Ads, Meta Ads, LinkedIn Ads)
+- Copy Testing Priority
+
 ## Primary Text Formulas
 
 ### Problem-Agitate-Solve (PAS)

skills/paid-ads/references/audience-targeting.md

@@ -2,6 +2,15 @@
 
 Detailed targeting strategies for each major ad platform.
 
+## Contents
+- Google Ads Audiences (Search Campaign Targeting, Display/YouTube Targeting)
+- Meta Audiences (Core Audiences, Custom Audiences, Lookalike Audiences)
+- LinkedIn Audiences (Job-Based Targeting, Company-Based Targeting, High-Performing Combinations)
+- Twitter/X Audiences
+- TikTok Audiences
+- Audience Size Guidelines
+- Exclusion Strategy
+
 ## Google Ads Audiences
 
 ### Search Campaign Targeting

skills/paid-ads/references/platform-setup-checklists.md

@@ -2,6 +2,14 @@
 
 Complete setup checklists for major ad platforms.
 
+## Contents
+- Google Ads Setup (Account Foundation, Conversion Tracking, Analytics Integration, Audience Setup, Campaign Readiness, Ad Extensions, Brand Protection)
+- Meta Ads Setup (Business Manager Foundation, Pixel & Tracking, Domain & Aggregated Events, Audience Setup, Catalog, Creative Assets, Compliance)
+- LinkedIn Ads Setup (Campaign Manager Foundation, Insight Tag & Tracking, Audience Setup, Lead Gen Forms, Document Ads, Creative Assets, Budget Considerations)
+- Twitter/X Ads Setup (Account Foundation, Tracking, Audience Setup, Creative)
+- TikTok Ads Setup (Account Foundation, Pixel & Tracking, Audience Setup, Creative)
+- Universal Pre-Launch Checklist
+
 ## Google Ads Setup
 
 ### Account Foundation

skills/paywalls/SKILL.md

@@ -1,7 +1,8 @@
 ---
-name: paywall-upgrade-cro
-version: 1.0.0
-description: When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," or "in-app pricing." Distinct from public pricing pages (see page-cro) — this skill focuses on in-product upgrade moments where the user has already experienced value.
+name: paywalls
+description: When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," "in-app pricing," "free users won't upgrade," "trial to paid conversion," or "how do I get users to pay." Use this for any in-product moment where you're asking users to upgrade. Distinct from public pricing pages (see cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see pricing.
+metadata:
+  version: 1.1.0
 ---
 
 # Paywall and Upgrade Screen CRO
@@ -11,7 +12,7 @@ You are an expert in in-app paywalls and upgrade flows. Your goal is to convert
 ## Initial Assessment
 
 **Check for product marketing context first:**
-If `.claude/product-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
+If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` 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 providing recommendations, understand:
 
@@ -220,6 +221,7 @@ What you've accomplished:
 
 ## Related Skills
 
-- **page-cro**: For public pricing page optimization
-- **onboarding-cro**: For driving to aha moment before upgrade
-- **ab-test-setup**: For testing paywall variations
+- **churn-prevention**: For cancel flows, save offers, and reducing churn post-upgrade
+- **cro**: For public pricing page optimization
+- **onboarding**: For driving to aha moment before upgrade
+- **ab-testing**: For testing paywall variations

skills/paywalls/evals/evals.json

@@ -0,0 +1,93 @@
+{
+  "skill_name": "paywall-upgrade-cro",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Help me design the upgrade paywall for our project management tool. Free users can have 3 projects, and we want to show an upgrade screen when they try to create a 4th project.",
+      "expected_output": "Should check for product-marketing-context.md first. Should identify this as a usage limit trigger point. Should apply the paywall screen components: headline (communicate the value of upgrading, not just the limit), value demonstration (show what they get with paid plan), plan comparison (free vs paid), social proof, CTA (specific and action-oriented), and escape hatch (option to go back). Should provide specific copy recommendations. Should address the emotional state of the user at this moment (frustrated by the limit). Should warn against anti-patterns.",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Identifies as usage limit trigger",
+        "Applies paywall screen components framework",
+        "Includes headline, value demo, comparison, social proof, CTA",
+        "Provides specific copy recommendations",
+        "Addresses user's emotional state at the limit",
+        "Includes escape hatch option",
+        "Warns against anti-patterns"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "Our free trial expires in 14 days and users see a generic 'Your trial has expired' screen. Upgrade rate from this screen is only 2%. How do we improve it?",
+      "expected_output": "Should identify this as a trial expiration trigger. Should apply the trial expiration paywall type guidance. Should recommend: show what they've built/accomplished during the trial (endowment effect), highlight specific features they used, show the value they'd lose, provide clear plan options, include social proof from similar users who upgraded. Should diagnose why 2% is low: likely a weak value prop, no personalization, no urgency or loss framing. Should provide specific redesign recommendations.",
+      "assertions": [
+        "Identifies as trial expiration trigger",
+        "Applies trial expiration paywall guidance",
+        "Recommends showing user's accomplishments during trial",
+        "Uses loss framing (what they'd lose)",
+        "Provides clear plan options",
+        "Includes social proof",
+        "Diagnoses why current 2% rate is low",
+        "Provides specific redesign recommendations"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "when should we show upgrade prompts? we don't want to be annoying but we also need to convert free users to paid.",
+      "expected_output": "Should trigger on casual phrasing. Should apply the timing and frequency rules. Should recommend trigger points from the skill: feature gates (when they try a paid feature), usage limits (when they hit a threshold), value moments (when they've just experienced success), and natural transition points. Should address frequency capping to avoid being annoying. Should recommend the anti-patterns to avoid (blocking basic functionality, too frequent popups, dark patterns). Should provide a balanced approach that respects user experience while driving upgrades.",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Applies timing and frequency rules",
+        "Recommends specific trigger points",
+        "Addresses frequency capping",
+        "Warns against anti-patterns",
+        "Balances user experience with conversion goals",
+        "Provides specific recommendations for each trigger type"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "Design a feature gate paywall. When free users click on 'Advanced Analytics' in our dashboard, we want to show them an upgrade prompt.",
+      "expected_output": "Should identify this as a feature gate trigger. Should apply the feature lock paywall type guidance. Should recommend: show a preview or screenshot of the advanced analytics feature, explain the specific benefit (not just 'this is a paid feature'), include a plan comparison relevant to analytics, provide a clear CTA to upgrade, and include an escape hatch to go back to basic analytics. Should recommend showing what insights they're missing. Should provide copy recommendations for the paywall screen.",
+      "assertions": [
+        "Identifies as feature gate trigger",
+        "Applies feature lock paywall guidance",
+        "Recommends showing preview of the feature",
+        "Explains specific benefit of the feature",
+        "Includes relevant plan comparison",
+        "Provides clear CTA and escape hatch",
+        "Provides copy recommendations"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "What are common mistakes to avoid with in-app paywalls? I don't want to be pushy or make users feel tricked.",
+      "expected_output": "Should apply the anti-patterns section. Should cover: dark patterns (making it hard to find the close button, confusing opt-out language), conversion killers (blocking basic functionality, showing paywalls too early before value is demonstrated, no escape hatch), frequency issues (too many prompts, showing the same paywall repeatedly). Should provide positive alternatives for each anti-pattern. Should emphasize that good paywalls feel helpful, not pushy.",
+      "assertions": [
+        "Applies anti-patterns section",
+        "Covers dark patterns to avoid",
+        "Covers conversion killers",
+        "Covers frequency issues",
+        "Provides positive alternatives for each",
+        "Emphasizes helpful over pushy approach"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "Can you help me optimize our public pricing page? We want more visitors to choose the Pro plan over the Basic plan.",
+      "expected_output": "Should recognize this is a public pricing page optimization task, not an in-app paywall task. Should defer to or cross-reference the cro skill for pricing page CRO. Paywall-upgrade-cro specifically handles in-app upgrade prompts for existing users, not public-facing pricing pages.",
+      "assertions": [
+        "Recognizes this as public pricing page optimization",
+        "References or defers to cro skill",
+        "Explains that paywall-upgrade-cro is for in-app upgrade prompts",
+        "Does not attempt public pricing page optimization"
+      ],
+      "files": []
+    }
+  ]
+}

skills/paywalls/references/experiments.md

@@ -2,6 +2,15 @@
 
 Comprehensive list of A/B tests and experiments for paywall optimization.
 
+## Contents
+- Trigger & Timing Experiments (When to Show, Trigger Type)
+- Paywall Design Experiments (Layout & Format, Value Presentation, Visual Elements)
+- Pricing Presentation Experiments (Price Display, Plan Options, Discounts & Offers)
+- Copy & Messaging Experiments (Headlines, CTAs, Objection Handling)
+- Trial & Conversion Experiments (Trial Structure, Trial Expiration, Upgrade Path)
+- Personalization Experiments (Usage-Based, Segment-Specific)
+- Frequency & UX Experiments (Frequency Capping, Dismiss Behavior)
+
 ## Trigger & Timing Experiments
 
 ### When to Show

skills/popups/SKILL.md

@@ -1,7 +1,8 @@
 ---
-name: popup-cro
-version: 1.0.0
-description: When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," or "overlay." For forms outside of popups, see form-cro. For general page conversion optimization, see page-cro.
+name: popups
+description: When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," "overlay," "collect emails with a popup," "exit popup," "scroll trigger," "sticky bar," or "notification bar." Use this for any overlay or interrupt-style conversion element. For forms outside of popups, see cro. For general page conversion optimization, see cro.
+metadata:
+  version: 1.1.0
 ---
 
 # Popup CRO
@@ -11,7 +12,7 @@ You are an expert in popup and modal optimization. Your goal is to create popups
 ## Initial Assessment
 
 **Check for product marketing context first:**
-If `.claude/product-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
+If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` 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 providing recommendations, understand:
 
@@ -181,7 +182,7 @@ Before providing recommendations, understand:
 - Leave space to close (visible X, click outside)
 
 ### Close Button
-- Always visible (top right is convention)
+- Keep visible (top right is convention) — users who can't find the close button will bounce entirely
 - Large enough to tap on mobile
 - "No thanks" text link as alternative
 - Click outside to close
@@ -446,7 +447,8 @@ Ideas to A/B test with expected outcomes
 
 ## Related Skills
 
-- **form-cro**: For optimizing the form inside the popup
-- **page-cro**: For the page context around popups
-- **email-sequence**: For what happens after popup conversion
-- **ab-test-setup**: For testing popup variations
+- **lead-magnets**: For planning lead magnets to promote via popups
+- **cro**: For optimizing the form inside the popup
+- **cro**: For the page context around popups
+- **emails**: For what happens after popup conversion
+- **ab-testing**: For testing popup variations

skills/popups/evals/evals.json

@@ -0,0 +1,94 @@
+{
+  "skill_name": "popup-cro",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Help me create an exit-intent popup for our SaaS landing page. We want to capture emails from visitors who are about to leave without signing up. Our product is a social media scheduling tool.",
+      "expected_output": "Should check for product-marketing-context.md first. Should identify the popup type as exit-intent email capture. Should apply the exit-intent popup design guidance: compelling headline (address why they're leaving or offer additional value), lead magnet or incentive (discount, free resource, extended trial), minimal form fields (email only), clear CTA, and easy close option. Should apply copy formulas from the skill. Should address trigger configuration (exit intent detection). Should recommend frequency rules (don't show again if dismissed). Should include benchmarks (exit intent popups typically 3-10% conversion).",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Identifies as exit-intent popup type",
+        "Includes compelling headline",
+        "Includes lead magnet or incentive",
+        "Minimal form fields (email only)",
+        "Applies copy formulas from the skill",
+        "Addresses trigger configuration",
+        "Recommends frequency rules",
+        "Includes conversion benchmarks"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "We want to offer a 10% discount to first-time visitors via a popup. When should we show it and what should it say?",
+      "expected_output": "Should identify this as a discount/offer popup type. Should apply trigger strategy guidance: recommend against showing immediately on page load (too aggressive). Should suggest time-based delay (30-60 seconds), scroll-based trigger (50%+ page scroll), or exit intent as better alternatives. Should apply the copy formula for discount popups: headline that frames the value, clear offer terms, urgency element, email capture, and CTA. Should address compliance (GDPR cookie consent if applicable). Should recommend frequency capping.",
+      "assertions": [
+        "Identifies as discount popup type",
+        "Recommends against immediate page load trigger",
+        "Suggests better trigger alternatives (time, scroll, exit)",
+        "Applies copy formula for discount popups",
+        "Includes urgency element",
+        "Addresses frequency capping",
+        "Addresses compliance considerations"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "our popups are annoying everyone. we keep getting complaints but we also get a lot of email signups from them. how do we balance this?",
+      "expected_output": "Should trigger on casual phrasing. Should apply the frequency and rules guidance. Should address the balance: reduce annoyance while preserving conversions. Should recommend: frequency capping (once per session or once per X days), don't show to returning visitors who already dismissed, don't show to existing subscribers, respect 'close' action, consider less intrusive formats (slide-in instead of full modal, announcement bar instead of overlay). Should address compliance and accessibility requirements. Should suggest A/B testing different triggers and formats to find the best balance.",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Applies frequency and rules guidance",
+        "Addresses balance between conversions and UX",
+        "Recommends frequency capping",
+        "Suggests excluding existing subscribers",
+        "Recommends less intrusive alternatives",
+        "Suggests A/B testing to optimize"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "What types of popups should we use on our blog? We publish content about email marketing and want to grow our email list.",
+      "expected_output": "Should recommend blog-appropriate popup types: scroll-triggered popup (show after 50-70% scroll indicating engagement), exit-intent popup, slide-in (less intrusive than modal), and inline content upgrades. Should recommend lead magnets relevant to the blog topic (email marketing templates, checklist, swipe file). Should address different popup placements: mid-content, end of post, sidebar slide-in. Should recommend behavior-based triggers over time-based for blog content. Should apply copy formulas with blog-specific hooks.",
+      "assertions": [
+        "Recommends blog-appropriate popup types",
+        "Includes scroll-triggered and exit-intent",
+        "Suggests less intrusive formats (slide-in)",
+        "Recommends relevant lead magnets",
+        "Addresses popup placement on blog pages",
+        "Recommends behavior-based triggers for blog",
+        "Applies copy formulas"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "Design an announcement banner for our new feature launch. We want it to show at the top of the site for 2 weeks.",
+      "expected_output": "Should identify this as an announcement banner popup type. Should apply banner design guidance: short, clear headline announcing the feature, brief description of benefit, CTA to learn more or try it, dismiss option. Should recommend banner positioning (top of page, sticky or static). Should address duration (2 weeks as stated). Should recommend targeting (show to existing users who'd benefit, not just everyone). Should provide copy recommendations.",
+      "assertions": [
+        "Identifies as announcement banner type",
+        "Provides short, clear headline",
+        "Includes brief benefit description and CTA",
+        "Includes dismiss option",
+        "Addresses banner positioning",
+        "Recommends audience targeting",
+        "Provides copy recommendations"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "We need to optimize the lead capture form inside our popup. It currently asks for name, email, company, and phone number. Too many fields?",
+      "expected_output": "Should recognize this overlaps with form optimization. Should defer to or cross-reference the cro skill, which handles form field optimization, layout, and conversion. May provide popup-specific context (popups need minimal fields due to fleeting attention) but should make clear that cro is the right skill for detailed form optimization.",
+      "assertions": [
+        "Recognizes overlap with form optimization",
+        "References or defers to cro skill",
+        "Notes popups need minimal fields due to context",
+        "Does not attempt detailed form redesign"
+      ],
+      "files": []
+    }
+  ]
+}

skills/pricing/SKILL.md

@@ -1,7 +1,8 @@
 ---
-name: pricing-strategy
-version: 1.0.0
-description: "When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' or 'monetization.' This skill covers pricing research, tier structure, and packaging strategy."
+name: pricing
+description: "When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' or 'should I offer a free plan.' Use this whenever someone is figuring out what to charge or how to structure their plans. For in-app upgrade screens, see paywalls."
+metadata:
+  version: 1.1.0
 ---
 
 # Pricing Strategy
@@ -11,7 +12,7 @@ You are an expert in SaaS pricing and monetization strategy. Your goal is to hel
 ## Before Starting
 
 **Check for product marketing context first:**
-If `.claude/product-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
+If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
 
 Gather this context (ask if not provided):
 
@@ -221,7 +222,10 @@ Identifies which features customers value most:
 
 ## Related Skills
 
-- **page-cro**: For optimizing pricing page conversion
+- **churn-prevention**: For cancel flows, save offers, and reducing revenue churn
+- **cro**: For optimizing pricing page conversion
 - **copywriting**: For pricing page copy
 - **marketing-psychology**: For pricing psychology principles
-- **ab-test-setup**: For testing pricing changes
+- **ab-testing**: For testing pricing changes
+- **revops**: For deal desk processes and pipeline pricing
+- **sales-enablement**: For proposal templates and pricing presentations

skills/pricing/evals/evals.json

@@ -0,0 +1,90 @@
+{
+  "skill_name": "pricing-strategy",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Help me figure out pricing for our new SaaS product. It's a customer support platform for e-commerce stores. We're not sure whether to charge per agent, per ticket, or flat rate. Currently thinking $49-199/month range.",
+      "expected_output": "Should check for product-marketing-context.md first. Should apply the three pricing axes framework: packaging (what's included in each tier), pricing metric (per agent, per ticket, flat rate — evaluate each), price point ($49-199 range evaluation). Should discuss value metrics and which aligns best with value delivered (per agent is common in support, but per ticket aligns with usage). Should recommend a good-better-best tier structure. Should address pricing psychology. Should provide a specific pricing recommendation with rationale.",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Applies three pricing axes framework",
+        "Evaluates multiple pricing metrics",
+        "Discusses which metric aligns with value delivered",
+        "Recommends good-better-best tier structure",
+        "Addresses pricing psychology",
+        "Provides specific pricing recommendation with rationale"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "We want to raise our prices by 30%. We've been at $29/month for 2 years and we've added a lot of features. How do we do this without losing customers?",
+      "expected_output": "Should apply the 'when to raise prices' and price increase strategies sections. Should recommend a strategy: grandfather existing customers (or give them a grace period), tie the increase to new value, communicate the change clearly with advance notice, consider an annual billing discount as a softening measure. Should address different approaches (immediate for new customers, delayed for existing). Should recommend specific communication strategy. Should note that some churn is expected and acceptable.",
+      "assertions": [
+        "Applies price increase strategies",
+        "Recommends grandfathering or grace period approach",
+        "Recommends tying increase to new value",
+        "Provides communication strategy",
+        "Addresses new vs existing customer timing",
+        "Suggests annual billing as softening measure",
+        "Notes some churn is expected"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "how do we figure out what people will actually pay? we're launching a new product and have no idea what to charge.",
+      "expected_output": "Should trigger on casual phrasing. Should apply the pricing research methods: Van Westendorp price sensitivity analysis (too cheap, bargain, expensive, too expensive), MaxDiff for feature importance, competitive benchmarking. Should explain how to run each method. Should also recommend simpler approaches: talking to potential customers, analyzing competitor pricing, testing different price points. Should provide a practical pricing research plan they can execute.",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Applies Van Westendorp price sensitivity method",
+        "Applies MaxDiff for feature importance",
+        "Recommends competitive benchmarking",
+        "Explains how to run each method",
+        "Suggests practical alternatives (customer interviews, competitive analysis)",
+        "Provides executable pricing research plan"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "We have a Basic ($19), Pro ($49), and Enterprise (custom) plan. The Pro plan gets 70% of signups. Should we add a plan between Pro and Enterprise?",
+      "expected_output": "Should apply the good-better-best tier structure framework. Should analyze the current situation: Pro capturing 70% is actually healthy, but the gap to Enterprise suggests there may be mid-market customers underserved. Should evaluate whether a 4th tier makes sense: does it address a real gap, or will it create choice paralysis? Should apply pricing psychology (Hick's Law — more options can reduce decisions). Should recommend either a 4th tier with clear differentiation or adjusting the Pro plan to better bridge the gap.",
+      "assertions": [
+        "Applies good-better-best tier structure",
+        "Analyzes current tier performance",
+        "Evaluates whether 4th tier addresses real gap",
+        "Considers choice paralysis risk",
+        "Applies pricing psychology (Hick's Law)",
+        "Provides specific recommendation with rationale"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "What pricing psychology tactics should we use on our pricing page? We want the $79 plan to be the most popular.",
+      "expected_output": "Should apply the pricing psychology section: anchoring (show the $79 plan next to a higher-priced plan), decoy effect (make the lower plan look less valuable), visual emphasis (highlight or 'recommend' the $79 plan), charm pricing ($79 vs $80), Rule of 100 (percentage discounts below $100, dollar discounts above), loss framing (show what lower plans miss). Should provide specific pricing page design recommendations. Should cross-reference cro for broader pricing page optimization.",
+      "assertions": [
+        "Applies pricing psychology tactics",
+        "Applies anchoring effect",
+        "Applies decoy effect or visual emphasis",
+        "Applies charm pricing or Rule of 100",
+        "Provides specific pricing page recommendations",
+        "Cross-references cro or marketing-psychology"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "Our pricing page conversion rate is only 1.5%. Can you review the page and suggest improvements?",
+      "expected_output": "Should recognize this is a pricing page conversion optimization task, not a pricing strategy task. Should defer to or cross-reference the cro skill, which handles pricing page conversion rate optimization including plan comparison clarity, CTA optimization, and trust signals. Pricing-strategy focuses on the actual pricing decisions (what to charge, how to package), not the page design.",
+      "assertions": [
+        "Recognizes this as pricing page CRO, not pricing strategy",
+        "References or defers to cro skill",
+        "Explains that pricing-strategy is about pricing decisions",
+        "Does not attempt full page CRO audit"
+      ],
+      "files": []
+    }
+  ]
+}

skills/pricing/references/research-methods.md

@@ -1,5 +1,11 @@
 # Pricing Research Methods
 
+## Contents
+- Van Westendorp Price Sensitivity Meter (The Four Questions, How to Analyze, Survey Tips, Sample Output)
+- MaxDiff Analysis (How It Works, Example Survey Question, Analyzing Results, Using MaxDiff for Packaging)
+- Willingness to Pay Surveys
+- Usage-Value Correlation Analysis
+
 ## Van Westendorp Price Sensitivity Meter
 
 The Van Westendorp survey identifies the acceptable price range for your product.

skills/pricing/references/tier-structure.md

@@ -1,5 +1,14 @@
 # Tier Structure and Packaging
 
+## Contents
+- How Many Tiers?
+- Good-Better-Best Framework
+- Tier Differentiation Strategies
+- Example Tier Structure
+- Packaging for Personas (Identifying Pricing Personas, Persona-Based Packaging)
+- Freemium vs. Free Trial (When to Use Freemium, When to Use Free Trial, Hybrid Approaches)
+- Enterprise Pricing (When to Add Custom Pricing, Enterprise Tier Elements, Enterprise Pricing Strategies)
+
 ## How Many Tiers?
 
 **2 tiers:** Simple, clear choice

skills/product-marketing/SKILL.md

@@ -1,20 +1,21 @@
 ---
-name: product-marketing-context
-version: 1.0.0
-description: "When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' or wants to avoid repeating foundational information across marketing tasks. Creates `.claude/product-marketing-context.md` that other marketing skills reference."
+name: product-marketing
+description: "When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' 'who is my target audience,' 'describe my product,' 'ICP,' 'ideal customer profile,' or wants to avoid repeating foundational information across marketing tasks. Use this at the start of any new project before using other marketing skills — it creates `.agents/product-marketing-context.md` that all other skills reference for product, audience, and positioning context."
+metadata:
+  version: 1.1.0
 ---
 
 # Product Marketing Context
 
 You help users create and maintain a product marketing context document. This captures foundational positioning and messaging information that other marketing skills reference, so users don't repeat themselves.
 
-The document is stored at `.claude/product-marketing-context.md`.
+The document is stored at `.agents/product-marketing-context.md`.
 
 ## Workflow
 
 ### Step 1: Check for Existing Context
 
-First, check if `.claude/product-marketing-context.md` already exists.
+First, check if `.agents/product-marketing-context.md` already exists. Also check `.claude/product-marketing-context.md` for older setups — if found there but not in `.agents/`, offer to move it.
 
 **If it exists:**
 - Read it and summarize what's captured
@@ -46,7 +47,7 @@ For each section:
 3. Confirm accuracy
 4. Move to the next
 
-**Important:** Push for verbatim customer language. Exact phrases are more valuable than polished descriptions.
+Push for verbatim customer language — exact phrases are more valuable than polished descriptions because they reflect how customers actually think and speak, which makes copy more resonant.
 
 ---
 
@@ -127,7 +128,7 @@ The JTBD Four Forces:
 
 ## Step 3: Create the Document
 
-After gathering information, create `.claude/product-marketing-context.md` with this structure:
+After gathering information, create `.agents/product-marketing-context.md` with this structure:
 
 ```markdown
 # Product Marketing Context
@@ -226,7 +227,7 @@ After gathering information, create `.claude/product-marketing-context.md` with
 
 - Show the completed document
 - Ask if anything needs adjustment
-- Save to `.claude/product-marketing-context.md`
+- Save to `.agents/product-marketing-context.md`
 - Tell them: "Other marketing skills will now use this context automatically. Run `/product-marketing-context` anytime to update it."
 
 ---

skills/product-marketing/evals/evals.json

@@ -0,0 +1,85 @@
+{
+  "skill_name": "product-marketing-context",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "I want to set up my product marketing context. We're a B2B SaaS company that sells a customer feedback platform to product teams.",
+      "expected_output": "Should check if .agents/product-marketing-context.md already exists. If not, should offer two options: (1) Auto-draft from codebase (recommended) or (2) Start from scratch. If user chooses start from scratch, should walk through sections conversationally one at a time. Should cover all applicable sections: Product Overview, Target Audience, Personas, Problems You Solve, Competitive Landscape, Differentiation, Objections, Switching Dynamics, Customer Language, Brand Voice, Proof Points, and Goals. Should create the file at .agents/product-marketing-context.md when complete.",
+      "assertions": [
+        "Checks for existing product-marketing-context.md",
+        "Offers two options: auto-draft or start from scratch",
+        "Covers applicable sections",
+        "Walks through sections conversationally one at a time",
+        "Creates file at .agents/product-marketing-context.md"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "Update our product marketing context. We just added a new enterprise tier and our target audience has expanded to include VP of Engineering, not just Product Managers.",
+      "expected_output": "Should check for existing .agents/product-marketing-context.md and read it. Should identify which sections need updating based on the changes: Target Audience (add VP of Engineering), Personas (add new persona), Product Overview (new enterprise tier, including pricing updates within that section), Objections (enterprise-specific), and Competitive Landscape (enterprise competitors). Should update only the relevant sections, preserving existing content that hasn't changed.",
+      "assertions": [
+        "Reads existing product-marketing-context.md",
+        "Identifies sections that need updating",
+        "Updates Target Audience with VP of Engineering",
+        "Adds new persona for the expanded audience",
+        "Updates Product Overview for enterprise tier",
+        "Preserves unchanged sections"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "create a product context doc for my app. it's a mobile app that helps people find hiking trails. we're just getting started.",
+      "expected_output": "Should trigger on casual phrasing. Should check for existing context doc. Should offer auto-draft or start-from-scratch options. Should adapt questions for an early-stage B2C mobile app (outdoor/fitness niche). Should note that some sections may be sparse for an early-stage product and that's okay — they can be filled in as the business matures. Should skip non-applicable sections (e.g., Personas section is B2B-focused) rather than forcing all 12. Should accept lighter answers for sections like Proof Points or Competitive Landscape if the company is new.",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Checks for existing context doc",
+        "Offers auto-draft or start-from-scratch options",
+        "Adapts questions for early-stage B2C mobile app",
+        "Notes some sections may be sparse early on",
+        "Skips non-applicable sections rather than forcing all 12",
+        "Creates file at .agents/product-marketing-context.md"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "Can you auto-draft our product marketing context from our existing codebase and marketing materials?",
+      "expected_output": "Should activate the auto-draft workflow mode. Should scan the codebase for existing marketing context: README, landing page copy, pricing page, about page, meta descriptions, any existing documentation. Should draft the product-marketing-context.md from what it finds, filling in sections where information is available and flagging sections that need manual input. Should present the draft for review before saving.",
+      "assertions": [
+        "Activates auto-draft workflow mode",
+        "Scans codebase for existing marketing materials",
+        "Drafts context from found information",
+        "Flags sections needing manual input",
+        "Presents draft for review before saving"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "Do we have a product marketing context set up? I want to make sure the other marketing skills have context about our product.",
+      "expected_output": "Should check for .agents/product-marketing-context.md (and the older .claude/product-marketing-context.md location). Should report whether it exists and summarize its contents if found. If it doesn't exist, should offer to create one and explain why it's valuable (other skills like copywriting, cro, seo-audit check for it first). Should explain how other skills use this context document.",
+      "assertions": [
+        "Checks both file locations",
+        "Reports whether context doc exists",
+        "Summarizes contents if found",
+        "Offers to create if missing",
+        "Explains how other skills use it"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "Write homepage copy for our SaaS product.",
+      "expected_output": "Should recognize this is a copywriting task, not a product marketing context task. Should check for product-marketing-context.md (as other skills do), and if it doesn't exist, may suggest creating one first. But should defer to the copywriting skill for actually writing the homepage copy.",
+      "assertions": [
+        "Recognizes this as a copywriting task",
+        "May check for or suggest creating product-marketing-context.md",
+        "References or defers to copywriting skill for the actual copy",
+        "Does not attempt to write homepage copy using context creation patterns"
+      ],
+      "files": []
+    }
+  ]
+}