Merge pull request #220 from coreyhaines31/release/v1.6.0

release: v1.6.0 — community-marketing skill, 3 new tools, skill enhancements
Merge pull request #214 from coreyhaines31/feature/copy-editing-content-refresh
2026-04-06 11:33:38 -07:00 · 2026-04-03 17:02:17 -07:00 · 2026-04-03 17:02:17 -07:00 · 2026-04-03 17:02:17 -07:00 · 2026-04-03 17:02:17 -07:00 · 2026-04-03 17:02:17 -07:00
124 changed files with 14938 additions and 161 deletions
@@ -5,14 +5,14 @@
    "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": "29 marketing skills for technical marketers and founders: CRO, copywriting, cold email, SEO, AI SEO, paid ads, ad creative, churn prevention, pricing strategy, referral programs, and more",
+      "description": "33 marketing skills for technical marketers and founders: 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": [
@@ -26,10 +26,12 @@
        "./skills/content-strategy",
        "./skills/copy-editing",
        "./skills/copywriting",
+        "./skills/customer-research",
        "./skills/email-sequence",
        "./skills/form-cro",
        "./skills/free-tool-strategy",
        "./skills/launch-strategy",
+        "./skills/lead-magnets",
        "./skills/marketing-ideas",
        "./skills/marketing-psychology",
        "./skills/onboarding-cro",
@@ -41,9 +43,12 @@
        "./skills/product-marketing-context",
        "./skills/programmatic-seo",
        "./skills/referral-program",
+        "./skills/revops",
+        "./skills/sales-enablement",
        "./skills/schema-markup",
        "./skills/seo-audit",
        "./skills/signup-flow-cro",
+        "./skills/site-architecture",
        "./skills/social-content"
      ]
    }
@@ -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)
@@ -22,6 +22,7 @@ marketingskills/
 │       └── 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
@@ -167,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

@@ -189,6 +191,8 @@ Skills reference relevant tools for implementation. For example:
 - `email-sequence` 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:
@@ -215,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.
@@ -1,16 +1,53 @@
-# 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 │ │page-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  │ │form-cro  │ │email-seq │ │analytics   │ │ prevent  │ │pricing      │ │research   │
+│schema    │ │popup-cro │ │social    │ │            │ │          │ │competitor   │ │           │
+│content   │ │paywall   │ │          │ │            │ │          │ │             │ │           │
+└────┬─────┘ └────┬─────┘ └────┬─────┘ └─────┬──────┘ └────┬─────┘ └──────┬──────┘ └─────┬─────┘
+     │            │            │              │             │              │              │
+     └────────────┴─────┬──────┴──────────────┴─────────────┴──────────────┴──────────────┘
+                        │
+         Skills cross-reference each other:
+           copywriting ↔ page-cro ↔ ab-test-setup
+           revops ↔ sales-enablement ↔ cold-email
+           seo-audit ↔ schema-markup ↔ ai-seo
+           customer-research → copywriting, page-cro, competitor-alternatives
+```
+
+See each skill's **Related Skills** section for the full dependency map.

 ## Available Skills

@@ -27,10 +64,12 @@ Skills are markdown files that give AI agents specialized knowledge and workflow
 | [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,... |
+| [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)... |
 | [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... |
+| [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... |
@@ -42,9 +81,12 @@ Skills are markdown files that give AI agents specialized knowledge and workflow
 | [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.... |
+| [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-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... |
 | [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... |
+| [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-content](skills/social-content/) | When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram,... |
 <!-- SKILLS:END -->

@@ -65,7 +107,7 @@ npx skills add coreyhaines31/marketingskills --skill page-cro copywriting
 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

@@ -85,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
@@ -93,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

@@ -119,9 +161,20 @@ npx skillkit install coreyhaines31/marketingskills --skill page-cro copywriting
 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"
@@ -166,6 +219,7 @@ You can also invoke skills directly:
 - `seo-audit` - Technical and on-page SEO
 - `ai-seo` - AI search optimization (AEO, GEO, LLMO)
 - `programmatic-seo` - Scaled page generation
+- `site-architecture` - Page hierarchy, navigation, URL structure
 - `competitor-alternatives` - Comparison and alternative pages
 - `schema-markup` - Structured data

@@ -191,6 +245,10 @@ You can also invoke skills directly:
 - `launch-strategy` - Product launches and announcements
 - `pricing-strategy` - Pricing, packaging, and monetization

+### Sales & RevOps
+- `revops` - Lead lifecycle, scoring, routing, pipeline management
+- `sales-enablement` - Sales decks, one-pagers, objection docs, demo scripts
+
 ## Contributing

 Found a way to improve a skill? Have a new skill to suggest? PRs and issues welcome!
@@ -4,38 +4,66 @@ 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 |
-| ad-creative | 1.0.0 | 2026-02-17 |
-| ai-seo | 1.0.0 | 2026-02-18 |
-| analytics-tracking | 1.0.0 | 2026-01-27 |
-| churn-prevention | 1.0.0 | 2026-02-18 |
-| cold-email | 1.0.0 | 2026-02-14 |
-| 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
@@ -1,8 +1,8 @@
 ---
 name: ab-test-setup
-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.
+description: When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics-tracking. For page-level conversion optimization, see page-cro.
 metadata:
-  version: 1.0.0
+  version: 1.2.0
 ---

 # A/B Test Setup
@@ -12,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:

@@ -180,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
@@ -229,6 +229,93 @@ Document every test with:

 ---

+## Growth Experimentation Program
+
+Individual tests are valuable. A continuous experimentation program is a compounding asset. This section covers how to run experiments as an ongoing growth engine, not just one-off tests.
+
+### The Experiment Loop
+
+```
+1. Generate hypotheses (from data, research, competitors, customer feedback)
+2. Prioritize with ICE scoring
+3. Design and run the test
+4. Analyze results with statistical rigor
+5. Promote winners to a playbook
+6. Generate new hypotheses from learnings
+→ Repeat
+```
+
+### Hypothesis Generation
+
+Feed your experiment backlog from multiple sources:
+
+| Source | What to Look For |
+|--------|-----------------|
+| Analytics | Drop-off points, low-converting pages, underperforming segments |
+| Customer research | Pain points, confusion, unmet expectations |
+| Competitor analysis | Features, messaging, or UX patterns they use that you don't |
+| Support tickets | Recurring questions or complaints about conversion flows |
+| Heatmaps/recordings | Where users hesitate, rage-click, or abandon |
+| Past experiments | "Significant loser" tests often reveal new angles to try |
+
+### ICE Prioritization
+
+Score each hypothesis 1-10 on three dimensions:
+
+| Dimension | Question |
+|-----------|----------|
+| **Impact** | If this works, how much will it move the primary metric? |
+| **Confidence** | How sure are we this will work? (Based on data, not gut.) |
+| **Ease** | How fast and cheap can we ship and measure this? |
+
+**ICE Score** = (Impact + Confidence + Ease) / 3
+
+Run highest-scoring experiments first. Re-score monthly as context changes.
+
+### Experiment Velocity
+
+Track your experimentation rate as a leading indicator of growth:
+
+| Metric | Target |
+|--------|--------|
+| Experiments launched per month | 4-8 for most teams |
+| Win rate | 20-30% is common for mature programs (sustained higher rates may indicate conservative hypotheses) |
+| Average test duration | 2-4 weeks |
+| Backlog depth | 20+ hypotheses queued |
+| Cumulative lift | Compound gains from all winners |
+
+### The Experiment Playbook
+
+When a test wins, don't just implement it — document the pattern:
+
+```
+## [Experiment Name]
+**Date**: [date]
+**Hypothesis**: [the hypothesis]
+**Sample size**: [n per variant]
+**Result**: [winner/loser/inconclusive] — [primary metric] changed by [X%] (95% CI: [range], p=[value])
+**Guardrails**: [any guardrail metrics and their outcomes]
+**Segment deltas**: [notable differences by device, segment, or cohort]
+**Why it worked/failed**: [analysis]
+**Pattern**: [the reusable insight — e.g., "social proof near pricing CTAs increases plan selection"]
+**Apply to**: [other pages/flows where this pattern might work]
+**Status**: [implemented / parked / needs follow-up test]
+```
+
+Over time, your playbook becomes a library of proven growth patterns specific to your product and audience.
+
+### Experiment Cadence
+
+**Weekly (30 min)**: Review running experiments for technical issues and guardrail metrics. Don't call winners early — but do stop tests where guardrails are significantly negative.
+
+**Bi-weekly**: Conclude completed experiments. Analyze results, update playbook, launch next experiment from backlog.
+
+**Monthly (1 hour)**: Review experiment velocity, win rate, cumulative lift. Replenish hypothesis backlog. Re-prioritize with ICE.
+
+**Quarterly**: Audit the playbook. Which patterns have been applied broadly? Which winning patterns haven't been scaled yet? What areas of the funnel are under-tested?
+
+---
+
 ## Common Mistakes

 ### Test Design
@@ -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": []
+    }
+  ]
+}
@@ -1,8 +1,8 @@
 ---
 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,' or 'ad performance optimization.' This skill covers generating ad creative at scale, iterating based on performance data, and enforcing platform character limits. For campaign strategy and targeting, see paid-ads. For landing page copy, see copywriting."
+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.0.0
+  version: 1.1.0
 ---

 # Ad Creative
@@ -12,7 +12,7 @@ You are an expert performance creative strategist. Your goal is to generate high
 ## 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):

@@ -64,7 +64,7 @@ Pull performance data → Identify winning patterns → Generate new variations

 ## Platform Specs

-**Always enforce these limits.** Never deliver creative that exceeds platform character limits.
+Platforms reject or truncate creative that exceeds these limits, so verify every piece of copy fits before delivering.

 ### Google Ads (Responsive Search Ads)

@@ -320,7 +320,7 @@ For large-scale creative production (Anthropic's growth team generates 100+ vari
 - **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** — Always include action-oriented headlines
+- **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
@@ -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": []
+    }
+  ]
+}
@@ -1,8 +1,8 @@
 ---
 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,' or 'zero-click search.' This skill covers content optimization for AI answer engines, monitoring AI visibility, and getting cited as a source. For traditional technical and on-page SEO audits, see seo-audit. For structured data implementation, see schema-markup."
+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.0.0
+  version: 1.2.0
 ---

 # AI SEO
@@ -12,7 +12,7 @@ You are an expert in AI search optimization — the practice of making content d
 ## 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):

@@ -226,6 +226,50 @@ AI systems don't just cite your website — they cite where you appear.
 - Create YouTube content for key how-to queries
 - Answer relevant Quora questions with depth

+### Machine-Readable Files for AI Agents
+
+AI agents aren't just answering questions — they're becoming buyers. When an AI agent evaluates tools on behalf of a user, it needs structured, parseable information. If your pricing is locked in a JavaScript-rendered page or a "contact sales" wall, agents will skip you and recommend competitors whose information they can actually read.
+
+Add these machine-readable files to your site root:
+
+**`/pricing.md` or `/pricing.txt`** — Structured pricing data for AI agents
+
+```markdown
+# Pricing — [Your Product Name]
+
+## Free
+- Price: $0/month
+- Limits: 100 emails/month, 1 user
+- Features: Basic templates, API access
+
+## Pro
+- Price: $29/month (billed annually) | $35/month (billed monthly)
+- Limits: 10,000 emails/month, 5 users
+- Features: Custom domains, analytics, priority support
+
+## Enterprise
+- Price: Custom — contact sales@example.com
+- Limits: Unlimited emails, unlimited users
+- Features: SSO, SLA, dedicated account manager
+```
+
+**Why this matters now:**
+- AI agents increasingly compare products programmatically before a human ever visits your site
+- Opaque pricing gets filtered out of AI-mediated buying journeys
+- A simple markdown file is trivially parseable by any LLM — no rendering, no JavaScript, no login walls
+- Same principle as `robots.txt` (for crawlers), `llms.txt` (for AI context), and `AGENTS.md` (for agent capabilities)
+
+**Best practices:**
+- Use consistent units (monthly vs. annual, per-seat vs. flat)
+- Include specific limits and thresholds, not just feature names
+- List what's included at each tier, not just what's different
+- Keep it updated — stale pricing is worse than no file
+- Link to it from your sitemap and main pricing page
+
+**`/llms.txt`** — Context file for AI systems (see [llmstxt.org](https://llmstxt.org))
+
+If you don't have one yet, add an `llms.txt` that gives AI systems a quick overview of what your product does, who it's for, and links to key pages (including your pricing).
+
 ### Schema Markup for AI

 Structured data helps AI systems understand your content. Key schemas:
@@ -309,7 +353,7 @@ Monthly manual check:
 - 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)
+- Pricing transparency (AI cites pages with visible pricing) — add a `/pricing.md` file so AI agents can parse your plans without rendering your page (see "Machine-Readable Files" above)
 - FAQ section addressing common buyer questions

 ### Blog Content
@@ -353,11 +397,12 @@ Monthly manual check:
 - **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. Always show when content was last updated
+- **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)
+- **Hiding pricing behind "contact sales" or JS-rendered pages** — AI agents evaluating your product on behalf of buyers can't parse what they can't read. Add a `/pricing.md` file
 - **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
@@ -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": []
+    }
+  ]
+}
@@ -1,8 +1,8 @@
 ---
 name: analytics-tracking
-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.
+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-test-setup.
 metadata:
-  version: 1.0.0
+  version: 1.1.0
 ---

 # Analytics Tracking
@@ -12,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:

@@ -306,3 +306,4 @@ For implementation, see the [tools registry](../../tools/REGISTRY.md). Key analy
 - **ab-test-setup**: For experiment tracking
 - **seo-audit**: For organic traffic analysis
 - **page-cro**: For conversion optimization (uses this data)
+- **revops**: For pipeline metrics, CRM tracking, and revenue attribution
@@ -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": []
+    }
+  ]
+}
@@ -1,8 +1,8 @@
 ---
 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,' or 'involuntary churn.' This skill covers voluntary churn (cancel flows, save offers, exit surveys) and involuntary churn (dunning, payment recovery). For post-cancel win-back email sequences, see email-sequence. For in-app upgrade paywalls, see paywall-upgrade-cro."
+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 email-sequence. For in-app upgrade paywalls, see paywall-upgrade-cro."
 metadata:
-  version: 1.0.0
+  version: 1.1.0
 ---

 # Churn Prevention
@@ -12,7 +12,7 @@ You are an expert in SaaS retention and churn prevention. Your goal is to help r
 ## 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):

@@ -375,7 +375,7 @@ Test one variable at a time:
 - **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** — Always make reactivation easy and trigger win-back emails
+- **No post-cancel path** — Make reactivation easy and trigger win-back emails, because some churned users will want to come back

 ---

@@ -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": []
+    }
+  ]
+}
@@ -1,6 +1,8 @@
 ---
 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. Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences.
+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 email-sequence. For sales collateral beyond emails, see sales-enablement.
+metadata:
+  version: 1.1.0
 ---

 # Cold Email Writing
@@ -10,7 +12,7 @@ You are an expert cold email writer. Your goal is to write emails that sound lik
 ## 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.

 Understand the situation (ask if not provided):

@@ -98,7 +100,7 @@ See [subject-lines.md](references/subject-lines.md) for the full data.

 ## Follow-Up Sequences

-Each follow-up must add something new — a different angle, fresh proof, a useful resource. Never "just checking in."
+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)
@@ -153,3 +155,4 @@ Use this data to inform your writing — not as a checklist to satisfy.
 - **email-sequence**: For lifecycle/nurture email sequences (not cold outreach)
 - **social-content**: For LinkedIn and social posts
 - **product-marketing-context**: For establishing foundational positioning
+- **revops**: For lead scoring, routing, and pipeline management
@@ -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": []
+    }
+  ]
+}
@@ -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.
@@ -1,8 +1,8 @@
 ---
 name: competitor-alternatives
-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."
+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.0.0
+  version: 1.1.0
 ---

 # Competitor & Alternative Pages
@@ -12,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:

@@ -253,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
@@ -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": []
+    }
+  ]
+}
@@ -1,8 +1,8 @@
 ---
 name: content-strategy
-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-content.
 metadata:
-  version: 1.0.0
+  version: 1.1.0
 ---

 # Content Strategy
@@ -12,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):

@@ -348,11 +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
+- **site-architecture**: For page hierarchy, navigation design, and URL structure
 - **email-sequence**: For email-based content
 - **social-content**: For social media content
@@ -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": []
+    }
+  ]
+}
@@ -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 **email-sequence** 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
@@ -1,8 +1,8 @@
 ---
 name: copy-editing
-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, or refresh outdated content. 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,' 'sharpen the messaging,' 'refresh this content,' 'update this page,' 'this content is outdated,' or 'content audit.' Use this when the user already has copy and wants it improved or refreshed rather than rewritten from scratch. For writing new copy, see copywriting."
 metadata:
-  version: 1.0.0
+  version: 1.3.0
 ---

 # Copy Editing
@@ -12,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.

@@ -256,6 +256,57 @@ For every statement, ask "Okay, so what?" If the copy doesn't answer that questi

 ---

+## Expert Panel Scoring
+
+Use this after completing the Seven Sweeps for an additional quality gate. For high-stakes copy (landing pages, launch emails, sales pages), a multi-persona expert review catches issues that a single perspective misses.
+
+### How It Works
+
+1. **Assemble 3-5 expert personas** relevant to the copy type
+2. **Each persona scores the copy 1-10** on their area of expertise
+3. **Collect specific critiques** — not just scores, but what to fix
+4. **Revise based on feedback** — address the lowest-scoring areas first
+5. **Re-score after revisions** — iterate until all personas score 7+, with an average of 8+ across the panel
+
+### Recommended Expert Panels
+
+**Landing page copy:**
+- Conversion copywriter (clarity, CTA strength, benefit hierarchy)
+- UX writer (scannability, cognitive load, user flow)
+- Target customer persona (does this speak to me? do I trust it?)
+- Brand strategist (voice consistency, positioning accuracy)
+
+**Email sequence:**
+- Email marketing specialist (subject lines, open/click optimization)
+- Copywriter (hooks, storytelling, persuasion)
+- Spam filter analyst (deliverability red flags, trigger words)
+- Target customer persona (relevance, value, unsubscribe risk)
+
+**Sales page / long-form:**
+- Direct response copywriter (offer structure, objection handling, urgency)
+- Skeptical buyer persona (proof gaps, trust issues, red flags)
+- Editor (flow, readability, conciseness)
+- SEO specialist (keyword coverage, search intent alignment)
+
+### Scoring Rubric
+
+| Score | Meaning |
+|-------|---------|
+| 9-10 | Publish-ready. No meaningful improvements. |
+| 7-8 | Strong. Minor tweaks only. |
+| 5-6 | Functional but has clear gaps. Needs another pass. |
+| 3-4 | Significant issues. Major revision needed. |
+| 1-2 | Fundamentally broken. Rethink approach. |
+
+### When to Use
+
+- **Always** for launch copy, pricing pages, and high-traffic landing pages
+- **Recommended** for email sequences, sales pages, and ad copy
+- **Optional** for blog posts, social content, and internal docs
+- **Skip** for quick updates, minor edits, and low-stakes content
+
+---
+
 ## Quick-Pass Editing Checks

 Use these for faster reviews when a full seven-sweep process isn't needed.
@@ -416,6 +467,15 @@ This iterative process ensures each edit doesn't create new problems while respe
 ## References

 - [Plain English Alternatives](references/plain-english-alternatives.md): Replace complex words with simpler alternatives
+- [Content Refresh](references/content-refresh.md): Full checklist, refresh vs. rewrite matrix, and cadence guide
+
+---
+
+## Content Refresh Editing
+
+Copy editing isn't just for new content. Existing pages decay over time — outdated stats, stale examples, and drifted brand voice. Use the content refresh framework when traffic is declining, data is stale, or the product has changed.
+
+**For the full refresh checklist, refresh vs. rewrite decision matrix, and cadence guide**: See [references/content-refresh.md](references/content-refresh.md)

 ---

@@ -425,6 +485,7 @@ This iterative process ensures each edit doesn't create new problems while respe
 2. What action should readers take?
 3. Are there specific concerns or known issues?
 4. What proof/evidence do you have available?
+5. Is this new copy or a refresh of existing content?

 ---

@@ -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": []
+    }
+  ]
+}
@@ -0,0 +1,38 @@
+# Content Refresh Editing
+
+Copy editing isn't just for new content. Existing pages and posts decay over time — outdated stats, stale examples, drifted brand voice, and missed SEO opportunities. A content refresh applies the same editing rigor to content that's already published.
+
+## When to Refresh
+
+- **Traffic declining** on a page that used to perform well
+- **Stats or data** are more than 12 months old
+- **Product has changed** — features, pricing, or positioning no longer match
+- **Competitors updated** their version of the same content
+- **AI search visibility** matters — outdated content gets cited less (see ai-seo skill)
+
+## Content Refresh Checklist
+
+1. **Freshness pass** — Update all dates, stats, and examples. Replace "in 2024" with current data. Remove references to deprecated features or tools.
+2. **Accuracy pass** — Verify all claims are still true. Check that linked resources still exist. Confirm pricing and feature descriptions match current state.
+3. **Voice pass** — Does the tone match your current brand voice? Older content often reflects an earlier stage of the company.
+4. **SEO pass** — Has search intent shifted for this topic? Are there new keywords or questions to address? Add "Last updated: [date]" prominently.
+5. **Proof pass** — Can you add newer testimonials, case studies, or data points that didn't exist when this was first published?
+6. **Structure pass** — Add comparison tables, FAQ sections, or other scannable formats that make the content easier to consume.
+
+## Refresh vs. Rewrite
+
+| Signal | Action |
+|--------|--------|
+| Core message still valid, details outdated | Refresh (update facts, stats, examples) |
+| Brand voice has evolved significantly | Refresh + voice rewrite |
+| Topic angle or audience has shifted | Full rewrite |
+| Page structure doesn't match current search intent | Full rewrite |
+| Just needs updated stats and links | Light refresh |
+
+## Refresh Cadence
+
+- **Pricing and product pages**: Every quarter, or when pricing/features change
+- **High-traffic blog posts**: Every 6 months
+- **Comparison and alternatives pages**: Every 3-6 months (competitors change fast)
+- **Evergreen guides**: Annually, unless traffic drops sooner
+- **Low-traffic pages**: Only when traffic data suggests an opportunity
@@ -1,8 +1,8 @@
 ---
 name: copywriting
-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 email-sequence. For popup copy, see popup-cro. For editing existing copy, see copy-editing.
 metadata:
-  version: 1.0.0
+  version: 1.1.0
 ---

 # Copywriting
@@ -12,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):

@@ -67,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

@@ -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": []
+    }
+  ]
+}
@@ -0,0 +1,270 @@
+---
+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 page-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, SparkToro |
+| SMB / founders | Reddit (r/entrepreneur, r/smallbusiness), Indie Hackers, Product Hunt, Facebook Groups, SparkToro |
+| 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, SparkToro |
+
+**Quick decision guide:**
+- Have a product category? → Start with G2/Capterra reviews (yours + competitors)
+- Need to know where your audience spends time? → SparkToro (reveals podcasts, YouTube, subreddits, websites, social accounts)
+- 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; SparkToro competitor audience analysis
+
+### 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 | `page-cro` |
+| Building a competitor comparison page | `competitor-alternatives` |
+| 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` |
@@ -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": []
+    }
+  ]
+}
@@ -0,0 +1,401 @@
+# 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
+
+---
+
+## SparkToro (Audience Intelligence)
+
+SparkToro is a behavioral audience research tool. Instead of mining individual posts and comments, it aggregates clickstream, search, and social data to show what your audience does at scale — what they read, watch, listen to, follow, and search for.
+
+### When to Use SparkToro vs. Manual Research
+
+- **SparkToro first** when you need to understand where your ICP spends time, what content they consume, and which influencers they follow — it answers these questions in seconds with aggregated data
+- **Manual research first** (Reddit, G2, communities) when you need raw language, exact quotes, emotional context, and the "why" behind behavior
+- **Best together**: Use SparkToro to identify which podcasts, subreddits, and websites matter, then go mine those sources manually for voice-of-customer language
+
+### Key Queries to Run
+
+**By competitor:**
+- "People who follow @competitor" — reveals shared audience affinities
+- "People who visit competitor.com" — shows what else they consume
+
+**By audience description:**
+- "People who frequently talk about [topic]" — finds audience behaviors
+- "People whose bio contains [job title]" — profiles a role-based segment
+
+**By your own audience:**
+- "People who visit yourdomain.com" — understand your actual audience
+- Compare against competitor audience profiles to find gaps
+
+### What to Extract
+
+| Data Type | What It Tells You | Use It For |
+|-----------|------------------|------------|
+| Top websites visited | Where your audience reads | Content partnerships, guest posting targets |
+| Top podcasts | What they listen to | Podcast guesting, sponsorship decisions |
+| Top YouTube channels | What they watch | Video content strategy, ad placements |
+| Top subreddits | Where they discuss | Community participation, Reddit ad targeting |
+| Search keywords | What they Google | SEO and content topic planning |
+| AI prompt topics | What they ask AI tools | Emerging content opportunities |
+| Social accounts followed | Who influences them | Influencer partnerships, co-marketing |
+| Demographics | Who they are | Persona building, ad targeting |
+
+### Source Weighting
+
+SparkToro data is aggregated and anonymized — it shows patterns, not individual opinions. Treat it as:
+- **High confidence** for behavioral data (what they visit, follow, search for)
+- **Medium confidence** for demographic data (self-reported, may be incomplete)
+- **Not a substitute** for qualitative research (doesn't capture language, emotions, or the "why")
+
+### Limitations
+
+- Free tier: 5 reports/month, shallow results (top 5–10)
+- No public API — all research done through web interface
+- Skews English-language, US-centric
+- Shows what audiences do, not why — pair with qualitative sources
+
+See [tools/integrations/sparktoro.md](../../../tools/integrations/sparktoro.md) for full tool details and pricing.
+
+---
+
+## 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 |
+| SparkToro audience data | Medium-high | Aggregated behavioral data; strong for "what" but not "why" |
+| 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.
@@ -1,8 +1,8 @@
 ---
 name: email-sequence
-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.
+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-cro.
 metadata:
-  version: 1.0.0
+  version: 1.1.0
 ---

 # Email Sequence Design
@@ -12,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:

@@ -293,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) |
@@ -301,8 +302,10 @@ For implementation, see the [tools registry](../../tools/REGISTRY.md). Key email

 ## Related Skills

+- **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-cro**: 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
+- **revops**: For lifecycle stages that trigger email sequences
@@ -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": []
+    }
+  ]
+}
@@ -1,8 +1,8 @@
 ---
 name: form-cro
-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.
+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," "contact form," "nobody fills out our form," "form abandonment," "too many fields," "demo request form," or "lead form isn't converting." Use this for any non-signup form that captures information. For signup/registration forms, see signup-flow-cro. For popups containing forms, see popup-cro.
 metadata:
-  version: 1.0.0
+  version: 1.1.0
 ---

 # Form CRO
@@ -12,7 +12,7 @@ You are an expert in form optimization. Your goal is to maximize form completion
 ## 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:

@@ -120,7 +120,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

@@ -0,0 +1,90 @@
+{
+  "skill_name": "form-cro",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Audit our demo request form. It currently has these fields: First Name, Last Name, Work Email, Phone Number, Company Name, Company Size, Job Title, Industry, Current Solution, Budget Range, and a 'Tell us about your needs' textarea. Our conversion rate is 3.1% and we want to improve it.",
+      "expected_output": "Should check for product-marketing-context.md first. Should apply the 'every field has a cost' principle — 11 fields is excessive for a demo form. Should reference the field cost data (3 fields baseline, 7+ fields = 25-50% conversion reduction). Should evaluate each field: which are essential for demo prep, which can be collected later or inferred. Should recommend cutting to essential fields (likely Work Email, Company Name, and maybe one qualifier). Should provide audit findings in the structured format (Issue, Impact, Fix, Priority). Should recommend Quick Wins, High-Impact Changes, and Test Ideas.",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Applies 'every field has a cost' principle",
+        "References field count impact data",
+        "Evaluates each field for necessity",
+        "Recommends cutting to essential fields",
+        "Provides findings in structured format (Issue, Impact, Fix, Priority)",
+        "Includes Quick Wins, High-Impact Changes, Test Ideas"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "Our contact form just has Name, Email, and Message fields but we're getting a lot of spam submissions and low-quality leads. How do we fix this without adding too much friction?",
+      "expected_output": "Should apply the contact form type guidance. Should address spam with non-friction solutions first: honeypot fields, reCAPTCHA, server-side validation. Should then address lead quality: suggest adding one qualifying field (company name or budget range) to filter without excessive friction. Should apply the error handling guidance for validation. Should recommend form layout and submit button optimization. Should balance quality vs quantity in recommendations.",
+      "assertions": [
+        "Applies contact form type guidance",
+        "Recommends anti-spam solutions (honeypot, reCAPTCHA)",
+        "Suggests minimal qualifying fields for lead quality",
+        "Balances quality vs quantity",
+        "Addresses error handling and validation",
+        "Recommends non-friction solutions first"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "should we use a single-step or multi-step form for our quote request? we need company info, project details, timeline, and budget.",
+      "expected_output": "Should trigger on casual phrasing. Should apply the multi-step form guidance — with this many required data types, multi-step is likely better. Should reference the threshold: multi-step recommended when more than 5-6 fields. Should recommend grouping by type (contact info → project details → budget/timeline). Should include progress indicator recommendation. Should apply best practices: easy questions first, save progress, allow back navigation. Should note that multi-step often increases completion for longer forms.",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Recommends multi-step based on field count",
+        "References the 5-6 field threshold for multi-step",
+        "Suggests logical field grouping",
+        "Recommends progress indicator",
+        "Applies multi-step best practices",
+        "Notes multi-step increases completion for longer forms"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "How should we handle form errors? Users keep getting frustrated and abandoning our lead capture form when they hit validation errors.",
+      "expected_output": "Should apply the error handling guidance. Should recommend inline validation (not just on submit). Should provide specific error message examples (helpful, not generic). Should recommend: don't clear the form on error, focus on the problem field, show requirements upfront not after failure. Should address common validation UX issues: email format, phone format, required field indicators. Should provide examples of good vs bad error messages.",
+      "assertions": [
+        "Applies error handling guidance",
+        "Recommends inline validation",
+        "Provides specific error message examples",
+        "Recommends not clearing form on error",
+        "Recommends showing requirements upfront",
+        "Provides good vs bad error message examples",
+        "Addresses common validation UX issues"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "We need to optimize our form for mobile. Over 60% of our traffic is mobile but our form conversion rate on mobile is half of desktop.",
+      "expected_output": "Should apply the mobile optimization guidance. Should recommend: larger touch targets (44px+ height), appropriate keyboard types (email, tel), autofill support, single column layout, sticky CTA button, reduce typing (use dropdowns, toggles). Should address mobile-specific form issues: viewport, font size, button placement, scroll behavior. Should recommend testing with actual devices.",
+      "assertions": [
+        "Applies mobile optimization guidance",
+        "Recommends larger touch targets (44px+)",
+        "Recommends appropriate keyboard types",
+        "Recommends autofill support",
+        "Recommends single column layout",
+        "Addresses mobile-specific issues",
+        "Recommends testing with actual devices"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "Our signup form has too many fields and people keep abandoning it halfway through. Can you help optimize it?",
+      "expected_output": "Should recognize this is about signup/registration form optimization, not general form CRO. Should defer to or cross-reference the signup-flow-cro skill, which specifically handles signup, registration, and account creation flows. May provide general form friction advice but should make clear that signup-flow-cro is the right skill for signup forms.",
+      "assertions": [
+        "Recognizes this as signup flow optimization",
+        "References or defers to signup-flow-cro skill",
+        "Does not attempt full signup form optimization using general form CRO patterns"
+      ],
+      "files": []
+    }
+  ]
+}
@@ -1,8 +1,8 @@
 ---
 name: free-tool-strategy
-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.
+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.0.0
+  version: 1.1.0
 ---

 # Free Tool Strategy (Engineering as Marketing)
@@ -12,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:

@@ -172,6 +172,7 @@ Rate each factor 1-5:

 ## Related Skills

+- **lead-magnets**: For downloadable content lead magnets (ebooks, checklists, templates)
 - **page-cro**: For optimizing the tool's landing page
 - **seo-audit**: For SEO-optimizing the tool
 - **analytics-tracking**: For measuring tool usage
@@ -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 page-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 page-cro is the right skill for page conversion optimization.",
+      "assertions": [
+        "Recognizes this as page CRO, not free tool strategy",
+        "References or defers to page-cro skill",
+        "May provide free-tool-specific context",
+        "Does not attempt full page CRO using free tool strategy patterns"
+      ],
+      "files": []
+    }
+  ]
+}
@@ -1,8 +1,8 @@
 ---
 name: launch-strategy
-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."
+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.0.0
+  version: 1.1.0
 ---

 # Launch Strategy
@@ -12,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.

 ---

@@ -93,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.
@@ -350,3 +350,4 @@ Even small changelog updates remind customers your product is evolving. This bui
 - **page-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
@@ -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": []
+    }
+  ]
+}
@@ -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-tool-strategy. For writing the actual content, see copywriting. For the email sequence after capture, see email-sequence.
+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-tool-strategy**) |
+
+---
+
+## 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 **form-cro** skill
+**For popup implementation**: See **popup-cro** 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 **page-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 popup-cro** 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-content** 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-tool-strategy**: For interactive tools as lead magnets (calculators, graders, quizzes)
+- **copywriting**: For writing the lead magnet content itself
+- **email-sequence**: For nurture sequences after lead capture
+- **page-cro**: For optimizing lead magnet landing pages
+- **popup-cro**: For popup-based lead capture
+- **form-cro**: For optimizing capture forms
+- **content-strategy**: For content planning and topic selection
+- **analytics-tracking**: For measuring lead magnet performance
+- **paid-ads**: For paid promotion of lead magnets
+- **social-content**: For social media promotion
@@ -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.
@@ -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-tool-strategy** 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.
@@ -1,8 +1,8 @@
 ---
 name: marketing-ideas
-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-content, email-sequence, etc.)."
 metadata:
-  version: 1.0.0
+  version: 1.1.0
 ---

 # Marketing Ideas for SaaS
@@ -12,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
@@ -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": []
+    }
+  ]
+}
@@ -1,8 +1,8 @@
 ---
 name: marketing-psychology
-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.0.0
+  version: 1.1.0
 ---

 # Marketing Psychology & Mental Models
@@ -12,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:

@@ -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": []
+    }
+  ]
+}
@@ -1,8 +1,8 @@
 ---
 name: onboarding-cro
-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.
+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-flow-cro. For ongoing email sequences, see email-sequence.
 metadata:
-  version: 1.0.0
+  version: 1.1.0
 ---

 # Onboarding CRO
@@ -12,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:

@@ -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": []
+    }
+  ]
+}
@@ -1,8 +1,8 @@
 ---
 name: page-cro
-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.
+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," "why isn't this page working," "my landing page sucks," "nobody's converting," "low conversion rate," "bounce rate is too high," "people leave without signing up," or "this page needs work." Use this even if the user just shares a URL and asks for feedback — they probably want conversion help. 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.
 metadata:
-  version: 1.0.0
+  version: 1.1.0
 ---

 # Page Conversion Rate Optimization (CRO)
@@ -12,7 +12,7 @@ You are a conversion rate optimization expert. Your goal is to analyze marketing
 ## 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:

@@ -0,0 +1,111 @@
+{
+  "skill_name": "page-cro",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Here's my SaaS landing page: https://example.com/product. We get about 5,000 visitors/month from Google Ads but only 1.2% convert to free trial signups. Can you help me figure out what's wrong?",
+      "expected_output": "Should check for product-marketing-context.md first. Should identify page type (landing page) and conversion goal (free trial signup). Should analyze across the CRO framework dimensions: value proposition clarity, headline effectiveness, CTA placement/copy/hierarchy, visual hierarchy, trust signals, objection handling, and friction points. Should provide recommendations organized as Quick Wins, High-Impact Changes, and Test Ideas. Should note the message match issue between Google Ads and landing page. Should provide 2-3 headline and CTA copy alternatives with rationale.",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Identifies page type as landing page",
+        "Identifies conversion goal as free trial signup",
+        "Analyzes value proposition clarity",
+        "Analyzes CTA placement and copy",
+        "Notes message match between ads and landing page",
+        "Output has Quick Wins section",
+        "Output has High-Impact Changes section",
+        "Output has Test Ideas section",
+        "Provides 2-3 headline or CTA alternatives"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "Our pricing page has three tiers but nobody picks the middle one. 60% choose the cheapest plan and 30% bounce entirely. What should we change?",
+      "expected_output": "Should apply the Pricing Page CRO framework. Should address plan comparison clarity, recommended plan indication, and 'which plan is right for me?' anxiety. Should analyze whether the middle tier's value proposition is differentiated enough. Should recommend trust signals and social proof near pricing. Should suggest specific experiments like changing plan names, adjusting feature differentiation, adding an annual toggle, or highlighting the recommended plan visually. Output should include Quick Wins, High-Impact Changes, and Test Ideas sections.",
+      "assertions": [
+        "Applies Pricing Page CRO framework",
+        "Addresses recommended plan indication",
+        "Addresses 'which plan is right for me' anxiety",
+        "Analyzes middle tier differentiation",
+        "Suggests specific experiments",
+        "Output has Quick Wins section",
+        "Output has High-Impact Changes section",
+        "Output has Test Ideas section"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "this page isn't converting. can you take a look? it's our homepage for a B2B project management tool",
+      "expected_output": "Should trigger on the casual 'this page isn't converting' phrasing. Should identify this as a Homepage CRO analysis. Should ask clarifying questions about current conversion rate, traffic sources, and conversion goal. Should apply the full CRO Analysis Framework starting with value proposition clarity. Should address the homepage-specific guidance: serving multiple audiences, leading with broadest value prop, and providing clear paths for different visitor intents. Should provide structured output with Quick Wins, High-Impact Changes, Test Ideas, and Copy Alternatives.",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Identifies as Homepage CRO",
+        "Asks about current conversion rate",
+        "Asks about traffic sources",
+        "Applies CRO Analysis Framework",
+        "Addresses serving multiple audiences",
+        "Addresses clear paths for different visitor intents",
+        "Output has structured sections"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "We have a blog that gets 20k organic visits/month but almost nobody clicks through to our product. How do we get more conversions from blog readers?",
+      "expected_output": "Should apply the Blog Post CRO framework. Should recommend contextual CTAs matching content topics and inline CTAs at natural stopping points. Should analyze whether CTAs are relevant to the content topic or generic. Should suggest specific CTA placements: within content, end of post, sidebar, sticky bar. Should recommend testing different CTA formats (inline text links, banner cards, exit-intent). Should cross-reference copywriting skill for CTA copy improvement.",
+      "assertions": [
+        "Applies Blog Post CRO framework",
+        "Recommends contextual CTAs matching content",
+        "Recommends inline CTAs at natural stopping points",
+        "Suggests specific CTA placements",
+        "Suggests testing different CTA formats",
+        "Cross-references copywriting or related skill"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "We redesigned our landing page and conversions dropped from 4.2% to 2.8%. Here's the new page. What went wrong?",
+      "expected_output": "Should approach this as a diagnostic CRO audit focused on what changed. Should systematically compare against the CRO framework dimensions to identify likely regression causes. Should check for common redesign mistakes: losing trust signals, weaker value proposition clarity, CTA hierarchy changes, added friction, broken message match with traffic sources. Should provide specific fixes organized by likely impact. Should recommend reverting high-risk changes while testing others.",
+      "assertions": [
+        "Approaches as diagnostic audit",
+        "Checks for lost trust signals",
+        "Checks for weakened value proposition",
+        "Checks for CTA hierarchy changes",
+        "Checks for added friction",
+        "Checks for broken message match with traffic sources",
+        "Provides fixes organized by impact",
+        "Recommends reverting high-risk changes"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "Our signup form has too many fields and people keep abandoning it halfway through. Can you help optimize it?",
+      "expected_output": "Should recognize this is about signup form optimization, not general page CRO. Should defer to or cross-reference the signup-flow-cro skill, which specifically handles signup, registration, and account creation flows. May provide some general friction reduction advice but should make clear that signup-flow-cro is the right skill for this task.",
+      "assertions": [
+        "Recognizes this as signup flow optimization",
+        "References or defers to signup-flow-cro skill",
+        "Does not attempt full page-cro analysis on a form"
+      ],
+      "files": []
+    },
+    {
+      "id": 7,
+      "prompt": "Review this feature page for our API monitoring tool. Most traffic comes from organic search for 'API monitoring tools'. We want them to start a free trial.",
+      "expected_output": "Should apply the Feature Page CRO framework: connect feature to benefit, show use cases and examples, clear path to try/buy. Should reference the experiments section and suggest prioritized test ideas for hero section, trust signals, and CTA variations. Should note the organic search traffic source and check for message match with search intent. Should cross-reference ab-test-setup skill for proper test implementation.",
+      "assertions": [
+        "Applies Feature Page CRO framework",
+        "Connects features to benefits",
+        "Suggests use cases and examples",
+        "Provides clear path to try/buy",
+        "Notes organic traffic source and search intent match",
+        "Suggests specific experiment hypotheses",
+        "Cross-references ab-test-setup skill"
+      ],
+      "files": []
+    }
+  ]
+}
@@ -1,8 +1,8 @@
 ---
 name: paid-ads
-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,' or 'audience targeting.' This skill covers campaign strategy, audience targeting, and optimization. For bulk ad creative generation and iteration, see ad-creative."
+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 page-cro."
 metadata:
-  version: 1.0.0
+  version: 1.1.0
 ---

 # Paid Ads
@@ -12,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):

@@ -122,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)

@@ -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": []
+    }
+  ]
+}
@@ -1,8 +1,8 @@
 ---
 name: paywall-upgrade-cro
-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.
+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 page-cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see pricing-strategy.
 metadata:
-  version: 1.0.0
+  version: 1.1.0
 ---

 # Paywall and Upgrade Screen CRO
@@ -12,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:

@@ -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 page-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 page-cro skill",
+        "Explains that paywall-upgrade-cro is for in-app upgrade prompts",
+        "Does not attempt public pricing page optimization"
+      ],
+      "files": []
+    }
+  ]
+}
@@ -1,8 +1,8 @@
 ---
 name: popup-cro
-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.
+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 form-cro. For general page conversion optimization, see page-cro.
 metadata:
-  version: 1.0.0
+  version: 1.1.0
 ---

 # Popup CRO
@@ -12,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:

@@ -182,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
@@ -447,6 +447,7 @@ Ideas to A/B test with expected outcomes

 ## Related Skills

+- **lead-magnets**: For planning lead magnets to promote via popups
 - **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
@@ -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 form-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 form-cro is the right skill for detailed form optimization.",
+      "assertions": [
+        "Recognizes overlap with form optimization",
+        "References or defers to form-cro skill",
+        "Notes popups need minimal fields due to context",
+        "Does not attempt detailed form redesign"
+      ],
+      "files": []
+    }
+  ]
+}
@@ -1,8 +1,8 @@
 ---
 name: pricing-strategy
-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."
+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 paywall-upgrade-cro."
 metadata:
-  version: 1.0.0
+  version: 1.1.0
 ---

 # Pricing Strategy
@@ -12,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):

@@ -227,3 +227,5 @@ Identifies which features customers value most:
 - **copywriting**: For pricing page copy
 - **marketing-psychology**: For pricing psychology principles
 - **ab-test-setup**: For testing pricing changes
+- **revops**: For deal desk processes and pipeline pricing
+- **sales-enablement**: For proposal templates and pricing presentations
@@ -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 page-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 page-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 page-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 page-cro skill",
+        "Explains that pricing-strategy is about pricing decisions",
+        "Does not attempt full page CRO audit"
+      ],
+      "files": []
+    }
+  ]
+}
@@ -1,21 +1,21 @@
 ---
 name: product-marketing-context
-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."
+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.0.0
+  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
@@ -47,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.

 ---

@@ -128,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
@@ -227,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."

 ---
@@ -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, page-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": []
+    }
+  ]
+}
@@ -1,8 +1,8 @@
 ---
 name: programmatic-seo
-description: When the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions "programmatic SEO," "template pages," "pages at scale," "directory pages," "location pages," "[keyword] + [city] pages," "comparison pages," "integration pages," or "building many pages for SEO." For auditing existing SEO issues, see seo-audit.
+description: When the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions "programmatic SEO," "template pages," "pages at scale," "directory pages," "location pages," "[keyword] + [city] pages," "comparison pages," "integration pages," "building many pages for SEO," "pSEO," "generate 100 pages," "data-driven pages," or "templated landing pages." Use this whenever someone wants to create many similar pages targeting different keywords or locations. For auditing existing SEO issues, see seo-audit. For content strategy planning, see content-strategy.
 metadata:
-  version: 1.0.0
+  version: 1.1.0
 ---

 # Programmatic SEO
@@ -12,7 +12,7 @@ You are an expert in programmatic SEO—building SEO-optimized pages at scale us
 ## 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 programmatic SEO strategy, understand:

@@ -49,7 +49,7 @@ Hierarchy of data defensibility:
 5. Public (anyone can use—weakest)

 ### 3. Clean URL Structure
-**Always use subfolders, not subdomains**:
+**Use subfolders, not subdomains** — subfolders consolidate domain authority while subdomains split it:
 - Good: `yoursite.com/templates/resume/`
 - Bad: `templates.yoursite.com/resume/`

@@ -234,4 +234,5 @@ Watch for: Thin content warnings, Ranking drops, Manual actions, Crawl errors

 - **seo-audit**: For auditing programmatic pages after launch
 - **schema-markup**: For adding structured data
+- **site-architecture**: For page hierarchy, URL structure, and internal linking
 - **competitor-alternatives**: For comparison page frameworks
@@ -0,0 +1,94 @@
+{
+  "skill_name": "programmatic-seo",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "We want to create programmatic SEO pages for our CRM. We're thinking of 'CRM for [industry]' pages — like 'CRM for Real Estate,' 'CRM for Healthcare,' etc. How should we approach this?",
+      "expected_output": "Should check for product-marketing-context.md first. Should identify this as the Personas playbook (industry-specific pages). Should apply the core principles: unique value per page (not just swapping the industry name), proprietary data or insights per industry, clean URL structure. Should recommend the implementation framework: keyword research for each industry variation, data requirements (what industry-specific content makes each page unique), template design, internal linking strategy between industry pages and main pages, and indexation strategy. Should warn against thin content (just template + keyword swap).",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Identifies as Personas playbook",
+        "Applies core principles (unique value, proprietary data, clean URLs)",
+        "Recommends keyword research per variation",
+        "Addresses data requirements for unique content",
+        "Provides template design guidance",
+        "Includes internal linking strategy",
+        "Warns against thin content"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "Create a comparison page strategy. We want pages like 'Notion vs Asana', 'Notion vs Monday', etc. for all our competitors. We have 15 competitors.",
+      "expected_output": "Should identify this as the Comparisons playbook. Should apply the programmatic approach for competitor comparison pages at scale. Should recommend: template structure for comparison pages, unique data per comparison (not just the same template with names swapped), keyword research for each '[competitor A] vs [competitor B]' variation, URL structure (/compare/notion-vs-asana), internal linking between comparison pages, and quality checks. Should cross-reference the competitor-alternatives skill for page content structure.",
+      "assertions": [
+        "Identifies as Comparisons playbook",
+        "Recommends template structure for scale",
+        "Addresses unique data per comparison",
+        "Includes keyword research for variations",
+        "Provides URL structure recommendation",
+        "Includes internal linking strategy",
+        "Cross-references competitor-alternatives skill",
+        "Applies quality checks"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "we want to rank for '[tool name] integration' keywords. we integrate with 50+ tools and want a page for each. like 'Slack integration', 'Salesforce integration' etc.",
+      "expected_output": "Should trigger on casual phrasing. Should identify this as the Integrations playbook. Should recommend: template design for integration pages (what it does, how to set up, use cases), unique content per integration (specific workflows, screenshots, setup steps), keyword research for '[tool] + [your product] integration', URL structure (/integrations/slack), hub page linking to all integration pages, and schema markup considerations. Should emphasize that each page needs genuine unique value, not just 'we integrate with [tool].'",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Identifies as Integrations playbook",
+        "Recommends template with unique content per integration",
+        "Includes setup steps and use cases per page",
+        "Provides URL structure recommendation",
+        "Recommends hub page for all integrations",
+        "Emphasizes genuine unique value per page"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "We built 500 programmatic pages but Google isn't indexing most of them. Only 80 are in the index. What's going wrong?",
+      "expected_output": "Should diagnose the indexation problem. Should apply the quality checks and indexation strategy guidance. Should investigate: thin content (are pages providing unique value or just template + keyword?), crawl budget (500 pages may be fine but depends on site authority), internal linking (are the pages discoverable?), XML sitemap inclusion, duplicate/near-duplicate content issues. Should recommend specific fixes: improve content uniqueness, strengthen internal linking, submit sitemap, check robots.txt, use Search Console for indexation requests. Should warn that Google may choose not to index thin pages regardless.",
+      "assertions": [
+        "Diagnoses indexation problem",
+        "Investigates thin content as likely cause",
+        "Checks crawl budget considerations",
+        "Checks internal linking to programmatic pages",
+        "Checks XML sitemap and robots.txt",
+        "Recommends specific fixes for indexation",
+        "Warns about Google's thin content policies"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "Help me create a glossary section for our marketing automation platform. We want to define 200+ marketing terms and rank for '[term] definition' keywords.",
+      "expected_output": "Should identify this as the Glossary playbook. Should apply the template design: term definition page template (definition, examples, related terms, how it applies to the user's product), hub/index page linking to all terms, URL structure (/glossary/[term]), alphabetical and categorical navigation. Should address quality: each definition should provide genuine value beyond a dictionary definition. Should include internal linking strategy and schema markup (DefinedTerm schema). Should recommend starting with highest-volume terms.",
+      "assertions": [
+        "Identifies as Glossary playbook",
+        "Provides template design for term pages",
+        "Recommends hub/index page",
+        "Provides URL structure",
+        "Addresses content quality beyond dictionary definitions",
+        "Includes internal linking strategy",
+        "Recommends starting with highest-volume terms"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "Can you audit our existing programmatic SEO pages for technical issues? We have crawl errors and some pages return 404s.",
+      "expected_output": "Should recognize this is a technical SEO audit task, not a programmatic SEO strategy task. Should defer to or cross-reference the seo-audit skill, which handles crawlability, indexation, and technical SEO issues. Programmatic-seo focuses on strategy, template design, and content planning for scaled pages.",
+      "assertions": [
+        "Recognizes this as technical SEO audit task",
+        "References or defers to seo-audit skill",
+        "Explains that programmatic-seo is for strategy and template design",
+        "Does not attempt full technical SEO audit"
+      ],
+      "files": []
+    }
+  ]
+}
@@ -1,8 +1,8 @@
 ---
 name: referral-program
-description: "When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy. Also use when the user mentions 'referral,' 'affiliate,' 'ambassador,' 'word of mouth,' 'viral loop,' 'refer a friend,' or 'partner program.' This skill covers program design, incentive structure, and growth optimization."
+description: "When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy. Also use when the user mentions 'referral,' 'affiliate,' 'ambassador,' 'word of mouth,' 'viral loop,' 'refer a friend,' 'partner program,' 'referral incentive,' 'how to get referrals,' 'customers referring customers,' or 'affiliate payout.' Use this whenever someone wants existing users or partners to bring in new customers. For launch-specific virality, see launch-strategy."
 metadata:
-  version: 1.0.0
+  version: 1.1.0
 ---

 # Referral & Affiliate Programs
@@ -12,7 +12,7 @@ You are an expert in viral growth and referral marketing. Your goal is to help d
 ## 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):

@@ -244,6 +244,8 @@ For implementation, see the [tools registry](../../tools/REGISTRY.md). Key tools
 | **Mention Me** | Enterprise referral programs | [mention-me.md](../../tools/integrations/mention-me.md) |
 | **Dub.co** | Link tracking and attribution | [dub-co.md](../../tools/integrations/dub-co.md) |
 | **Stripe** | Payment processing (for commission tracking) | [stripe.md](../../tools/integrations/stripe.md) |
+| **Introw** | Channel partner programs with tiers, deal registration, QBRs | [introw.md](../../tools/integrations/introw.md) |
+| **PartnerStack** | Enterprise partner and affiliate programs | [partnerstack.md](../../tools/integrations/partnerstack.md) |

 ---

@@ -0,0 +1,89 @@
+{
+  "skill_name": "referral-program",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Help me design a referral program for our SaaS product. We're a $49/month project management tool with about 1,000 customers. We want to encourage word-of-mouth growth.",
+      "expected_output": "Should check for product-marketing-context.md first. Should distinguish between referral and affiliate programs (this is referral — existing customers referring peers). Should design the referral loop: trigger point (when to ask for referral), share mechanism (unique link, email invite, social share), conversion flow (what the referred person experiences), and reward structure. Should recommend incentive type: double-sided recommended (both referrer and referred get value). Should suggest specific incentives appropriate for $49/month SaaS (e.g., free month for both). Should include the launch checklist. Should recommend tool integrations (Rewardful, Tolt, etc.).",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Distinguishes referral from affiliate",
+        "Designs the referral loop (trigger, share, convert, reward)",
+        "Recommends double-sided incentive structure",
+        "Suggests specific incentives for the price point",
+        "Includes launch checklist",
+        "Recommends tool integrations"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "We have a referral program but only 5% of customers have ever referred someone. How do we increase participation?",
+      "expected_output": "Should apply the program optimization guidance. Should diagnose low participation: are customers aware of the program? Is the trigger point well-timed? Is the incentive compelling enough? Is sharing easy? Should recommend optimization tactics: better placement/visibility, timing referral asks at peak satisfaction moments, improving the incentive, simplifying the share mechanism, adding referral reminders in email and in-app. Should provide specific experiment ideas to test improvements.",
+      "assertions": [
+        "Applies program optimization guidance",
+        "Diagnoses potential causes of low participation",
+        "Checks awareness, timing, incentive, and friction",
+        "Recommends optimization tactics",
+        "Suggests timing referral asks at satisfaction moments",
+        "Provides experiment ideas"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "should we do referral or affiliate? we sell online courses for $199-499 and want to get other creators and influencers to promote us.",
+      "expected_output": "Should trigger on casual phrasing. Should apply the referral vs affiliate distinction clearly. For this use case (getting creators/influencers to promote), should recommend an affiliate program (not referral — affiliates are third-party promoters, not existing customers). Should apply the affiliate program section guidance: commission structure for digital products (typically 20-40% for courses), cookie duration, payout terms, affiliate onboarding. Should recommend affiliate platforms/tools appropriate for course creators.",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Clearly distinguishes referral from affiliate",
+        "Recommends affiliate for this use case",
+        "Provides commission structure guidance for courses",
+        "Addresses cookie duration and payout terms",
+        "Recommends appropriate affiliate platforms"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "What incentive structure works best? We've been offering $10 off for referrers but it's not working. Our product is $29/month.",
+      "expected_output": "Should evaluate the current incentive: $10 off on a $29/month product is significant but only benefits the referrer (single-sided). Should recommend testing double-sided incentives (both parties get value). Should discuss incentive types: account credit, free months, feature upgrades, cash. Should apply the tiered incentive concept (increasing rewards for multiple referrals). Should provide specific alternative incentive structures to test. Should note that incentive alone may not be the problem — placement and timing matter too.",
+      "assertions": [
+        "Evaluates current incentive structure",
+        "Identifies as single-sided and recommends double-sided",
+        "Discusses multiple incentive types",
+        "Applies tiered incentive concept",
+        "Provides specific alternatives to test",
+        "Notes incentive may not be the only issue"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "How do we measure the success of our referral program? What metrics should we track?",
+      "expected_output": "Should apply the measuring success framework. Should define key metrics: participation rate (% of customers who refer), share rate (referrals sent per participant), conversion rate (referred visitors who become customers), viral coefficient (k-factor), customer acquisition cost via referral vs other channels, referred customer LTV vs organic customer LTV. Should recommend tracking tools and dashboards. Should provide benchmark ranges for each metric.",
+      "assertions": [
+        "Applies measuring success framework",
+        "Defines participation rate, share rate, conversion rate",
+        "Includes viral coefficient / k-factor",
+        "Compares referral CAC to other channels",
+        "Compares referred customer LTV to organic",
+        "Recommends tracking approach",
+        "Provides benchmark ranges"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "Can you write the referral invitation emails? I need the email that goes out when someone shares their referral link.",
+      "expected_output": "Should recognize this overlaps with email writing. Should apply the referral email sequence section from the skill for referral-specific emails. However, for detailed email sequence design (multi-email nurture for referred users), should cross-reference the email-sequence skill. Should provide the referral invitation email but note that broader email sequence work is handled by email-sequence.",
+      "assertions": [
+        "Applies referral email section from the skill",
+        "Provides referral invitation email guidance",
+        "Cross-references email-sequence for broader email work",
+        "Provides specific referral email copy or template"
+      ],
+      "files": []
+    }
+  ]
+}
@@ -118,6 +118,9 @@ Provide affiliates with:
 - Tapfiliate — Simple SaaS affiliate tracking
 - FirstPromoter — SaaS affiliate management

+**Partner Relationship Management (PRM):**
+- Introw — Full PRM with deal registration, commissions, tiers, QBRs, and partner engagement tracking ([integration guide](../../../tools/integrations/introw.md))
+
 **Self-hosted:**
 - Rewardful — Stripe-integrated affiliates
 - Refersion — E-commerce affiliates
@@ -0,0 +1,345 @@
+---
+name: revops
+description: "When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see email-sequence. For pricing decisions, see pricing-strategy."
+metadata:
+  version: 1.1.0
+---
+
+# RevOps
+
+You are an expert in revenue operations. Your goal is to help design and optimize the systems that connect marketing, sales, and customer success into a unified revenue engine.
+
+## 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. **GTM motion** — Product-led (PLG), sales-led, or hybrid?
+2. **ACV range** — What's the average contract value?
+3. **Sales cycle length** — Days from first touch to closed-won?
+4. **Current stack** — CRM, marketing automation, scheduling, enrichment tools?
+5. **Current state** — How are leads managed today? What's working and what's not?
+6. **Goals** — Increase conversion? Reduce speed-to-lead? Fix handoff leaks? Build from scratch?
+
+Work with whatever the user gives you. If they have a clear problem area, start there. Don't block on missing inputs — use what you have and note what would strengthen the solution.
+
+---
+
+## Core Principles
+
+### Single Source of Truth
+One system of record for every lead and account. If data lives in multiple places, it will conflict. Pick a CRM as the canonical source and sync everything to it.
+
+### Define Before Automate
+Get stage definitions, scoring criteria, and routing rules right on paper before building workflows. Automating a broken process just creates broken results faster.
+
+### Measure Every Handoff
+Every handoff between teams is a potential leak. Marketing-to-sales, SDR-to-AE, AE-to-CS — each needs an SLA, a tracking mechanism, and someone accountable for follow-through.
+
+### Revenue Team Alignment
+Marketing, sales, and customer success must agree on definitions. If marketing calls something an MQL but sales won't work it, the definition is wrong. Alignment meetings aren't optional.
+
+---
+
+## Lead Lifecycle Framework
+
+### Stage Definitions
+
+| Stage | Entry Criteria | Exit Criteria | Owner |
+|-------|---------------|---------------|-------|
+| **Subscriber** | Opts in to content (blog, newsletter) | Provides company info or shows engagement | Marketing |
+| **Lead** | Identified contact with basic info | Meets minimum fit criteria | Marketing |
+| **MQL** | Passes fit + engagement threshold | Sales accepts or rejects within SLA | Marketing |
+| **SQL** | Sales accepts and qualifies via conversation | Opportunity created or recycled | Sales (SDR/AE) |
+| **Opportunity** | Budget, authority, need, timeline confirmed | Closed-won or closed-lost | Sales (AE) |
+| **Customer** | Closed-won deal | Expands, renews, or churns | CS / Account Mgmt |
+| **Evangelist** | High NPS, referral activity, case study | Ongoing program participation | CS / Marketing |
+
+### MQL Definition
+
+An MQL requires both **fit** and **engagement**:
+
+- **Fit score** — Does this person match your ICP? (company size, industry, role, tech stack)
+- **Engagement score** — Have they shown buying intent? (pricing page, demo request, multiple visits)
+
+Neither alone is sufficient. A perfect-fit company that never engages isn't an MQL. A student downloading every ebook isn't an MQL.
+
+### MQL-to-SQL Handoff SLA
+
+Define response times and document them:
+- MQL alert sent to assigned rep
+- Rep contacts within **4 hours** (business hours)
+- Rep qualifies or rejects within **48 hours**
+- Rejected MQLs go to recycling nurture with reason code
+
+**For complete lifecycle stage templates and SLA examples**: See [references/lifecycle-definitions.md](references/lifecycle-definitions.md)
+
+---
+
+## Lead Scoring
+
+### Scoring Dimensions
+
+**Explicit scoring (fit)** — Who they are:
+- Company size, industry, revenue
+- Job title, seniority, department
+- Tech stack, geography
+
+**Implicit scoring (engagement)** — What they do:
+- Page visits (especially pricing, demo, case studies)
+- Content downloads, webinar attendance
+- Email engagement (opens, clicks)
+- Product usage (for PLG)
+
+**Negative scoring** — Disqualifying signals:
+- Competitor email domains
+- Student/personal email
+- Unsubscribes, spam complaints
+- Job title mismatches (intern, student)
+
+### Building a Scoring Model
+
+1. Define your ICP attributes and weight them
+2. Identify high-intent behavioral signals from closed-won data
+3. Set point values for each attribute and behavior
+4. Set MQL threshold (typically 50-80 points on a 100-point scale)
+5. Test against historical data — does the model correctly identify past wins?
+6. Launch, measure, and recalibrate quarterly
+
+### Common Scoring Mistakes
+
+- Weighting content downloads too heavily (research ≠ buying intent)
+- Not including negative scoring (lets bad leads through)
+- Setting and forgetting (buyer behavior changes; recalibrate quarterly)
+- Scoring all page visits equally (pricing page ≠ blog post)
+
+**For detailed scoring templates and example models**: See [references/scoring-models.md](references/scoring-models.md)
+
+---
+
+## Lead Routing
+
+### Routing Methods
+
+| Method | How It Works | Best For |
+|--------|-------------|----------|
+| **Round-robin** | Distribute evenly across reps | Equal territories, similar deal sizes |
+| **Territory-based** | Assign by geography, vertical, or segment | Regional teams, industry specialists |
+| **Account-based** | Named accounts go to named reps | ABM motions, strategic accounts |
+| **Skill-based** | Route by deal complexity, product line, or language | Diverse product lines, global teams |
+
+### Routing Rules Essentials
+
+- Route to the **most specific match** first, then fall back to general
+- Include a **fallback owner** — unassigned leads go cold fast and waste pipeline
+- Round-robin should account for **rep capacity and availability** (PTO, quota attainment)
+- Log every routing decision for audit and optimization
+
+### Speed-to-Lead
+
+Response time is the single biggest factor in lead conversion:
+- Contact within **5 minutes** = 21x more likely to qualify (Lead Connect)
+- After **30 minutes**, conversion drops by 10x
+- After **24 hours**, the lead is effectively cold
+
+Build routing rules that prioritize speed. Alert reps immediately. Escalate if SLA is missed.
+
+**For routing decision trees and platform-specific setup**: See [references/routing-rules.md](references/routing-rules.md)
+
+---
+
+## Pipeline Stage Management
+
+### Pipeline Stages
+
+| Stage | Required Fields | Exit Criteria |
+|-------|----------------|---------------|
+| **Qualified** | Contact info, company, source, fit score | Discovery call scheduled |
+| **Discovery** | Pain points, current solution, timeline | Needs confirmed, demo scheduled |
+| **Demo/Evaluation** | Technical requirements, decision makers | Positive evaluation, proposal requested |
+| **Proposal** | Pricing, terms, stakeholder map | Proposal delivered and reviewed |
+| **Negotiation** | Redlines, approval chain, close date | Terms agreed, contract sent |
+| **Closed Won** | Signed contract, payment terms | Handoff to CS complete |
+| **Closed Lost** | Loss reason, competitor (if any) | Post-mortem logged |
+
+### Stage Hygiene
+
+- **Required fields per stage** — Don't let reps advance a deal without filling in required data
+- **Stale deal alerts** — Flag deals that sit in a stage beyond the average time (e.g., 2x average days)
+- **Stage skip detection** — Alert when deals jump stages (Qualified → Proposal skipping Discovery)
+- **Close date discipline** — Push dates must include a reason; no silent pushes
+
+### Pipeline Metrics
+
+| Metric | What It Tells You |
+|--------|-------------------|
+| Stage conversion rates | Where deals die |
+| Average time in stage | Where deals stall |
+| Pipeline velocity | Revenue per day through the funnel |
+| Coverage ratio | Pipeline value vs. quota (target 3-4x) |
+| Win rate by source | Which channels produce real revenue |
+
+---
+
+## CRM Automation Workflows
+
+### Essential Automations
+
+- **Lifecycle stage updates** — Auto-advance stages when criteria are met
+- **Task creation on handoff** — Create follow-up task when MQL assigned to rep
+- **SLA alerts** — Notify manager if rep misses response time SLA
+- **Deal stage triggers** — Auto-send proposals, update forecasts, notify CS on close
+
+### Marketing-to-Sales Automations
+
+- **MQL alert** — Instant notification to assigned rep with lead context
+- **Meeting booked** — Notify AE when prospect books via scheduling tool
+- **Lead activity digest** — Daily summary of high-intent actions by active leads
+- **Re-engagement trigger** — Alert sales when a dormant lead returns to site
+
+### Calendar Scheduling Integration
+
+- **Round-robin scheduling** — Distribute meetings evenly across team
+- **Routing by criteria** — Send enterprise leads to senior AEs, SMB to junior reps
+- **Pre-meeting enrichment** — Auto-populate CRM record before the call
+- **No-show workflows** — Auto-follow-up if prospect misses meeting
+
+**For platform-specific workflow recipes**: See [references/automation-playbooks.md](references/automation-playbooks.md)
+
+---
+
+## Deal Desk Processes
+
+### When You Need a Deal Desk
+
+- ACV above **$25K** (or your threshold for non-standard deals)
+- Non-standard payment terms (net-90, quarterly billing)
+- Multi-year contracts with custom pricing
+- Volume discounts beyond published tiers
+- Custom legal terms or SLAs
+
+### Approval Workflow Tiers
+
+| Deal Size | Approval Required |
+|-----------|-------------------|
+| Standard pricing | Auto-approved |
+| 10-20% discount | Sales manager |
+| 20-40% discount | VP Sales |
+| 40%+ discount or custom terms | Deal desk review |
+| Multi-year / enterprise | Finance + Legal |
+
+### Non-Standard Terms Handling
+
+Document every exception. Track which non-standard terms get requested most — if everyone asks for the same exception, it should become standard. Review quarterly.
+
+---
+
+## Data Hygiene & Enrichment
+
+### Dedup Strategy
+
+- **Matching rules** — Email domain + company name + phone as primary match keys
+- **Merge priority** — CRM record wins over marketing automation; most recent activity wins for fields
+- **Scheduled dedup** — Run weekly automated dedup with manual review for edge cases
+
+### Required Fields Enforcement
+
+- Enforce required fields at each lifecycle stage
+- Block stage advancement if fields are empty
+- Use progressive profiling — don't require everything upfront
+
+### Enrichment Tools
+
+| Tool | Strength |
+|------|----------|
+| Clearbit | Real-time enrichment, good for tech companies |
+| Apollo | Contact data + sequences, strong for prospecting |
+| ZoomInfo | Enterprise-grade, largest B2B database |
+
+### Quarterly Audit Checklist
+
+- Review and merge duplicates
+- Validate email deliverability on stale contacts
+- Archive contacts with no activity in 12+ months
+- Audit lifecycle stage distribution (look for bottlenecks)
+- Verify enrichment data accuracy on a sample set
+
+---
+
+## RevOps Metrics Dashboard
+
+### Key Metrics
+
+| Metric | Formula / Definition | Benchmark |
+|--------|---------------------|-----------|
+| Lead-to-MQL rate | MQLs / Total leads | 5-15% |
+| MQL-to-SQL rate | SQLs / MQLs | 30-50% |
+| SQL-to-Opportunity | Opportunities / SQLs | 50-70% |
+| Pipeline velocity | (# deals x avg deal size x win rate) / avg sales cycle | Varies by ACV |
+| CAC | Total sales + marketing spend / new customers | LTV:CAC > 3:1 |
+| LTV:CAC ratio | Customer lifetime value / CAC | 3:1 to 5:1 healthy |
+| Speed-to-lead | Time from form fill to first rep contact | < 5 minutes ideal |
+| Win rate | Closed-won / total opportunities | 20-30% (varies) |
+
+### Dashboard Structure
+
+Build three views:
+1. **Marketing view** — Lead volume, MQL rate, source attribution, cost per MQL
+2. **Sales view** — Pipeline value, stage conversion, velocity, forecast accuracy
+3. **Executive view** — CAC, LTV:CAC, revenue vs. target, pipeline coverage
+
+---
+
+## Output Format
+
+When delivering RevOps recommendations, provide:
+
+1. **Lifecycle stage document** — Stage definitions with entry/exit criteria, owners, and SLAs
+2. **Scoring specification** — Fit and engagement attributes with point values and MQL threshold
+3. **Routing rules document** — Decision tree with assignment logic and fallbacks
+4. **Pipeline configuration** — Stage definitions, required fields, and automation triggers
+5. **Metrics dashboard spec** — Key metrics, data sources, and target benchmarks
+
+Format each as a standalone document the user can implement directly. Include platform-specific guidance when the CRM is known.
+
+---
+
+## Task-Specific Questions
+
+1. What CRM platform are you using (or planning to use)?
+2. How many leads per month do you generate?
+3. What's your current MQL definition?
+4. Where do leads get stuck in your funnel?
+5. Do you have SLAs between marketing and sales today?
+
+---
+
+## Tool Integrations
+
+For implementation, see the [tools registry](../../tools/REGISTRY.md). Key RevOps tools:
+
+| Tool | What It Does | Guide |
+|------|-------------|-------|
+| **HubSpot** | CRM, marketing automation, lead scoring, workflows | [hubspot.md](../../tools/integrations/hubspot.md) |
+| **Salesforce** | Enterprise CRM, pipeline management, reporting | [salesforce.md](../../tools/integrations/salesforce.md) |
+| **Calendly** | Meeting scheduling, round-robin routing | [calendly.md](../../tools/integrations/calendly.md) |
+| **SavvyCal** | Scheduling with priority-based availability | [savvycal.md](../../tools/integrations/savvycal.md) |
+| **Clearbit** | Real-time lead enrichment and scoring | [clearbit.md](../../tools/integrations/clearbit.md) |
+| **Apollo** | Contact data, enrichment, and outbound sequences | [apollo.md](../../tools/integrations/apollo.md) |
+| **ActiveCampaign** | Marketing automation for SMBs, lead scoring | [activecampaign.md](../../tools/integrations/activecampaign.md) |
+| **Zapier** | Cross-tool automation and workflow glue | [zapier.md](../../tools/integrations/zapier.md) |
+| **Introw** | Partner-sourced pipeline, commissions, deal registration, QBRs | [introw.md](../../tools/integrations/introw.md) |
+| **Crossbeam** | Partner account overlaps and co-sell identification | [crossbeam.md](../../tools/integrations/crossbeam.md) |
+
+---
+
+## Related Skills
+
+- **cold-email**: For outbound prospecting emails
+- **email-sequence**: For lifecycle and nurture email flows
+- **pricing-strategy**: For pricing decisions and packaging
+- **analytics-tracking**: For tracking pipeline metrics and attribution
+- **launch-strategy**: For go-to-market launch planning
+- **sales-enablement**: For sales collateral, decks, and objection handling
@@ -0,0 +1,91 @@
+{
+  "skill_name": "revops",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Help me set up our lead lifecycle stages. We're a B2B SaaS company selling to mid-market. We use HubSpot as our CRM and have marketing and sales teams that aren't aligned on lead definitions.",
+      "expected_output": "Should check for product-marketing-context.md first. Should apply the lead lifecycle framework: Subscriber → Lead → MQL → SQL → Opportunity → Customer → Evangelist. Should define clear criteria for each stage transition (what makes a Lead become an MQL, etc.). Should address the alignment issue between marketing and sales — define shared definitions and SLAs. Should recommend CRM implementation steps for HubSpot. Should include lead scoring setup. Should provide a handoff process between marketing and sales.",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Applies lead lifecycle framework with all stages",
+        "Defines criteria for each stage transition",
+        "Addresses marketing-sales alignment",
+        "Provides CRM implementation guidance for HubSpot",
+        "Includes lead scoring setup",
+        "Provides handoff process between teams"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "Set up lead scoring for us. We want to prioritize which leads sales should call first. We sell enterprise software ($50k+ ACV).",
+      "expected_output": "Should apply the lead scoring framework with three dimensions: explicit scoring (firmographics — company size, industry, title match), implicit scoring (behavioral — page visits, content downloads, email engagement), and negative scoring (unsubscribes, competitor emails, student emails). Should provide specific scoring criteria appropriate for enterprise ($50k+ ACV): weight firmographic signals heavily, include budget and authority signals. Should define score thresholds for MQL and SQL. Should recommend lead routing based on scores.",
+      "assertions": [
+        "Applies lead scoring with explicit, implicit, and negative dimensions",
+        "Provides specific scoring criteria for enterprise",
+        "Weights firmographic signals appropriately",
+        "Includes behavioral scoring signals",
+        "Includes negative scoring signals",
+        "Defines MQL and SQL score thresholds",
+        "Recommends lead routing based on scores"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "our pipeline is a mess. deals sit in stages forever and we don't know what's actually going to close. how do we fix this?",
+      "expected_output": "Should trigger on casual phrasing. Should apply the pipeline stage management guidance. Should recommend: define clear pipeline stages with entry/exit criteria, set maximum time in each stage, implement stage velocity tracking, add required fields per stage to force data entry. Should address deal hygiene: regular pipeline reviews, stale deal flagging, win/loss analysis. Should recommend CRM automation to enforce stage rules. Should provide a practical cleanup plan for the current mess.",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Applies pipeline stage management",
+        "Defines stages with entry/exit criteria",
+        "Recommends maximum time per stage",
+        "Addresses deal hygiene and pipeline reviews",
+        "Recommends CRM automation for enforcement",
+        "Provides practical cleanup plan"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "What RevOps metrics should we be tracking? We want to build a dashboard for our leadership team.",
+      "expected_output": "Should apply the RevOps metrics dashboard framework. Should recommend metrics across the funnel: lead volume by source, MQL-to-SQL conversion rate, SQL-to-Opportunity rate, win rate, average deal size, sales cycle length, pipeline velocity, pipeline coverage ratio, CAC, LTV, LTV:CAC ratio. Should organize metrics by audience (marketing team, sales team, leadership). Should recommend dashboard structure and cadence for reviews.",
+      "assertions": [
+        "Applies RevOps metrics dashboard",
+        "Covers full-funnel metrics",
+        "Includes conversion rates between stages",
+        "Includes pipeline velocity and coverage",
+        "Includes CAC, LTV, LTV:CAC",
+        "Organizes by audience",
+        "Recommends dashboard structure and review cadence"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "Our CRM data is a disaster. Duplicate records, missing fields, inconsistent naming. How do we clean it up and keep it clean?",
+      "expected_output": "Should apply the data hygiene guidance. Should recommend: duplicate detection and merging strategy, required field enforcement, standardized naming conventions (picklists over free text), data validation rules, regular audit cadence. Should address both cleanup (one-time fix) and prevention (ongoing processes). Should recommend CRM automation for data hygiene. Should provide a prioritized cleanup plan (start with highest-impact data quality issues).",
+      "assertions": [
+        "Applies data hygiene guidance",
+        "Recommends duplicate detection and merging",
+        "Recommends required field enforcement",
+        "Addresses standardized naming conventions",
+        "Covers both cleanup and prevention",
+        "Recommends CRM automation for hygiene",
+        "Provides prioritized cleanup plan"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "Can you help me write cold outreach emails to prospects in our pipeline?",
+      "expected_output": "Should recognize this is a cold email / outbound writing task, not RevOps. Should defer to or cross-reference the cold-email skill for writing outbound prospecting emails. RevOps covers the systems, processes, and data infrastructure — not the actual email content.",
+      "assertions": [
+        "Recognizes this as cold email writing, not RevOps",
+        "References or defers to cold-email skill",
+        "Explains RevOps covers systems and processes, not email content"
+      ],
+      "files": []
+    }
+  ]
+}
@@ -0,0 +1,290 @@
+# Automation Playbooks
+
+Platform-specific workflow recipes for HubSpot, Salesforce, scheduling tools, and cross-tool automation.
+
+## HubSpot Workflow Recipes
+
+### 1. MQL Alert and Assignment
+
+**Name:** MQL Notification and Task Creation
+**Trigger:** Contact property "Lifecycle Stage" is changed to "Marketing Qualified Lead"
+**Actions:**
+1. Rotate contact owner among sales team (round-robin)
+2. Send internal email notification to contact owner with lead context
+3. Create task: "Follow up with [Contact Name]" — due in 4 hours
+4. Send Slack notification to #sales-alerts channel
+5. Enroll in "MQL Follow-Up" sequence (if using HubSpot Sequences)
+**Outcome:** Every MQL gets assigned instantly with a clear SLA
+**Notes:** Set enrollment criteria to exclude leads already owned by a rep
+
+---
+
+### 2. MQL SLA Escalation
+
+**Name:** MQL SLA Breach Alert
+**Trigger:** Contact property "Lifecycle Stage" equals "MQL" AND "Days since last contacted" is greater than 0.5 (12 hours)
+**Actions:**
+1. Send internal email to contact owner: "SLA warning: [Contact Name] has not been contacted"
+2. If still no activity after 24 hours → send alert to sales manager
+3. If still no activity after 48 hours → reassign contact owner via rotation
+4. Create task for new owner: "Urgent: Contact [Contact Name] — reassigned due to SLA breach"
+**Outcome:** No MQL goes unworked for more than 48 hours
+**Notes:** Exclude contacts where last activity type is "Call" or "Meeting" (already engaged)
+
+---
+
+### 3. Lead Scoring Update and MQL Promotion
+
+**Name:** Auto-MQL on Score Threshold
+**Trigger:** Contact property "HubSpot Score" is greater than or equal to 65
+**Actions:**
+1. Set lifecycle stage to "Marketing Qualified Lead"
+2. Set "MQL Date" to current date
+3. Suppress from marketing nurture workflows
+4. Trigger MQL Alert workflow (recipe #1)
+**Outcome:** Leads automatically promote to MQL when they hit the scoring threshold
+**Notes:** Add suppression list for existing customers and competitors
+
+---
+
+### 4. Meeting Booked Notification
+
+**Name:** Meeting Booked Alert to AE
+**Trigger:** Meeting activity is logged for contact (via Calendly/HubSpot meetings)
+**Actions:**
+1. Send internal email to contact owner with meeting details
+2. Update contact property "Last Meeting Booked" to current date
+3. If lifecycle stage is "Lead" → update to "MQL"
+4. Create task: "Prepare for meeting with [Contact Name]" — due 1 hour before meeting
+5. Send Slack notification to #meetings channel
+**Outcome:** AEs are prepared for every meeting with full context
+**Notes:** Include recent page views and content downloads in notification email
+
+---
+
+### 5. Closed-Won Handoff to CS
+
+**Name:** Customer Onboarding Trigger
+**Trigger:** Deal stage is changed to "Closed Won"
+**Actions:**
+1. Update associated contact lifecycle stage to "Customer"
+2. Set "Customer Since" date to current date
+3. Assign contact owner to CS team member (based on segment/territory)
+4. Create task for CS: "Schedule kickoff call with [Company Name]" — due in 2 business days
+5. Enroll contact in "Customer Onboarding" email sequence
+6. Send internal notification to CS manager
+7. Remove from all sales sequences
+**Outcome:** Seamless handoff from sales to customer success
+**Notes:** Include deal notes, contract value, and key stakeholders in CS notification
+
+---
+
+### 6. Stale Deal Alert
+
+**Name:** Pipeline Hygiene — Stale Deal Detection
+**Trigger:** Deal property "Days in current stage" is greater than [2x average for that stage]
+**Actions:**
+1. Send internal email to deal owner: "Deal stale alert: [Deal Name] has been in [Stage] for [X] days"
+2. Create task: "Update or close [Deal Name]" — due in 3 business days
+3. If no update after 7 days → alert sales manager
+4. Add to "Stale Deals" dashboard list
+**Outcome:** Pipeline stays clean and forecast stays accurate
+**Notes:** Customize thresholds per stage (Discovery: 14 days, Proposal: 10 days, Negotiation: 21 days)
+
+---
+
+### 7. Recycled Lead Nurture Re-Entry
+
+**Name:** MQL Recycling to Nurture
+**Trigger:** Contact property "Sales Rejection Reason" is known (any value)
+**Actions:**
+1. Update lifecycle stage to "Recycled"
+2. Reset engagement score to baseline (keep fit score)
+3. Enroll in "Recycled Lead Nurture" sequence (lower frequency)
+4. Set "Recycle Date" to current date
+5. Set re-enrollment trigger: if HubSpot Score exceeds threshold again, re-trigger MQL workflow
+**Outcome:** Rejected leads get a second chance without clogging the pipeline
+**Notes:** Track recycled-to-MQL conversion rate as a separate metric
+
+---
+
+### 8. Lead Activity Digest
+
+**Name:** Daily Lead Activity Summary
+**Trigger:** Scheduled — daily at 8:00 AM local time
+**Actions:**
+1. Filter contacts: lifecycle stage is "SQL" or "Opportunity" AND had website activity in last 24 hours
+2. Send digest email to each contact owner with their leads' activity
+3. Include: pages visited, content downloaded, emails opened/clicked
+**Outcome:** Sales reps start each day knowing which leads are active
+**Notes:** Only include leads with meaningful activity (exclude single homepage visits)
+
+---
+
+## Salesforce Flow Equivalents
+
+### 1. MQL Alert and Assignment (Salesforce Flow)
+
+**Type:** Record-Triggered Flow
+**Object:** Lead
+**Trigger:** Lead field "Status" is changed to "MQL"
+**Flow steps:**
+1. Get Records: Query "Rep Assignment" custom object for next available rep
+2. Update Records: Set Lead Owner to assigned rep
+3. Create Records: Create Task — "Contact MQL: {Lead.Name}" with due date = NOW + 4 hours
+4. Action: Send email alert to new lead owner
+5. Update Records: Update "Rep Assignment" last-assigned timestamp
+**Notes:** Use a custom "Rep Assignment" object to manage round-robin state
+
+### 2. SLA Escalation (Salesforce Flow)
+
+**Type:** Scheduled-Triggered Flow
+**Schedule:** Every 4 hours during business hours
+**Flow steps:**
+1. Get Records: Leads where Status = "MQL" AND LastActivityDate < TODAY - 1
+2. Decision: Is lead older than 48 hours with no activity?
+   - YES → Reassign to next rep, create urgent task, alert manager
+   - NO → Send reminder email to current owner
+**Notes:** Pair with Process Builder for real-time alerts on initial assignment
+
+### 3. Pipeline Stage Automation (Salesforce Flow)
+
+**Type:** Record-Triggered Flow
+**Object:** Opportunity
+**Trigger:** Stage field is updated
+**Flow steps:**
+1. Decision: Which stage was it changed to?
+2. For each stage:
+   - **Discovery:** Create task "Complete discovery questionnaire"
+   - **Demo:** Create task "Prepare demo environment"
+   - **Proposal:** Create task "Send proposal" + alert deal desk if ACV > $25K
+   - **Closed Won:** Trigger CS handoff (create Case, assign CS owner, send welcome email)
+   - **Closed Lost:** Create task "Log loss reason" + add to win/loss analysis report
+
+### 4. Stale Deal Detection (Salesforce Flow)
+
+**Type:** Scheduled-Triggered Flow
+**Schedule:** Daily at 7:00 AM
+**Flow steps:**
+1. Get Records: Open Opportunities where Days_In_Stage > Stage_SLA_Threshold
+2. Loop through results:
+   - Create Task: "Update stale deal: {Opportunity.Name}"
+   - Send email to Opportunity Owner
+   - If Days_In_Stage > 2x threshold → send email to Owner's Manager
+3. Update custom field "Stale Flag" = true for dashboard visibility
+
+---
+
+## Calendly / SavvyCal Integration Patterns
+
+### Round-Robin Meeting Scheduling
+
+**Calendly setup:**
+1. Create a team event type with all eligible reps
+2. Distribution: "Optimize for equal distribution"
+3. Availability: Each rep manages their own calendar
+4. Buffer: 15 min before and after meetings
+5. Minimum notice: 4 hours (avoid last-minute bookings)
+
+**CRM integration:**
+1. Calendly webhook fires on booking
+2. Match invitee email to CRM contact
+3. If contact exists → assign meeting to contact owner (override round-robin if owned)
+4. If new contact → create lead, assign via routing rules, log meeting
+5. Set lifecycle stage to MQL (meeting = high intent)
+
+### SavvyCal Setup
+
+**Advantages over Calendly:**
+- Priority-based scheduling (prefer certain time slots)
+- Overlay calendars (show team availability in one view)
+- Personalized booking links per rep
+
+**Integration pattern:**
+1. Create team scheduling link with priority rules
+2. Webhook on booking → Zapier/Make → CRM
+3. Match or create contact, assign owner, create task
+4. Send confirmation with meeting prep materials
+
+### Meeting Routing by Criteria
+
+```
+Booking form submitted
+├─ Company size > 500? (form field)
+│  ├─ YES → Route to enterprise AE calendar
+│  └─ NO ↓
+├─ Existing customer? (CRM lookup)
+│  ├─ YES → Route to account owner's calendar
+│  └─ NO ↓
+└─ Round-robin across SDR team
+```
+
+### No-Show Workflow
+
+**Trigger:** Meeting time passes + no meeting notes logged within 30 minutes
+**Actions:**
+1. Wait 30 minutes after scheduled meeting time
+2. Check: Was a call or meeting logged?
+   - YES → No action
+   - NO → Send "Sorry we missed you" email to prospect
+3. Create task: "Reschedule with [Contact Name]" — due next business day
+4. If second no-show → flag contact and alert manager
+
+---
+
+## Zapier Cross-Tool Patterns
+
+### 1. New Lead → CRM + Slack + Task
+
+**Trigger:** New form submission (Typeform, HubSpot, Webflow)
+**Actions:**
+1. Create/update contact in CRM
+2. Enrich with Clearbit (if available)
+3. Post to Slack #new-leads with enriched data
+4. Create task in project management tool (Asana, Linear)
+
+### 2. Meeting Booked → CRM + Prep Email
+
+**Trigger:** New Calendly/SavvyCal booking
+**Actions:**
+1. Find or create CRM contact
+2. Update lifecycle stage to MQL
+3. Send prep email to assigned rep (include CRM link, LinkedIn profile, recent activity)
+4. Create pre-meeting task
+
+### 3. Deal Closed → Onboarding Stack
+
+**Trigger:** CRM deal stage changed to "Closed Won"
+**Actions:**
+1. Create customer record in CS tool (Vitally, Gainsight, ChurnZero)
+2. Add to onboarding project template
+3. Send welcome email via email tool
+4. Create Slack channel: #customer-[company-name]
+5. Notify CS team in Slack
+
+### 4. Lead Scoring → Cross-Tool Sync
+
+**Trigger:** CRM lead score crosses MQL threshold
+**Actions:**
+1. Update marketing automation platform status
+2. Add to retargeting audience (Facebook, Google Ads)
+3. Trigger SDR outreach sequence
+4. Log event in analytics (Mixpanel, Amplitude)
+
+### 5. SLA Breach → Multi-Channel Alert
+
+**Trigger:** CRM task overdue (MQL follow-up task)
+**Actions:**
+1. Send Slack DM to rep
+2. Send email to rep
+3. If 2+ hours overdue → Slack DM to manager
+4. If 4+ hours overdue → reassign in CRM (via webhook back to CRM)
+
+### 6. Weekly Pipeline Digest
+
+**Trigger:** Schedule — every Monday at 8:00 AM
+**Actions:**
+1. Query CRM for pipeline summary (total value, new deals, stale deals, expected closes)
+2. Format as summary
+3. Post to Slack #sales-team
+4. Send email digest to sales leadership
@@ -0,0 +1,278 @@
+# Lifecycle Stage Definitions
+
+Complete templates for lead lifecycle stages, MQL criteria by business type, SLAs, and rejection/recycling workflows.
+
+## Stage Templates
+
+### Subscriber
+
+**Entry criteria:**
+- Opted in to blog, newsletter, or content updates
+- No company information required
+
+**Exit criteria:**
+- Provides company information via form or enrichment
+- Visits 3+ pages in a session
+- Downloads gated content
+
+**Owner:** Marketing (automated)
+
+**Actions on entry:**
+- Add to newsletter nurture
+- Begin tracking engagement score
+
+---
+
+### Lead
+
+**Entry criteria:**
+- Identified contact with name + email + company
+- May come from form fill, enrichment, or import
+
+**Exit criteria:**
+- Reaches MQL threshold (fit + engagement)
+- Manually qualified by marketing/SDR
+
+**Owner:** Marketing
+
+**Actions on entry:**
+- Enrich contact data (company size, industry, role)
+- Begin scoring
+- Add to relevant nurture sequence
+
+---
+
+### MQL (Marketing Qualified Lead)
+
+**Entry criteria:**
+- Meets fit score threshold AND engagement score threshold
+- OR triggers high-intent action (demo request, pricing page + form fill)
+
+**Exit criteria:**
+- Sales accepts (becomes SQL)
+- Sales rejects (recycled to nurture with reason code)
+- No response within SLA (escalated to manager)
+
+**Owner:** Marketing → Sales (handoff)
+
+**Actions on entry:**
+- Instant alert to assigned sales rep
+- Create follow-up task with 4-hour SLA
+- Pause marketing nurture sequences
+- Log all recent activity for sales context
+
+---
+
+### SQL (Sales Qualified Lead)
+
+**Entry criteria:**
+- Sales rep has had qualifying conversation
+- Confirmed: budget, authority, need, or timeline (at least 2 of 4)
+
+**Exit criteria:**
+- Opportunity created with projected value
+- Disqualified (recycled with reason code)
+
+**Owner:** Sales (SDR or AE)
+
+**Actions on entry:**
+- Update lifecycle stage in CRM
+- Notify AE if SDR-qualified
+- Begin sales sequence if not already in conversation
+
+---
+
+### Opportunity
+
+**Entry criteria:**
+- Formal opportunity created in CRM
+- Deal value, close date, and stage assigned
+
+**Exit criteria:**
+- Closed-won or closed-lost
+
+**Owner:** Sales (AE)
+
+**Actions on entry:**
+- Add to pipeline reporting
+- Create deal tasks (proposal, demo, etc.)
+- Notify CS if deal is likely to close
+
+---
+
+### Customer
+
+**Entry criteria:**
+- Closed-won deal
+- Contract signed and payment terms set
+
+**Exit criteria:**
+- Churns, expands, or renews
+
+**Owner:** Customer Success / Account Management
+
+**Actions on entry:**
+- Trigger onboarding sequence
+- Assign CS manager
+- Schedule kickoff call
+- Remove from all sales sequences
+
+---
+
+### Evangelist
+
+**Entry criteria:**
+- NPS score 9-10, or active referral behavior
+- Agreed to case study, testimonial, or referral program
+
+**Exit criteria:**
+- Ongoing program participation
+
+**Owner:** Customer Success + Marketing
+
+**Actions on entry:**
+- Add to advocacy program
+- Request case study or testimonial
+- Invite to referral program
+- Feature in marketing campaigns (with permission)
+
+---
+
+## MQL Criteria Templates by Business Type
+
+### PLG (Product-Led Growth)
+
+**Fit score (40% weight):**
+
+| Attribute | Points |
+|-----------|--------|
+| Company size 10-500 | +15 |
+| Company size 500-5000 | +20 |
+| Target industry | +10 |
+| Decision-maker role | +15 |
+| Uses complementary tool | +10 |
+
+**Engagement score (60% weight) — weight product usage heavily:**
+
+| Signal | Points |
+|--------|--------|
+| Created free account | +15 |
+| Completed onboarding | +20 |
+| Used core feature 3+ times | +25 |
+| Invited team member | +20 |
+| Hit usage limit | +15 |
+| Visited pricing page | +10 |
+
+**MQL threshold:** 65 points
+
+---
+
+### Sales-Led (Enterprise)
+
+**Fit score (60% weight) — weight fit heavily:**
+
+| Attribute | Points |
+|-----------|--------|
+| Company size 500+ | +20 |
+| Target industry | +15 |
+| VP+ title | +20 |
+| Budget authority confirmed | +15 |
+| Uses competitor product | +10 |
+
+**Engagement score (40% weight):**
+
+| Signal | Points |
+|--------|--------|
+| Requested demo | +25 |
+| Attended webinar | +10 |
+| Downloaded whitepaper | +10 |
+| Visited pricing page 2+ times | +15 |
+| Engaged with sales email | +10 |
+
+**MQL threshold:** 70 points
+
+---
+
+### Mid-Market (Balanced)
+
+**Fit score (50% weight):**
+
+| Attribute | Points |
+|-----------|--------|
+| Company size 50-1000 | +15 |
+| Target industry | +10 |
+| Manager+ title | +15 |
+| Target geography | +10 |
+
+**Engagement score (50% weight):**
+
+| Signal | Points |
+|--------|--------|
+| Demo request | +25 |
+| Free trial signup | +20 |
+| Pricing page visit | +10 |
+| Content download (2+) | +10 |
+| Email click (3+) | +10 |
+| Webinar attendance | +10 |
+
+**MQL threshold:** 60 points
+
+---
+
+## SLA Templates
+
+### MQL-to-SQL SLA
+
+| Metric | Target | Escalation |
+|--------|--------|------------|
+| First contact attempt | Within 4 business hours | Alert to sales manager at 4 hours |
+| Qualification decision | Within 48 hours | Auto-escalate at 48 hours |
+| Meeting scheduled (if qualified) | Within 5 business days | Weekly pipeline review flag |
+
+### SQL-to-Opportunity SLA
+
+| Metric | Target | Escalation |
+|--------|--------|------------|
+| Discovery call completed | Within 3 business days of SQL | Alert to AE manager |
+| Opportunity created | Within 5 business days of SQL | Pipeline review flag |
+
+### Opportunity-to-Close SLA
+
+| Metric | Target | Escalation |
+|--------|--------|------------|
+| Proposal delivered | Within 5 business days of demo | AE manager alert |
+| Deal stale in stage | 2x average days for that stage | Pipeline review flag |
+| Close date pushed 2+ times | Immediate | Forecast review required |
+
+---
+
+## Lead Rejection and Recycling
+
+### Rejection Reason Codes
+
+| Code | Reason | Recycle Action |
+|------|--------|----------------|
+| **FIT-01** | Company too small | Nurture; re-score if company grows |
+| **FIT-02** | Wrong industry | Archive; do not recycle |
+| **FIT-03** | Wrong role / no authority | Nurture; monitor for org changes |
+| **ENG-01** | No response after 3 attempts | Recycle to nurture in 90 days |
+| **ENG-02** | Interested but bad timing | Recycle to nurture; re-engage in 60 days |
+| **QUAL-01** | No budget | Recycle to nurture in 90 days |
+| **QUAL-02** | Using competitor, locked in | Recycle; trigger before contract renewal |
+| **QUAL-03** | Not a real project | Archive; do not recycle |
+
+### Recycling Workflow
+
+1. Sales rejects MQL with reason code
+2. CRM updates lifecycle stage to "Recycled"
+3. Lead enters recycling nurture sequence (different from original nurture)
+4. Engagement score resets to baseline (keep fit score)
+5. If lead re-engages and crosses MQL threshold, re-route to sales with "Recycled MQL" flag
+6. Track recycled MQL conversion rate separately
+
+### Recycling Nurture Sequence
+
+- **Frequency:** Bi-weekly or monthly (lower frequency than initial nurture)
+- **Content:** Industry insights, case studies, product updates
+- **Duration:** 6 months, then archive if no engagement
+- **Re-MQL trigger:** High-intent action (demo request, pricing page revisit)
@@ -0,0 +1,203 @@
+# Lead Routing Rules
+
+Decision trees, platform-specific configurations, territory routing, ABM routing, and speed-to-lead benchmarks.
+
+## Routing Decision Tree
+
+Use this template to map your routing logic:
+
+```
+New Lead Arrives
+│
+├─ Is this a named/target account?
+│  ├─ YES → Route to assigned account owner
+│  └─ NO ↓
+│
+├─ Is ACV likely > $50K? (based on company size + industry)
+│  ├─ YES → Route to enterprise AE team
+│  └─ NO ↓
+│
+├─ Is this a PLG signup with team usage?
+│  ├─ YES → Route to PLG sales specialist
+│  └─ NO ↓
+│
+├─ Does lead match a territory?
+│  ├─ YES → Route to territory owner
+│  └─ NO ↓
+│
+└─ Default: Round-robin across available reps
+   └─ If no rep available: Assign to team queue with 1-hour SLA
+```
+
+Customize this tree for your business. The key principle: **route to the most specific match first, fall back to general.**
+
+---
+
+## Round-Robin Configuration
+
+### Basic Round-Robin Rules
+
+1. Distribute leads evenly across eligible reps
+2. Skip reps who are on PTO, at capacity, or have a full pipeline
+3. Weight by quota attainment (reps below quota get slight priority)
+4. Reset distribution count weekly or monthly
+5. Log every assignment for auditing
+
+### HubSpot Round-Robin Setup
+
+**Using HubSpot's rotation tool:**
+- Navigate to Automation → Workflows
+- Trigger: Contact property "Lifecycle Stage" equals "MQL"
+- Action: Rotate contact owner among selected users
+- Options: Even distribution, skip unavailable owners
+- Add delay + task creation after assignment
+
+**Custom rotation with workflows:**
+1. Create a custom property "Rotation Counter" (number)
+2. Workflow trigger: New MQL created
+3. Branch by rotation counter value (0, 1, 2... for each rep)
+4. Set contact owner to corresponding rep
+5. Increment counter (reset at max)
+6. Create follow-up task with SLA deadline
+
+### Salesforce Round-Robin Setup
+
+**Using Lead Assignment Rules:**
+1. Setup → Feature Settings → Marketing → Lead Assignment Rules
+2. Create rule entries in priority order (most specific first)
+3. For round-robin: Use assignment rule + custom logic
+
+**Using Flow for advanced routing:**
+1. Create a Record-Triggered Flow on Lead creation
+2. Get Records: Query a custom "Rep Queue" object for next available rep
+3. Decision element: Check rep availability, capacity, territory
+4. Update Records: Assign lead owner
+5. Create Task: Follow-up task with SLA
+6. Update "Rep Queue" to track last assignment
+
+---
+
+## Territory Routing
+
+### By Geography
+
+| Territory | Regions | Assigned Team |
+|-----------|---------|---------------|
+| West | CA, WA, OR, NV, AZ, UT, CO, HI | Team West |
+| Central | TX, IL, MN, MO, OH, MI, WI, IN | Team Central |
+| East | NY, MA, PA, NJ, CT, VA, FL, GA | Team East |
+| International | All non-US | International team |
+
+### By Company Size
+
+| Segment | Company Size | Team |
+|---------|-------------|------|
+| SMB | 1-50 employees | Inside sales |
+| Mid-market | 51-500 employees | Mid-market AEs |
+| Enterprise | 501-5000 employees | Enterprise AEs |
+| Strategic | 5000+ employees | Strategic account team |
+
+### By Industry
+
+| Vertical | Industries | Specialist |
+|----------|-----------|------------|
+| Tech | SaaS, IT services, hardware | Tech vertical rep |
+| Financial | Banking, insurance, fintech | Financial vertical rep |
+| Healthcare | Hospitals, pharma, healthtech | Healthcare vertical rep |
+| General | All others | General pool (round-robin) |
+
+### Hybrid Territory Model
+
+Combine multiple dimensions for precision:
+
+```
+Lead arrives
+├─ Company size > 1000?
+│  ├─ YES → Enterprise team
+│  │  └─ Sub-route by geography
+│  └─ NO ↓
+├─ Industry = Healthcare or Financial?
+│  ├─ YES → Vertical specialist
+│  └─ NO ↓
+└─ Round-robin across general pool
+   └─ Weighted by geography preference
+```
+
+---
+
+## Named Account / ABM Routing
+
+### Setup
+
+1. **Define target account list** (typically 50-500 accounts)
+2. **Assign account owners** in CRM (1 rep per account)
+3. **Match logic:** Any lead from a target account domain routes to account owner
+4. **Matching rules:**
+   - Email domain match (primary)
+   - Company name fuzzy match (secondary, requires manual review)
+   - IP-to-company resolution (tertiary, for anonymous visitors)
+
+### ABM Routing Rules
+
+| Tier | Account Type | Routing | Response SLA |
+|------|-------------|---------|--------------|
+| Tier 1 | Top 20 strategic accounts | Named owner, instant alert | 1 hour |
+| Tier 2 | Top 100 target accounts | Named owner, standard alert | 4 hours |
+| Tier 3 | Target industry / size match | Territory or round-robin | Same business day |
+
+### Multi-Contact Handling
+
+When multiple contacts from the same account engage:
+- Route all contacts to the **same account owner**
+- Notify the owner of new contacts entering
+- Track account-level engagement score (sum of all contacts)
+- Trigger "buying committee" alert when 3+ contacts from one account engage
+
+---
+
+## Speed-to-Lead Data
+
+### Response Time Impact on Conversion
+
+| Response Time | Relative Qualification Rate | Notes |
+|---------------|---------------------------|-------|
+| Under 5 minutes | **21x** more likely to qualify | Gold standard |
+| 5-10 minutes | 10x more likely | Still strong |
+| 10-30 minutes | 4x more likely | Acceptable for most |
+| 30 min - 1 hour | 2x more likely | Below best practice |
+| 1-24 hours | Baseline | Industry average |
+| 24+ hours | 60% lower than baseline | Lead is effectively cold |
+
+Source: Lead Connect, InsideSales.com
+
+### Implementing Speed-to-Lead
+
+1. **Instant notification** — Push notification + email to rep on MQL creation
+2. **Auto-task with timer** — Create task with 5-minute SLA countdown
+3. **Escalation chain:**
+   - 5 min: Original rep alerted
+   - 15 min: Backup rep alerted
+   - 30 min: Manager alerted
+   - 1 hour: Lead reassigned to next available rep
+4. **Measure and report** — Track actual response times weekly; recognize fast responders
+
+### Speed-to-Lead Automation
+
+**Trigger:** New MQL created
+**Actions:**
+1. Assign to rep via routing rules (instant)
+2. Send push notification + email to rep
+3. Create task: "Contact [Lead Name] — 5 min SLA"
+4. Start SLA timer
+5. If no activity logged in 15 min → alert backup rep
+6. If no activity in 30 min → alert manager
+7. If no activity in 60 min → reassign via round-robin
+
+### Measuring Speed-to-Lead
+
+Track these metrics weekly:
+- **Average time to first contact** (from MQL creation to first call/email)
+- **Median time to first contact** (less skewed by outliers)
+- **% of leads contacted within SLA** (target: 90%+)
+- **Contact rate by time of day** (identify coverage gaps)
+- **Conversion rate by response time** (prove the ROI of speed)
@@ -0,0 +1,247 @@
+# Lead Scoring Models
+
+Detailed scoring templates, example models by business type, and calibration guidance.
+
+## Explicit Scoring Template (Fit)
+
+### Company Attributes
+
+| Attribute | Criteria | Points |
+|-----------|----------|--------|
+| **Company size** | 1-10 employees | +5 |
+| | 11-50 employees | +10 |
+| | 51-200 employees | +15 |
+| | 201-1000 employees | +20 |
+| | 1000+ employees | +15 (unless enterprise-focused, then +25) |
+| **Industry** | Primary target industry | +20 |
+| | Secondary target industry | +10 |
+| | Non-target industry | 0 |
+| **Revenue** | Under $1M | +5 |
+| | $1M-$10M | +10 |
+| | $10M-$100M | +15 |
+| | $100M+ | +20 |
+| **Geography** | Primary market | +10 |
+| | Secondary market | +5 |
+| | Non-target market | 0 |
+
+### Contact Attributes
+
+| Attribute | Criteria | Points |
+|-----------|----------|--------|
+| **Job title** | C-suite (CEO, CTO, CMO) | +25 |
+| | VP level | +20 |
+| | Director level | +15 |
+| | Manager level | +10 |
+| | Individual contributor | +5 |
+| **Department** | Primary buying department | +15 |
+| | Adjacent department | +5 |
+| | Unrelated department | 0 |
+| **Seniority** | Decision maker | +20 |
+| | Influencer | +10 |
+| | End user | +5 |
+
+### Technology Attributes
+
+| Attribute | Criteria | Points |
+|-----------|----------|--------|
+| **Tech stack** | Uses complementary tool | +15 |
+| | Uses competitor | +10 (they understand the category) |
+| | Uses tool you replace | +20 |
+| **Tech maturity** | Modern stack (cloud, SaaS-forward) | +10 |
+| | Legacy stack | +5 |
+
+---
+
+## Implicit Scoring Template (Engagement)
+
+### High-Intent Signals
+
+| Signal | Points | Decay |
+|--------|--------|-------|
+| **Demo request** | +30 | None |
+| **Pricing page visit** | +20 | -5 per week |
+| **Free trial signup** | +25 | None |
+| **Contact sales form** | +30 | None |
+| **Case study page (2+)** | +15 | -5 per 2 weeks |
+| **Comparison page visit** | +15 | -5 per week |
+| **ROI calculator used** | +20 | -5 per 2 weeks |
+
+### Medium-Intent Signals
+
+| Signal | Points | Decay |
+|--------|--------|-------|
+| **Webinar registration** | +10 | -5 per month |
+| **Webinar attendance** | +15 | -5 per month |
+| **Whitepaper download** | +10 | -5 per month |
+| **Blog visit (3+ in a week)** | +10 | -5 per 2 weeks |
+| **Email click** | +5 per click | -2 per month |
+| **Email open (3+)** | +5 | -2 per month |
+| **Social media engagement** | +5 | -2 per month |
+
+### Low-Intent Signals
+
+| Signal | Points | Decay |
+|--------|--------|-------|
+| **Single blog visit** | +2 | -2 per month |
+| **Newsletter open** | +2 | -1 per month |
+| **Single email open** | +1 | -1 per month |
+| **Visited homepage only** | +1 | -1 per week |
+
+### Product Usage Signals (PLG)
+
+| Signal | Points | Decay |
+|--------|--------|-------|
+| **Created account** | +15 | None |
+| **Completed onboarding** | +20 | None |
+| **Used core feature (3+ times)** | +25 | -5 per month inactive |
+| **Invited team member** | +25 | None |
+| **Hit usage limit** | +20 | -10 per month |
+| **Exported data** | +10 | -5 per month |
+| **Connected integration** | +15 | None |
+| **Daily active for 5+ days** | +20 | -10 per 2 weeks inactive |
+
+---
+
+## Negative Scoring Signals
+
+| Signal | Points | Notes |
+|--------|--------|-------|
+| **Competitor email domain** | -50 | Auto-flag for review |
+| **Student email (.edu)** | -30 | May still be valid in some cases |
+| **Personal email (gmail, yahoo)** | -10 | Less relevant for B2B; adjust for SMB |
+| **Unsubscribe from emails** | -20 | Reduce engagement score |
+| **Bounce (hard)** | -50 | Remove from scoring |
+| **Spam complaint** | -100 | Remove from all sequences |
+| **Job title: Student/Intern** | -25 | Low buying authority |
+| **Job title: Consultant** | -10 | May be evaluating for client |
+| **No website visit in 90 days** | -15 | Score decay |
+| **Invalid phone number** | -10 | Data quality signal |
+| **Careers page visitor only** | -30 | Likely a job seeker |
+
+---
+
+## Example Scoring Models
+
+### Model 1: PLG SaaS (ACV $500-$5K)
+
+**Weight: 30% fit / 70% engagement (heavily favor product usage)**
+
+**Fit criteria:**
+- Company size 10-500: +15
+- Target industry: +10
+- Manager+ role: +10
+- Uses complementary tool: +10
+
+**Engagement criteria:**
+- Created free account: +15
+- Completed onboarding: +20
+- Used core feature 3+ times: +25
+- Invited team member: +25
+- Hit usage limit: +20
+- Pricing page visit: +15
+
+**Negative:**
+- Personal email: -10
+- No login in 14 days: -15
+- Competitor domain: -50
+
+**MQL threshold: 60 points**
+**Recalibration: Monthly** (fast feedback loop with high volume)
+
+---
+
+### Model 2: Enterprise Sales-Led (ACV $50K+)
+
+**Weight: 60% fit / 40% engagement (fit is critical at this ACV)**
+
+**Fit criteria:**
+- Company size 500+: +20
+- Revenue $50M+: +15
+- Target industry: +15
+- VP+ title: +20
+- Decision maker confirmed: +15
+- Uses competitor: +10
+
+**Engagement criteria:**
+- Demo request: +30
+- Multiple stakeholders engaged: +20
+- Attended executive webinar: +15
+- Downloaded ROI guide: +10
+- Visited pricing page 2+: +15
+
+**Negative:**
+- Company too small (<100): -30
+- Individual contributor only: -15
+- Competitor domain: -50
+
+**MQL threshold: 75 points**
+**Recalibration: Quarterly** (longer sales cycles, smaller sample size)
+
+---
+
+### Model 3: Mid-Market Hybrid (ACV $5K-$25K)
+
+**Weight: 50% fit / 50% engagement (balanced approach)**
+
+**Fit criteria:**
+- Company size 50-1000: +15
+- Target industry: +10
+- Manager-VP title: +15
+- Target geography: +10
+- Uses complementary tool: +10
+
+**Engagement criteria:**
+- Demo request or trial signup: +25
+- Pricing page visit: +15
+- Case study download: +10
+- Webinar attendance: +10
+- Email engagement (3+ clicks): +10
+- Blog visits (5+ pages): +10
+
+**Negative:**
+- Personal email: -10
+- No engagement in 30 days: -10
+- Competitor domain: -50
+- Student/intern title: -25
+
+**MQL threshold: 65 points**
+**Recalibration: Quarterly**
+
+---
+
+## Threshold Calibration
+
+### Setting the Initial Threshold
+
+1. **Pull closed-won data** from the last 6-12 months
+2. **Retroactively score** each deal using your new model
+3. **Find the natural breakpoint** — what score separated wins from losses?
+4. **Set threshold** just below where 80% of closed-won deals would have scored
+5. **Validate** against closed-lost — if many closed-lost score above threshold, tighten criteria
+
+### Calibration Cadence
+
+| Business Type | Recalibration Frequency | Why |
+|---------------|------------------------|-----|
+| PLG / High volume | Monthly | Fast feedback loop, lots of data |
+| Mid-market | Quarterly | Moderate cycle length |
+| Enterprise | Quarterly to semi-annually | Long cycles, small sample size |
+
+### Calibration Steps
+
+1. **Pull MQL-to-closed data** for the calibration period
+2. **Compare scored MQLs vs. actual outcomes:**
+   - High score + closed-won = correctly scored
+   - High score + closed-lost = possible false positive (tighten)
+   - Low score + closed-won = possible false negative (loosen)
+3. **Adjust weights** based on which attributes actually correlated with wins
+4. **Adjust threshold** if MQL volume is too high (raise) or too low (lower)
+5. **Document changes** and communicate to sales team
+
+### Warning Signs Your Model Needs Recalibration
+
+- MQL-to-SQL acceptance rate drops below 30%
+- Sales consistently rejects MQLs as "not ready"
+- High-scoring leads don't convert; low-scoring leads do
+- MQL volume spikes without corresponding revenue
+- New product/market changes since last calibration
@@ -0,0 +1,359 @@
+---
+name: sales-enablement
+description: "When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps.' Use this for any document or asset that helps a sales team close deals. For competitor comparison pages and battle cards, see competitor-alternatives. For marketing website copy, see copywriting. For cold outreach emails, see cold-email."
+metadata:
+  version: 1.1.0
+---
+
+# Sales Enablement
+
+You are an expert in B2B sales enablement. Your goal is to create sales collateral that reps actually use — decks, one-pagers, objection docs, demo scripts, and playbooks that help close deals.
+
+## 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. **Value Proposition & Differentiators**
+   - What do you sell and who is it for?
+   - What makes you different from the next best alternative?
+   - What outcomes can you prove?
+
+2. **Sales Motion**
+   - How do you sell? (self-serve, inside sales, field sales, hybrid)
+   - Average deal size and sales cycle length
+   - Key personas involved in the buying decision
+
+3. **Collateral Needs**
+   - What specific assets do you need?
+   - What stage of the funnel are they for?
+   - Who will use them? (AE, SDR, champion, prospect)
+
+4. **Current State**
+   - What materials exist today?
+   - What's working and what's not?
+   - What do reps ask for most?
+
+---
+
+## Core Principles
+
+### Sales Uses What Sales Trusts
+Involve reps in creation. Use their language, not marketing's. If reps rewrite your deck before sending it, you wrote the wrong deck. Test drafts with your top performers first.
+
+### Situation-Specific, Not Generic
+Tailor to persona, deal stage, and use case. A deck for a CTO should look different from one for a VP of Sales. A one-pager for post-meeting follow-up serves a different purpose than one for a trade show.
+
+### Scannable Over Comprehensive
+Reps need information in 3 seconds, not 30. Use bold headers, short bullets, and visual hierarchy. If a rep can't find the answer mid-call, the doc has failed.
+
+### Tie Back to Business Outcomes
+Every claim connects to revenue, efficiency, or risk reduction. Features mean nothing without the "so what." Replace "AI-powered analytics" with "cut reporting time by 80%."
+
+---
+
+## Sales Deck / Pitch Deck
+
+### 10-12 Slide Framework
+
+1. **Current World Problem** — The pain your buyer lives with today
+2. **Cost of the Problem** — What inaction costs (time, money, risk)
+3. **The Shift Happening** — Market or technology change creating urgency
+4. **Your Approach** — How you solve it differently
+5. **Product Walkthrough** — 3-4 key workflows, not a feature tour
+6. **Proof Points** — Metrics, logos, analyst recognition
+7. **Case Study** — One customer story told well
+8. **Implementation / Timeline** — How they get from here to live
+9. **ROI / Value** — Expected return and payback period
+10. **Pricing Overview** — Transparent, tiered if applicable
+11. **Next Steps / CTA** — Clear action with timeline
+
+### Deck Principles
+
+- **Story arc, not feature tour.** Every deck tells a story: the world has a problem, there's a better way, here's proof, here's how to get there.
+- **One idea per slide.** If you need two points, use two slides.
+- **Design for presenting, not reading.** Slides support the conversation — they don't replace it. Minimal text, strong visuals.
+
+### Customization by Buyer Type
+
+| Buyer | Emphasize | De-emphasize |
+|-------|-----------|--------------|
+| Technical buyer | Architecture, security, integrations, API | ROI calculations, business metrics |
+| Economic buyer | ROI, payback period, total cost, risk | Technical details, implementation specifics |
+| Champion | Internal selling points, quick wins, peer proof | Deep technical or financial detail |
+
+**For full slide-by-slide guidance**: See [references/deck-frameworks.md](references/deck-frameworks.md)
+
+---
+
+## One-Pagers / Leave-Behinds
+
+### When to Use
+
+- **Post-meeting recap** — Reinforce what you discussed, keep momentum
+- **Champion internal selling** — Arm your champion to sell for you
+- **Trade show handout** — Quick intro that drives follow-up
+
+### Structure
+
+1. **Problem statement** — The pain in one sentence
+2. **Your solution** — What you do and how
+3. **3 differentiators** — Why you vs. alternatives
+4. **Proof point** — One strong metric or customer quote
+5. **CTA** — Clear next step with contact info
+
+### Design Principles
+
+- One page, literally. Front only, or front and back maximum.
+- Scannable in 30 seconds. Bold headers, short bullets, whitespace.
+- Include your logo, website, and a specific contact (not info@).
+- Match your brand but keep it clean — this is a sales tool, not a brand piece.
+
+**For templates by use case**: See [references/one-pager-templates.md](references/one-pager-templates.md)
+
+---
+
+## Objection Handling Docs
+
+### Objection Categories
+
+| Category | Examples |
+|----------|----------|
+| Price | "Too expensive," "No budget this quarter," "Competitor is cheaper" |
+| Timing | "Not the right time," "Maybe next quarter," "Too busy to implement" |
+| Competition | "We already use X," "What makes you different?" |
+| Authority | "I need to check with my boss," "The committee decides" |
+| Status quo | "What we have works fine," "Not broken, don't fix it" |
+| Technical | "Does it integrate with X?," "Security concerns," "Can it scale?" |
+
+### Response Framework
+
+For each objection, document:
+
+1. **Objection statement** — Exactly how reps hear it
+2. **Why they say it** — The real concern behind the words
+3. **Response approach** — How to acknowledge and redirect
+4. **Proof point** — Specific evidence that addresses the concern
+5. **Follow-up question** — Keep the conversation moving forward
+
+### Two Formats
+
+- **Quick-reference table** for live calls — objection, one-line response, proof point. Fits on one screen.
+- **Detailed doc** for prep and training — full context, talk tracks, role-play scenarios.
+
+**For the full objection library**: See [references/objection-library.md](references/objection-library.md)
+
+---
+
+## ROI Calculators & Value Props
+
+### Calculator Design
+
+**Inputs** (current state metrics the prospect provides):
+- Time spent on manual processes
+- Current tool costs
+- Error rates or inefficiency metrics
+- Team size
+
+**Calculations** (your formula for value):
+- Time saved per week/month/year
+- Cost reduction (tools, headcount, errors)
+- Revenue impact (faster deals, higher conversion)
+
+**Outputs** (what the prospect sees):
+- Annual ROI percentage
+- Payback period in months
+- Total 3-year value
+
+### Value Prop by Persona
+
+| Persona | Cares About | Lead With |
+|---------|-------------|-----------|
+| CTO / VP Eng | Architecture, scale, security, team velocity | Technical superiority, integration depth |
+| VP Sales | Pipeline, quota attainment, rep productivity | Revenue impact, time savings per rep |
+| CFO | Total cost, payback period, risk | ROI, cost reduction, financial predictability |
+| End user | Ease of use, daily workflow, learning curve | Time saved, frustration eliminated |
+
+### Implementation Options
+
+- **Spreadsheet** — Fastest to build, easy to customize per deal. Works for inside sales.
+- **Web tool** — More polished, captures leads, scales better. Worth building if deal volume is high.
+- **Slide-based** — ROI story embedded in the deck. Good for executive presentations.
+
+---
+
+## Demo Scripts & Talk Tracks
+
+### Script Structure
+
+1. **Opening** (2 min) — Context setting, agenda, confirm goals for the call
+2. **Discovery recap** (3 min) — Summarize what you learned, confirm priorities
+3. **Solution walkthrough** (15-20 min) — 3-4 key workflows mapped to their pain
+4. **Interaction points** — Questions to ask during the demo, not just at the end
+5. **Close** (5 min) — Summarize value, propose next steps with timeline
+
+### Talk Track Types
+
+| Type | Duration | Focus |
+|------|----------|-------|
+| Discovery call | 30 min | Qualify, understand pain, map buying process |
+| First demo | 30-45 min | Show 3-4 workflows tied to their pain |
+| Technical deep-dive | 45-60 min | Architecture, security, integrations, API |
+| Executive overview | 20-30 min | Business outcomes, ROI, strategic alignment |
+
+### Key Principles
+
+- **Demo after discovery, not before.** If you don't know their pain, you're guessing which features matter.
+- **Customize to their use case.** Use their terminology, their data (if possible), their workflow.
+- **Leave time for questions.** A demo where the prospect doesn't talk is a demo that doesn't close.
+
+**For full script templates**: See [references/demo-scripts.md](references/demo-scripts.md)
+
+---
+
+## Case Study Briefs (Sales Format)
+
+### How Sales Case Studies Differ
+
+Marketing case studies tell a story. Sales case studies arm reps with fast-access proof. Keep them short, outcome-focused, and tagged for retrieval.
+
+### Structure
+
+1. **Customer profile** — Industry, company size, buyer role
+2. **Challenge** — What they were struggling with (2-3 sentences)
+3. **Solution** — What they implemented (1-2 sentences)
+4. **Results** — 3 specific metrics (before/after)
+5. **Pull quote** — One sentence from the customer
+6. **Tags** — Industry, use case, company size, persona
+
+### Organization
+
+Organize case studies so reps can find the right one instantly:
+- **By industry** — "Show me a case study for healthcare"
+- **By use case** — "Show me someone who used us for X"
+- **By company size** — "Show me an enterprise example"
+
+---
+
+## Proposal Templates
+
+### Structure
+
+1. **Executive summary** — Their challenge, your solution, expected outcome (1 page max)
+2. **Proposed solution** — What you'll deliver, mapped to their requirements
+3. **Implementation plan** — Timeline, milestones, responsibilities
+4. **Investment** — Pricing, payment terms, what's included
+5. **Next steps** — How to move forward, decision timeline
+
+### Customization Guidance
+
+- Mirror their language from discovery calls
+- Reference specific pain points they mentioned
+- Include only relevant case studies (same industry or use case)
+- Name the stakeholders you've spoken with
+
+### Common Mistakes
+
+- **Too long** — If it's over 10 pages, it won't get read. Aim for 5-7.
+- **Too generic** — Templated proposals signal low effort. Customize the exec summary at minimum.
+- **Burying the price** — Don't make them hunt for it. Be transparent and confident.
+
+---
+
+## Sales Playbooks
+
+### What Goes in a Playbook
+
+- **Buyer profile** — Who you're selling to, their goals and pains
+- **Qualification criteria** — BANT, MEDDIC, or your framework
+- **Discovery questions** — Organized by topic, not a script
+- **Objection handling** — Top 10 objections with responses
+- **Competitive positioning** — How you win against each competitor
+- **Demo flow** — Recommended sequence for each persona
+- **Email templates** — Follow-up, proposal, check-in, breakup
+
+### When to Build
+
+- **New product launch** — Reps need a single source of truth
+- **New market segment** — Different buyers need different approaches
+- **New hire ramp** — Playbooks cut ramp time significantly
+
+### Keeping It Living
+
+Playbooks die when they're not updated. Review quarterly, get input from top reps, and remove anything outdated. Assign an owner — if nobody owns it, it rots.
+
+---
+
+## Buyer Persona Cards
+
+### Card Structure
+
+| Field | Description |
+|-------|-------------|
+| Role / title | Common titles and reporting structure |
+| Goals | What success looks like for them |
+| Pains | What frustrates them daily |
+| Top objections | The 3-5 objections you'll hear from this role |
+| Evaluation criteria | How they judge solutions |
+| Buying process | Their role in the decision, who they influence |
+| Messaging angle | The one sentence that resonates most |
+
+### Persona Types
+
+- **Economic buyer** — Signs the check. Cares about ROI and risk.
+- **Technical buyer** — Evaluates the product. Cares about capabilities and integration.
+- **End user** — Uses it daily. Cares about ease and workflow fit.
+- **Champion** — Advocates internally. Needs ammunition to sell for you.
+- **Blocker** — Opposes the purchase. Understand their concern to neutralize it.
+
+---
+
+## Output Format
+
+Deliver the right format for each asset type:
+
+| Asset | Deliverable |
+|-------|-------------|
+| Sales deck | Slide-by-slide outline with headline, body copy, and speaker notes |
+| One-pager | Full copy with layout guidance (visual hierarchy, sections) |
+| Objection doc | Table format: objection, response, proof point, follow-up |
+| Demo script | Scene-by-scene with timing, talk track, and interaction points |
+| ROI calculator | Input fields, formulas, output display with sample data |
+| Playbook | Structured document with table of contents and sections |
+| Persona card | One-page card format per persona |
+| Proposal | Section-by-section copy with customization notes |
+
+---
+
+## Task-Specific Questions
+
+If context is missing, ask:
+
+1. What collateral do you need? (deck, one-pager, objection doc, etc.)
+2. Who will use it? (AE, SDR, champion, prospect)
+3. What sales stage is it for? (prospecting, discovery, demo, negotiation, close)
+4. Who is the target persona? (title, seniority, department)
+5. What are the top 3 objections you hear most?
+
+---
+
+## Tool Integrations
+
+For partner sales enablement, see the [tools registry](../../tools/REGISTRY.md):
+
+| Tool | What It Does | Guide |
+|------|-------------|-------|
+| **Introw** | Partner engagement tracking, deal registration, mutual action plans | [introw.md](../../tools/integrations/introw.md) |
+
+---
+
+## Related Skills
+
+- **competitor-alternatives**: For public-facing comparison and alternative pages
+- **copywriting**: For marketing website copy
+- **cold-email**: For outbound prospecting emails
+- **revops**: For lead lifecycle, scoring, routing, and pipeline management
+- **pricing-strategy**: For pricing decisions and packaging
+- **product-marketing-context**: For foundational positioning and messaging
@@ -0,0 +1,91 @@
+{
+  "skill_name": "sales-enablement",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Help me create a sales deck for our B2B SaaS product. We sell an employee engagement platform to HR directors at companies with 500-5000 employees. Our main differentiator is real-time pulse surveys with AI-powered insights.",
+      "expected_output": "Should check for product-marketing-context.md first. Should apply the 10-12 slide sales deck framework: Title, Problem/Stakes, Current Solutions Failing, Vision, Product/Solution, How It Works, Proof (case studies/metrics), Pricing, Why Now, and Next Steps. Should tailor the deck to the HR director audience and employee engagement space. Should incorporate the differentiator (real-time pulse surveys + AI insights). Should provide slide-by-slide content recommendations with speaker notes. Should recommend visual direction.",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Applies 10-12 slide framework",
+        "Includes Problem, Solution, Proof, Pricing, Next Steps slides",
+        "Tailors to HR director audience",
+        "Incorporates stated differentiator",
+        "Provides slide-by-slide content",
+        "Includes speaker notes or talking points"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "Our sales team keeps getting the same objections. The top ones are: 'we already use SurveyMonkey,' 'we don't have budget right now,' and 'our team is too small to need this.' Help me create an objection handling doc.",
+      "expected_output": "Should apply the objection handling framework with the response structure for each objection. Should categorize the objections (competitor/status quo, budget, need/timing). For each objection, should provide: acknowledge, reframe, evidence/proof, bridge to value, and follow-up question. Should provide 2-3 response variations per objection for different contexts. Should organize as a document sales reps can reference quickly during calls.",
+      "assertions": [
+        "Applies objection handling framework",
+        "Categorizes the three objections",
+        "Provides structured response for each (acknowledge, reframe, evidence, bridge)",
+        "Provides 2-3 response variations per objection",
+        "Organizes for quick reference during calls",
+        "Categorizes objections using the skill's framework (competitor, budget, need/timing)"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "i need a one-pager we can leave behind after sales meetings. something that summarizes our product and key benefits.",
+      "expected_output": "Should trigger on casual phrasing. Should apply the one-pager/leave-behind framework. Should include: headline with core value proposition, key benefits (3-5), social proof (customer logos, key metric), how it works (simplified), pricing summary or 'starting at' range, and clear next step CTA. Should recommend design principles for a one-pager: scannable, visual hierarchy, not text-heavy. Should note this should fit on one page (front, or front and back).",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Applies one-pager/leave-behind framework",
+        "Includes headline, benefits, social proof, how it works, CTA",
+        "Keeps to one page format",
+        "Recommends scannable design",
+        "Provides specific content for each section"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "Create a demo script for our analytics dashboard product. Typical demo is 30 minutes with a VP of Marketing.",
+      "expected_output": "Should apply the demo script/talk track framework with the 5-part structure. Should include: opening (rapport, agenda setting, discovery questions), problem validation (confirm their pain), solution walkthrough (show product addressing their pain), proof points (metrics, case studies during demo), and close (next steps, timeline). Should time-box each section for 30 minutes. Should include key questions to ask during discovery. Should note when to customize based on prospect's answers.",
+      "assertions": [
+        "Applies 5-part demo script structure",
+        "Includes opening with discovery questions",
+        "Includes problem validation",
+        "Includes solution walkthrough",
+        "Includes proof points",
+        "Includes close with next steps",
+        "Time-boxes for 30 minutes",
+        "Notes customization based on prospect responses"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "Help me build an ROI calculator we can use during sales calls. We need to show prospects how much money they'll save by switching to our product.",
+      "expected_output": "Should apply the ROI calculator framework. Should define inputs (what data to collect from the prospect: team size, current costs, time spent on manual processes), calculation methodology (how to compute savings), and output format (visual showing ROI timeline, payback period, annual savings). Should recommend keeping calculations transparent and conservative. Should suggest validating assumptions during the sales call. Should provide the calculator structure and formula logic.",
+      "assertions": [
+        "Applies ROI calculator framework",
+        "Defines required inputs",
+        "Provides calculation methodology",
+        "Recommends conservative assumptions",
+        "Includes ROI timeline and payback period",
+        "Suggests validating assumptions during calls",
+        "Provides calculator structure"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "We need a public comparison page showing how we stack up against Zendesk and Intercom.",
+      "expected_output": "Should recognize this is a public-facing competitor comparison page, not internal sales collateral. Should defer to or cross-reference the competitor-alternatives skill, which handles public comparison and alternatives pages. Sales-enablement covers internal materials (battle cards, objection handling) while competitor-alternatives handles SEO-focused public comparison content.",
+      "assertions": [
+        "Recognizes this as a public comparison page",
+        "References or defers to competitor-alternatives skill",
+        "Explains the distinction between internal and public collateral",
+        "Does not attempt public SEO comparison page using sales enablement patterns"
+      ],
+      "files": []
+    }
+  ]
+}
@@ -0,0 +1,263 @@
+# Sales Deck Frameworks
+
+Detailed slide-by-slide guidance for building sales decks that tell a story and close deals.
+
+## The Storytelling Arc
+
+Every great deck follows a narrative structure: **Situation → Complication → Resolution.**
+
+- **Situation** (Slides 1-3): The world your buyer lives in. Establish shared understanding.
+- **Complication** (Slides 2-3): Why the status quo is no longer sustainable. Create urgency.
+- **Resolution** (Slides 4-11): Your approach, proof, and path forward.
+
+The goal is not to present features. The goal is to make the buyer feel understood, then show them a better way.
+
+---
+
+## Slide-by-Slide Template
+
+### Slide 1: Current World Problem
+
+**What to include:**
+- The challenge your buyer faces daily
+- A stat or data point that quantifies the problem
+- Visual: simple graphic or striking number
+
+**What to avoid:**
+- Starting with your company or product
+- Generic industry trends that don't connect to pain
+- More than one core problem
+
+**Copy prompt:** "What is the one problem that, if you could describe it perfectly, would make your buyer say 'that's exactly my situation'?"
+
+---
+
+### Slide 2: Cost of the Problem
+
+**What to include:**
+- Financial impact (revenue lost, costs incurred)
+- Time impact (hours wasted, delays)
+- Risk impact (what happens if they do nothing)
+- Specific numbers wherever possible
+
+**What to avoid:**
+- Vague claims without data
+- Fear-mongering without substance
+- Too many metrics (pick 2-3 that hit hardest)
+
+**Copy prompt:** "If your buyer does nothing for the next 12 months, what does it cost them?"
+
+---
+
+### Slide 3: The Shift Happening
+
+**What to include:**
+- Market trend or technology change creating a new opportunity
+- Why "the old way" no longer works
+- Why now is the right time to act
+
+**What to avoid:**
+- Hype-driven trends without substance
+- Making it about your product yet
+- Overly technical explanations
+
+**Copy prompt:** "What has changed in the market that makes the old approach unsustainable?"
+
+---
+
+### Slide 4: Your Approach
+
+**What to include:**
+- Your philosophy or unique point of view
+- How your approach differs from conventional solutions
+- The "aha" insight that led to your product
+
+**What to avoid:**
+- Feature lists (too early)
+- Jargon or acronyms
+- Claiming to be "the only" or "the first" unless provably true
+
+**Copy prompt:** "What do you believe about solving this problem that most people get wrong?"
+
+---
+
+### Slide 5: Product Walkthrough
+
+**What to include:**
+- 3-4 key workflows that map to the pain from Slide 1
+- Screenshots or product visuals
+- Brief description of what each workflow accomplishes
+
+**What to avoid:**
+- Showing every feature
+- Dense UI screenshots without callouts
+- Talking about technology instead of outcomes
+
+**Copy prompt:** "Walk through 3 things the buyer would do in your product in their first week."
+
+---
+
+### Slide 6: Proof Points
+
+**What to include:**
+- Customer logos (aim for recognizable names in their industry)
+- Key metrics: "X% improvement," "Y hours saved," "Z% increase"
+- Analyst recognition, awards, or certifications if relevant
+
+**What to avoid:**
+- Unsubstantiated claims
+- Too many logos without context
+- Vanity metrics that don't relate to the buyer's pain
+
+**Copy prompt:** "What are 3 numbers that prove your product works?"
+
+---
+
+### Slide 7: Case Study
+
+**What to include:**
+- One customer story told well: challenge, solution, results
+- Specific metrics (before and after)
+- Customer quote if available
+- Choose a customer similar to the prospect
+
+**What to avoid:**
+- Multiple case studies crammed into one slide
+- Generic outcomes without specifics
+- Customers from irrelevant industries
+
+**Copy prompt:** "Tell the story of one customer who went from struggling to succeeding with your product."
+
+---
+
+### Slide 8: Implementation / Timeline
+
+**What to include:**
+- Clear phases with timeline (e.g., Week 1: Setup, Week 2-3: Integration, Week 4: Live)
+- What's required from their side vs. yours
+- Support resources available
+
+**What to avoid:**
+- Overcomplicating the process
+- Hiding time requirements
+- Skipping the "what do I need to do?" question
+
+**Copy prompt:** "How does a customer get from signing to live? What does each week look like?"
+
+---
+
+### Slide 9: ROI / Value
+
+**What to include:**
+- Expected return based on their inputs or industry benchmarks
+- Payback period
+- Total value over 1-3 years
+- Comparison to cost of inaction
+
+**What to avoid:**
+- Unrealistic projections
+- ROI without showing your math
+- Generic numbers not tied to their situation
+
+**Copy prompt:** "If they buy today, what does the next 12 months look like in dollars and hours?"
+
+---
+
+### Slide 10: Pricing Overview
+
+**What to include:**
+- Pricing tiers or structure
+- What's included at each level
+- Recommended plan for their situation
+
+**What to avoid:**
+- Burying the price or being cagey
+- Too many options (3 tiers max)
+- Surprising them with hidden costs
+
+**Copy prompt:** "What does it cost, what do they get, and which plan is right for them?"
+
+---
+
+### Slide 11: Next Steps / CTA
+
+**What to include:**
+- Specific next action with timeline ("Start a pilot next week")
+- What happens after they say yes
+- Your contact information
+
+**What to avoid:**
+- Vague CTAs ("Let's stay in touch")
+- Multiple competing next steps
+- Ending without energy
+
+**Copy prompt:** "What is the one thing you want them to do after this meeting?"
+
+---
+
+## Persona Customization Guide
+
+### Technical Buyer Deck
+
+**Add:**
+- Architecture diagram slide after Product Walkthrough
+- Security and compliance details
+- Integration ecosystem and API capabilities
+- Technical implementation requirements
+
+**Remove or minimize:**
+- ROI calculations (they care about capability, not cost)
+- High-level market trends (they want specifics)
+
+**Adjust tone:** Precise, no fluff, respect their expertise. Avoid marketing superlatives.
+
+### Economic Buyer Deck
+
+**Add:**
+- Detailed ROI slide with calculations shown
+- Total cost of ownership comparison
+- Risk mitigation and compliance
+- Executive summary slide up front
+
+**Remove or minimize:**
+- Technical details and architecture
+- Feature-level walkthroughs
+- Implementation specifics (they'll delegate)
+
+**Adjust tone:** Business-focused, outcome-driven. Speak in dollars and percentages.
+
+### Champion Deck
+
+**Add:**
+- "Internal selling" slide — key points for them to present to their team
+- Quick-win slide — what success looks like in 30 days
+- Peer proof — companies like theirs who succeeded
+- Objection pre-handling — common pushback they'll face internally
+
+**Remove or minimize:**
+- Deep technical or financial detail
+- Anything that requires context they can't relay
+
+**Adjust tone:** Empowering, equipping. Make them look smart to their boss.
+
+---
+
+## Anti-Patterns
+
+### The Feature Dump
+Every slide is a feature with a screenshot. No story, no "so what," no connection to the buyer's world. Reps click through it; prospects tune out.
+
+### The Wall of Text
+Slides with 200+ words. Nobody reads them during a presentation. If the slide requires reading, it belongs in a leave-behind.
+
+### The Missing Story Arc
+Slides exist in isolation — no narrative flow from problem to solution to proof. The deck feels like a brochure, not a conversation.
+
+### The Generic Screenshot
+Product screenshots without callouts, annotations, or context. The prospect can't tell what they're looking at or why it matters.
+
+### The Premature Demo
+Jumping to product features before establishing the problem. The buyer has no frame of reference for why your features matter.
+
+### The Kitchen Sink
+Trying to address every persona, every use case, every feature in one deck. The result is a 40-slide monster that nobody wants to sit through.
@@ -0,0 +1,355 @@
+# Demo Script Templates
+
+Scene-by-scene templates for different call types, with timing, talk tracks, and interaction guidance.
+
+## Discovery Call Script
+
+**Duration:** 30 minutes
+**Goal:** Qualify the opportunity, understand pain, map the buying process.
+
+### Scene 1: Opening (3 min)
+
+**Talk track:**
+> "Thanks for taking the time, [Name]. I've done some research on [Company] but I'd love to hear from you directly. My goal for today is to understand what you're working on and see if there's a fit — and if there's not, I'll tell you that too. Sound good?"
+
+**What to establish:**
+- Set the agenda and time expectation
+- Position yourself as a peer, not a pitch person
+- Get permission to ask questions
+
+---
+
+### Scene 2: Situation Questions (7 min)
+
+**Questions to ask:**
+- "Can you walk me through how your team handles [relevant process] today?"
+- "What tools are you currently using for this?"
+- "How many people are involved in this workflow?"
+- "How long has this been in place?"
+
+**What you're listening for:**
+- Current process and tools
+- Team size and structure
+- How established (and how entrenched) the current approach is
+
+---
+
+### Scene 3: Pain Identification (10 min)
+
+**Questions to ask:**
+- "What's the biggest challenge with that process today?"
+- "When that breaks down, what happens?"
+- "How much time does your team spend on [specific task] per week?"
+- "What have you tried to fix this?"
+- "If you could wave a magic wand, what would change?"
+
+**What you're listening for:**
+- Specific, quantifiable pain points
+- Emotional frustration (not just logical problems)
+- Failed attempts to solve this (shows urgency)
+- The "magic wand" answer reveals their ideal state
+
+**Interaction tip:** Take notes visibly. Repeat back what you hear: "So if I understand correctly, the biggest issue is [X], which costs you about [Y] per month. Is that right?"
+
+---
+
+### Scene 4: Impact & Priority (5 min)
+
+**Questions to ask:**
+- "Where does solving this sit on your priority list this quarter?"
+- "What happens if you don't solve this in the next 6 months?"
+- "Who else is affected by this problem?"
+- "Is there budget allocated for solving this?"
+
+**What you're listening for:**
+- Priority level (nice-to-have vs. must-solve)
+- Urgency and consequences of inaction
+- Organizational breadth of the problem
+- Budget signals
+
+---
+
+### Scene 5: Buying Process (3 min)
+
+**Questions to ask:**
+- "If you decided this was the right solution, what does the evaluation process look like?"
+- "Who else would be involved in the decision?"
+- "Have you evaluated solutions for this before?"
+- "What's your timeline for making a decision?"
+
+**What you're listening for:**
+- Decision-making process and stakeholders
+- Past evaluation experience (and why they didn't buy)
+- Timeline for decision
+
+---
+
+### Scene 6: Close (2 min)
+
+**Talk track:**
+> "Based on what you've shared, I think there's a strong fit — specifically around [pain point 1] and [pain point 2]. What I'd suggest as a next step is a 30-minute demo where I can show you exactly how we'd address those. I'll customize it to your workflow. Does [specific date/time] work?"
+
+**What to do:**
+- Summarize the 2-3 key pain points
+- Propose a specific next step with a date
+- Send a calendar invite before you hang up
+
+---
+
+## First Demo Script
+
+**Duration:** 30-45 minutes
+**Goal:** Show how your product solves their specific pain. Advance to evaluation/pilot.
+
+### Scene 1: Opening & Recap (5 min)
+
+**Talk track:**
+> "Last time we spoke, you mentioned [pain point 1], [pain point 2], and [goal]. I've put together a demo focused on those three areas. If I've missed anything, flag it and we'll adjust. Sound good?"
+
+**What to do:**
+- Recap discovery findings to show you listened
+- Confirm priorities haven't changed
+- Set expectation for what they'll see
+
+---
+
+### Scene 2: Workflow 1 — Primary Pain Point (10 min)
+
+**Structure:**
+1. Restate the pain: "You mentioned [specific problem]..."
+2. Show the solution: Walk through the workflow step by step
+3. Highlight the outcome: "This means [specific benefit]..."
+
+**Interaction point (at the 5-min mark):**
+> "How does this compare to how you're handling it today?"
+
+**What to avoid:**
+- Showing every feature of this section
+- Getting lost in settings or configuration
+- Talking for more than 3 minutes without asking a question
+
+---
+
+### Scene 3: Workflow 2 — Secondary Pain Point (8 min)
+
+**Structure:**
+Same as Workflow 1 — restate pain, show solution, highlight outcome.
+
+**Interaction point:**
+> "Is this the kind of visibility your team has been asking for?"
+
+---
+
+### Scene 4: Workflow 3 — Differentiator (7 min)
+
+**Structure:**
+Show something they can't do today and can't get from competitors.
+
+**Talk track:**
+> "This is where we're really different from [competitor/status quo]. [Explain the unique capability]. For example, [Customer] uses this to [specific outcome]."
+
+**Interaction point:**
+> "How would your team use this?"
+
+---
+
+### Scene 5: Proof Point (3 min)
+
+**Talk track:**
+> "Let me share a quick example. [Customer similar to them] was in a similar situation — [brief challenge]. After implementing, they saw [specific metrics]. Their [role] said [quote]."
+
+**What to do:**
+- Choose a case study that matches their industry, size, or use case
+- Keep it brief — this is reinforcement, not a presentation
+
+---
+
+### Scene 6: Close (5 min)
+
+**Talk track:**
+> "Based on what we've covered, here's what I'd recommend as next steps: [specific next step]. This typically takes [timeline]. Who else on your team should be involved? I can set up a [follow-up meeting type] for [date]."
+
+**What to do:**
+- Propose a specific next step (not "let me know")
+- Identify additional stakeholders to involve
+- Set a follow-up date before ending the call
+- Send recap email within 2 hours
+
+---
+
+## Technical Deep-Dive Script
+
+**Duration:** 45-60 minutes
+**Goal:** Satisfy technical evaluation criteria. Address architecture, security, and integration concerns.
+
+### Scene 1: Opening (3 min)
+
+**Talk track:**
+> "I know your goal today is to understand the technical details — architecture, security, integrations, and how this fits your stack. I'll walk through each area and leave plenty of time for questions. What's your top priority for this session?"
+
+**Attendees:** Typically includes their technical evaluator (engineer, architect, IT lead) plus your SE or solutions engineer.
+
+---
+
+### Scene 2: Architecture Overview (10 min)
+
+**Cover:**
+- High-level architecture diagram
+- Infrastructure and hosting (cloud provider, regions)
+- Data flow and storage
+- Scalability approach
+- Uptime SLA and reliability track record
+
+**Interaction point:**
+> "How does this compare to your current infrastructure requirements?"
+
+---
+
+### Scene 3: Security & Compliance (10 min)
+
+**Cover:**
+- Certifications (SOC 2, ISO 27001, HIPAA, etc.)
+- Data encryption (at rest, in transit)
+- Access controls and authentication (SSO, RBAC)
+- Audit logging
+- Data residency and privacy (GDPR, CCPA)
+- Penetration testing cadence
+
+**Interaction point:**
+> "What are your must-have security requirements? I want to make sure we address them specifically."
+
+---
+
+### Scene 4: Integrations & API (15 min)
+
+**Cover:**
+- Native integrations relevant to their stack
+- API capabilities (REST, GraphQL, webhooks)
+- Authentication methods
+- Rate limits and data sync frequency
+- Live demo of relevant integration
+
+**Interaction point:**
+> "Walk me through your current stack — I want to map out exactly how we'd fit in."
+
+---
+
+### Scene 5: Implementation & Migration (5 min)
+
+**Cover:**
+- Implementation timeline and phases
+- Data migration process
+- Configuration requirements
+- Training and onboarding
+- Ongoing support model
+
+**Interaction point:**
+> "What does your team's capacity look like for implementation? That helps me scope the right timeline."
+
+---
+
+### Scene 6: Q&A and Close (10 min)
+
+**Talk track:**
+> "What questions do I need to answer for you to feel confident about the technical fit?"
+
+**What to do:**
+- Answer directly — if you don't know, say so and follow up
+- Document all questions for follow-up
+- Propose next step (security review, proof of concept, pilot)
+- Send technical documentation summary within 24 hours
+
+---
+
+## Executive Overview Script
+
+**Duration:** 20-30 minutes
+**Goal:** Get executive buy-in on the business case. Advance to budget approval or decision.
+
+### Scene 1: Opening (2 min)
+
+**Talk track:**
+> "Thanks for your time, [Name]. [Champion] has been evaluating [your product] and the results look strong. I'll keep this focused on the business impact and what a partnership looks like. I know your time is valuable so I'll aim to leave 10 minutes for questions."
+
+**What to do:**
+- Be concise — executives punish rambling
+- Reference the champion and work done so far
+- Set a clear agenda
+
+---
+
+### Scene 2: The Problem & Cost (5 min)
+
+**Talk track:**
+> "Based on what [Champion] shared, your team is spending [X hours/$ amount] on [problem]. That's [annual cost]. It's also creating [secondary impact: risk, delays, churn]. This isn't unique to you — it's an industry-wide challenge, and the companies solving it are seeing [outcome]."
+
+**What to do:**
+- Use their numbers, not generic benchmarks
+- Connect to metrics they care about (revenue, cost, risk)
+- Keep it to 2-3 key points
+
+---
+
+### Scene 3: The Solution & Differentiation (5 min)
+
+**Talk track:**
+> "Here's what we do differently. [One-sentence explanation]. For your team specifically, this means [specific benefit 1] and [specific benefit 2]. [Champion]'s team has already seen [early result or reaction from evaluation]."
+
+**What to do:**
+- High-level, not feature-level
+- Tie to their strategic priorities
+- Reference the champion's evaluation
+
+---
+
+### Scene 4: ROI & Business Case (5 min)
+
+**Talk track:**
+> "Here's the business case. Based on your team's numbers: [walk through ROI calculation]. Expected payback period is [X months]. Over 3 years, the total value is [$ amount]. [Customer similar to them] saw [specific result] within [timeframe]."
+
+**What to do:**
+- Show the math, not just the conclusion
+- Use conservative estimates (executives discount inflated numbers)
+- One strong case study, not three weak ones
+
+---
+
+### Scene 5: Q&A and Decision (5-10 min)
+
+**Talk track:**
+> "What questions do you have? And — assuming the business case holds up, what does the decision process look like from here?"
+
+**What to do:**
+- Listen more than talk
+- Answer concisely
+- Get a clear next step and timeline
+- Thank the champion in front of the executive
+
+---
+
+## Interaction Point Guidance
+
+### When to Ask Questions During Demos
+
+- **After showing each workflow** — "How does this compare to your current process?"
+- **When you see a reaction** — "I noticed you reacted to that — what are you thinking?"
+- **Before moving to the next section** — "Any questions on this before we move on?"
+- **When showing a differentiator** — "How would your team use this?"
+- **At the midpoint** — "Are we covering the right things, or should we adjust?"
+
+### Questions NOT to Ask During Demos
+
+- "Does that make sense?" (patronizing)
+- "Are you still with me?" (implies they're lost)
+- "Isn't that cool?" (salesy)
+- Rhetorical questions that don't invite real dialogue
+
+### How to Handle "Can You Show Me X?"
+
+When a prospect asks to see something during the demo:
+
+1. **If it's quick** — show it now, then return to your flow
+2. **If it's a tangent** — "Great question. Let me note that and show you after the main flow so we stay on track."
+3. **If it's not possible** — "We don't do that today. Here's how customers handle it: [alternative]."
+
+Never say "I'll get back to you" without writing it down and following up within 24 hours.
@@ -0,0 +1,270 @@
+# Objection Library
+
+Common B2B SaaS objections with response frameworks. Organized by category for quick reference.
+
+## Quick-Reference Table
+
+For live calls. Find the objection, scan the response, reference the proof.
+
+| Objection | Response (1-line) | Proof Point |
+|-----------|--------------------|-------------|
+| "Too expensive" | "Compared to what? Let's look at what the problem costs you today." | ROI case study showing payback in X months |
+| "No budget" | "When budget opens up, what would need to be true for this to be a priority?" | Customer who started with a pilot to prove value |
+| "Competitor is cheaper" | "They are — here's what you give up at that price point." | Feature comparison + customer who switched |
+| "Not the right time" | "What changes next quarter that makes it better timing?" | Cost-of-delay calculation |
+| "Maybe next quarter" | "Happy to reconnect. What would a pilot look like before then?" | Customer who started small and expanded |
+| "We use X already" | "How's that working for [specific pain area]?" | Customer who switched from X |
+| "What makes you different?" | "For teams like yours, the biggest difference is [specific differentiator]." | Side-by-side comparison for their use case |
+| "Need to check with my boss" | "Absolutely. What would help you make the case? I can send materials." | Champion one-pager, ROI calculator |
+| "The committee decides" | "Who's on the committee and what does each person care about?" | Multi-persona case study |
+| "What we have works fine" | "It does work — the question is whether it's costing you more than it should." | Benchmark data showing efficiency gaps |
+| "Not broken, don't fix it" | "Agreed — this isn't about fixing, it's about the opportunity cost of the current approach." | Customer who didn't know what they were missing |
+| "Does it integrate with X?" | "Yes / Let me check and get you specifics by end of day." | Integration documentation, customer using same stack |
+| "Security concerns" | "Completely fair. Here's our security overview — happy to loop in our team." | SOC 2 report, security whitepaper |
+| "Can it scale?" | "We serve companies from [small] to [large]. Here's an example at your scale." | Case study at similar scale |
+| "We tried something like this before" | "What went wrong? Understanding that helps me show how we're different." | Customer with same failed experience who succeeded with you |
+
+---
+
+## Detailed Objection Responses
+
+### Price Objections
+
+#### "It's too expensive"
+
+**Why they say it:** May be genuine budget constraint, sticker shock, or negotiation tactic. Often means they don't yet see enough value to justify the cost.
+
+**Response approach:**
+1. Don't defend the price immediately. Ask "Compared to what?"
+2. Reframe from cost to investment — what does the problem cost them today?
+3. Walk through the ROI calculation together
+4. If budget is real, explore smaller starting points
+
+**Talk track:**
+> "I hear that. Let me ask — what's the cost of the problem we discussed? You mentioned your team spends [X hours] on [task] every week. At your team's loaded cost, that's roughly [$ amount] per year. Our solution runs [$ price] — so the question is whether eliminating that problem is worth the investment."
+
+**Proof point:** ROI calculator or case study showing payback period.
+
+**Follow-up question:** "If the ROI was clear, is this something you'd prioritize this quarter?"
+
+---
+
+#### "We don't have budget for this"
+
+**Why they say it:** Budget may genuinely be allocated. Or they haven't identified budget because priority isn't established.
+
+**Response approach:**
+1. Validate — budget constraints are real
+2. Understand timing — when does budget cycle reset?
+3. Explore alternatives — pilot, smaller scope, different budget line
+4. Help them build the business case to create budget
+
+**Talk track:**
+> "Totally understand. Two questions: When does your next budget cycle open? And — if we could show clear ROI with a limited pilot, is that something you could fund from a different line item? Sometimes teams fund this from the efficiency savings it creates."
+
+**Proof point:** Customer who started with a small pilot and expanded after proving ROI.
+
+**Follow-up question:** "Would it help if I put together an ROI brief you could share with your finance team?"
+
+---
+
+#### "Competitor X is cheaper"
+
+**Why they say it:** They're comparing prices, possibly without comparing capabilities. May be using competitor price as leverage.
+
+**Response approach:**
+1. Acknowledge the price difference — don't pretend it doesn't exist
+2. Shift to total cost of ownership and value delivered
+3. Highlight what they lose at the lower price point
+4. Share proof from customers who evaluated both
+
+**Talk track:**
+> "You're right, [Competitor] is less expensive. Here's what I've seen from teams who evaluated both: [Competitor] works well for [their strength]. Where it falls short is [specific gap]. Customers like [name] actually switched to us after starting with [Competitor] because [specific reason]. The question is whether [specific capability] is worth the difference for your team."
+
+**Proof point:** Customer who switched from the competitor, with specific reasons.
+
+**Follow-up question:** "What's most important to your team — the lowest price or the best fit for [their specific need]?"
+
+---
+
+### Timing Objections
+
+#### "Not the right time"
+
+**Why they say it:** Competing priorities, organizational change, genuine capacity constraint, or lack of urgency.
+
+**Response approach:**
+1. Understand what's competing for their attention
+2. Quantify the cost of waiting
+3. Explore low-commitment next steps that keep momentum
+4. Set a concrete follow-up date
+
+**Talk track:**
+> "I get it — timing matters. Can I ask what's taking priority right now? The reason I bring up timing is that every month of [problem], based on our earlier conversation, costs your team roughly [$ amount]. A 3-month delay is [$ amount]. What if we mapped out a start date that works with your calendar so you're not losing that value?"
+
+**Proof point:** Cost-of-delay calculation based on their specific numbers.
+
+**Follow-up question:** "What would need to change for this to move up in priority?"
+
+---
+
+#### "Maybe next quarter"
+
+**Why they say it:** Genuine scheduling, or a polite way of saying "not interested enough right now."
+
+**Response approach:**
+1. Accept the timeline gracefully
+2. Propose a small action now that maintains momentum
+3. Get a specific date for follow-up
+4. Send value in the meantime (content, benchmarks, insights)
+
+**Talk track:**
+> "Next quarter works. To make sure we hit the ground running, would it make sense to do [small next step] now? That way when Q[X] starts, you're not starting from scratch. I'll also send over [relevant content] in the meantime. Can we lock in [specific date] to reconnect?"
+
+**Proof point:** Customer who started the evaluation process early and was live by their target date.
+
+**Follow-up question:** "Is there anything I can send between now and then that would be helpful?"
+
+---
+
+### Competition Objections
+
+#### "We already use X"
+
+**Why they say it:** They have an existing solution and switching has real costs. May be satisfied, or may have frustrations they haven't voiced.
+
+**Response approach:**
+1. Don't trash the competitor — ask how it's working
+2. Probe for specific pain points with their current solution
+3. Position as complementary if possible, replacement if not
+4. Offer a side-by-side comparison or trial
+
+**Talk track:**
+> "How's that working for you? Specifically, when it comes to [area where you're stronger] — is that meeting your needs? The reason I ask is that most teams who come to us from [Competitor] tell us [specific pain point] was the tipping point. Not saying that's you, but worth exploring."
+
+**Proof point:** Customer who switched from that specific competitor.
+
+**Follow-up question:** "If you could change one thing about your current setup, what would it be?"
+
+---
+
+#### "What makes you different?"
+
+**Why they say it:** They're evaluating options and want a clear differentiator. Sometimes a genuine question, sometimes a test.
+
+**Response approach:**
+1. Don't list features — give the one thing that matters most for their situation
+2. Tie the differentiator to their specific pain
+3. Back it up with proof
+4. Offer to show, not just tell
+
+**Talk track:**
+> "For teams like yours — [their industry/size/use case] — the biggest difference is [specific differentiator]. That matters because [connection to their pain]. For example, [Customer] was evaluating us alongside [Competitor] and chose us because [specific reason]. Want me to walk you through how that works?"
+
+**Proof point:** Case study of a customer who chose you over alternatives.
+
+**Follow-up question:** "What's the most important criteria for your decision?"
+
+---
+
+### Authority Objections
+
+#### "I need to check with my boss"
+
+**Why they say it:** They may not be the decision maker, or they need internal buy-in to proceed. Could also be a stall tactic.
+
+**Response approach:**
+1. Support them, don't pressure them
+2. Arm them with materials to sell internally
+3. Offer to join a meeting with their boss
+4. Understand what their boss cares about
+
+**Talk track:**
+> "Absolutely — what would help you make the case? I can put together a one-pager that covers the ROI and addresses the concerns your boss is likely to have. Also happy to jump on a quick call with them if that would be helpful. What does your boss typically prioritize — cost savings, risk reduction, or efficiency?"
+
+**Proof point:** Champion enablement one-pager, ROI calculator.
+
+**Follow-up question:** "What questions do you think your boss will ask?"
+
+---
+
+#### "A committee decides this"
+
+**Why they say it:** Enterprise buying involves multiple stakeholders. Genuine process, not a brush-off.
+
+**Response approach:**
+1. Map the buying committee — who's involved and what each person cares about
+2. Provide persona-specific materials
+3. Offer to present to the committee
+4. Help your champion navigate the internal process
+
+**Talk track:**
+> "That makes sense. Can you walk me through who's on the committee and what each person cares about? I can tailor materials for each stakeholder so you're not doing all the heavy lifting. I've also got a deck designed for executive presentations if that would be useful."
+
+**Proof point:** Multi-stakeholder case study showing how different personas were addressed.
+
+**Follow-up question:** "Who on the committee is most likely to push back, and what would their concern be?"
+
+---
+
+### Status Quo Objections
+
+#### "What we have works fine"
+
+**Why they say it:** Inertia is real. The current solution may be adequate, and change has real costs.
+
+**Response approach:**
+1. Agree — don't argue with their experience
+2. Shift from "broken vs. fixed" to "good vs. great"
+3. Introduce the concept of opportunity cost
+4. Show what peers are achieving
+
+**Talk track:**
+> "It probably does work — and I wouldn't suggest changing something that's truly meeting your needs. The question I'd ask is: is 'works fine' the bar? Teams using [your product] are seeing [specific outcome]. If you're leaving [X% improvement] on the table, is that worth exploring?"
+
+**Proof point:** Benchmark data showing what's possible vs. status quo.
+
+**Follow-up question:** "If there were one area where your current approach could be better, what would it be?"
+
+---
+
+### Technical Objections
+
+#### "Does it integrate with X?"
+
+**Why they say it:** Integration is a real requirement. They need to know your product fits their stack.
+
+**Response approach:**
+1. Answer directly — yes, no, or "let me check"
+2. If yes, provide specifics (native, API, Zapier, etc.)
+3. If no, explain alternatives or workarounds
+4. Never bluff — they'll find out during evaluation
+
+**Talk track (if yes):**
+> "Yes, we integrate with [X] natively. It takes about [time] to set up. [Customer] runs the same stack and here's how they have it configured."
+
+**Talk track (if no):**
+> "We don't have a native integration with [X] today. Here's what customers typically do: [alternative]. We also have an open API that [description]. Would it help to get our technical team on a call to explore options?"
+
+**Proof point:** Customer using the same tech stack, integration documentation.
+
+**Follow-up question:** "What other tools are in your stack that we'd need to work with?"
+
+---
+
+#### "We have security concerns"
+
+**Why they say it:** Legitimate concern, especially in regulated industries or enterprise. Non-negotiable for many buyers.
+
+**Response approach:**
+1. Take it seriously — never dismiss security concerns
+2. Provide documentation proactively (SOC 2, security whitepaper)
+3. Offer to loop in your security team
+4. Ask about their specific requirements
+
+**Talk track:**
+> "That's exactly the right question to ask. Here's our security overview — we're [SOC 2 Type II / ISO 27001 / etc.] certified, and I can share our full security documentation. We also have a security team that's happy to do a review call with your infosec team. What are your specific requirements?"
+
+**Proof point:** Security certifications, compliance documentation, customers in regulated industries.
+
+**Follow-up question:** "Do you have a security questionnaire you'd like us to fill out?"
@@ -0,0 +1,208 @@
+# One-Pager Templates
+
+Templates for different one-pager use cases, with layout guidance and copy prompts.
+
+## Product Overview One-Pager
+
+The default one-pager. Introduces your product to someone who knows nothing about you.
+
+### Structure
+
+```
+[Logo]                                              [Tagline]
+
+HEADLINE: One sentence describing what you do and who it's for.
+
+THE PROBLEM
+2-3 sentences describing the pain your buyer faces.
+
+THE SOLUTION
+2-3 sentences describing how your product solves it.
+
+WHY [YOUR PRODUCT]
+• Differentiator 1 — One sentence explaining the benefit
+• Differentiator 2 — One sentence explaining the benefit
+• Differentiator 3 — One sentence explaining the benefit
+
+PROOF
+"Customer quote with specific result." — Name, Title, Company
+[Optional: 2-3 metric callouts: "X% improvement", "Y hours saved"]
+
+[CTA Button/Link]                    [Contact: name@company.com]
+```
+
+### Copy Prompts
+
+- Headline: "What do you do, in one sentence, that makes someone say 'tell me more'?"
+- Problem: "What is your buyer struggling with before they find you?"
+- Differentiators: "If you could only tell them 3 things, what would make them choose you?"
+
+---
+
+## Use-Case Specific One-Pager
+
+Tailored to a specific workflow, vertical, or problem. More targeted than the product overview.
+
+### Structure
+
+```
+[Logo]                                    [Use Case: e.g., "For Sales Teams"]
+
+HEADLINE: How [your product] helps [persona] [achieve outcome].
+
+THE CHALLENGE
+When [persona] needs to [task], they face [specific pain].
+This leads to [consequence]: [time wasted / money lost / risk].
+
+HOW IT WORKS
+1. [Step 1] — What happens and why it matters
+2. [Step 2] — What happens and why it matters
+3. [Step 3] — What happens and why it matters
+
+RESULTS
+• [Metric 1]: Before → After
+• [Metric 2]: Before → After
+• [Metric 3]: Before → After
+
+CUSTOMER SPOTLIGHT
+"Quote about this specific use case." — Name, Title, Company
+
+[CTA: "See it in action" or "Start a pilot"]       [Contact info]
+```
+
+### When to Use
+
+- Different buyer personas need different one-pagers
+- Industry-specific versions (healthcare, fintech, e-commerce)
+- Use-case versions (reporting, onboarding, security)
+
+---
+
+## Post-Meeting Leave-Behind
+
+Designed to reinforce a conversation that already happened. Summarizes what you discussed and proposes next steps.
+
+### Structure
+
+```
+[Logo]                                            [Date of Meeting]
+
+MEETING RECAP: [Company Name]
+
+WHAT WE DISCUSSED
+• [Pain point 1 they mentioned]
+• [Pain point 2 they mentioned]
+• [Goal they're trying to achieve]
+
+HOW [YOUR PRODUCT] HELPS
+• [Solution to pain 1] — [Specific capability or workflow]
+• [Solution to pain 2] — [Specific capability or workflow]
+• [How you help them reach their goal]
+
+RELEVANT PROOF
+"Quote from a similar customer." — Name, Title, Company
+[1-2 metrics from a similar customer]
+
+PROPOSED NEXT STEPS
+1. [Next step with date]
+2. [Follow-up action]
+3. [Decision timeline]
+
+[Your name]  |  [Your title]  |  [Email]  |  [Phone]
+```
+
+### Tips
+
+- Send within 24 hours of the meeting
+- Reference specific things they said (shows you listened)
+- Keep proposed next steps concrete and time-bound
+- This is the asset your champion forwards to their boss
+
+---
+
+## Champion Enablement One-Pager
+
+Designed specifically for your internal champion to share with their team and leadership. Written to make them look smart.
+
+### Structure
+
+```
+[Logo]
+
+WHY WE'RE EVALUATING [YOUR PRODUCT]
+
+THE SITUATION
+[2-3 sentences about the internal challenge, written as if the champion
+is explaining it to their team. Use "we" and "our" language.]
+
+WHAT [YOUR PRODUCT] DOES
+[1-2 sentences. Plain language, no jargon.]
+
+WHY THIS SOLUTION
+• [Reason 1] — How it solves our specific problem
+• [Reason 2] — How it compares to what we do today
+• [Reason 3] — How it compares to alternatives we evaluated
+
+EXPECTED IMPACT
+• [Metric]: Current state → Expected state
+• [Metric]: Current state → Expected state
+• [Time to value]: Live within [X weeks]
+
+WHO ELSE USES IT
+[2-3 recognizable company names in their industry]
+"Relevant customer quote." — Name, Title, Company
+
+NEXT STEPS
+• [What we're doing next]
+• [What we need from the team]
+• [Decision timeline]
+
+Questions? Talk to [Champion name] or [Your name at email].
+```
+
+### Why This Works
+
+- Written in the champion's voice, not yours
+- Answers the questions their boss will ask
+- Includes peer proof from companies they respect
+- Clear ask and timeline to drive internal momentum
+
+---
+
+## Layout Guidance
+
+### Visual Hierarchy
+
+1. **Headline** — Largest text, top of page, immediately communicates value
+2. **Section headers** — Bold, clear, act as scannable anchors
+3. **Body text** — Short sentences, bullet points preferred over paragraphs
+4. **Proof elements** — Metrics and quotes should visually stand out (larger font, color, or callout box)
+5. **CTA** — Prominent placement, bottom of page or bottom-right
+
+### Whitespace
+
+- Margins: at least 0.75" on all sides
+- Space between sections: enough to visually separate (don't cram)
+- If it feels crowded, cut content. Never shrink font below 9pt.
+
+### Font Sizing
+
+| Element | Suggested Size |
+|---------|---------------|
+| Headline | 18-24pt |
+| Section headers | 12-14pt bold |
+| Body text | 10-11pt |
+| Fine print / footer | 8-9pt |
+
+### Color
+
+- Use brand colors for headers and accents
+- Keep body text dark (black or near-black) on white
+- Limit accent colors to 1-2 for visual consistency
+- Use color to draw attention to metrics and CTAs
+
+### File Format
+
+- **PDF** for email attachments and leave-behinds
+- **Google Slides / PowerPoint** for editable versions reps can customize
+- Always include both — reps will customize, prospects want clean PDFs
@@ -1,8 +1,8 @@
 ---
 name: schema-markup
-description: When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," or "breadcrumb schema." For broader SEO issues, see seo-audit.
+description: When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," "breadcrumb schema," "Google rich results," "knowledge panel," "star ratings in search," or "add structured data." Use this whenever someone wants their pages to show enhanced results in Google. For broader SEO issues, see seo-audit. For AI search optimization, see ai-seo.
 metadata:
-  version: 1.0.0
+  version: 1.1.0
 ---

 # Schema Markup
@@ -12,7 +12,7 @@ You are an expert in structured data and schema markup. Your goal is to implemen
 ## 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 schema, understand:

@@ -176,3 +176,4 @@ You can combine multiple schema types on one page using `@graph`:
 - **seo-audit**: For overall SEO including schema review
 - **ai-seo**: For AI search optimization (schema helps AI understand content)
 - **programmatic-seo**: For templated schema at scale
+- **site-architecture**: For breadcrumb structure and navigation schema planning
@@ -0,0 +1,87 @@
+{
+  "skill_name": "schema-markup",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Add schema markup to our SaaS product's homepage. We're a project management tool called TaskFlow. We need Organization schema and any other relevant types.",
+      "expected_output": "Should check for product-marketing-context.md first. Should implement Organization schema in JSON-LD format with all required and recommended properties (name, url, logo, description, sameAs for social profiles). Should recommend additional schema types for a SaaS homepage: WebSite (with SearchAction if applicable), SoftwareApplication or Product. Should use @graph for multiple schema types on one page. Should provide the complete JSON-LD code ready to implement. Should recommend validation with Google's Rich Results Test and Schema.org validator.",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Implements Organization schema in JSON-LD",
+        "Includes required and recommended properties",
+        "Recommends additional relevant schema types",
+        "Uses @graph for multiple types",
+        "Provides complete JSON-LD code",
+        "Recommends validation tools"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "We have a FAQ page with 20 questions about our product. How do I add FAQ schema to get the rich results in Google?",
+      "expected_output": "Should implement FAQPage schema in JSON-LD format. Should show the correct structure: FAQPage as mainEntity containing Question items, each with acceptedAnswer. Should provide a complete code example with 2-3 sample questions. Should explain that FAQ schema can enable rich results showing questions/answers directly in search. Should note Google's guidelines for FAQ schema (factual answers, not promotional). Should recommend validation approach.",
+      "assertions": [
+        "Implements FAQPage schema in JSON-LD",
+        "Shows correct nested structure (FAQPage > Question > Answer)",
+        "Provides complete code example",
+        "Explains rich result benefits",
+        "Notes Google's FAQ schema guidelines",
+        "Recommends validation"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "add schema to our blog posts. we publish articles about marketing tips.",
+      "expected_output": "Should trigger on casual phrasing. Should implement Article (or BlogPosting) schema in JSON-LD. Should include required properties: headline, author (as Person with name and url), datePublished, dateModified, image, publisher (as Organization). Should recommend BreadcrumbList schema alongside the article schema. Should provide template code that can be reused across blog posts. Should address how to populate dynamic fields (date, author, headline) from the CMS.",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Implements Article or BlogPosting schema",
+        "Includes author, datePublished, image, publisher",
+        "Recommends BreadcrumbList alongside",
+        "Provides reusable template code",
+        "Addresses CMS integration for dynamic fields"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "We're an e-commerce site selling physical products. What schema markup do we need for our product pages?",
+      "expected_output": "Should implement Product schema with full properties: name, description, image, brand, sku, offers (with price, priceCurrency, availability, url). Should recommend AggregateRating if they have reviews, and Review schema for individual reviews. Should include BreadcrumbList for navigation. Should address common e-commerce schema types: Product, Offer, AggregateRating, Review. Should provide complete JSON-LD code. Should note that Product schema can enable rich results (price, availability, ratings in search).",
+      "assertions": [
+        "Implements Product schema with full properties",
+        "Includes Offer with price, availability",
+        "Recommends AggregateRating and Review schema",
+        "Includes BreadcrumbList",
+        "Provides complete JSON-LD code",
+        "Notes rich result benefits for products"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "We added schema markup to our site but it's not showing rich results in Google. Can you help debug?",
+      "expected_output": "Should provide a systematic debugging approach: first validate with Google Rich Results Test and Schema.org validator (syntax errors), then check for common issues (incorrect nesting, missing required properties, JSON-LD placement errors). Should explain that valid schema doesn't guarantee rich results — Google chooses when to show them. Should recommend checking Search Console for structured data reports and errors. Should address common debugging scenarios: schema not detected, warnings vs errors, eligible vs displayed.",
+      "assertions": [
+        "Recommends validation tools for debugging",
+        "Checks for common schema errors",
+        "Explains valid schema doesn't guarantee rich results",
+        "Recommends Search Console structured data reports",
+        "Addresses warnings vs errors distinction",
+        "Provides systematic debugging approach"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "Our organic search traffic dropped after a site redesign. Can you do a technical SEO audit?",
+      "expected_output": "Should recognize this is a technical SEO audit request, not a schema markup task. Should defer to or cross-reference the seo-audit skill, which handles comprehensive technical SEO audits. Schema markup is one component of SEO but doesn't address the broader technical issues (redirects, crawlability, indexation) that likely caused the traffic drop.",
+      "assertions": [
+        "Recognizes this as a technical SEO audit request",
+        "References or defers to seo-audit skill",
+        "Does not attempt full SEO audit using schema markup patterns"
+      ],
+      "files": []
+    }
+  ]
+}
@@ -1,8 +1,8 @@
 ---
 name: seo-audit
-description: When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," or "SEO health check." For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.
+description: When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup. For AI search optimization, see ai-seo.
 metadata:
-  version: 1.0.0
+  version: 1.1.0
 ---

 # SEO Audit
@@ -12,7 +12,7 @@ You are an expert in search engine optimization. Your goal is to identify SEO is
 ## 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 auditing, understand:

@@ -35,7 +35,7 @@ Before auditing, understand:

 ## Audit Framework

-### ⚠️ Important: Schema Markup Detection Limitation
+### Schema Markup Detection Limitation

 **`web_fetch` and `curl` cannot reliably detect structured data / schema markup.**

@@ -46,7 +46,7 @@ Many CMS plugins (AIOSEO, Yoast, RankMath) inject JSON-LD via client-side JavaSc
 2. **Google Rich Results Test** — https://search.google.com/test/rich-results
 3. **Screaming Frog export** — if the client provides one, use it (SF renders JavaScript)

-**Never report "no schema found" based solely on `web_fetch` or `curl`.** This has led to false audit findings in production.
+Reporting "no schema found" based solely on `web_fetch` or `curl` leads to false audit findings — these tools can't see JS-injected schema.

 ### Priority Order
 1. **Crawlability & Indexation** (can Google find and index it?)
@@ -164,7 +164,7 @@ Many CMS plugins (AIOSEO, Yoast, RankMath) inject JSON-LD via client-side JavaSc
 - Primary keyword near beginning
 - 50-60 characters (visible in SERP)
 - Compelling and click-worthy
- Brand name placement (end, usually)
+- No brand name placement (SERPs include brand name above title already)

 **Common issues:**
 - Duplicate titles
@@ -382,7 +382,7 @@ Same format as above
 - Mobile-Friendly Test
 - Schema Validator

-> **Note on schema detection:** `web_fetch` strips `<script>` tags (including JSON-LD) and cannot detect JS-injected schema. Always use the browser tool, Rich Results Test, or Screaming Frog for schema checks. See the warning at the top of the Audit Framework section.
+> **Note on schema detection:** `web_fetch` strips `<script>` tags (including JSON-LD) and cannot detect JS-injected schema. Use the browser tool, Rich Results Test, or Screaming Frog instead — they render JavaScript and capture dynamically-injected markup. See the Schema Markup Detection Limitation section above.

 **Paid Tools** (if available)
 - Screaming Frog
@@ -406,6 +406,7 @@ Same format as above

 - **ai-seo**: For optimizing content for AI search engines (AEO, GEO, LLMO)
 - **programmatic-seo**: For building SEO pages at scale
+- **site-architecture**: For page hierarchy, navigation design, and URL structure
 - **schema-markup**: For implementing structured data
 - **page-cro**: For optimizing pages for conversion (not just ranking)
 - **analytics-tracking**: For measuring SEO performance
@@ -0,0 +1,136 @@
+{
+  "skill_name": "seo-audit",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Can you do an SEO audit of our SaaS website? We're getting about 2,000 organic visits/month but feel like we should be getting more. URL: https://example.com",
+      "expected_output": "Should check for product-marketing-context.md first. Should ask clarifying questions about priority keywords, Search Console access, recent changes, and competitors. Should follow the audit framework priority order: Crawlability & Indexation, Technical Foundations, On-Page Optimization, Content Quality, Authority & Links. Should check robots.txt, XML sitemap, site architecture. Should evaluate title tags, meta descriptions, heading structure, and content optimization. Should NOT report on schema markup based solely on web_fetch (must note the detection limitation). Output should follow the Audit Report Structure: Executive Summary, Technical SEO Findings, On-Page SEO Findings, Content Findings, and Prioritized Action Plan.",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Asks clarifying questions about keywords, Search Console, recent changes",
+        "Follows audit priority order: crawlability first, then technical, on-page, content, authority",
+        "Checks robots.txt and XML sitemap",
+        "Evaluates title tags, meta descriptions, heading structure",
+        "Does NOT claim 'no schema found' based on web_fetch alone",
+        "Notes schema markup detection limitation",
+        "Output has Executive Summary",
+        "Output has Prioritized Action Plan",
+        "Each finding has Issue, Impact, Evidence, Fix, and Priority"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "Why am I not ranking for 'project management software'? We have a page targeting that keyword but it's stuck on page 3.",
+      "expected_output": "Should trigger on the casual 'why am I not ranking' phrasing. Should investigate both on-page and off-page factors. On-page: check title tag, H1, URL alignment with keyword; evaluate content depth vs competitors; check for keyword cannibalization. Technical: check indexation status, canonical tags, crawlability. Content quality: assess E-E-A-T signals, content depth, user engagement. Should provide specific, actionable fixes organized by priority. Should mention competitive analysis against current top-ranking pages.",
+      "assertions": [
+        "Triggers on casual 'why am I not ranking' phrasing",
+        "Checks title tag, H1, URL alignment with target keyword",
+        "Evaluates content depth vs competitors",
+        "Checks for keyword cannibalization",
+        "Checks indexation status and canonical tags",
+        "Assesses E-E-A-T signals",
+        "Mentions competitive analysis against top-ranking pages",
+        "Provides actionable fixes organized by priority"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "We just migrated from WordPress to Next.js and our organic traffic dropped 40% in the last month. Help!",
+      "expected_output": "Should treat this as an urgent migration diagnostic. Should immediately check: redirect mapping (301s from old URLs to new), canonical tags on new pages, robots.txt not blocking crawlers, XML sitemap submitted and updated, meta tags preserved. Should check for common migration issues: redirect chains/loops, soft 404s, lost internal links, changed URL structures without redirects. Should reference Search Console coverage report for indexation issues. Should provide a prioritized recovery plan with critical fixes first. Should mention monitoring timeline expectations (recovery can take weeks).",
+      "assertions": [
+        "Treats as urgent migration diagnostic",
+        "Checks redirect mapping (301s)",
+        "Checks canonical tags on new pages",
+        "Checks robots.txt not blocking crawlers",
+        "Checks XML sitemap updated and submitted",
+        "Checks for redirect chains or loops",
+        "Checks for soft 404s",
+        "References Search Console coverage report",
+        "Provides prioritized recovery plan",
+        "Mentions recovery timeline expectations"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "Review the technical SEO of our e-commerce site. We have about 50,000 products and use faceted navigation.",
+      "expected_output": "Should focus on e-commerce-specific technical issues: faceted navigation creating duplicate content, crawl budget management for large product catalog, parameterized URLs, product schema markup (with the caveat about detection limitations). Should check for thin category pages, duplicate product descriptions, out-of-stock page handling. Should address crawl budget issues: pagination, infinite scroll handling, session IDs in URLs. Should provide structured findings with Impact ratings and specific fixes.",
+      "assertions": [
+        "Addresses faceted navigation duplicate content",
+        "Addresses crawl budget for large catalog",
+        "Checks for parameterized URL issues",
+        "Mentions product schema with detection limitation caveat",
+        "Checks for thin category pages",
+        "Checks for duplicate product descriptions",
+        "Addresses out-of-stock page handling",
+        "Addresses pagination and infinite scroll",
+        "Findings include Impact ratings and specific fixes"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "Can you check our blog posts for on-page SEO issues? We publish 4 posts per week but traffic has been flat for 6 months.",
+      "expected_output": "Should apply the Content/Blog Sites framework: check for outdated content not refreshed, keyword cannibalization, missing topical clustering, poor internal linking, missing author pages. Should audit on-page elements: title tags, meta descriptions, heading structure, keyword targeting per post. Should assess E-E-A-T signals for blog content. Should check for content depth issues and whether posts answer search intent. Should recommend a content audit process and provide a prioritized action plan for the existing content library.",
+      "assertions": [
+        "Applies Content/Blog Sites framework",
+        "Checks for outdated content",
+        "Checks for keyword cannibalization",
+        "Checks for topical clustering",
+        "Checks for internal linking quality",
+        "Checks for author pages and E-E-A-T signals",
+        "Audits title tags, meta descriptions, heading structure",
+        "Assesses whether content answers search intent",
+        "Recommends content audit process",
+        "Provides prioritized action plan"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "I run a local plumbing business with 3 locations. My website barely shows up when people search for 'plumber near me' in our areas. What's wrong?",
+      "expected_output": "Should apply the Local Business site-type framework. Should check for: inconsistent NAP (Name, Address, Phone) across the site, missing local schema markup (with detection limitation caveat), Google Business Profile optimization, missing individual location pages for each of the 3 locations, and missing local content. Should also check standard technical and on-page factors. Should recommend local-specific fixes: location-specific pages with unique content, local schema on each, GBP optimization, citation consistency.",
+      "assertions": [
+        "Applies Local Business framework",
+        "Checks NAP consistency",
+        "Checks for local schema markup with detection caveat",
+        "Addresses Google Business Profile optimization",
+        "Recommends individual location pages for each location",
+        "Recommends local content strategy",
+        "Checks standard technical SEO factors too",
+        "Provides prioritized local SEO action plan"
+      ],
+      "files": []
+    },
+    {
+      "id": 7,
+      "prompt": "Our site loads really slowly, especially on mobile. Pages take 5-6 seconds to load. Is this hurting our SEO?",
+      "expected_output": "Should focus on Site Speed and Core Web Vitals. Should explain CWV thresholds: LCP < 2.5s, INP < 200ms, CLS < 0.1, and that 5-6s load time is well above acceptable. Should investigate speed factors: server response time (TTFB), image optimization, JavaScript execution, CSS delivery, caching headers, CDN usage, font loading. Should recommend specific tools: PageSpeed Insights, WebPageTest, Chrome DevTools, Search Console CWV report. Should explain that yes, page speed is a ranking factor and directly impacts SEO. Should provide prioritized fixes.",
+      "assertions": [
+        "Focuses on Core Web Vitals",
+        "Explains CWV thresholds (LCP, INP, CLS)",
+        "Identifies 5-6s as well above acceptable",
+        "Investigates specific speed factors",
+        "Recommends specific diagnostic tools",
+        "Confirms page speed impacts SEO rankings",
+        "Provides prioritized speed fixes",
+        "Addresses mobile-specific performance"
+      ],
+      "files": []
+    },
+    {
+      "id": 8,
+      "prompt": "I want to add FAQ schema to my product pages. Can you help me set that up?",
+      "expected_output": "Should recognize this is a schema markup implementation task, not an SEO audit. Should defer to or cross-reference the schema-markup skill, which specifically handles structured data implementation including FAQ schema. May briefly mention that FAQ schema can enable rich results, but should make clear that schema-markup is the right skill for implementation.",
+      "assertions": [
+        "Recognizes this as schema markup implementation",
+        "References or defers to schema-markup skill",
+        "Does not attempt a full SEO audit",
+        "May briefly mention FAQ schema benefits"
+      ],
+      "files": []
+    }
+  ]
+}
@@ -1,8 +1,8 @@
 ---
 name: signup-flow-cro
-description: When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions "signup conversions," "registration friction," "signup form optimization," "free trial signup," "reduce signup dropoff," or "account creation flow." For post-signup onboarding, see onboarding-cro. For lead capture forms (not account creation), see form-cro.
+description: When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions "signup conversions," "registration friction," "signup form optimization," "free trial signup," "reduce signup dropoff," "account creation flow," "people aren't signing up," "signup abandonment," "trial conversion rate," "nobody completes registration," "too many steps to sign up," or "simplify our signup." Use this whenever the user has a signup or registration flow that isn't performing. For post-signup onboarding, see onboarding-cro. For lead capture forms (not account creation), see form-cro.
 metadata:
-  version: 1.0.0
+  version: 1.1.0
 ---

 # Signup Flow CRO
@@ -12,7 +12,7 @@ You are an expert in optimizing signup and registration flows. Your goal is to r
 ## 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:

@@ -161,7 +161,7 @@ Every field reduces conversion. For each field, ask:

 ### Microcopy
 - Placeholder text: Use for examples, not labels
- Labels: Always visible (not just placeholders)
+- Labels: Keep visible (not just placeholders) — placeholders disappear when typing, leaving users unsure what they're filling in
 - Help text: Only when needed, placed close to field

 ---
@@ -0,0 +1,88 @@
+{
+  "skill_name": "signup-flow-cro",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Audit our signup flow. We have a 3-step process: Step 1 asks for email, password, and full name. Step 2 asks for company name, company size, role, and industry. Step 3 asks for use case and how they heard about us. Current completion rate is 45%.",
+      "expected_output": "Should check for product-marketing-context.md first. Should identify the flow type (likely B2B SaaS trial). Should apply the core principles: minimize required fields (which of these are genuinely needed before they can use the product?). Should evaluate each step: Step 1 is reasonable, Step 2 fields are mostly deferrable to progressive profiling, Step 3 is entirely deferrable. Should recommend cutting to Step 1 only or at most 2 steps. Should provide audit findings in structured format (Issue, Impact, Fix, Priority). Should include Quick Wins, High-Impact Changes, and Test Hypotheses.",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Identifies flow type",
+        "Applies minimize required fields principle",
+        "Evaluates each field for necessity",
+        "Recommends deferring most Step 2 and all Step 3 fields",
+        "Provides findings in structured format",
+        "Includes Quick Wins, High-Impact Changes, Test Hypotheses"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "Should we add Google and Microsoft SSO to our signup page? We're a B2B project management tool and currently only have email/password signup.",
+      "expected_output": "Should apply the social auth options guidance. For B2B, should recommend Google and Microsoft as the primary SSO options (matching the B2B recommendation). Should explain benefits: higher conversion (less friction), pre-verified email, faster onboarding. Should recommend placing SSO prominently (often higher conversion than email). Should address implementation considerations: clear visual separation from email signup, button copy ('Sign up with Google' not just Google icon), consider which option to emphasize based on audience.",
+      "assertions": [
+        "Applies social auth options guidance",
+        "Recommends Google and Microsoft for B2B",
+        "Explains conversion benefits of SSO",
+        "Recommends prominent placement",
+        "Addresses visual separation from email signup",
+        "Provides implementation recommendations"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "our signup form is just email and password but we still only get 35% of visitors to complete it. what else could be wrong?",
+      "expected_output": "Should trigger on casual phrasing. Should investigate beyond just form fields since the form is already minimal. Should apply trust and friction reduction guidance: is there a 'No credit card required' message? Privacy assurance? Testimonial near the form? Should check form-level issues: error handling, password requirements clarity, submit button copy. Should also look at pre-form factors: is the value proposition clear? Is the page optimized? (cross-reference page-cro). Should provide diagnostic checklist and recommendations.",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Investigates beyond form fields",
+        "Applies trust and friction reduction",
+        "Checks for 'No credit card required' messaging",
+        "Checks error handling and password UX",
+        "Considers pre-form factors (value prop, page CRO)",
+        "Provides diagnostic checklist"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "We require email verification before users can access the product. Is that hurting our conversion? Should we change it?",
+      "expected_output": "Should apply the verification flows guidance. Should explain that requiring verification before product access does create friction and likely reduces activation. Should recommend alternatives: delay verification until needed (let users explore first), magic link as alternative to password, let users start while verification is pending. Should discuss when email verification IS required (compliance, preventing abuse). Should provide specific recommendations for improving the verification experience if kept.",
+      "assertions": [
+        "Applies verification flows guidance",
+        "Explains verification friction impact",
+        "Recommends delaying verification",
+        "Suggests letting users explore while pending",
+        "Discusses when verification is required",
+        "Provides improvements if verification is kept"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "What experiments should we run on our signup page? We want to improve our trial signup rate.",
+      "expected_output": "Should apply the experiment ideas section. Should provide experiments across categories: form design experiments (layout, field count, SSO), copy and messaging experiments (headline, CTA text, trust elements), trial and commitment experiments (credit card required vs not, trial length), and post-submit experiments. Should prioritize experiments by likely impact. Should cross-reference ab-test-setup for proper experiment design.",
+      "assertions": [
+        "Applies experiment ideas section",
+        "Covers form design experiments",
+        "Covers copy and messaging experiments",
+        "Covers trial and commitment experiments",
+        "Prioritizes by likely impact",
+        "Cross-references ab-test-setup skill"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "Users sign up fine but then never activate. Only 20% complete onboarding. What do we do?",
+      "expected_output": "Should recognize this is a post-signup onboarding problem, not a signup flow problem. Should defer to or cross-reference the onboarding-cro skill, which handles post-signup activation and onboarding optimization. Signup-flow-cro covers getting users through the signup form, not what happens after.",
+      "assertions": [
+        "Recognizes this as post-signup onboarding, not signup flow",
+        "References or defers to onboarding-cro skill",
+        "Explains signup-flow-cro covers the signup form, not post-signup"
+      ],
+      "files": []
+    }
+  ]
+}
@@ -0,0 +1,357 @@
+---
+name: site-architecture
+description: When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," or "site navigation." Use this whenever someone is planning what pages a website should have and how they connect. NOT for XML sitemaps (that's technical SEO — see seo-audit). For SEO audits, see seo-audit. For structured data, see schema-markup.
+metadata:
+  version: 1.1.0
+---
+
+# Site Architecture
+
+You are an information architecture expert. Your goal is to help plan website structure — page hierarchy, navigation, URL patterns, and internal linking — so the site is intuitive for users and optimized for search engines.
+
+## 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 are the primary audiences?
+- What are the top 3 goals for the site? (conversions, SEO traffic, education, support)
+
+### 2. Current State
+- New site or restructuring an existing one?
+- If restructuring: what's broken? (high bounce, poor SEO, users can't find things)
+- Existing URLs that must be preserved (for redirects)?
+
+### 3. Site Type
+- SaaS marketing site
+- Content/blog site
+- E-commerce
+- Documentation
+- Hybrid (SaaS + content)
+- Small business / local
+
+### 4. Content Inventory
+- How many pages exist or are planned?
+- What are the most important pages? (by traffic, conversions, or business value)
+- Any planned sections or expansions?
+
+---
+
+## Site Types and Starting Points
+
+| Site Type | Typical Depth | Key Sections | URL Pattern |
+|-----------|--------------|--------------|-------------|
+| SaaS marketing | 2-3 levels | Home, Features, Pricing, Blog, Docs | `/features/name`, `/blog/slug` |
+| Content/blog | 2-3 levels | Home, Blog, Categories, About | `/blog/slug`, `/category/slug` |
+| E-commerce | 3-4 levels | Home, Categories, Products, Cart | `/category/subcategory/product` |
+| Documentation | 3-4 levels | Home, Guides, API Reference | `/docs/section/page` |
+| Hybrid SaaS+content | 3-4 levels | Home, Product, Blog, Resources, Docs | `/product/feature`, `/blog/slug` |
+| Small business | 1-2 levels | Home, Services, About, Contact | `/services/name` |
+
+**For full page hierarchy templates**: See [references/site-type-templates.md](references/site-type-templates.md)
+
+---
+
+## Page Hierarchy Design
+
+### The 3-Click Rule
+
+Users should reach any important page within 3 clicks from the homepage. This isn't absolute, but if critical pages are buried 4+ levels deep, something is wrong.
+
+### Flat vs Deep
+
+| Approach | Best For | Tradeoff |
+|----------|----------|----------|
+| Flat (2 levels) | Small sites, portfolios | Simple but doesn't scale |
+| Moderate (3 levels) | Most SaaS, content sites | Good balance of depth and findability |
+| Deep (4+ levels) | E-commerce, large docs | Scales but risks burying content |
+
+**Rule of thumb**: Go as flat as possible while keeping navigation clean. If a nav dropdown has 20+ items, add a level of hierarchy.
+
+### Hierarchy Levels
+
+| Level | What It Is | Example |
+|-------|-----------|---------|
+| L0 | Homepage | `/` |
+| L1 | Primary sections | `/features`, `/blog`, `/pricing` |
+| L2 | Section pages | `/features/analytics`, `/blog/seo-guide` |
+| L3+ | Detail pages | `/docs/api/authentication` |
+
+### ASCII Tree Format
+
+Use this format for page hierarchies:
+
+```
+Homepage (/)
+├── Features (/features)
+│   ├── Analytics (/features/analytics)
+│   ├── Automation (/features/automation)
+│   └── Integrations (/features/integrations)
+├── Pricing (/pricing)
+├── Blog (/blog)
+│   ├── [Category: SEO] (/blog/category/seo)
+│   └── [Category: CRO] (/blog/category/cro)
+├── Resources (/resources)
+│   ├── Case Studies (/resources/case-studies)
+│   └── Templates (/resources/templates)
+├── Docs (/docs)
+│   ├── Getting Started (/docs/getting-started)
+│   └── API Reference (/docs/api)
+├── About (/about)
+│   └── Careers (/about/careers)
+└── Contact (/contact)
+```
+
+**When to use ASCII vs Mermaid**:
+- ASCII: quick hierarchy drafts, text-only contexts, simple structures
+- Mermaid: visual presentations, complex relationships, showing nav zones or linking patterns
+
+---
+
+## Navigation Design
+
+### Navigation Types
+
+| Nav Type | Purpose | Placement |
+|----------|---------|-----------|
+| Header nav | Primary navigation, always visible | Top of every page |
+| Dropdown menus | Organize sub-pages under parent | Expands from header items |
+| Footer nav | Secondary links, legal, sitemap | Bottom of every page |
+| Sidebar nav | Section navigation (docs, blog) | Left side within a section |
+| Breadcrumbs | Show current location in hierarchy | Below header, above content |
+| Contextual links | Related content, next steps | Within page content |
+
+### Header Navigation Rules
+
+- **4-7 items max** in the primary nav (more causes decision paralysis)
+- **CTA button** goes rightmost (e.g., "Start Free Trial," "Get Started")
+- **Logo** links to homepage (left side)
+- **Order by priority**: most important/visited pages first
+- If you have a mega menu, limit to 3-4 columns
+
+### Footer Organization
+
+Group footer links into columns:
+- **Product**: Features, Pricing, Integrations, Changelog
+- **Resources**: Blog, Case Studies, Templates, Docs
+- **Company**: About, Careers, Contact, Press
+- **Legal**: Privacy, Terms, Security
+
+### Breadcrumb Format
+
+```
+Home > Features > Analytics
+Home > Blog > SEO Category > Post Title
+```
+
+Breadcrumbs should mirror the URL hierarchy. Every breadcrumb segment should be a clickable link except the current page.
+
+**For detailed navigation patterns**: See [references/navigation-patterns.md](references/navigation-patterns.md)
+
+---
+
+## URL Structure
+
+### Design Principles
+
+1. **Readable by humans** — `/features/analytics` not `/f/a123`
+2. **Hyphens, not underscores** — `/blog/seo-guide` not `/blog/seo_guide`
+3. **Reflect the hierarchy** — URL path should match site structure
+4. **Consistent trailing slash policy** — pick one (with or without) and enforce it
+5. **Lowercase always** — `/About` should redirect to `/about`
+6. **Short but descriptive** — `/blog/how-to-improve-landing-page-conversion-rates` is too long; `/blog/landing-page-conversions` is better
+
+### URL Patterns by Page Type
+
+| Page Type | Pattern | Example |
+|-----------|---------|---------|
+| Homepage | `/` | `example.com` |
+| Feature page | `/features/{name}` | `/features/analytics` |
+| Pricing | `/pricing` | `/pricing` |
+| Blog post | `/blog/{slug}` | `/blog/seo-guide` |
+| Blog category | `/blog/category/{slug}` | `/blog/category/seo` |
+| Case study | `/customers/{slug}` | `/customers/acme-corp` |
+| Documentation | `/docs/{section}/{page}` | `/docs/api/authentication` |
+| Legal | `/{page}` | `/privacy`, `/terms` |
+| Landing page | `/{slug}` or `/lp/{slug}` | `/free-trial`, `/lp/webinar` |
+| Comparison | `/compare/{competitor}` or `/vs/{competitor}` | `/compare/competitor-name` |
+| Integration | `/integrations/{name}` | `/integrations/slack` |
+| Template | `/templates/{slug}` | `/templates/marketing-plan` |
+
+### Common Mistakes
+
+- **Dates in blog URLs** — `/blog/2024/01/15/post-title` adds no value and makes URLs long. Use `/blog/post-title`.
+- **Over-nesting** — `/products/category/subcategory/item/detail` is too deep. Flatten where possible.
+- **Changing URLs without redirects** — Every old URL needs a 301 redirect to its new URL. Without them, you lose backlink equity and create broken pages for anyone with the old URL bookmarked or linked.
+- **IDs in URLs** — `/product/12345` is not human-readable. Use slugs.
+- **Query parameters for content** — `/blog?id=123` should be `/blog/post-title`.
+- **Inconsistent patterns** — Don't mix `/features/analytics` and `/product/automation`. Pick one parent.
+
+### Breadcrumb-URL Alignment
+
+The breadcrumb trail should mirror the URL path:
+
+| URL | Breadcrumb |
+|-----|-----------|
+| `/features/analytics` | Home > Features > Analytics |
+| `/blog/seo-guide` | Home > Blog > SEO Guide |
+| `/docs/api/auth` | Home > Docs > API > Authentication |
+
+---
+
+## Visual Sitemap Output (Mermaid)
+
+Use Mermaid `graph TD` for visual sitemaps. This makes hierarchy relationships clear and can annotate navigation zones.
+
+### Basic Hierarchy
+
+```mermaid
+graph TD
+    HOME[Homepage] --> FEAT[Features]
+    HOME --> PRICE[Pricing]
+    HOME --> BLOG[Blog]
+    HOME --> ABOUT[About]
+
+    FEAT --> F1[Analytics]
+    FEAT --> F2[Automation]
+    FEAT --> F3[Integrations]
+
+    BLOG --> B1[Post 1]
+    BLOG --> B2[Post 2]
+```
+
+### With Navigation Zones
+
+```mermaid
+graph TD
+    subgraph Header Nav
+        HOME[Homepage]
+        FEAT[Features]
+        PRICE[Pricing]
+        BLOG[Blog]
+        CTA[Get Started]
+    end
+
+    subgraph Footer Nav
+        ABOUT[About]
+        CAREERS[Careers]
+        CONTACT[Contact]
+        PRIVACY[Privacy]
+    end
+
+    HOME --> FEAT
+    HOME --> PRICE
+    HOME --> BLOG
+    HOME --> ABOUT
+
+    FEAT --> F1[Analytics]
+    FEAT --> F2[Automation]
+```
+
+**For more Mermaid templates**: See [references/mermaid-templates.md](references/mermaid-templates.md)
+
+---
+
+## Internal Linking Strategy
+
+### Link Types
+
+| Type | Purpose | Example |
+|------|---------|---------|
+| Navigational | Move between sections | Header, footer, sidebar links |
+| Contextual | Related content within text | "Learn more about [analytics](/features/analytics)" |
+| Hub-and-spoke | Connect cluster content to hub | Blog posts linking to pillar page |
+| Cross-section | Connect related pages across sections | Feature page linking to related case study |
+
+### Internal Linking Rules
+
+1. **No orphan pages** — every page must have at least one internal link pointing to it
+2. **Descriptive anchor text** — "our analytics features" not "click here"
+3. **5-10 internal links per 1000 words** of content (approximate guideline)
+4. **Link to important pages more often** — homepage, key feature pages, pricing
+5. **Use breadcrumbs** — free internal links on every page
+6. **Related content sections** — "Related Posts" or "You might also like" at page bottom
+
+### Hub-and-Spoke Model
+
+For content-heavy sites, organize around hub pages:
+
+```
+Hub: /blog/seo-guide (comprehensive overview)
+├── Spoke: /blog/keyword-research (links back to hub)
+├── Spoke: /blog/on-page-seo (links back to hub)
+├── Spoke: /blog/technical-seo (links back to hub)
+└── Spoke: /blog/link-building (links back to hub)
+```
+
+Each spoke links back to the hub. The hub links to all spokes. Spokes link to each other where relevant.
+
+### Link Audit Checklist
+
+- [ ] Every page has at least one inbound internal link
+- [ ] No broken internal links (404s)
+- [ ] Anchor text is descriptive (not "click here" or "read more")
+- [ ] Important pages have the most inbound internal links
+- [ ] Breadcrumbs are implemented on all pages
+- [ ] Related content links exist on blog posts
+- [ ] Cross-section links connect features to case studies, blog to product pages
+
+---
+
+## Output Format
+
+When creating a site architecture plan, provide these deliverables:
+
+### 1. Page Hierarchy (ASCII Tree)
+Full site structure with URLs at each node. Use the ASCII tree format from the Page Hierarchy Design section.
+
+### 2. Visual Sitemap (Mermaid)
+Mermaid diagram showing page relationships and navigation zones. Use `graph TD` with subgraphs for nav zones where helpful.
+
+### 3. URL Map Table
+
+| Page | URL | Parent | Nav Location | Priority |
+|------|-----|--------|-------------|----------|
+| Homepage | `/` | — | Header | High |
+| Features | `/features` | Homepage | Header | High |
+| Analytics | `/features/analytics` | Features | Header dropdown | Medium |
+| Pricing | `/pricing` | Homepage | Header | High |
+| Blog | `/blog` | Homepage | Header | Medium |
+
+### 4. Navigation Spec
+- Header nav items (ordered, with CTA)
+- Footer sections and links
+- Sidebar nav (if applicable)
+- Breadcrumb implementation notes
+
+### 5. Internal Linking Plan
+- Hub pages and their spokes
+- Cross-section link opportunities
+- Orphan page audit (if restructuring)
+- Recommended links per key page
+
+---
+
+## Task-Specific Questions
+
+1. Is this a new site or are you restructuring an existing one?
+2. What type of site is it? (SaaS, content, e-commerce, docs, hybrid, small business)
+3. How many pages exist or are planned?
+4. What are the 5 most important pages on the site?
+5. Are there existing URLs that need to be preserved or redirected?
+6. Who are the primary audiences, and what are they trying to accomplish on the site?
+
+---
+
+## Related Skills
+
+- **content-strategy**: For planning what content to create and topic clusters
+- **programmatic-seo**: For building SEO pages at scale with templates and data
+- **seo-audit**: For technical SEO, on-page optimization, and indexation issues
+- **page-cro**: For optimizing individual pages for conversion
+- **schema-markup**: For implementing breadcrumb and site navigation structured data
+- **competitor-alternatives**: For comparison page frameworks and URL patterns
@@ -0,0 +1,88 @@
+{
+  "skill_name": "site-architecture",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Help me plan the site architecture for our new SaaS marketing website. We have a homepage, product page, pricing page, about page, blog, and want to add competitor comparison pages and integration pages.",
+      "expected_output": "Should check for product-marketing-context.md first. Should apply the page hierarchy design principles (3-click rule, flat vs deep). Should create an ASCII tree showing the full site structure. Should organize pages logically: main nav (Home, Product, Pricing, About, Blog), comparison pages section, integrations hub. Should recommend URL structure patterns for each section. Should provide navigation design recommendations (4-7 header items). Should include internal linking strategy (hub-and-spoke for comparisons and integrations). Should provide the full deliverable set: hierarchy, URL map, nav spec.",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Applies 3-click rule and flat vs deep principles",
+        "Creates ASCII tree for site structure",
+        "Organizes pages logically",
+        "Recommends URL structure for each section",
+        "Provides navigation design (4-7 header items)",
+        "Includes internal linking strategy",
+        "Provides hierarchy, URL map, and nav spec"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "Our website has grown organically and the navigation is a mess. We have 50+ pages and users can't find anything. Help us reorganize.",
+      "expected_output": "Should treat this as a site architecture audit and redesign. Should recommend starting with a content inventory of all 50+ pages. Should apply the page hierarchy design to reorganize: group related pages, establish clear parent-child relationships, apply the 3-click rule. Should redesign the navigation (reduce header items, use mega-menu or dropdowns for deeper pages). Should provide before/after ASCII tree structure. Should address URL redirects for any pages that move. Should include a visual sitemap (Mermaid).",
+      "assertions": [
+        "Recommends content inventory first",
+        "Groups related pages logically",
+        "Applies 3-click rule",
+        "Redesigns navigation structure",
+        "Provides ASCII tree or visual sitemap",
+        "Addresses URL redirects for moved pages",
+        "Reduces header navigation items"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "what should our url structure look like? we keep debating between /blog/post-name vs /resources/blog/post-name and /product/feature vs /features/feature-name",
+      "expected_output": "Should trigger on casual phrasing. Should apply the URL structure patterns guidance. Should recommend clean, descriptive URLs: prefer shorter paths (/blog/post-name over /resources/blog/post-name), use consistent patterns, avoid unnecessary nesting. Should provide URL structure recommendations for each section type (blog, features, comparisons, integrations). Should address SEO implications of URL structure. Should provide a complete URL map as a reference.",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Applies URL structure patterns",
+        "Recommends shorter, cleaner paths",
+        "Provides recommendations for each section type",
+        "Addresses SEO implications",
+        "Provides URL map reference"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "We're adding programmatic SEO pages — 200 integration pages and 50 comparison pages. How should these fit into our site architecture?",
+      "expected_output": "Should address how to integrate scaled content into the site architecture. Should recommend hub pages for both sections (/integrations and /compare or /vs). Should apply the hub-and-spoke internal linking model. Should address navigation: these shouldn't clutter the main nav, but should be accessible via hub pages. Should provide URL structure for both sections. Should address crawl budget considerations for 250 new pages. Should cross-reference programmatic-seo for the content strategy.",
+      "assertions": [
+        "Recommends hub pages for each section",
+        "Applies hub-and-spoke internal linking",
+        "Keeps programmatic pages out of main nav",
+        "Provides URL structure for both sections",
+        "Addresses crawl budget for 250 pages",
+        "Cross-references programmatic-seo skill"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "Can you create a visual sitemap for our site? We want something we can share with our design team.",
+      "expected_output": "Should provide a visual sitemap using Mermaid diagram format. Should organize the sitemap hierarchically showing page relationships. Should use the Mermaid graph syntax that can be rendered by most tools. Should include all major sections and key pages. Should be clear enough for a design team to use as a reference for navigation and wireframing.",
+      "assertions": [
+        "Provides visual sitemap in Mermaid format",
+        "Shows hierarchical page relationships",
+        "Includes all major sections",
+        "Uses clear, readable format",
+        "Suitable for sharing with design team"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "Our XML sitemap hasn't been updated in 6 months and we have crawl errors in Search Console. Can you fix our technical SEO?",
+      "expected_output": "Should recognize this is a technical SEO audit task, not a site architecture design task. Should defer to or cross-reference the seo-audit skill, which handles XML sitemaps, crawl errors, and technical SEO issues. Site-architecture focuses on page hierarchy, navigation, and URL structure design — not technical SEO troubleshooting.",
+      "assertions": [
+        "Recognizes this as technical SEO, not site architecture",
+        "References or defers to seo-audit skill",
+        "Explains site-architecture covers design, not technical SEO"
+      ],
+      "files": []
+    }
+  ]
+}
@@ -0,0 +1,216 @@
+# Mermaid Diagram Templates
+
+Copy-paste-ready Mermaid diagrams for visual sitemaps. Customize node labels and connections for your site.
+
+---
+
+## Basic Hierarchy
+
+Simple top-down page hierarchy.
+
+```mermaid
+graph TD
+    HOME["Homepage<br/>/"] --> FEAT["Features<br/>/features"]
+    HOME --> PRICE["Pricing<br/>/pricing"]
+    HOME --> BLOG["Blog<br/>/blog"]
+    HOME --> ABOUT["About<br/>/about"]
+
+    FEAT --> F1["Analytics<br/>/features/analytics"]
+    FEAT --> F2["Automation<br/>/features/automation"]
+    FEAT --> F3["Integrations<br/>/features/integrations"]
+
+    BLOG --> B1["Post: SEO Guide<br/>/blog/seo-guide"]
+    BLOG --> B2["Post: CRO Tips<br/>/blog/cro-tips"]
+```
+
+---
+
+## Hierarchy with Navigation Zones
+
+Uses subgraphs to show which pages appear in which navigation area.
+
+```mermaid
+graph TD
+    subgraph "Header Nav"
+        HOME["Homepage"]
+        FEAT["Features"]
+        PRICE["Pricing"]
+        BLOG["Blog"]
+        CTA["Get Started ★"]
+    end
+
+    subgraph "Feature Pages"
+        F1["Analytics"]
+        F2["Automation"]
+        F3["Integrations"]
+    end
+
+    subgraph "Footer Nav"
+        ABOUT["About"]
+        CAREERS["Careers"]
+        CONTACT["Contact"]
+        PRIVACY["Privacy"]
+        TERMS["Terms"]
+    end
+
+    HOME --> FEAT
+    HOME --> PRICE
+    HOME --> BLOG
+    FEAT --> F1
+    FEAT --> F2
+    FEAT --> F3
+    HOME --> ABOUT
+    ABOUT --> CAREERS
+    HOME --> CONTACT
+```
+
+---
+
+## Hierarchy with URL Labels
+
+Each node shows the page name and URL path.
+
+```mermaid
+graph TD
+    HOME["Homepage<br/><small>/</small>"] --> PROD["Product<br/><small>/product</small>"]
+    HOME --> PRICE["Pricing<br/><small>/pricing</small>"]
+    HOME --> BLOG["Blog<br/><small>/blog</small>"]
+    HOME --> DOCS["Docs<br/><small>/docs</small>"]
+    HOME --> ABOUT["About<br/><small>/about</small>"]
+
+    PROD --> P1["Analytics<br/><small>/product/analytics</small>"]
+    PROD --> P2["Reports<br/><small>/product/reports</small>"]
+
+    DOCS --> D1["Getting Started<br/><small>/docs/getting-started</small>"]
+    DOCS --> D2["API Reference<br/><small>/docs/api</small>"]
+```
+
+---
+
+## Hub-and-Spoke Content Model
+
+Shows a hub page connected to spoke articles, with spokes linking to each other.
+
+```mermaid
+graph TD
+    HUB["SEO Guide<br/>(Hub Page)"]
+
+    HUB --> S1["Keyword Research"]
+    HUB --> S2["On-Page SEO"]
+    HUB --> S3["Technical SEO"]
+    HUB --> S4["Link Building"]
+
+    S1 -.-> S2
+    S2 -.-> S3
+    S3 -.-> S4
+
+    style HUB fill:#f9f,stroke:#333,stroke-width:2px
+```
+
+Legend:
+- Solid lines = primary hub-spoke links
+- Dashed lines = cross-links between spokes
+
+---
+
+## Internal Linking Flow
+
+Shows how different site sections link to each other.
+
+```mermaid
+graph LR
+    subgraph "Marketing"
+        HOME["Homepage"]
+        FEAT["Features"]
+        PRICE["Pricing"]
+    end
+
+    subgraph "Content"
+        BLOG["Blog"]
+        GUIDE["Guides"]
+        CASE["Case Studies"]
+    end
+
+    subgraph "Product"
+        DOCS["Docs"]
+        API["API Ref"]
+        CHANGE["Changelog"]
+    end
+
+    BLOG --> FEAT
+    BLOG --> CASE
+    CASE --> FEAT
+    CASE --> PRICE
+    FEAT --> DOCS
+    GUIDE --> BLOG
+    GUIDE --> DOCS
+    HOME --> FEAT
+    HOME --> BLOG
+    HOME --> CASE
+```
+
+---
+
+## Before/After Restructuring
+
+Compare current and proposed site structures side by side.
+
+```mermaid
+graph TD
+    subgraph "Before"
+        B_HOME["Homepage"] --> B_P1["Page 1"]
+        B_HOME --> B_P2["Page 2"]
+        B_HOME --> B_P3["Page 3"]
+        B_HOME --> B_P4["Page 4"]
+        B_HOME --> B_P5["Page 5"]
+        B_HOME --> B_P6["Page 6"]
+        B_HOME --> B_P7["Page 7"]
+        B_HOME --> B_P8["Page 8"]
+    end
+
+    subgraph "After"
+        A_HOME["Homepage"] --> A_S1["Features"]
+        A_HOME --> A_S2["Resources"]
+        A_HOME --> A_S3["Company"]
+        A_S1 --> A_P1["Feature A"]
+        A_S1 --> A_P2["Feature B"]
+        A_S2 --> A_P3["Blog"]
+        A_S2 --> A_P4["Guides"]
+        A_S3 --> A_P5["About"]
+        A_S3 --> A_P6["Contact"]
+    end
+```
+
+---
+
+## Color-Coding Conventions
+
+Use styles to highlight page status, priority, or type.
+
+```mermaid
+graph TD
+    HOME["Homepage"] --> FEAT["Features"]
+    HOME --> PRICE["Pricing"]
+    HOME --> BLOG["Blog"]
+    HOME --> NEW["New Section"]
+    HOME --> REMOVE["Deprecated Page"]
+
+    FEAT --> F1["Existing Feature"]
+    FEAT --> F2["New Feature"]
+
+    style HOME fill:#4CAF50,color:#fff
+    style PRICE fill:#4CAF50,color:#fff
+    style FEAT fill:#4CAF50,color:#fff
+    style BLOG fill:#4CAF50,color:#fff
+    style F1 fill:#4CAF50,color:#fff
+    style NEW fill:#2196F3,color:#fff
+    style F2 fill:#2196F3,color:#fff
+    style REMOVE fill:#f44336,color:#fff
+```
+
+Color key:
+- **Green** (`#4CAF50`): Existing pages (no changes)
+- **Blue** (`#2196F3`): New pages to create
+- **Red** (`#f44336`): Pages to remove or redirect
+- **Yellow** (`#FFC107`): Pages to restructure or move
+- **Purple** (`#9C27B0`): High-priority / CTA pages
@@ -0,0 +1,305 @@
+# Navigation Patterns
+
+Detailed navigation patterns for different site types and contexts.
+
+---
+
+## Header Navigation
+
+### Simple Header (4-6 items)
+
+Best for: small businesses, simple SaaS, portfolios.
+
+```
+[Logo]   Features   Pricing   Blog   About   [CTA Button]
+```
+
+Rules:
+- Logo always links to homepage
+- CTA button is rightmost, visually distinct (filled button, contrasting color)
+- Items ordered by priority (most visited first)
+- Active page gets visual indicator (underline, bold, color)
+
+### Mega Menu Header
+
+Best for: SaaS with many features, e-commerce with categories, large content sites.
+
+```
+[Logo]   Product ▾   Solutions ▾   Resources ▾   Pricing   Docs   [CTA]
+```
+
+When "Product" is hovered/clicked:
+
+```
+┌─────────────────────────────────────────────────┐
+│  Features           Platform        Integrations │
+│  ─────────          ─────────       ──────────── │
+│  Analytics           Security       Slack         │
+│  Automation          API            HubSpot       │
+│  Reporting           Compliance     Salesforce    │
+│  Dashboards                         Zapier        │
+│                                                   │
+│  [See all features →]                             │
+└─────────────────────────────────────────────────┘
+```
+
+Mega menu rules:
+- 2-4 columns max
+- Group items logically (by feature area, use case, or audience)
+- Include a "See all" link at the bottom
+- Don't nest dropdowns inside mega menus
+- Show descriptions for items when labels alone aren't clear
+
+### Split Navigation
+
+Best for: apps with both marketing and product nav.
+
+```
+[Logo]   Features   Pricing   Blog        [Login]   [Sign Up]
+├── Marketing nav (left) ──────┘          └── Auth nav (right) ──┤
+```
+
+Right side handles authentication actions. Left side handles page navigation.
+
+---
+
+## Footer Navigation
+
+### Column-Based Footer (Standard)
+
+Best for: most sites. Organize links into 3-5 themed columns.
+
+```
+┌──────────────────────────────────────────────────────────┐
+│                                                          │
+│  Product          Resources        Company       Legal   │
+│  ─────────        ──────────       ─────────     ─────   │
+│  Features         Blog             About         Privacy │
+│  Pricing          Guides           Careers       Terms   │
+│  Integrations     Templates        Contact       GDPR    │
+│  Changelog        Case Studies     Press                 │
+│  Security         Webinars         Partners              │
+│                                                          │
+│  [Logo]  © 2026 Company Name                             │
+│  Social: [Twitter] [LinkedIn] [GitHub]                   │
+│                                                          │
+└──────────────────────────────────────────────────────────┘
+```
+
+### Minimal Footer
+
+Best for: simple sites, landing pages.
+
+```
+┌──────────────────────────────────────────────────────────┐
+│  [Logo]                                                  │
+│  © 2026 Company  ·  Privacy  ·  Terms  ·  Contact        │
+└──────────────────────────────────────────────────────────┘
+```
+
+### Expanded Footer
+
+Best for: sites using footer for SEO (comparison pages, location pages, resource links).
+
+```
+┌──────────────────────────────────────────────────────────┐
+│  Product     Resources    Compare         Use Cases      │
+│  Features    Blog         vs Competitor A  For Startups  │
+│  Pricing     Guides       vs Competitor B  For Enterprise│
+│  API         Templates    vs Competitor C  For Agencies  │
+│                                                          │
+│  Integrations             Popular Posts                  │
+│  Slack       Zapier       How to Do X                    │
+│  HubSpot     Salesforce   Guide to Y                     │
+│                           Template: Z                    │
+│                                                          │
+│  [Logo]  © 2026  ·  Privacy  ·  Terms  ·  Security      │
+└──────────────────────────────────────────────────────────┘
+```
+
+---
+
+## Sidebar Navigation
+
+### Documentation Sidebar
+
+Persistent left sidebar with collapsible sections.
+
+```
+Getting Started
+  ├── Installation
+  ├── Quick Start
+  └── Configuration
+
+Guides
+  ├── Authentication
+  ├── Data Models
+  └── Deployment
+
+API Reference
+  ├── REST API
+  │   ├── Users
+  │   ├── Projects
+  │   └── Webhooks
+  └── GraphQL
+
+Examples
+  ├── Next.js
+  ├── Rails
+  └── Python
+
+Changelog
+```
+
+Rules:
+- Current page highlighted
+- Sections collapsible (expanded by default for active section)
+- Search at top of sidebar
+- "Previous / Next" page navigation at bottom of content area
+- Sticky on scroll (doesn't scroll away)
+
+### Blog Category Sidebar
+
+```
+Categories
+  ├── SEO (24)
+  ├── CRO (18)
+  ├── Content (15)
+  ├── Paid Ads (12)
+  └── Analytics (9)
+
+Popular Posts
+  ├── How to Improve SEO
+  ├── Landing Page Guide
+  └── Analytics Setup
+
+Newsletter
+  └── [Email signup form]
+```
+
+---
+
+## Breadcrumbs
+
+### Standard Format
+
+```
+Home > Features > Analytics
+Home > Blog > SEO Category > How to Do Keyword Research
+Home > Docs > API Reference > Authentication
+```
+
+Rules:
+- Separator: `>` or `/` (be consistent)
+- Every segment is a link except the current page
+- Current page is plain text (not linked)
+- Don't include the current page if the title is already visible as an H1
+
+### With Schema Markup
+
+```html
+<nav aria-label="Breadcrumb">
+  <ol itemscope itemtype="https://schema.org/BreadcrumbList">
+    <li itemprop="itemListElement" itemscope itemtype="https://schema.org/ListItem">
+      <a itemprop="item" href="/"><span itemprop="name">Home</span></a>
+      <meta itemprop="position" content="1" />
+    </li>
+    <li itemprop="itemListElement" itemscope itemtype="https://schema.org/ListItem">
+      <a itemprop="item" href="/features"><span itemprop="name">Features</span></a>
+      <meta itemprop="position" content="2" />
+    </li>
+    <li itemprop="itemListElement" itemscope itemtype="https://schema.org/ListItem">
+      <span itemprop="name">Analytics</span>
+      <meta itemprop="position" content="3" />
+    </li>
+  </ol>
+</nav>
+```
+
+Or use JSON-LD (recommended):
+
+```json
+{
+  "@context": "https://schema.org",
+  "@type": "BreadcrumbList",
+  "itemListElement": [
+    { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://example.com/" },
+    { "@type": "ListItem", "position": 2, "name": "Features", "item": "https://example.com/features" },
+    { "@type": "ListItem", "position": 3, "name": "Analytics" }
+  ]
+}
+```
+
+---
+
+## Mobile Navigation
+
+### Hamburger Menu
+
+Standard for mobile. All nav items collapse into a menu icon.
+
+Rules:
+- Hamburger icon (three lines) top-right or top-left
+- Full-screen or slide-out panel
+- CTA button visible without opening the menu (sticky header)
+- Search accessible from mobile menu
+- Accordion pattern for nested items
+
+### Bottom Tab Bar
+
+Best for: web apps, PWAs, mobile-first products.
+
+```
+┌──────────────────────────────────────┐
+│                                      │
+│           [Page Content]             │
+│                                      │
+├──────────────────────────────────────┤
+│  Home    Search    Create    Profile │
+│   🏠       🔍        ➕       👤    │
+└──────────────────────────────────────┘
+```
+
+Rules:
+- 3-5 items max
+- Icons + labels (not just icons)
+- Active state clearly indicated
+- Most important action in the center
+
+---
+
+## Anti-Patterns
+
+### Things to Avoid
+
+- **Too many header items** (8+): causes decision paralysis, nav becomes unreadable on smaller screens
+- **Dropdown inception**: dropdowns inside dropdowns inside dropdowns
+- **Mystery icons**: icons without labels — users don't know what they mean
+- **Hidden primary nav**: burying important pages in hamburger menus on desktop
+- **Inconsistent nav between pages**: nav should be identical across the site (except app vs marketing)
+- **No mobile consideration**: desktop nav that doesn't translate to mobile
+- **Footer as sitemap dump**: 50+ links in the footer with no organization
+- **Breadcrumbs that don't match URLs**: breadcrumb says "Products > Widget" but URL is `/shop/widget-pro`
+
+### Common Fixes
+
+| Problem | Fix |
+|---------|-----|
+| Too many nav items | Group into dropdowns or mega menus |
+| Users can't find pages | Add search, improve labeling |
+| High bounce from nav | Simplify choices, use clearer labels |
+| SEO pages not linked | Add to footer or resource sections |
+| Mobile nav is broken | Test on real devices, use hamburger pattern |
+
+---
+
+## Navigation for SEO
+
+Internal links in navigation pass PageRank. Use this strategically:
+
+- **Header nav links are strongest** — put your most important pages here
+- **Footer links pass less value** but still matter — good for comparison pages, location pages
+- **Sidebar links** help with section-level authority — good for blog categories, doc sections
+- **Breadcrumbs** provide structural signals to search engines — implement with schema markup
+- **Don't use JavaScript-only nav** — search engines need crawlable HTML links
+- **Use descriptive anchor text** — "Analytics Features" not just "Features"
@@ -0,0 +1,293 @@
+# Site Type Templates
+
+Full page hierarchy templates with ASCII trees, URL maps, and navigation recommendations for common site types.
+
+---
+
+## SaaS Marketing Site
+
+### Page Hierarchy
+
+```
+Homepage (/)
+├── Features (/features)
+│   ├── Feature A (/features/feature-a)
+│   ├── Feature B (/features/feature-b)
+│   └── Feature C (/features/feature-c)
+├── Pricing (/pricing)
+├── Customers (/customers)
+│   ├── Case Study 1 (/customers/company-name)
+│   └── Case Study 2 (/customers/company-name-2)
+├── Resources (/resources)
+│   ├── Blog (/blog)
+│   │   └── [Posts] (/blog/post-slug)
+│   ├── Templates (/resources/templates)
+│   │   └── [Template] (/resources/templates/template-slug)
+│   └── Guides (/resources/guides)
+│       └── [Guide] (/resources/guides/guide-slug)
+├── Integrations (/integrations)
+│   └── [Integration] (/integrations/integration-name)
+├── Docs (/docs)
+│   ├── Getting Started (/docs/getting-started)
+│   ├── Guides (/docs/guides)
+│   └── API Reference (/docs/api)
+├── About (/about)
+│   ├── Careers (/about/careers)
+│   └── Contact (/contact)
+├── Compare (/compare)
+│   └── [Competitor] (/compare/competitor-name)
+├── Privacy (/privacy)
+└── Terms (/terms)
+```
+
+### URL Map
+
+| Page | URL | Nav Location | Priority |
+|------|-----|-------------|----------|
+| Homepage | `/` | Header (logo) | Critical |
+| Features | `/features` | Header | High |
+| Feature pages | `/features/{slug}` | Header dropdown | Medium |
+| Pricing | `/pricing` | Header | Critical |
+| Customers | `/customers` | Header | Medium |
+| Case studies | `/customers/{slug}` | Customers dropdown | Medium |
+| Blog | `/blog` | Header (Resources) | High |
+| Blog posts | `/blog/{slug}` | — | Medium |
+| Integrations | `/integrations` | Header | Medium |
+| Docs | `/docs` | Header | Medium |
+| Compare | `/compare/{slug}` | Footer | High (SEO) |
+| About | `/about` | Footer | Low |
+| Pricing CTA | `/pricing` | Header (CTA button) | Critical |
+
+### Navigation
+
+**Header (6 items + CTA)**: Features | Pricing | Customers | Resources | Integrations | Docs | [Get Started]
+
+**Footer columns**:
+- Product: Features, Pricing, Integrations, Changelog, Security
+- Resources: Blog, Templates, Guides, Case Studies
+- Company: About, Careers, Contact, Press
+- Legal: Privacy, Terms, Security
+
+---
+
+## Content / Blog Site
+
+### Page Hierarchy
+
+```
+Homepage (/)
+├── Blog (/blog)
+│   ├── [Category: Topic A] (/blog/category/topic-a)
+│   ├── [Category: Topic B] (/blog/category/topic-b)
+│   ├── [Category: Topic C] (/blog/category/topic-c)
+│   └── [Posts] (/blog/post-slug)
+├── Newsletter (/newsletter)
+├── Resources (/resources)
+│   ├── Guides (/resources/guides)
+│   │   └── [Guide] (/resources/guides/guide-slug)
+│   └── Tools (/resources/tools)
+│       └── [Tool] (/resources/tools/tool-slug)
+├── About (/about)
+├── Contact (/contact)
+├── Privacy (/privacy)
+└── Terms (/terms)
+```
+
+### URL Map
+
+| Page | URL | Nav Location | Priority |
+|------|-----|-------------|----------|
+| Homepage | `/` | Header (logo) | Critical |
+| Blog index | `/blog` | Header | High |
+| Categories | `/blog/category/{slug}` | Header dropdown | Medium |
+| Posts | `/blog/{slug}` | — | Medium |
+| Newsletter | `/newsletter` | Header (CTA) | High |
+| Guides | `/resources/guides` | Header | Medium |
+| About | `/about` | Header | Low |
+
+### Navigation
+
+**Header (4 items + CTA)**: Blog | Resources | About | Contact | [Subscribe]
+
+**Sidebar** (on blog): Categories, Popular Posts, Newsletter signup
+
+---
+
+## E-Commerce
+
+### Page Hierarchy
+
+```
+Homepage (/)
+├── Shop (/shop)
+│   ├── Category A (/shop/category-a)
+│   │   ├── Subcategory (/shop/category-a/subcategory)
+│   │   │   └── [Product] (/shop/category-a/subcategory/product-slug)
+│   │   └── [Product] (/shop/category-a/product-slug)
+│   ├── Category B (/shop/category-b)
+│   │   └── [Product] (/shop/category-b/product-slug)
+│   └── Category C (/shop/category-c)
+│       └── [Product] (/shop/category-c/product-slug)
+├── Collections (/collections)
+│   └── [Collection] (/collections/collection-slug)
+├── Sale (/sale)
+├── Blog (/blog)
+│   └── [Posts] (/blog/post-slug)
+├── About (/about)
+│   └── Our Story (/about/our-story)
+├── Help (/help)
+│   ├── FAQ (/help/faq)
+│   ├── Shipping (/help/shipping)
+│   ├── Returns (/help/returns)
+│   └── Contact (/contact)
+├── Cart (/cart)
+├── Account (/account)
+├── Privacy (/privacy)
+└── Terms (/terms)
+```
+
+### URL Map
+
+| Page | URL | Nav Location | Priority |
+|------|-----|-------------|----------|
+| Homepage | `/` | Header (logo) | Critical |
+| Shop | `/shop` | Header | Critical |
+| Categories | `/shop/{category}` | Header mega menu | High |
+| Products | `/shop/{category}/{product}` | — | High |
+| Collections | `/collections/{slug}` | Header | Medium |
+| Sale | `/sale` | Header (highlighted) | High |
+| Cart | `/cart` | Header (icon) | Critical |
+| Account | `/account` | Header (icon) | Medium |
+
+### Navigation
+
+**Header (5 items + cart/account)**: Shop (mega menu) | Collections | Sale | Blog | Help | [Cart icon] [Account icon]
+
+**Mega menu under Shop**: Category columns with featured products/images
+
+---
+
+## Documentation Site
+
+### Page Hierarchy
+
+```
+Docs Home (/docs)
+├── Getting Started (/docs/getting-started)
+│   ├── Installation (/docs/getting-started/installation)
+│   ├── Quick Start (/docs/getting-started/quick-start)
+│   └── Configuration (/docs/getting-started/configuration)
+├── Guides (/docs/guides)
+│   ├── Guide A (/docs/guides/guide-a)
+│   ├── Guide B (/docs/guides/guide-b)
+│   └── Guide C (/docs/guides/guide-c)
+├── API Reference (/docs/api)
+│   ├── Authentication (/docs/api/authentication)
+│   ├── Endpoints (/docs/api/endpoints)
+│   └── Webhooks (/docs/api/webhooks)
+├── Examples (/docs/examples)
+│   └── [Example] (/docs/examples/example-slug)
+├── Changelog (/docs/changelog)
+└── FAQ (/docs/faq)
+```
+
+### URL Map
+
+| Page | URL | Nav Location | Priority |
+|------|-----|-------------|----------|
+| Docs home | `/docs` | Header | High |
+| Getting Started | `/docs/getting-started` | Sidebar (top) | Critical |
+| Guides | `/docs/guides` | Sidebar | High |
+| API Reference | `/docs/api` | Sidebar | High |
+| Changelog | `/docs/changelog` | Sidebar (bottom) | Low |
+
+### Navigation
+
+**Header**: Docs | API | Blog | Community | GitHub | [Dashboard]
+
+**Sidebar** (persistent, left): Getting Started, Guides, API Reference, Examples, Changelog — with expandable subsections
+
+**On-page**: Previous/Next navigation at bottom of each doc page
+
+---
+
+## Hybrid SaaS + Content
+
+### Page Hierarchy
+
+```
+Homepage (/)
+├── Product (/product)
+│   ├── Feature A (/product/feature-a)
+│   ├── Feature B (/product/feature-b)
+│   └── Feature C (/product/feature-c)
+├── Solutions (/solutions)
+│   ├── By Use Case (/solutions/use-case-slug)
+│   └── By Industry (/solutions/industry-slug)
+├── Pricing (/pricing)
+├── Blog (/blog)
+│   ├── [Category] (/blog/category/slug)
+│   └── [Posts] (/blog/post-slug)
+├── Resources (/resources)
+│   ├── Guides (/resources/guides)
+│   ├── Templates (/resources/templates)
+│   ├── Webinars (/resources/webinars)
+│   └── Case Studies (/resources/case-studies)
+├── Docs (/docs)
+│   ├── Getting Started (/docs/getting-started)
+│   └── API (/docs/api)
+├── Integrations (/integrations)
+│   └── [Integration] (/integrations/slug)
+├── Compare (/compare)
+│   └── [Competitor] (/compare/competitor-slug)
+├── About (/about)
+│   ├── Careers (/about/careers)
+│   └── Contact (/contact)
+├── Privacy (/privacy)
+└── Terms (/terms)
+```
+
+### Navigation
+
+**Header (7 items + CTA)**: Product | Solutions | Pricing | Resources | Blog | Docs | Integrations | [Start Free Trial]
+
+Use mega menus for Product (features list), Solutions (use cases + industries), and Resources (blog, guides, templates, webinars, case studies).
+
+---
+
+## Small Business / Local
+
+### Page Hierarchy
+
+```
+Homepage (/)
+├── Services (/services)
+│   ├── Service A (/services/service-a)
+│   ├── Service B (/services/service-b)
+│   └── Service C (/services/service-c)
+├── About (/about)
+├── Testimonials (/testimonials)
+├── Blog (/blog)
+│   └── [Posts] (/blog/post-slug)
+├── Contact (/contact)
+├── Privacy (/privacy)
+└── Terms (/terms)
+```
+
+### URL Map
+
+| Page | URL | Nav Location | Priority |
+|------|-----|-------------|----------|
+| Homepage | `/` | Header (logo) | Critical |
+| Services | `/services` | Header | High |
+| Service pages | `/services/{slug}` | Header dropdown | High |
+| About | `/about` | Header | Medium |
+| Testimonials | `/testimonials` | Header | Medium |
+| Blog | `/blog` | Header | Medium |
+| Contact | `/contact` | Header (CTA) | High |
+
+### Navigation
+
+**Header (5 items + CTA)**: Services | About | Testimonials | Blog | [Contact Us]
+
+Keep it simple. Small business sites should be flat (1-2 levels max). Every page should be reachable from the header.
@@ -1,8 +1,8 @@
 ---
 name: social-content
-description: "When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms. Also use when the user mentions 'LinkedIn post,' 'Twitter thread,' 'social media,' 'content calendar,' 'social scheduling,' 'engagement,' or 'viral content.' This skill covers content creation, repurposing, and platform-specific strategies."
+description: "When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms. Also use when the user mentions 'LinkedIn post,' 'Twitter thread,' 'social media,' 'content calendar,' 'social scheduling,' 'engagement,' 'viral content,' 'what should I post,' 'repurpose this content,' 'tweet ideas,' 'LinkedIn carousel,' 'social media strategy,' or 'grow my following.' Use this for any social media content creation, repurposing, or scheduling task. For broader content strategy, see content-strategy."
 metadata:
-  version: 1.0.0
+  version: 1.2.0
 ---

 # Social Content
@@ -12,7 +12,7 @@ You are an expert social media strategist. Your goal is to help create engaging
 ## Before Creating Content

 **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):

@@ -49,6 +49,7 @@ Gather this context (ask if not provided):
 | Facebook | Communities, local businesses | 1-2x/day | Groups, native video |

 **For detailed platform strategies**: See [references/platforms.md](references/platforms.md)
+**For hashtag limits and character counts**: See [references/platform-limits.md](references/platform-limits.md)

 ---

@@ -107,7 +108,7 @@ The first line determines whether anyone reads the rest.

 ## Content Repurposing System

-Turn one piece of content into many:
+Turn one piece of content into many. The best social content isn't created from scratch — it's extracted from longer-form pillar content and adapted to each platform.

 ### Blog Post → Social Content

@@ -119,13 +120,61 @@ Turn one piece of content into many:
 | Instagram | Carousel with visuals |
 | Instagram | Reel summarizing the post |

+### Podcast / Video → Social Content
+
+Extract "content atoms" — self-contained moments from any long-form content that work on their own:
+
+| Atom Type | What to Look For | Best Platform |
+|-----------|-----------------|---------------|
+| Quotable moment | A bold claim, hot take, or memorable line (15-60 sec) | Twitter/X, LinkedIn, TikTok |
+| Story arc | A complete mini-story with setup, conflict, resolution (60-90 sec) | Instagram Reels, TikTok, YouTube Shorts |
+| Tactical tip | A specific how-to or framework explained clearly (30-60 sec) | LinkedIn, YouTube Shorts |
+| Controversial take | A contrarian opinion that sparks debate | Twitter/X, LinkedIn |
+| Data/stat callout | A surprising number or research finding | LinkedIn carousel, Twitter/X |
+| Behind-the-scenes | Authentic, unpolished moments | Instagram Stories, TikTok |
+
+**Podcast repurposing workflow:**
+1. **Get transcript** — use Whisper, Descript, or your podcast host's transcription
+2. **Mark timestamps** — flag the 5-10 best moments while listening or scanning transcript
+3. **Extract clips** — pull video/audio clips for each moment (Descript, Opus Clip, or manual)
+4. **Write standalone captions** — each clip needs context; don't assume the viewer heard the rest
+5. **Add subtitles** — most social video is watched without sound
+6. **Schedule across 1-2 weeks** — spread a single episode across multiple posts
+
+**Per episode, aim for:**
+- 3-5 short video clips or audiograms (15-60 sec) for Reels/TikTok/Shorts
+- 1-2 LinkedIn text posts from key insights
+- 1 Twitter/X thread of takeaways
+- 1 carousel summarizing the main framework or list
+- 1 newsletter section or blog post from the best segment
+
+### Webinar / Live Event → Social Content
+
+| Extract | Format |
+|---------|--------|
+| Key slides with commentary | LinkedIn carousel |
+| Q&A highlights | Twitter/X thread |
+| Speaker quotes | Quote graphics for Instagram/LinkedIn |
+| Audience reactions/poll results | Engagement posts |
+| Full recording → short clips | Reels, TikTok, Shorts |
+
+### Newsletter → Social Content
+
+| Extract | Format |
+|---------|--------|
+| Main insight | LinkedIn post |
+| Curated links with commentary | Twitter/X thread |
+| Data or stat | Quote graphic |
+| Hot take or opinion | Twitter/X post, LinkedIn |
+
 ### Repurposing Workflow

-1. **Create pillar content** (blog, video, podcast)
-2. **Extract key insights** (3-5 per piece)
-3. **Adapt to each platform** (format and tone)
-4. **Schedule across the week** (spread distribution)
-5. **Update and reshare** (evergreen content can repeat)
+1. **Create pillar content** (blog, video, podcast, webinar, newsletter)
+2. **Extract content atoms** (5-10 per piece — quotes, stories, tips, data)
+3. **Adapt to each platform** (format, length, and tone)
+4. **Write standalone captions** (each post must work without context)
+5. **Schedule across the week** (spread distribution, don't dump all at once)
+6. **Update and reshare** (evergreen content can repeat every 3-6 months)

 ---

@@ -0,0 +1,92 @@
+{
+  "skill_name": "social-content",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Help me create a LinkedIn content strategy. I'm a SaaS founder building in public and want to grow my personal brand to drive awareness for my product. I currently have 500 followers and post maybe once a week.",
+      "expected_output": "Should check for product-marketing-context.md first. Should establish content pillars (3-5) appropriate for a SaaS founder building in public: industry insights, behind-the-scenes, educational content, personal stories, promotional (minimal). Should apply the platform quick reference for LinkedIn (3-5x/week recommended, carousels and stories perform well). Should provide hook formulas for LinkedIn posts. Should create a weekly content calendar. Should include engagement strategy (daily 30-min routine). Should address going from 1x/week to 3-5x/week with a batching strategy.",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Establishes 3-5 content pillars",
+        "Applies LinkedIn platform guidance",
+        "Provides hook formulas",
+        "Creates weekly content calendar",
+        "Includes engagement strategy",
+        "Addresses batching strategy for consistency",
+        "Recommends increasing from 1x to 3-5x per week"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "Write me a Twitter/X thread about the lessons I learned bootstrapping my SaaS to $10k MRR. Include hooks and a CTA at the end.",
+      "expected_output": "Should apply the hook formulas for a story hook (e.g., '6 months ago, I had $0 MRR. Today, I hit $10k.'). Should structure the thread following platform best practices: strong hook in tweet 1, each tweet should stand alone but flow together, use specific numbers and stories, end with a CTA. Should reference the content pillar this fits into (behind-the-scenes / founder journey). Should provide the actual thread content with 8-12 tweets. Should include engagement prompts.",
+      "assertions": [
+        "Applies hook formulas from the skill",
+        "Uses a story hook for the first tweet",
+        "Structures thread with standalone but flowing tweets",
+        "Uses specific numbers and stories",
+        "Ends with clear CTA",
+        "Provides 8-12 tweet thread content",
+        "Includes engagement prompts"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "i have a blog post that did really well. how do i turn it into social media content for multiple platforms?",
+      "expected_output": "Should trigger on casual phrasing. Should apply the content repurposing system. Should use the Blog Post → Social Content mapping: LinkedIn (key insight post + carousel of main points), Twitter/X (thread of key takeaways), Instagram (carousel with visuals + Reel summarizing the post). Should follow the repurposing workflow: create pillar content → extract key insights (3-5) → adapt to each platform → schedule across the week. Should provide specific format recommendations per platform.",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Applies content repurposing system",
+        "Uses Blog Post → Social Content mapping",
+        "Provides format for LinkedIn, Twitter/X, and Instagram",
+        "Follows the repurposing workflow",
+        "Extracts 3-5 key insights to repurpose",
+        "Provides platform-specific format recommendations"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "My LinkedIn posts get like 200 impressions and almost no engagement. What am I doing wrong?",
+      "expected_output": "Should apply the analytics and optimization section, specifically the 'if engagement is low' guidance. Should diagnose potential issues: weak hooks (first line not compelling), posting at wrong times, not engaging with others' content, poor formatting (no line breaks, walls of text), content not resonating with audience. Should recommend specific fixes: test new hook formulas, post at different times, increase engagement with others (the daily engagement routine), try different formats (carousels, stories). Should provide before/after hook examples.",
+      "assertions": [
+        "Applies analytics and optimization guidance",
+        "Diagnoses potential engagement issues",
+        "Addresses hook quality",
+        "Addresses posting timing",
+        "Recommends daily engagement routine",
+        "Suggests trying different content formats",
+        "Provides specific before/after hook examples"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "Help me reverse-engineer what's working for top creators in the DevTools space on Twitter. I want to understand their content patterns.",
+      "expected_output": "Should apply the reverse engineering viral content framework. Should walk through the process: identify 10-20 top accounts in DevTools, collect high-performing posts, analyze patterns (hooks, formats, CTAs, topics, posting times), codify a playbook of repeatable patterns, then layer the user's authentic voice. Should provide specific guidance on what to look for in the analysis. Should recommend tools or methods for collecting the data.",
+      "assertions": [
+        "Applies reverse engineering viral content framework",
+        "Walks through the full process (find, collect, analyze, codify, apply)",
+        "Recommends identifying 10-20 accounts",
+        "Describes what patterns to analyze",
+        "Emphasizes layering authentic voice",
+        "Provides data collection guidance"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "Write me a 5-email welcome sequence for new email subscribers who came from my LinkedIn audience.",
+      "expected_output": "Should recognize this is an email sequence task, not social content. Should defer to or cross-reference the email-sequence skill, which handles welcome sequences, drip campaigns, and lifecycle emails. May note the social-to-email bridge context but should make clear that email-sequence is the right skill for writing email sequences.",
+      "assertions": [
+        "Recognizes this as email sequence work",
+        "References or defers to email-sequence skill",
+        "Does not attempt to write email sequence using social content patterns",
+        "May note social-to-email bridge context"
+      ],
+      "files": []
+    }
+  ]
+}
@@ -0,0 +1,110 @@
+# Platform Limits Reference
+
+Quick reference for hashtag limits, character counts, and visible text thresholds on each major social platform.
+
+---
+
+## Instagram
+
+| Element | Limit |
+|---------|-------|
+| Max hashtags | 5 (official limit) |
+| Recommended hashtags | 3 – 5 |
+| Max caption chars | 2,200 |
+| Visible before "more" | ~125 chars |
+
+---
+
+## Facebook
+
+| Element | Limit |
+|---------|-------|
+| Max hashtags | No official limit |
+| Recommended hashtags | 1 – 2 |
+| Max post chars | 63,206 |
+| Ideal for engagement | 40 – 80 chars |
+
+---
+
+## TikTok
+
+| Element | Limit |
+|---------|-------|
+| Max hashtags | 5 (since August 2025) |
+| Recommended hashtags | 3 – 5 |
+| Max caption chars | 4,000 |
+| Visible before "more" | ~150 chars |
+
+---
+
+## LinkedIn
+
+| Element | Limit |
+|---------|-------|
+| Max hashtags | No official limit |
+| Recommended hashtags | 3 – 5 |
+| Max post chars | 3,000 |
+| Visible before "more" | ~210 chars |
+
+---
+
+## Twitter/X
+
+| Element | Limit |
+|---------|-------|
+| Max hashtags | No official limit |
+| Recommended hashtags | 1 – 2 |
+| Max tweet chars | 280 (standard) / 25,000 (Premium+) |
+| Visible before "more" | Full tweet (280 standard) |
+
+---
+
+## YouTube
+
+| Element | Limit |
+|---------|-------|
+| Max hashtags | 15 (exceeding this causes YouTube to ignore ALL hashtags) |
+| Recommended hashtags | 3 – 5 |
+| Max title chars | 100 (visible before truncation: ~70) |
+| Max description chars | 5,000 |
+| Visible before "Show more" | ~100 chars |
+
+> The first 3 hashtags in the description automatically appear above the title as clickable links. For Shorts, use 1 – 5 hashtags.
+
+---
+
+## Pinterest
+
+| Element | Limit |
+|---------|-------|
+| Max hashtags | 20 per pin |
+| Recommended hashtags | 2 – 5 |
+| Max pin title chars | 100 |
+| Max description chars | 500 |
+| Visible before "More" | ~50 chars (desktop) |
+
+> Pinterest has deprioritized hashtags. Focus on keywords as natural sentences within the description for better SEO instead of relying on hashtags.
+
+---
+
+## Threads (Meta)
+
+| Element | Limit |
+|---------|-------|
+| Max hashtags | 1 per post (topic tag) |
+| Recommended hashtags | 1 |
+| Max post chars | 500 |
+| Max with text attachment | 10,500 (500 + 10,000 expandable) |
+| Visible without expanding | First ~1 – 2 lines |
+
+> Threads limits topic tags to one per post. The platform is not hashtag-driven — the algorithm prioritizes content from followed accounts mixed with recommendations.
+
+---
+
+## Usage Tips
+
+- **Hashtags count against character limits** on all platforms
+- **Front-load your message** before the "more" truncation point
+- On Instagram and TikTok, fewer hashtags now outperform hashtag-stuffing
+- On LinkedIn, hashtags at the end of the post perform better than inline
+- On Facebook, hashtags have minimal impact on reach — use sparingly
@@ -28,8 +28,13 @@ Quick reference for AI agents to discover tool capabilities and integration meth
 | keywords-everywhere | SEO | ✓ | - | [✓](clis/keywords-everywhere.js) | - | [keywords-everywhere.md](integrations/keywords-everywhere.md) |
 | clearbit | Data Enrichment | ✓ | - | [✓](clis/clearbit.js) | ✓ | [clearbit.md](integrations/clearbit.md) |
 | apollo | Data Enrichment | ✓ | - | [✓](clis/apollo.js) | - | [apollo.md](integrations/apollo.md) |
+| zoominfo | Data Enrichment | ✓ | ✓ | [✓](clis/zoominfo.js) | - | [zoominfo.md](integrations/zoominfo.md) |
+| clay | Data Enrichment | ✓ | ✓ | [✓](clis/clay.js) | - | [clay.md](integrations/clay.md) |
+| supermetrics | Data Aggregation | ✓ | ✓ | [✓](clis/supermetrics.js) | - | [supermetrics.md](integrations/supermetrics.md) |
+| coupler | Data Aggregation | ✓ | ✓ | [✓](clis/coupler.js) | - | [coupler.md](integrations/coupler.md) |
 | hubspot | CRM | ✓ | - | ✓ | ✓ | [hubspot.md](integrations/hubspot.md) |
 | salesforce | CRM | ✓ | - | ✓ | ✓ | [salesforce.md](integrations/salesforce.md) |
+| close | CRM | ✓ | - | [✓](clis/close.js) | - | [close.md](integrations/close.md) |
 | stripe | Payments | ✓ | ✓ | ✓ | ✓ | [stripe.md](integrations/stripe.md) |
 | paddle | Payments | ✓ | - | [✓](clis/paddle.js) | ✓ | [paddle.md](integrations/paddle.md) |
 | rewardful | Referral | ✓ | - | [✓](clis/rewardful.js) | - | [rewardful.md](integrations/rewardful.md) |
@@ -41,6 +46,7 @@ Quick reference for AI agents to discover tool capabilities and integration meth
 | customer-io | Email | ✓ | - | [✓](clis/customer-io.js) | ✓ | [customer-io.md](integrations/customer-io.md) |
 | sendgrid | Email | ✓ | - | [✓](clis/sendgrid.js) | ✓ | [sendgrid.md](integrations/sendgrid.md) |
 | resend | Email | ✓ | ✓ | [✓](clis/resend.js) | ✓ | [resend.md](integrations/resend.md) |
+| nitrosend | Email | ✓ | ✓ | - | - | [nitrosend.md](integrations/nitrosend.md) |
 | kit | Email | ✓ | - | [✓](clis/kit.js) | ✓ | [kit.md](integrations/kit.md) |
 | beehiiv | Newsletter | ✓ | - | [✓](clis/beehiiv.js) | - | [beehiiv.md](integrations/beehiiv.md) |
 | klaviyo | Email/SMS | ✓ | - | [✓](clis/klaviyo.js) | ✓ | [klaviyo.md](integrations/klaviyo.md) |
@@ -62,6 +68,16 @@ Quick reference for AI agents to discover tool capabilities and integration meth
 | savvycal | Scheduling | ✓ | - | [✓](clis/savvycal.js) | - | [savvycal.md](integrations/savvycal.md) |
 | typeform | Forms | ✓ | - | [✓](clis/typeform.js) | ✓ | [typeform.md](integrations/typeform.md) |
 | intercom | Messaging | ✓ | - | [✓](clis/intercom.js) | ✓ | [intercom.md](integrations/intercom.md) |
+| outreach | Sales Engagement | ✓ | ✓ | [✓](clis/outreach.js) | - | [outreach.md](integrations/outreach.md) |
+| crossbeam | Partner Ecosystem | ✓ | ✓ | [✓](clis/crossbeam.js) | - | [crossbeam.md](integrations/crossbeam.md) |
+| introw | Partner Ecosystem | - | ✓ | - | - | [introw.md](integrations/introw.md) |
+| pendo | Product Analytics | ✓ | - | [✓](clis/pendo.js) | - | [pendo.md](integrations/pendo.md) |
+| similarweb | Competitive Intelligence | ✓ | - | [✓](clis/similarweb.js) | - | [similarweb.md](integrations/similarweb.md) |
+| firehose | Competitive Intelligence | ✓ | - | - | - | [firehose.md](integrations/firehose.md) |
+| sparktoro | Audience Research | - | - | - | - | [sparktoro.md](integrations/sparktoro.md) |
+| rb2b | Visitor Identification | ✓ | - | - | - | [rb2b.md](integrations/rb2b.md) |
+| gong | Revenue Intelligence | ✓ | - | - | - | [gong.md](integrations/gong.md) |
+| airops | AI Content | ✓ | - | [✓](clis/airops.js) | - | [airops.md](integrations/airops.md) |
 | buffer | Social | ✓ | - | [✓](clis/buffer.js) | - | [buffer.md](integrations/buffer.md) |
 | wistia | Video | ✓ | - | [✓](clis/wistia.js) | - | [wistia.md](integrations/wistia.md) |
 | trustpilot | Reviews | ✓ | - | [✓](clis/trustpilot.js) | - | [trustpilot.md](integrations/trustpilot.md) |
@@ -72,6 +88,10 @@ Quick reference for AI agents to discover tool capabilities and integration meth
 | shopify | Commerce | ✓ | - | ✓ | ✓ | [shopify.md](integrations/shopify.md) |
 | wordpress | CMS | ✓ | - | ✓ | ✓ | [wordpress.md](integrations/wordpress.md) |
 | webflow | CMS | ✓ | - | ✓ | ✓ | [webflow.md](integrations/webflow.md) |
+| sanity | Headless CMS | ✓ | - | ✓ | ✓ | [sanity.md](integrations/sanity.md) |
+| contentful | Headless CMS | ✓ | - | ✓ | ✓ | [contentful.md](integrations/contentful.md) |
+| strapi | Headless CMS | ✓ | - | ✓ | ✓ | [strapi.md](integrations/strapi.md) |
+| composio | Integration Layer | ✓ | ✓ | ✓ | ✓ | [composio.md](integrations/composio.md) |

 ---

@@ -115,8 +135,9 @@ Customer relationship management and sales tools.
 |------|----------|:-------------:|
 | **hubspot** | SMB, marketing + sales alignment | ✓ |
 | **salesforce** | Enterprise, complex sales processes | ✓ |
+| **close** | SMB, high-velocity sales | [✓](clis/close.js) |

-**Agent recommendation**: HubSpot for startups/SMBs, Salesforce for enterprise.
+**Agent recommendation**: HubSpot for startups/SMBs. Close for high-velocity inside sales. Salesforce for enterprise.

 ### Payments

@@ -125,7 +146,6 @@ Payment processing and subscription management.
 | Tool | Best For | MCP Available |
 |------|----------|:-------------:|
 | **stripe** | SaaS subscriptions, developer-friendly | ✓ |
-
 | **paddle** | SaaS billing with tax handling | - |

 **Agent recommendation**: Stripe is the default for SaaS. Paddle for built-in tax compliance.
@@ -256,8 +276,10 @@ Company and person data enrichment for sales and marketing.
 |------|----------|-------|
 | **clearbit** | Company/person enrichment | Now HubSpot Breeze |
 | **apollo** | B2B prospecting, email finding | Large database |
+| **zoominfo** | B2B contacts, intent data | Enterprise-grade |
+| **clay** | Waterfall enrichment, outbound | 75+ data providers |

-**Agent recommendation**: Clearbit for enrichment. Apollo for prospecting and outbound.
+**Agent recommendation**: Clearbit for enrichment. Apollo for prospecting and outbound. ZoomInfo for enterprise B2B data with intent signals. Clay for waterfall enrichment across multiple providers.

 ### Reviews

@@ -291,6 +313,87 @@ Webinar and virtual event platforms.

 **Agent recommendation**: Demio for marketing-focused webinars. Livestorm for full event engagement.

+### Sales Engagement
+
+Sales engagement and outreach automation platforms.
+
+| Tool | Best For | Notes |
+|------|----------|-------|
+| **outreach** | Enterprise sales engagement | Sequences, tasks, analytics |
+
+**Agent recommendation**: Outreach for enterprise sales teams managing multi-touch sequences at scale.
+
+### Product Analytics
+
+Product analytics, feature adoption tracking, and in-app guidance.
+
+| Tool | Best For | Notes |
+|------|----------|-------|
+| **pendo** | Feature adoption, in-app guides | Product-led growth |
+
+**Agent recommendation**: Pendo for tracking feature adoption and delivering targeted in-app guidance.
+
+### Competitive Intelligence
+
+Traffic analytics, competitor benchmarking, and market research.
+
+| Tool | Best For | Notes |
+|------|----------|-------|
+| **similarweb** | Website traffic, competitor analysis | Traffic sources, keywords |
+
+**Agent recommendation**: Similarweb for competitor traffic analysis and market benchmarking.
+
+### Audience Research
+
+Audience intelligence and behavioral research tools.
+
+| Tool | Best For | Notes |
+|------|----------|-------|
+| **sparktoro** | Audience affinities, behavioral data | Clickstream + social data |
+
+**Agent recommendation**: SparkToro for discovering where your ICP spends time — what they read, watch, listen to, follow, and search for. Essential for customer research, content strategy, and media buying decisions.
+
+### Visitor Identification
+
+Website visitor de-anonymization for B2B sales and marketing.
+
+| Tool | Best For | Notes |
+|------|----------|-------|
+| **rb2b** | Person-level visitor ID, intent signals | LinkedIn profiles, emails, page-level data |
+
+**Agent recommendation**: RB2B for identifying anonymous B2B website visitors and routing high-intent visitors to outreach tools. Pairs well with Clay for enrichment and Instantly/Lemlist for cold email.
+
+### Revenue Intelligence
+
+Sales conversation analytics, call recording, and deal intelligence.
+
+| Tool | Best For | Notes |
+|------|----------|-------|
+| **gong** | Call recording, transcript analysis, deal insights | REST API, 10k API calls/day |
+
+**Agent recommendation**: Gong for mining sales call transcripts for customer research, competitive intelligence, and coaching insights. Essential for revenue attribution and win/loss analysis.
+
+### AI Content
+
+AI-powered content generation and optimization platforms.
+
+| Tool | Best For | Notes |
+|------|----------|-------|
+| **airops** | AI content workflows, SEO content | Flow-based automation |
+
+**Agent recommendation**: AirOps for building AI content workflows that generate SEO-optimized content at scale.
+
+### Partner Ecosystem
+
+Partner data sharing, co-sell, and ecosystem management.
+
+| Tool | Best For | Notes |
+|------|----------|-------|
+| **crossbeam** | Account overlaps, co-sell | Now part of Reveal |
+| **introw** | Partner management, deal registration, QBRs | MCP-enabled PRM |
+
+**Agent recommendation**: Crossbeam for identifying partner account overlaps and co-sell opportunities. Introw for full partner relationship management — partner pipeline, commissions, tasks, and automated business review prep.
+
 ### Email Outreach

 Cold email outreach and email finding tools for link building and sales prospecting.
@@ -304,6 +407,17 @@ Cold email outreach and email finding tools for link building and sales prospect

 **Agent recommendation**: Hunter for finding emails. Lemlist or Instantly for sending cold email campaigns. Snov for combined finding + outreach.

+### Data Aggregation
+
+Marketing data pipeline tools that connect multiple platforms for unified reporting.
+
+| Tool | Best For | Notes |
+|------|----------|-------|
+| **supermetrics** | Cross-platform data pulling | 200+ connectors |
+| **coupler** | Automated data flows to sheets/BI | Scheduled pipelines |
+
+**Agent recommendation**: Supermetrics for pulling data from multiple marketing platforms into unified reports. Coupler.io for automated data flows to spreadsheets and BI tools.
+
 ### Commerce & CMS

 E-commerce platforms and content management systems.
@@ -313,8 +427,11 @@ E-commerce platforms and content management systems.
 | **shopify** | E-commerce, product sales | ✓ |
 | **wordpress** | Blogs, content sites | ✓ |
 | **webflow** | Design-focused marketing sites | ✓ |
+| **sanity** | Headless CMS, structured content | ✓ |
+| **contentful** | Enterprise headless CMS, multi-locale | ✓ |
+| **strapi** | Open-source headless CMS, self-hosted | ✓ |

-**Agent recommendation**: Shopify for e-commerce. Webflow for marketing sites. WordPress for blogs.
+**Agent recommendation**: Shopify for e-commerce. Webflow for marketing sites. WordPress for blogs. For headless CMS: Sanity for developer-flexible content, Contentful for enterprise multi-locale, Strapi for self-hosted/budget-conscious. See [headless CMS guide](../skills/content-strategy/references/headless-cms.md) for selection criteria.

 ---

@@ -340,9 +457,26 @@ These tools have Model Context Protocol servers available, enabling direct agent
 - **google-ads** - Ad campaign management
 - **resend** - Transactional email sending
 - **zapier** - Workflow automation
+- **zoominfo** - B2B contacts and intent data
+- **clay** - Data enrichment and outbound automation
+- **supermetrics** - Cross-platform marketing data
+- **coupler** - Marketing data pipelines
+- **outreach** - Sales engagement sequences
+- **crossbeam** - Partner ecosystem data
+- **introw** - Partner relationship management

 To use MCP tools, ensure the appropriate MCP server is configured in your environment.

+### Composio Integration
+
+[Composio](integrations/composio.md) provides managed OAuth and pre-built connectors for 500+ tools via a single MCP server. It adds MCP access to tools that don't have native MCP servers, including HubSpot, Salesforce, Meta Ads, LinkedIn Ads, Google Sheets, Slack, Notion, and more.
+
+- **Setup**: `npx @composio/mcp@latest setup`
+- **Quick start**: See [tools/composio/README.md](composio/README.md)
+- **Marketing tool mapping**: See [tools/composio/marketing-tools.md](composio/marketing-tools.md)
+
+Use Composio when you need MCP access to OAuth-heavy tools. Prefer native MCP servers (GA4, Stripe, Mailchimp, etc.) when available — they have deeper coverage.
+
 ---

 ## Quick Start by Use Case
@@ -0,0 +1,163 @@
+#!/usr/bin/env node
+
+const API_KEY = process.env.AIROPS_API_KEY
+const WORKSPACE_ID = process.env.AIROPS_WORKSPACE_ID
+const BASE_URL = 'https://api.airops.com/public_api/v1'
+
+if (!API_KEY) {
+  console.error(JSON.stringify({ error: 'AIROPS_API_KEY environment variable required' }))
+  process.exit(1)
+}
+
+if (!WORKSPACE_ID) {
+  console.error(JSON.stringify({ error: 'AIROPS_WORKSPACE_ID environment variable required' }))
+  process.exit(1)
+}
+
+async function api(method, path, body) {
+  const url = `${BASE_URL}${path}`
+  if (args['dry-run']) {
+    return { _dry_run: true, method, url, headers: { 'Authorization': 'Bearer ***', 'Content-Type': 'application/json' }, body: body || undefined }
+  }
+  const res = await fetch(url, {
+    method,
+    headers: {
+      'Authorization': `Bearer ${API_KEY}`,
+      'Content-Type': 'application/json',
+      'Accept': 'application/json',
+    },
+    body: body ? JSON.stringify(body) : undefined,
+  })
+  const text = await res.text()
+  try {
+    return JSON.parse(text)
+  } catch {
+    return { status: res.status, body: text }
+  }
+}
+
+function parseArgs(args) {
+  const result = { _: [] }
+  for (let i = 0; i < args.length; i++) {
+    const arg = args[i]
+    if (arg.startsWith('--')) {
+      const key = arg.slice(2)
+      const next = args[i + 1]
+      if (next && !next.startsWith('--')) {
+        result[key] = next
+        i++
+      } else {
+        result[key] = true
+      }
+    } else {
+      result._.push(arg)
+    }
+  }
+  return result
+}
+
+const args = parseArgs(process.argv.slice(2))
+const [cmd, sub, ...rest] = args._
+
+async function main() {
+  let result
+
+  switch (cmd) {
+    case 'flows':
+      switch (sub) {
+        case 'list': {
+          result = await api('GET', `/workspaces/${WORKSPACE_ID}/flows`)
+          break
+        }
+        case 'get': {
+          const id = args.id
+          if (!id) { result = { error: '--id required' }; break }
+          result = await api('GET', `/workspaces/${WORKSPACE_ID}/flows/${id}`)
+          break
+        }
+        case 'execute': {
+          const id = args.id
+          if (!id) { result = { error: '--id required' }; break }
+          const inputs = args.inputs
+          let parsedInputs = {}
+          if (inputs) {
+            try {
+              parsedInputs = JSON.parse(inputs)
+            } catch {
+              result = { error: '--inputs must be valid JSON' }
+              break
+            }
+          }
+          result = await api('POST', `/workspaces/${WORKSPACE_ID}/flows/${id}/execute`, { inputs: parsedInputs })
+          break
+        }
+        case 'runs': {
+          const id = args.id
+          if (!id) { result = { error: '--id required' }; break }
+          result = await api('GET', `/workspaces/${WORKSPACE_ID}/flows/${id}/runs`)
+          break
+        }
+        case 'run-status': {
+          const runId = args['run-id']
+          if (!runId) { result = { error: '--run-id required' }; break }
+          result = await api('GET', `/workspaces/${WORKSPACE_ID}/runs/${runId}`)
+          break
+        }
+        default:
+          result = { error: 'Unknown flows subcommand. Use: list, get, execute, runs, run-status' }
+      }
+      break
+
+    case 'workflows':
+      switch (sub) {
+        case 'list': {
+          result = await api('GET', `/workspaces/${WORKSPACE_ID}/workflows`)
+          break
+        }
+        case 'execute': {
+          const id = args.id
+          if (!id) { result = { error: '--id required' }; break }
+          const inputs = args.inputs
+          let parsedInputs = {}
+          if (inputs) {
+            try {
+              parsedInputs = JSON.parse(inputs)
+            } catch {
+              result = { error: '--inputs must be valid JSON' }
+              break
+            }
+          }
+          result = await api('POST', `/workspaces/${WORKSPACE_ID}/workflows/${id}/execute`, { inputs: parsedInputs })
+          break
+        }
+        default:
+          result = { error: 'Unknown workflows subcommand. Use: list, execute' }
+      }
+      break
+
+    default:
+      result = {
+        error: 'Unknown command',
+        usage: {
+          flows: {
+            list: 'flows list',
+            get: 'flows get --id <id>',
+            execute: 'flows execute --id <id> --inputs <json>',
+            runs: 'flows runs --id <id>',
+            'run-status': 'flows run-status --run-id <id>',
+          },
+          workflows: {
+            list: 'workflows list',
+            execute: 'workflows execute --id <id> --inputs <json>',
+          },
+        }
+      }
+  }
+
+  console.log(JSON.stringify(result, null, 2))
+}
+
+main().catch(err => {
+  console.error(JSON.stringify({ error: err.message }))
+  process.exit(1)
+})
@@ -0,0 +1,159 @@
+#!/usr/bin/env node
+
+const API_KEY = process.env.CLAY_API_KEY
+const BASE_URL = 'https://api.clay.com/v3'
+
+if (!API_KEY) {
+  console.error(JSON.stringify({ error: 'CLAY_API_KEY environment variable required' }))
+  process.exit(1)
+}
+
+async function api(method, path, body) {
+  if (args['dry-run']) {
+    return { _dry_run: true, method, url: `${BASE_URL}${path}`, headers: { 'Authorization': 'Bearer ***', 'Content-Type': 'application/json' }, body: body || undefined }
+  }
+  const options = {
+    method,
+    headers: {
+      'Authorization': `Bearer ${API_KEY}`,
+      'Content-Type': 'application/json',
+    },
+  }
+  if (body) options.body = JSON.stringify(body)
+  const res = await fetch(`${BASE_URL}${path}`, options)
+  const text = await res.text()
+  try {
+    return JSON.parse(text)
+  } catch {
+    return { status: res.status, body: text }
+  }
+}
+
+function parseArgs(args) {
+  const result = { _: [] }
+  for (let i = 0; i < args.length; i++) {
+    const arg = args[i]
+    if (arg.startsWith('--')) {
+      const key = arg.slice(2)
+      const next = args[i + 1]
+      if (next && !next.startsWith('--')) {
+        result[key] = next
+        i++
+      } else {
+        result[key] = true
+      }
+    } else {
+      result._.push(arg)
+    }
+  }
+  return result
+}
+
+const args = parseArgs(process.argv.slice(2))
+const [cmd, sub, ...rest] = args._
+
+async function main() {
+  let result
+  const page = args.page ? Number(args.page) : 1
+  const perPage = args['per-page'] ? Number(args['per-page']) : 25
+
+  switch (cmd) {
+    case 'tables':
+      switch (sub) {
+        case 'list': {
+          result = await api('GET', `/tables?page=${page}&per_page=${perPage}`)
+          break
+        }
+        case 'get': {
+          const id = args.id
+          if (!id) { result = { error: '--id required' }; break }
+          result = await api('GET', `/tables/${id}`)
+          break
+        }
+        case 'rows': {
+          const id = args.id
+          if (!id) { result = { error: '--id required' }; break }
+          result = await api('GET', `/tables/${id}/rows?page=${page}&per_page=${perPage}`)
+          break
+        }
+        case 'add-row': {
+          const id = args.id
+          const data = args.data
+          if (!id) { result = { error: '--id required' }; break }
+          if (!data) { result = { error: '--data required (JSON string)' }; break }
+          let parsed
+          try {
+            parsed = JSON.parse(data)
+          } catch {
+            result = { error: 'Invalid JSON in --data' }
+            break
+          }
+          result = await api('POST', `/tables/${id}/rows`, parsed)
+          break
+        }
+        default:
+          result = { error: 'Unknown tables subcommand. Use: list, get, rows, add-row' }
+      }
+      break
+
+    case 'people':
+      switch (sub) {
+        case 'enrich': {
+          const body = {}
+          if (args.email) body.email = args.email
+          if (args.linkedin) body.linkedin_url = args.linkedin
+          if (args['first-name']) body.first_name = args['first-name']
+          if (args['last-name']) body.last_name = args['last-name']
+          if (args['first-name'] && args['last-name'] && args.domain) body.domain = args.domain
+          if (!args.email && !args.linkedin && !(args['first-name'] && args['last-name'] && args.domain)) {
+            result = { error: '--email or --linkedin required (or --first-name + --last-name + --domain)' }
+            break
+          }
+          result = await api('POST', '/people/enrich', body)
+          break
+        }
+        default:
+          result = { error: 'Unknown people subcommand. Use: enrich' }
+      }
+      break
+
+    case 'companies':
+      switch (sub) {
+        case 'enrich': {
+          const domain = args.domain
+          if (!domain) { result = { error: '--domain required' }; break }
+          result = await api('POST', '/companies/enrich', { domain })
+          break
+        }
+        default:
+          result = { error: 'Unknown companies subcommand. Use: enrich' }
+      }
+      break
+
+    default:
+      result = {
+        error: 'Unknown command',
+        usage: {
+          tables: {
+            list: 'tables list [--page <n>] [--per-page <n>]',
+            get: 'tables get --id <table_id>',
+            rows: 'tables rows --id <table_id> [--page <n>] [--per-page <n>]',
+            'add-row': 'tables add-row --id <table_id> --data <json>',
+          },
+          people: {
+            enrich: 'people enrich --email <email> | --linkedin <url> | --first-name <n> --last-name <n> --domain <d>',
+          },
+          companies: {
+            enrich: 'companies enrich --domain <domain>',
+          },
+        }
+      }
+  }
+
+  console.log(JSON.stringify(result, null, 2))
+}
+
+main().catch(err => {
+  console.error(JSON.stringify({ error: err.message }))
+  process.exit(1)
+})
@@ -0,0 +1,232 @@
+#!/usr/bin/env node
+
+const API_KEY = process.env.CLOSE_API_KEY
+const BASE_URL = 'https://api.close.com/api/v1'
+
+if (!API_KEY) {
+  console.error(JSON.stringify({ error: 'CLOSE_API_KEY environment variable required' }))
+  process.exit(1)
+}
+
+async function api(method, path, body) {
+  const url = `${BASE_URL}${path}`
+  if (args['dry-run']) {
+    return { _dry_run: true, method, url, headers: { 'Content-Type': 'application/json', 'Authorization': 'Basic ***' }, body: body || undefined }
+  }
+  const res = await fetch(url, {
+    method,
+    headers: {
+      'Content-Type': 'application/json',
+      'Accept': 'application/json',
+      'Authorization': `Basic ${btoa(API_KEY + ':')}`,
+    },
+    body: body ? JSON.stringify(body) : undefined,
+  })
+  const text = await res.text()
+  try {
+    return JSON.parse(text)
+  } catch {
+    return { status: res.status, body: text }
+  }
+}
+
+function parseArgs(args) {
+  const result = { _: [] }
+  for (let i = 0; i < args.length; i++) {
+    const arg = args[i]
+    if (arg.startsWith('--')) {
+      const key = arg.slice(2)
+      const next = args[i + 1]
+      if (next && !next.startsWith('--')) {
+        result[key] = next
+        i++
+      } else {
+        result[key] = true
+      }
+    } else {
+      result._.push(arg)
+    }
+  }
+  return result
+}
+
+const args = parseArgs(process.argv.slice(2))
+const [cmd, sub, ...rest] = args._
+
+async function main() {
+  let result
+
+  switch (cmd) {
+    case 'leads':
+      switch (sub) {
+        case 'list': {
+          const params = new URLSearchParams()
+          if (args.query) params.set('query', args.query)
+          if (args.page) params.set('_skip', (parseInt(args.page) - 1) * 100)
+          const qs = params.toString()
+          result = await api('GET', `/lead/${qs ? '?' + qs : ''}`)
+          break
+        }
+        case 'get': {
+          const id = args.id
+          if (!id) { result = { error: '--id required' }; break }
+          result = await api('GET', `/lead/${id}/`)
+          break
+        }
+        case 'create': {
+          const name = args.name
+          if (!name) { result = { error: '--name required' }; break }
+          const body = { name }
+          if (args.url) body.url = args.url
+          if (args.description) body.description = args.description
+          result = await api('POST', '/lead/', body)
+          break
+        }
+        default:
+          result = { error: 'Unknown leads subcommand. Use: list, get, create' }
+      }
+      break
+
+    case 'contacts':
+      switch (sub) {
+        case 'list': {
+          const params = new URLSearchParams()
+          if (args['lead-id']) params.set('lead_id', args['lead-id'])
+          const qs = params.toString()
+          result = await api('GET', `/contact/${qs ? '?' + qs : ''}`)
+          break
+        }
+        case 'get': {
+          const id = args.id
+          if (!id) { result = { error: '--id required' }; break }
+          result = await api('GET', `/contact/${id}/`)
+          break
+        }
+        case 'create': {
+          const leadId = args['lead-id']
+          const name = args.name
+          if (!leadId) { result = { error: '--lead-id required' }; break }
+          if (!name) { result = { error: '--name required' }; break }
+          const body = { lead_id: leadId, name }
+          if (args.email) {
+            body.emails = [{ email: args.email, type: 'office' }]
+          }
+          if (args.phone) {
+            body.phones = [{ phone: args.phone, type: 'office' }]
+          }
+          result = await api('POST', '/contact/', body)
+          break
+        }
+        default:
+          result = { error: 'Unknown contacts subcommand. Use: list, get, create' }
+      }
+      break
+
+    case 'opportunities':
+      switch (sub) {
+        case 'list': {
+          const params = new URLSearchParams()
+          if (args.status) params.set('status', args.status)
+          const qs = params.toString()
+          result = await api('GET', `/opportunity/${qs ? '?' + qs : ''}`)
+          break
+        }
+        case 'get': {
+          const id = args.id
+          if (!id) { result = { error: '--id required' }; break }
+          result = await api('GET', `/opportunity/${id}/`)
+          break
+        }
+        case 'create': {
+          const leadId = args['lead-id']
+          const value = args.value
+          if (!leadId) { result = { error: '--lead-id required' }; break }
+          if (!value) { result = { error: '--value required (in cents)' }; break }
+          const body = { lead_id: leadId, value: parseInt(value) }
+          if (args.status) body.status_type = args.status
+          result = await api('POST', '/opportunity/', body)
+          break
+        }
+        default:
+          result = { error: 'Unknown opportunities subcommand. Use: list, get, create' }
+      }
+      break
+
+    case 'activities':
+      switch (sub) {
+        case 'list': {
+          const params = new URLSearchParams()
+          if (args['lead-id']) params.set('lead_id', args['lead-id'])
+          if (args.type) params.set('_type__type', args.type)
+          const qs = params.toString()
+          result = await api('GET', `/activity/${qs ? '?' + qs : ''}`)
+          break
+        }
+        default:
+          result = { error: 'Unknown activities subcommand. Use: list' }
+      }
+      break
+
+    case 'tasks':
+      switch (sub) {
+        case 'list': {
+          const params = new URLSearchParams()
+          if (args['assigned-to']) params.set('assigned_to', args['assigned-to'])
+          if (args['is-complete']) params.set('is_complete', args['is-complete'])
+          const qs = params.toString()
+          result = await api('GET', `/task/${qs ? '?' + qs : ''}`)
+          break
+        }
+        case 'create': {
+          const leadId = args['lead-id']
+          const text = args.text
+          if (!leadId) { result = { error: '--lead-id required' }; break }
+          if (!text) { result = { error: '--text required' }; break }
+          const body = { lead_id: leadId, text, _type: 'lead' }
+          if (args['assigned-to']) body.assigned_to = args['assigned-to']
+          if (args.date) body.date = args.date
+          result = await api('POST', '/task/', body)
+          break
+        }
+        default:
+          result = { error: 'Unknown tasks subcommand. Use: list, create' }
+      }
+      break
+
+    default:
+      result = {
+        error: 'Unknown command',
+        usage: {
+          leads: {
+            list: 'leads list [--query <q>] [--page <n>]',
+            get: 'leads get --id <id>',
+            create: 'leads create --name <name> [--url <url>] [--description <desc>]',
+          },
+          contacts: {
+            list: 'contacts list [--lead-id <id>]',
+            get: 'contacts get --id <id>',
+            create: 'contacts create --lead-id <id> --name <name> [--email <email>] [--phone <phone>]',
+          },
+          opportunities: {
+            list: 'opportunities list [--status <status>]',
+            get: 'opportunities get --id <id>',
+            create: 'opportunities create --lead-id <id> --value <cents> [--status <status>]',
+          },
+          activities: {
+            list: 'activities list [--lead-id <id>] [--type <type>]',
+          },
+          tasks: {
+            list: 'tasks list [--assigned-to <user-id>] [--is-complete <bool>]',
+            create: 'tasks create --lead-id <id> --text <text> [--assigned-to <user-id>] [--date <date>]',
+          },
+        }
+      }
+  }
+
+  console.log(JSON.stringify(result, null, 2))
+}
+
+main().catch(err => {
+  console.error(JSON.stringify({ error: err.message }))
+  process.exit(1)
+})
@@ -0,0 +1,173 @@
+#!/usr/bin/env node
+
+const API_KEY = process.env.COUPLER_API_KEY
+const BASE_URL = 'https://api.coupler.io/v1'
+
+if (!API_KEY) {
+  console.error(JSON.stringify({ error: 'COUPLER_API_KEY environment variable required' }))
+  process.exit(1)
+}
+
+async function api(method, path, body) {
+  if (args['dry-run']) {
+    return { _dry_run: true, method, url: `${BASE_URL}${path}`, headers: { 'Authorization': 'Bearer ***', 'Content-Type': 'application/json' }, body: body || undefined }
+  }
+  const res = await fetch(`${BASE_URL}${path}`, {
+    method,
+    headers: {
+      'Authorization': `Bearer ${API_KEY}`,
+      'Content-Type': 'application/json',
+    },
+    body: body ? JSON.stringify(body) : undefined,
+  })
+  const text = await res.text()
+  try {
+    return JSON.parse(text)
+  } catch {
+    return { status: res.status, body: text }
+  }
+}
+
+function parseArgs(args) {
+  const result = { _: [] }
+  for (let i = 0; i < args.length; i++) {
+    const arg = args[i]
+    if (arg.startsWith('--')) {
+      const key = arg.slice(2)
+      const next = args[i + 1]
+      if (next && !next.startsWith('--')) {
+        result[key] = next
+        i++
+      } else {
+        result[key] = true
+      }
+    } else {
+      result._.push(arg)
+    }
+  }
+  return result
+}
+
+const args = parseArgs(process.argv.slice(2))
+const [cmd, sub, ...rest] = args._
+
+async function main() {
+  let result
+
+  switch (cmd) {
+    case 'importers':
+      switch (sub) {
+        case 'list': {
+          const params = new URLSearchParams()
+          if (args.limit) params.set('limit', args.limit)
+          if (args.offset) params.set('offset', args.offset)
+          const qs = params.toString()
+          result = await api('GET', `/importers${qs ? '?' + qs : ''}`)
+          break
+        }
+        case 'get': {
+          const id = args.id
+          if (!id) { result = { error: '--id required' }; break }
+          result = await api('GET', `/importers/${id}`)
+          break
+        }
+        case 'run': {
+          const id = args.id
+          if (!id) { result = { error: '--id required' }; break }
+          result = await api('POST', `/importers/${id}/run`)
+          break
+        }
+        case 'create': {
+          const source = args.source
+          const destination = args.destination
+          const name = args.name
+          if (!source) { result = { error: '--source required' }; break }
+          if (!destination) { result = { error: '--destination required' }; break }
+          if (!name) { result = { error: '--name required' }; break }
+          const body = { source_type: source, destination_type: destination, name }
+          if (args.schedule) body.schedule = args.schedule
+          result = await api('POST', '/importers', body)
+          break
+        }
+        case 'delete': {
+          const id = args.id
+          if (!id) { result = { error: '--id required' }; break }
+          result = await api('DELETE', `/importers/${id}`)
+          break
+        }
+        default:
+          result = { error: 'Unknown importers subcommand. Use: list, get, run, create, delete' }
+      }
+      break
+
+    case 'runs':
+      switch (sub) {
+        case 'list': {
+          const importerId = args['importer-id']
+          if (!importerId) { result = { error: '--importer-id required' }; break }
+          const params = new URLSearchParams()
+          if (args.limit) params.set('limit', args.limit)
+          if (args.offset) params.set('offset', args.offset)
+          const qs = params.toString()
+          result = await api('GET', `/importers/${importerId}/runs${qs ? '?' + qs : ''}`)
+          break
+        }
+        case 'get': {
+          const id = args.id
+          if (!id) { result = { error: '--id required' }; break }
+          result = await api('GET', `/runs/${id}`)
+          break
+        }
+        default:
+          result = { error: 'Unknown runs subcommand. Use: list, get' }
+      }
+      break
+
+    case 'sources':
+      switch (sub) {
+        case 'list':
+          result = await api('GET', '/sources')
+          break
+        default:
+          result = { error: 'Unknown sources subcommand. Use: list' }
+      }
+      break
+
+    case 'destinations':
+      switch (sub) {
+        case 'list':
+          result = await api('GET', '/destinations')
+          break
+        default:
+          result = { error: 'Unknown destinations subcommand. Use: list' }
+      }
+      break
+
+    default:
+      result = {
+        error: 'Unknown command',
+        usage: {
+          importers: {
+            list: 'importers list [--limit <n>] [--offset <n>]',
+            get: 'importers get --id <id>',
+            run: 'importers run --id <id>',
+            create: 'importers create --source <source-type> --destination <dest-type> --name <name> [--schedule <schedule>]',
+            delete: 'importers delete --id <id>',
+          },
+          runs: {
+            list: 'runs list --importer-id <id> [--limit <n>] [--offset <n>]',
+            get: 'runs get --id <id>',
+          },
+          sources: 'sources list',
+          destinations: 'destinations list',
+        }
+      }
+  }
+
+  console.log(JSON.stringify(result, null, 2))
+}
+
+main().catch(err => {
+  console.error(JSON.stringify({ error: err.message }))
+  process.exit(1)
+})
@@ -0,0 +1,193 @@
+#!/usr/bin/env node
+
+const API_KEY = process.env.CROSSBEAM_API_KEY
+const BASE_URL = 'https://api.crossbeam.com/v1'
+
+if (!API_KEY) {
+  console.error(JSON.stringify({ error: 'CROSSBEAM_API_KEY environment variable required' }))
+  process.exit(1)
+}
+
+async function api(method, path, body) {
+  const url = `${BASE_URL}${path}`
+  if (args['dry-run']) {
+    return { _dry_run: true, method, url, headers: { 'Authorization': 'Bearer ***', 'Content-Type': 'application/json' }, body: body || undefined }
+  }
+  const res = await fetch(url, {
+    method,
+    headers: {
+      'Authorization': `Bearer ${API_KEY}`,
+      'Content-Type': 'application/json',
+      'Accept': 'application/json',
+    },
+    body: body ? JSON.stringify(body) : undefined,
+  })
+  const text = await res.text()
+  try {
+    return JSON.parse(text)
+  } catch {
+    return { status: res.status, body: text }
+  }
+}
+
+function parseArgs(args) {
+  const result = { _: [] }
+  for (let i = 0; i < args.length; i++) {
+    const arg = args[i]
+    if (arg.startsWith('--')) {
+      const key = arg.slice(2)
+      const next = args[i + 1]
+      if (next && !next.startsWith('--')) {
+        result[key] = next
+        i++
+      } else {
+        result[key] = true
+      }
+    } else {
+      result._.push(arg)
+    }
+  }
+  return result
+}
+
+const args = parseArgs(process.argv.slice(2))
+const [cmd, sub, ...rest] = args._
+
+async function main() {
+  let result
+
+  switch (cmd) {
+    case 'partners':
+      switch (sub) {
+        case 'list': {
+          result = await api('GET', '/partners')
+          break
+        }
+        case 'get': {
+          const id = args.id
+          if (!id) { result = { error: '--id required' }; break }
+          result = await api('GET', `/partners/${id}`)
+          break
+        }
+        default:
+          result = { error: 'Unknown partners subcommand. Use: list, get' }
+      }
+      break
+
+    case 'populations':
+      switch (sub) {
+        case 'list': {
+          result = await api('GET', '/populations')
+          break
+        }
+        case 'get': {
+          const id = args.id
+          if (!id) { result = { error: '--id required' }; break }
+          result = await api('GET', `/populations/${id}`)
+          break
+        }
+        default:
+          result = { error: 'Unknown populations subcommand. Use: list, get' }
+      }
+      break
+
+    case 'overlaps':
+      switch (sub) {
+        case 'list': {
+          const params = new URLSearchParams()
+          if (args['partner-id']) params.set('partner_id', args['partner-id'])
+          if (args['population-id']) params.set('population_id', args['population-id'])
+          const qs = params.toString()
+          result = await api('GET', `/overlaps${qs ? '?' + qs : ''}`)
+          break
+        }
+        case 'get': {
+          const id = args.id
+          if (!id) { result = { error: '--id required' }; break }
+          result = await api('GET', `/overlaps/${id}`)
+          break
+        }
+        default:
+          result = { error: 'Unknown overlaps subcommand. Use: list, get' }
+      }
+      break
+
+    case 'reports':
+      switch (sub) {
+        case 'list': {
+          result = await api('GET', '/reports')
+          break
+        }
+        case 'get': {
+          const id = args.id
+          if (!id) { result = { error: '--id required' }; break }
+          result = await api('GET', `/reports/${id}`)
+          break
+        }
+        default:
+          result = { error: 'Unknown reports subcommand. Use: list, get' }
+      }
+      break
+
+    case 'threads':
+      switch (sub) {
+        case 'list': {
+          result = await api('GET', '/threads')
+          break
+        }
+        default:
+          result = { error: 'Unknown threads subcommand. Use: list' }
+      }
+      break
+
+    case 'accounts':
+      switch (sub) {
+        case 'search': {
+          const domain = args.domain
+          if (!domain) { result = { error: '--domain required' }; break }
+          const params = new URLSearchParams({ domain })
+          result = await api('GET', `/accounts/search?${params.toString()}`)
+          break
+        }
+        default:
+          result = { error: 'Unknown accounts subcommand. Use: search' }
+      }
+      break
+
+    default:
+      result = {
+        error: 'Unknown command',
+        usage: {
+          partners: {
+            list: 'partners list',
+            get: 'partners get --id <id>',
+          },
+          populations: {
+            list: 'populations list',
+            get: 'populations get --id <id>',
+          },
+          overlaps: {
+            list: 'overlaps list [--partner-id <id>] [--population-id <id>]',
+            get: 'overlaps get --id <id>',
+          },
+          reports: {
+            list: 'reports list',
+            get: 'reports get --id <id>',
+          },
+          threads: {
+            list: 'threads list',
+          },
+          accounts: {
+            search: 'accounts search --domain <domain>',
+          },
+        }
+      }
+  }
+
+  console.log(JSON.stringify(result, null, 2))
+}
+
+main().catch(err => {
+  console.error(JSON.stringify({ error: err.message }))
+  process.exit(1)
+})
@@ -0,0 +1,213 @@
+#!/usr/bin/env node
+
+const ACCESS_TOKEN = process.env.OUTREACH_ACCESS_TOKEN
+const BASE_URL = 'https://api.outreach.io/api/v2'
+
+if (!ACCESS_TOKEN) {
+  console.error(JSON.stringify({ error: 'OUTREACH_ACCESS_TOKEN environment variable required' }))
+  process.exit(1)
+}
+
+async function api(method, path, body) {
+  const url = `${BASE_URL}${path}`
+  if (args['dry-run']) {
+    return { _dry_run: true, method, url, headers: { 'Authorization': 'Bearer ***', 'Content-Type': 'application/vnd.api+json', 'Accept': 'application/vnd.api+json' }, body: body || undefined }
+  }
+  const res = await fetch(url, {
+    method,
+    headers: {
+      'Authorization': `Bearer ${ACCESS_TOKEN}`,
+      'Content-Type': 'application/vnd.api+json',
+      'Accept': 'application/vnd.api+json',
+    },
+    body: body ? JSON.stringify(body) : undefined,
+  })
+  const text = await res.text()
+  try {
+    return JSON.parse(text)
+  } catch {
+    return { status: res.status, body: text }
+  }
+}
+
+function parseArgs(args) {
+  const result = { _: [] }
+  for (let i = 0; i < args.length; i++) {
+    const arg = args[i]
+    if (arg.startsWith('--')) {
+      const key = arg.slice(2)
+      const next = args[i + 1]
+      if (next && !next.startsWith('--')) {
+        result[key] = next
+        i++
+      } else {
+        result[key] = true
+      }
+    } else {
+      result._.push(arg)
+    }
+  }
+  return result
+}
+
+const args = parseArgs(process.argv.slice(2))
+const [cmd, sub, ...rest] = args._
+
+async function main() {
+  let result
+
+  switch (cmd) {
+    case 'prospects':
+      switch (sub) {
+        case 'list': {
+          const params = new URLSearchParams()
+          if (args.page) params.set('page[number]', args.page)
+          if (args['per-page']) params.set('page[size]', args['per-page'])
+          const qs = params.toString()
+          result = await api('GET', `/prospects${qs ? '?' + qs : ''}`)
+          break
+        }
+        case 'get': {
+          const id = args.id
+          if (!id) { result = { error: '--id required' }; break }
+          result = await api('GET', `/prospects/${id}`)
+          break
+        }
+        case 'create': {
+          const email = args.email
+          if (!email) { result = { error: '--email required' }; break }
+          const attributes = { emails: [email] }
+          if (args['first-name']) attributes.firstName = args['first-name']
+          if (args['last-name']) attributes.lastName = args['last-name']
+          const body = { data: { type: 'prospect', attributes } }
+          result = await api('POST', '/prospects', body)
+          break
+        }
+        default:
+          result = { error: 'Unknown prospects subcommand. Use: list, get, create' }
+      }
+      break
+
+    case 'sequences':
+      switch (sub) {
+        case 'list': {
+          result = await api('GET', '/sequences')
+          break
+        }
+        case 'get': {
+          const id = args.id
+          if (!id) { result = { error: '--id required' }; break }
+          result = await api('GET', `/sequences/${id}`)
+          break
+        }
+        default:
+          result = { error: 'Unknown sequences subcommand. Use: list, get' }
+      }
+      break
+
+    case 'sequence-states':
+      switch (sub) {
+        case 'create': {
+          const sequenceId = args['sequence-id']
+          const prospectId = args['prospect-id']
+          if (!sequenceId) { result = { error: '--sequence-id required' }; break }
+          if (!prospectId) { result = { error: '--prospect-id required' }; break }
+          const body = {
+            data: {
+              type: 'sequenceState',
+              relationships: {
+                prospect: { data: { type: 'prospect', id: prospectId } },
+                sequence: { data: { type: 'sequence', id: sequenceId } },
+              },
+            },
+          }
+          result = await api('POST', '/sequenceStates', body)
+          break
+        }
+        default:
+          result = { error: 'Unknown sequence-states subcommand. Use: create' }
+      }
+      break
+
+    case 'mailings':
+      switch (sub) {
+        case 'list': {
+          const params = new URLSearchParams()
+          if (args['sequence-id']) params.set('filter[sequence][id]', args['sequence-id'])
+          const qs = params.toString()
+          result = await api('GET', `/mailings${qs ? '?' + qs : ''}`)
+          break
+        }
+        default:
+          result = { error: 'Unknown mailings subcommand. Use: list' }
+      }
+      break
+
+    case 'accounts':
+      switch (sub) {
+        case 'list': {
+          result = await api('GET', '/accounts')
+          break
+        }
+        case 'get': {
+          const id = args.id
+          if (!id) { result = { error: '--id required' }; break }
+          result = await api('GET', `/accounts/${id}`)
+          break
+        }
+        default:
+          result = { error: 'Unknown accounts subcommand. Use: list, get' }
+      }
+      break
+
+    case 'tasks':
+      switch (sub) {
+        case 'list': {
+          const params = new URLSearchParams()
+          if (args.status) params.set('filter[status]', args.status)
+          const qs = params.toString()
+          result = await api('GET', `/tasks${qs ? '?' + qs : ''}`)
+          break
+        }
+        default:
+          result = { error: 'Unknown tasks subcommand. Use: list' }
+      }
+      break
+
+    default:
+      result = {
+        error: 'Unknown command',
+        usage: {
+          prospects: {
+            list: 'prospects list [--page <n>] [--per-page <n>]',
+            get: 'prospects get --id <id>',
+            create: 'prospects create --email <email> [--first-name <name>] [--last-name <name>]',
+          },
+          sequences: {
+            list: 'sequences list',
+            get: 'sequences get --id <id>',
+          },
+          'sequence-states': {
+            create: 'sequence-states create --sequence-id <id> --prospect-id <id>',
+          },
+          mailings: {
+            list: 'mailings list [--sequence-id <id>]',
+          },
+          accounts: {
+            list: 'accounts list',
+            get: 'accounts get --id <id>',
+          },
+          tasks: {
+            list: 'tasks list [--status <status>]',
+          },
+        }
+      }
+  }
+
+  console.log(JSON.stringify(result, null, 2))
+}
+
+main().catch(err => {
+  console.error(JSON.stringify({ error: err.message }))
+  process.exit(1)
+})
@@ -0,0 +1,221 @@
+#!/usr/bin/env node
+
+const API_KEY = process.env.PENDO_INTEGRATION_KEY
+const BASE_URL = 'https://app.pendo.io/api/v1'
+
+if (!API_KEY) {
+  console.error(JSON.stringify({ error: 'PENDO_INTEGRATION_KEY environment variable required' }))
+  process.exit(1)
+}
+
+async function api(method, path, body) {
+  const url = `${BASE_URL}${path}`
+  if (args['dry-run']) {
+    return { _dry_run: true, method, url, headers: { 'Content-Type': 'application/json', 'x-pendo-integration-key': '***' }, body: body || undefined }
+  }
+  const res = await fetch(url, {
+    method,
+    headers: {
+      'Content-Type': 'application/json',
+      'x-pendo-integration-key': API_KEY,
+    },
+    body: body ? JSON.stringify(body) : undefined,
+  })
+  const text = await res.text()
+  try {
+    return JSON.parse(text)
+  } catch {
+    return { status: res.status, body: text }
+  }
+}
+
+function parseArgs(args) {
+  const result = { _: [] }
+  for (let i = 0; i < args.length; i++) {
+    const arg = args[i]
+    if (arg.startsWith('--')) {
+      const key = arg.slice(2)
+      const next = args[i + 1]
+      if (next && !next.startsWith('--')) {
+        result[key] = next
+        i++
+      } else {
+        result[key] = true
+      }
+    } else {
+      result._.push(arg)
+    }
+  }
+  return result
+}
+
+const args = parseArgs(process.argv.slice(2))
+const [cmd, sub, ...rest] = args._
+
+async function main() {
+  let result
+
+  switch (cmd) {
+    case 'features':
+      switch (sub) {
+        case 'list':
+          result = await api('GET', '/feature')
+          break
+        case 'get': {
+          const id = args.id
+          if (!id) { result = { error: '--id required' }; break }
+          result = await api('GET', `/feature/${id}`)
+          break
+        }
+        default:
+          result = { error: 'Unknown features subcommand. Use: list, get' }
+      }
+      break
+
+    case 'pages':
+      switch (sub) {
+        case 'list':
+          result = await api('GET', '/page')
+          break
+        case 'get': {
+          const id = args.id
+          if (!id) { result = { error: '--id required' }; break }
+          result = await api('GET', `/page/${id}`)
+          break
+        }
+        default:
+          result = { error: 'Unknown pages subcommand. Use: list, get' }
+      }
+      break
+
+    case 'guides':
+      switch (sub) {
+        case 'list': {
+          const params = new URLSearchParams()
+          if (args.state) params.set('state', args.state)
+          const qs = params.toString()
+          result = await api('GET', `/guide${qs ? '?' + qs : ''}`)
+          break
+        }
+        case 'get': {
+          const id = args.id
+          if (!id) { result = { error: '--id required' }; break }
+          result = await api('GET', `/guide/${id}`)
+          break
+        }
+        default:
+          result = { error: 'Unknown guides subcommand. Use: list, get' }
+      }
+      break
+
+    case 'visitors':
+      switch (sub) {
+        case 'get': {
+          const id = args.id
+          if (!id) { result = { error: '--id required' }; break }
+          result = await api('GET', `/visitor/${id}`)
+          break
+        }
+        case 'search': {
+          const query = args.query
+          if (!query) { result = { error: '--query <json> required' }; break }
+          let body
+          try { body = JSON.parse(query) } catch { result = { error: 'Invalid JSON in --query' }; break }
+          result = await api('POST', '/aggregation', body)
+          break
+        }
+        default:
+          result = { error: 'Unknown visitors subcommand. Use: get, search' }
+      }
+      break
+
+    case 'accounts':
+      switch (sub) {
+        case 'get': {
+          const id = args.id
+          if (!id) { result = { error: '--id required' }; break }
+          result = await api('GET', `/account/${id}`)
+          break
+        }
+        case 'search': {
+          const query = args.query
+          if (!query) { result = { error: '--query <json> required' }; break }
+          let body
+          try { body = JSON.parse(query) } catch { result = { error: 'Invalid JSON in --query' }; break }
+          result = await api('POST', '/aggregation', body)
+          break
+        }
+        default:
+          result = { error: 'Unknown accounts subcommand. Use: get, search' }
+      }
+      break
+
+    case 'reports':
+      switch (sub) {
+        case 'funnel': {
+          const pipeline = args.pipeline
+          if (!pipeline) { result = { error: '--pipeline <json> required' }; break }
+          let body
+          try { body = JSON.parse(pipeline) } catch { result = { error: 'Invalid JSON in --pipeline' }; break }
+          result = await api('POST', '/aggregation', body)
+          break
+        }
+        default:
+          result = { error: 'Unknown reports subcommand. Use: funnel' }
+      }
+      break
+
+    case 'metadata':
+      switch (sub) {
+        case 'list': {
+          const kind = args.kind
+          if (!kind) { result = { error: '--kind <visitor|account|parentAccount> required' }; break }
+          result = await api('GET', `/metadata/schema/${kind}`)
+          break
+        }
+        default:
+          result = { error: 'Unknown metadata subcommand. Use: list' }
+      }
+      break
+
+    default:
+      result = {
+        error: 'Unknown command',
+        usage: {
+          features: {
+            list: 'features list',
+            get: 'features get --id <id>',
+          },
+          pages: {
+            list: 'pages list',
+            get: 'pages get --id <id>',
+          },
+          guides: {
+            list: 'guides list [--state <state>]',
+            get: 'guides get --id <id>',
+          },
+          visitors: {
+            get: 'visitors get --id <id>',
+            search: 'visitors search --query <json>',
+          },
+          accounts: {
+            get: 'accounts get --id <id>',
+            search: 'accounts search --query <json>',
+          },
+          reports: {
+            funnel: 'reports funnel --pipeline <json>',
+          },
+          metadata: {
+            list: 'metadata list --kind <visitor|account|parentAccount>',
+          },
+        }
+      }
+  }
+
+  console.log(JSON.stringify(result, null, 2))
+}
+
+main().catch(err => {
+  console.error(JSON.stringify({ error: err.message }))
+  process.exit(1)
+})
@@ -0,0 +1,214 @@
+#!/usr/bin/env node
+
+const API_KEY = process.env.SIMILARWEB_API_KEY
+const BASE_URL = 'https://api.similarweb.com/v1'
+
+if (!API_KEY) {
+  console.error(JSON.stringify({ error: 'SIMILARWEB_API_KEY environment variable required' }))
+  process.exit(1)
+}
+
+async function api(method, path, body) {
+  const separator = path.includes('?') ? '&' : '?'
+  const url = `${BASE_URL}${path}${separator}api_key=${API_KEY}`
+  if (args['dry-run']) {
+    return { _dry_run: true, method, url: url.replace(API_KEY, '***'), headers: { 'Content-Type': 'application/json', 'Accept': 'application/json' }, body: body || undefined }
+  }
+  const res = await fetch(url, {
+    method,
+    headers: {
+      'Content-Type': 'application/json',
+      'Accept': 'application/json',
+    },
+    body: body ? JSON.stringify(body) : undefined,
+  })
+  const text = await res.text()
+  try {
+    return JSON.parse(text)
+  } catch {
+    return { status: res.status, body: text }
+  }
+}
+
+function parseArgs(args) {
+  const result = { _: [] }
+  for (let i = 0; i < args.length; i++) {
+    const arg = args[i]
+    if (arg.startsWith('--')) {
+      const key = arg.slice(2)
+      const next = args[i + 1]
+      if (next && !next.startsWith('--')) {
+        result[key] = next
+        i++
+      } else {
+        result[key] = true
+      }
+    } else {
+      result._.push(arg)
+    }
+  }
+  return result
+}
+
+const args = parseArgs(process.argv.slice(2))
+const [cmd, sub, ...rest] = args._
+
+async function main() {
+  let result
+
+  switch (cmd) {
+    case 'traffic':
+      switch (sub) {
+        case 'visits': {
+          const domain = args.domain
+          if (!domain) { result = { error: '--domain required' }; break }
+          if (!args.start) { result = { error: '--start required (YYYY-MM)' }; break }
+          if (!args.end) { result = { error: '--end required (YYYY-MM)' }; break }
+          const params = new URLSearchParams({ start_date: args.start, end_date: args.end })
+          if (args.country) params.set('country', args.country)
+          if (args.granularity) params.set('granularity', args.granularity)
+          result = await api('GET', `/website/${encodeURIComponent(domain)}/total-traffic-and-engagement/visits?${params.toString()}`)
+          break
+        }
+        case 'pages-per-visit': {
+          const domain = args.domain
+          if (!domain) { result = { error: '--domain required' }; break }
+          if (!args.start) { result = { error: '--start required (YYYY-MM)' }; break }
+          if (!args.end) { result = { error: '--end required (YYYY-MM)' }; break }
+          const params = new URLSearchParams({ start_date: args.start, end_date: args.end })
+          if (args.country) params.set('country', args.country)
+          if (args.granularity) params.set('granularity', args.granularity)
+          result = await api('GET', `/website/${encodeURIComponent(domain)}/total-traffic-and-engagement/pages-per-visit?${params.toString()}`)
+          break
+        }
+        case 'avg-duration': {
+          const domain = args.domain
+          if (!domain) { result = { error: '--domain required' }; break }
+          if (!args.start) { result = { error: '--start required (YYYY-MM)' }; break }
+          if (!args.end) { result = { error: '--end required (YYYY-MM)' }; break }
+          const params = new URLSearchParams({ start_date: args.start, end_date: args.end })
+          if (args.country) params.set('country', args.country)
+          if (args.granularity) params.set('granularity', args.granularity)
+          result = await api('GET', `/website/${encodeURIComponent(domain)}/total-traffic-and-engagement/average-visit-duration?${params.toString()}`)
+          break
+        }
+        case 'bounce-rate': {
+          const domain = args.domain
+          if (!domain) { result = { error: '--domain required' }; break }
+          if (!args.start) { result = { error: '--start required (YYYY-MM)' }; break }
+          if (!args.end) { result = { error: '--end required (YYYY-MM)' }; break }
+          const params = new URLSearchParams({ start_date: args.start, end_date: args.end })
+          if (args.country) params.set('country', args.country)
+          if (args.granularity) params.set('granularity', args.granularity)
+          result = await api('GET', `/website/${encodeURIComponent(domain)}/total-traffic-and-engagement/bounce-rate?${params.toString()}`)
+          break
+        }
+        case 'sources': {
+          const domain = args.domain
+          if (!domain) { result = { error: '--domain required' }; break }
+          if (!args.start) { result = { error: '--start required (YYYY-MM)' }; break }
+          if (!args.end) { result = { error: '--end required (YYYY-MM)' }; break }
+          const params = new URLSearchParams({ start_date: args.start, end_date: args.end })
+          if (args.country) params.set('country', args.country)
+          result = await api('GET', `/website/${encodeURIComponent(domain)}/traffic-sources/overview?${params.toString()}`)
+          break
+        }
+        default:
+          result = { error: 'Unknown traffic subcommand. Use: visits, pages-per-visit, avg-duration, bounce-rate, sources' }
+      }
+      break
+
+    case 'referrals': {
+      const domain = args.domain
+      if (!domain) { result = { error: '--domain required' }; break }
+      if (!args.start) { result = { error: '--start required (YYYY-MM)' }; break }
+      if (!args.end) { result = { error: '--end required (YYYY-MM)' }; break }
+      const params = new URLSearchParams({ start_date: args.start, end_date: args.end })
+      if (args.country) params.set('country', args.country)
+      result = await api('GET', `/website/${encodeURIComponent(domain)}/traffic-sources/referrals?${params.toString()}`)
+      break
+    }
+
+    case 'search':
+      switch (sub) {
+        case 'keywords-organic': {
+          const domain = args.domain
+          if (!domain) { result = { error: '--domain required' }; break }
+          if (!args.start) { result = { error: '--start required (YYYY-MM)' }; break }
+          if (!args.end) { result = { error: '--end required (YYYY-MM)' }; break }
+          const params = new URLSearchParams({ start_date: args.start, end_date: args.end })
+          if (args.country) params.set('country', args.country)
+          if (args.limit) params.set('limit', args.limit)
+          result = await api('GET', `/website/${encodeURIComponent(domain)}/search/organic-search-keywords?${params.toString()}`)
+          break
+        }
+        case 'keywords-paid': {
+          const domain = args.domain
+          if (!domain) { result = { error: '--domain required' }; break }
+          if (!args.start) { result = { error: '--start required (YYYY-MM)' }; break }
+          if (!args.end) { result = { error: '--end required (YYYY-MM)' }; break }
+          const params = new URLSearchParams({ start_date: args.start, end_date: args.end })
+          if (args.country) params.set('country', args.country)
+          if (args.limit) params.set('limit', args.limit)
+          result = await api('GET', `/website/${encodeURIComponent(domain)}/search/paid-search-keywords?${params.toString()}`)
+          break
+        }
+        default:
+          result = { error: 'Unknown search subcommand. Use: keywords-organic, keywords-paid' }
+      }
+      break
+
+    case 'competitors': {
+      const domain = args.domain
+      if (!domain) { result = { error: '--domain required' }; break }
+      result = await api('GET', `/website/${encodeURIComponent(domain)}/similar-sites/similarsites`)
+      break
+    }
+
+    case 'category-rank': {
+      const domain = args.domain
+      if (!domain) { result = { error: '--domain required' }; break }
+      result = await api('GET', `/website/${encodeURIComponent(domain)}/category-rank/category-rank`)
+      break
+    }
+
+    case 'geography': {
+      const domain = args.domain
+      if (!domain) { result = { error: '--domain required' }; break }
+      if (!args.start) { result = { error: '--start required (YYYY-MM)' }; break }
+      if (!args.end) { result = { error: '--end required (YYYY-MM)' }; break }
+      const params = new URLSearchParams({ start_date: args.start, end_date: args.end })
+      result = await api('GET', `/website/${encodeURIComponent(domain)}/geo/traffic-by-country?${params.toString()}`)
+      break
+    }
+
+    default:
+      result = {
+        error: 'Unknown command',
+        usage: {
+          traffic: {
+            visits: 'traffic visits --domain <domain> --start <YYYY-MM> --end <YYYY-MM> [--country <cc>] [--granularity <monthly|weekly|daily>]',
+            'pages-per-visit': 'traffic pages-per-visit --domain <domain> --start <YYYY-MM> --end <YYYY-MM>',
+            'avg-duration': 'traffic avg-duration --domain <domain> --start <YYYY-MM> --end <YYYY-MM>',
+            'bounce-rate': 'traffic bounce-rate --domain <domain> --start <YYYY-MM> --end <YYYY-MM>',
+            sources: 'traffic sources --domain <domain> --start <YYYY-MM> --end <YYYY-MM>',
+          },
+          referrals: 'referrals --domain <domain> --start <YYYY-MM> --end <YYYY-MM>',
+          search: {
+            'keywords-organic': 'search keywords-organic --domain <domain> --start <YYYY-MM> --end <YYYY-MM>',
+            'keywords-paid': 'search keywords-paid --domain <domain> --start <YYYY-MM> --end <YYYY-MM>',
+          },
+          competitors: 'competitors --domain <domain>',
+          'category-rank': 'category-rank --domain <domain>',
+          geography: 'geography --domain <domain> --start <YYYY-MM> --end <YYYY-MM>',
+        }
+      }
+  }
+
+  console.log(JSON.stringify(result, null, 2))
+}
+
+main().catch(err => {
+  console.error(JSON.stringify({ error: err.message }))
+  process.exit(1)
+})
@@ -0,0 +1,168 @@
+#!/usr/bin/env node
+
+const API_KEY = process.env.SUPERMETRICS_API_KEY
+const BASE_URL = 'https://api.supermetrics.com/enterprise/v2'
+
+if (!API_KEY) {
+  console.error(JSON.stringify({ error: 'SUPERMETRICS_API_KEY environment variable required' }))
+  process.exit(1)
+}
+
+async function api(method, path, body) {
+  const separator = path.includes('?') ? '&' : '?'
+  const url = `${BASE_URL}${path}${separator}api_key=${API_KEY}`
+  if (args['dry-run']) {
+    return { _dry_run: true, method, url: url.replace(API_KEY, '***'), headers: { 'Content-Type': 'application/json', 'Accept': 'application/json' }, body: body || undefined }
+  }
+  const res = await fetch(url, {
+    method,
+    headers: {
+      'Content-Type': 'application/json',
+      'Accept': 'application/json',
+    },
+    body: body ? JSON.stringify(body) : undefined,
+  })
+  const text = await res.text()
+  try {
+    return JSON.parse(text)
+  } catch {
+    return { status: res.status, body: text }
+  }
+}
+
+function parseArgs(args) {
+  const result = { _: [] }
+  for (let i = 0; i < args.length; i++) {
+    const arg = args[i]
+    if (arg.startsWith('--')) {
+      const key = arg.slice(2)
+      const next = args[i + 1]
+      if (next && !next.startsWith('--')) {
+        result[key] = next
+        i++
+      } else {
+        result[key] = true
+      }
+    } else {
+      result._.push(arg)
+    }
+  }
+  return result
+}
+
+const args = parseArgs(process.argv.slice(2))
+const [cmd, sub, ...rest] = args._
+
+async function main() {
+  let result
+
+  switch (cmd) {
+    case 'query': {
+      const dsId = args['ds-id']
+      const dsAccounts = args['ds-accounts']
+      const dateRange = args['date-range']
+      const fields = args.fields
+      if (!dsId) { result = { error: '--ds-id required (e.g., GA4, AW, FB, LI, GSC)' }; break }
+      if (!dsAccounts) { result = { error: '--ds-accounts required' }; break }
+      if (!dateRange) { result = { error: '--date-range required (e.g., last_28_days, last_month, this_month, custom)' }; break }
+      if (!fields) { result = { error: '--fields required (comma-separated field names)' }; break }
+      const body = {
+        ds_id: dsId,
+        ds_accounts: dsAccounts,
+        date_range_type: dateRange,
+        fields: fields.split(',').map(f => ({ name: f.trim() })),
+      }
+      if (args.filter) body.filter = args.filter
+      if (args['max-rows']) body.max_rows = parseInt(args['max-rows'], 10)
+      if (args['start-date']) body.start_date = args['start-date']
+      if (args['end-date']) body.end_date = args['end-date']
+      result = await api('POST', '/query/data/json', body)
+      break
+    }
+
+    case 'sources':
+      switch (sub) {
+        case 'list':
+          result = await api('GET', '/datasources')
+          break
+        default:
+          result = { error: 'Unknown sources subcommand. Use: list' }
+      }
+      break
+
+    case 'accounts':
+      switch (sub) {
+        case 'list': {
+          const dsId = args['ds-id']
+          if (!dsId) { result = { error: '--ds-id required (e.g., GA4, AW, FB)' }; break }
+          const params = new URLSearchParams({ ds_id: dsId })
+          result = await api('GET', `/datasources/accounts?${params.toString()}`)
+          break
+        }
+        default:
+          result = { error: 'Unknown accounts subcommand. Use: list' }
+      }
+      break
+
+    case 'teams':
+      switch (sub) {
+        case 'list':
+          result = await api('GET', '/teams')
+          break
+        default:
+          result = { error: 'Unknown teams subcommand. Use: list' }
+      }
+      break
+
+    case 'users':
+      switch (sub) {
+        case 'list':
+          result = await api('GET', '/users')
+          break
+        default:
+          result = { error: 'Unknown users subcommand. Use: list' }
+      }
+      break
+
+    default:
+      result = {
+        error: 'Unknown command',
+        usage: {
+          query: 'query --ds-id <data-source> --ds-accounts <account-id> --date-range <range> --fields <f1,f2> [--filter <filter>] [--max-rows <n>] [--start-date <date>] [--end-date <date>]',
+          sources: {
+            list: 'sources list',
+          },
+          accounts: {
+            list: 'accounts list --ds-id <data-source>',
+          },
+          teams: {
+            list: 'teams list',
+          },
+          users: {
+            list: 'users list',
+          },
+          'data-source-ids': {
+            'GA4': 'Google Analytics 4',
+            'GA4_PAID': 'Google Analytics (paid)',
+            'AW': 'Google Ads',
+            'FB': 'Facebook Ads',
+            'LI': 'LinkedIn Ads',
+            'TW_ADS': 'Twitter Ads',
+            'IG_IA': 'Instagram',
+            'FB_IA': 'Facebook Pages',
+            'GSC': 'Google Search Console',
+            'SE': 'Semrush',
+            'MC': 'Mailchimp',
+          },
+          'date-ranges': ['last_28_days', 'last_month', 'this_month', 'custom'],
+        }
+      }
+  }
+
+  console.log(JSON.stringify(result, null, 2))
+}
+
+main().catch(err => {
+  console.error(JSON.stringify({ error: err.message }))
+  process.exit(1)
+})
--- a/Show More
+++ b/Show More