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
150 changed files with 1310 additions and 1519 deletions
@@ -12,45 +12,44 @@
  "plugins": [
    {
      "name": "marketing-skills",
-      "description": "34 marketing skills for technical marketers and founders: ASO, CRO, copywriting, cold email, SEO, AI SEO, paid ads, ad creative, churn prevention, pricing strategy, referral programs, revenue operations, sales enablement, customer research, site architecture, and more",
+      "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": [
-        "./skills/ab-testing",
+        "./skills/ab-test-setup",
        "./skills/ad-creative",
        "./skills/ai-seo",
-        "./skills/analytics",
-        "./skills/aso-audit",
+        "./skills/analytics-tracking",
        "./skills/churn-prevention",
        "./skills/cold-email",
-        "./skills/community-marketing",
-        "./skills/competitors",
+        "./skills/competitor-alternatives",
        "./skills/content-strategy",
        "./skills/copy-editing",
        "./skills/copywriting",
        "./skills/customer-research",
-        "./skills/cro",
-        "./skills/emails",
-        "./skills/free-tools",
-        "./skills/launch",
+        "./skills/email-sequence",
+        "./skills/form-cro",
+        "./skills/free-tool-strategy",
+        "./skills/launch-strategy",
        "./skills/lead-magnets",
        "./skills/marketing-ideas",
        "./skills/marketing-psychology",
-        "./skills/onboarding",
+        "./skills/onboarding-cro",
+        "./skills/page-cro",
        "./skills/paid-ads",
-        "./skills/paywalls",
-        "./skills/popups",
-        "./skills/pricing",
-        "./skills/product-marketing",
+        "./skills/paywall-upgrade-cro",
+        "./skills/popup-cro",
+        "./skills/pricing-strategy",
+        "./skills/product-marketing-context",
        "./skills/programmatic-seo",
-        "./skills/referrals",
+        "./skills/referral-program",
        "./skills/revops",
        "./skills/sales-enablement",
-        "./skills/schema",
+        "./skills/schema-markup",
        "./skills/seo-audit",
-        "./skills/signup",
+        "./skills/signup-flow-cro",
        "./skills/site-architecture",
-        "./skills/social"
+        "./skills/social-content"
      ]
    }
  ]
@@ -74,7 +74,7 @@ description: What this skill does and when to use it. Include trigger phrases.
 - No consecutive hyphens (`--`)
 - Must match parent directory name exactly

-**Valid**: `cro`, `emails`, `ab-testing`
+**Valid**: `page-cro`, `email-sequence`, `ab-test-setup`
 **Invalid**: `Page-CRO`, `-page`, `page--cro`

 ### Optional Skill Directories
@@ -124,7 +124,7 @@ The `description` is critical for skill discovery. Include:
 3. Related skills for scope boundaries

 ```yaml
-description: When the user wants to optimize conversions on any marketing page. Use when the user says "CRO," "conversion rate optimization," "this page isn't converting." For signup flows, see signup.
+description: When the user wants to optimize conversions on any marketing page. Use when the user says "CRO," "conversion rate optimization," "this page isn't converting." For signup flows, see signup-flow-cro.
 ```

 ## Claude Code Plugin
@@ -151,7 +151,7 @@ See [Claude Code plugins documentation](https://code.claude.com/docs/en/plugins.
 Follow the [Conventional Commits](https://www.conventionalcommits.org/) specification:

 - `feat: add skill-name skill`
- `fix: improve clarity in cro`
+- `fix: improve clarity in page-cro`
 - `docs: update README`

 ### Pull Request Checklist
@@ -186,9 +186,9 @@ tools/
 ### When to Use Tools

 Skills reference relevant tools for implementation. For example:
- `referrals` skill → rewardful, tolt, dub-co, mention-me guides
- `analytics` skill → ga4, mixpanel, segment guides
- `emails` skill → customer-io, mailchimp, resend guides
+- `referral-program` skill → rewardful, tolt, dub-co, mention-me guides
+- `analytics-tracking` skill → ga4, mixpanel, segment guides
+- `email-sequence` skill → customer-io, mailchimp, resend guides
 - `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.
@@ -33,7 +33,7 @@ Optional frontmatter fields: `license` (default: MIT), `metadata` (author, versi

 ### 3. Follow the naming conventions

- **Directory name**: lowercase, hyphens only (e.g., `emails`)
+- **Directory name**: lowercase, hyphens only (e.g., `email-sequence`)
 - **Name field**: must match directory name exactly
 - **Description**: 1-1024 characters, include trigger phrases

@@ -30,21 +30,21 @@ Skills reference each other and build on shared context. The `product-marketing-
 │  SEO &   │ │   CRO    │ │Content & │ │  Paid &    │ │ Growth & │ │  Sales &    │ │ Strategy  │
 │ Content  │ │          │ │   Copy   │ │Measurement │ │Retention │ │    GTM      │ │           │
 ├──────────┤ ├──────────┤ ├──────────┤ ├────────────┤ ├──────────┤ ├─────────────┤ ├───────────┤
-│seo-audit │ │cro  │ │copywritng│ │paid-ads    │ │referral  │ │revops       │ │mktg-ideas │
+│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  │ │cro  │ │email-seq │ │analytics   │ │ prevent  │ │pricing      │ │research   │
-│schema    │ │popups │ │social    │ │            │ │          │ │competitor   │ │           │
+│programm  │ │form-cro  │ │email-seq │ │analytics   │ │ prevent  │ │pricing      │ │research   │
+│schema    │ │popup-cro │ │social    │ │            │ │          │ │competitor   │ │           │
 │content   │ │paywall   │ │          │ │            │ │          │ │             │ │           │
 └────┬─────┘ └────┬─────┘ └────┬─────┘ └─────┬──────┘ └────┬─────┘ └──────┬──────┘ └─────┬─────┘
     │            │            │              │             │              │              │
     └────────────┴─────┬──────┴──────────────┴─────────────┴──────────────┴──────────────┘
                        │
         Skills cross-reference each other:
-           copywriting ↔ cro ↔ ab-testing
+           copywriting ↔ page-cro ↔ ab-test-setup
           revops ↔ sales-enablement ↔ cold-email
-           seo-audit ↔ schema ↔ ai-seo
-           customer-research → copywriting, cro, competitors
+           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.
@@ -54,40 +54,40 @@ See each skill's **Related Skills** section for the full dependency map.
 <!-- SKILLS:START -->
 | Skill | Description |
 |-------|-------------|
-| [ab-testing](skills/ab-testing/) | When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B... |
+| [ab-test-setup](skills/ab-test-setup/) | When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B... |
 | [ad-creative](skills/ad-creative/) | When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad... |
 | [ai-seo](skills/ai-seo/) | When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers.... |
-| [analytics](skills/analytics/) | When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions... |
+| [analytics-tracking](skills/analytics-tracking/) | When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions... |
 | [churn-prevention](skills/churn-prevention/) | When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or... |
 | [cold-email](skills/cold-email/) | Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails,... |
-| [competitors](skills/competitors/) | When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when... |
+| [competitor-alternatives](skills/competitor-alternatives/) | When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when... |
 | [content-strategy](skills/content-strategy/) | When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also... |
 | [copy-editing](skills/copy-editing/) | When the user wants to edit, review, or improve existing marketing copy. Also use when the user mentions 'edit this... |
 | [copywriting](skills/copywriting/) | When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages,... |
 | [customer-research](skills/customer-research/) | When the user wants to conduct, analyze, or synthesize customer research — including interview transcripts, surveys, support tickets, review mining, Reddit/G2/forum research, persona generation, and voice of customer (VOC)... |
-| [emails](skills/emails/) | When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email... |
-| [cro](skills/cro/) | When the user wants to optimize any form that is NOT signup/registration — including lead capture forms, contact forms,... |
-| [free-tools](skills/free-tools/) | When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or... |
-| [launch](skills/launch/) | When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user... |
+| [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](skills/onboarding/) | When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also... |
-| [cro](skills/cro/) | When the user wants to optimize, improve, or increase conversions on any marketing page — including homepage, landing... |
+| [onboarding-cro](skills/onboarding-cro/) | When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also... |
+| [page-cro](skills/page-cro/) | When the user wants to optimize, improve, or increase conversions on any marketing page — including homepage, landing... |
 | [paid-ads](skills/paid-ads/) | When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X,... |
-| [paywalls](skills/paywalls/) | When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use... |
-| [popups](skills/popups/) | When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also... |
-| [pricing](skills/pricing/) | When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions... |
+| [paywall-upgrade-cro](skills/paywall-upgrade-cro/) | When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use... |
+| [popup-cro](skills/popup-cro/) | When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also... |
+| [pricing-strategy](skills/pricing-strategy/) | When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions... |
 | [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... |
-| [referrals](skills/referrals/) | When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy.... |
+| [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](skills/schema/) | When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user... |
+| [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](skills/signup/) | When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the... |
+| [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](skills/social/) | When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram,... |
+| [social-content](skills/social-content/) | When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram,... |
 <!-- SKILLS:END -->

 ## Installation
@@ -101,7 +101,7 @@ Use [npx skills](https://github.com/vercel-labs/skills) to install skills direct
 npx skills add coreyhaines31/marketingskills

 # Install specific skills
-npx skills add coreyhaines31/marketingskills --skill cro copywriting
+npx skills add coreyhaines31/marketingskills --skill page-cro copywriting

 # List available skills
 npx skills add coreyhaines31/marketingskills --list
@@ -155,7 +155,7 @@ Use [SkillKit](https://github.com/rohitg00/skillkit) to install skills across mu
 npx skillkit install coreyhaines31/marketingskills

 # Install specific skills
-npx skillkit install coreyhaines31/marketingskills --skill cro copywriting
+npx skillkit install coreyhaines31/marketingskills --skill page-cro copywriting

 # List available skills
 npx skillkit install coreyhaines31/marketingskills --list
@@ -178,72 +178,72 @@ Once installed, just ask your agent to help with marketing tasks:

 ```
 "Help me optimize this landing page for conversions"
-→ Uses cro skill
+→ Uses page-cro skill

 "Write homepage copy for my SaaS"
 → Uses copywriting skill

 "Set up GA4 tracking for signups"
-→ Uses analytics skill
+→ Uses analytics-tracking skill

 "Create a 5-email welcome sequence"
-→ Uses emails skill
+→ Uses email-sequence skill
 ```

 You can also invoke skills directly:

 ```
-/cro
-/emails
+/page-cro
+/email-sequence
 /seo-audit
 ```

 ## Skill Categories

 ### Conversion Optimization
- `cro` - Any marketing page
- `signup` - Registration flows
- `onboarding` - Post-signup activation
- `cro` - Lead capture forms
- `popups` - Modals and overlays
- `paywalls` - In-app upgrade moments
+- `page-cro` - Any marketing page
+- `signup-flow-cro` - Registration flows
+- `onboarding-cro` - Post-signup activation
+- `form-cro` - Lead capture forms
+- `popup-cro` - Modals and overlays
+- `paywall-upgrade-cro` - In-app upgrade moments

 ### Content & Copy
 - `copywriting` - Marketing page copy
 - `copy-editing` - Edit and polish existing copy
 - `cold-email` - B2B cold outreach emails and sequences
- `emails` - Automated email flows
- `social` - Social media content
+- `email-sequence` - Automated email flows
+- `social-content` - Social media content

 ### SEO & Discovery
 - `seo-audit` - Technical and on-page SEO
 - `ai-seo` - AI search optimization (AEO, GEO, LLMO)
 - `programmatic-seo` - Scaled page generation
 - `site-architecture` - Page hierarchy, navigation, URL structure
- `competitors` - Comparison and alternative pages
- `schema` - Structured data
+- `competitor-alternatives` - Comparison and alternative pages
+- `schema-markup` - Structured data

 ### Paid & Distribution
 - `paid-ads` - Google, Meta, LinkedIn ad campaigns
 - `ad-creative` - Bulk ad creative generation and iteration
- `social` - Social media scheduling and strategy
+- `social-content` - Social media scheduling and strategy

 ### Measurement & Testing
- `analytics` - Event tracking setup
- `ab-testing` - Experiment design
+- `analytics-tracking` - Event tracking setup
+- `ab-test-setup` - Experiment design

 ### Retention
 - `churn-prevention` - Cancel flows, save offers, dunning, payment recovery

 ### Growth Engineering
- `free-tools` - Marketing tools and calculators
- `referrals` - Referral and affiliate programs
+- `free-tool-strategy` - Marketing tools and calculators
+- `referral-program` - Referral and affiliate programs

 ### Strategy & Monetization
 - `marketing-ideas` - 140 SaaS marketing ideas
 - `marketing-psychology` - Mental models and psychology
- `launch` - Product launches and announcements
- `pricing` - Pricing, packaging, and monetization
+- `launch-strategy` - Product launches and announcements
+- `pricing-strategy` - Pricing, packaging, and monetization

 ### Sales & RevOps
 - `revops` - Lead lifecycle, scoring, routing, pipeline management
@@ -1,8 +1,8 @@
 ---
-name: ab-testing
-description: When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," or "how long should I run this test." Use this whenever someone is comparing two approaches and wants to measure which performs better. For tracking implementation, see analytics. For page-level conversion optimization, see cro.
+name: ab-test-setup
+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.1.0
+  version: 1.2.0
 ---

 # A/B Test Setup
@@ -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
@@ -261,6 +348,6 @@ Document every test with:

 ## Related Skills

- **cro**: For generating test ideas based on CRO principles
- **analytics**: For setting up test measurement
+- **page-cro**: For generating test ideas based on CRO principles
+- **analytics-tracking**: For setting up test measurement
 - **copywriting**: For creating variant copy
@@ -357,6 +357,6 @@ node tools/clis/google-ads.js reports get --type ad_performance --date-range las

 - **paid-ads**: For campaign strategy, targeting, budgets, and optimization
 - **copywriting**: For landing page copy (where ad traffic lands)
- **ab-testing**: For structuring creative tests with statistical rigor
+- **ab-test-setup**: For structuring creative tests with statistical rigor
 - **marketing-psychology**: For psychological principles behind high-performing creative
 - **copy-editing**: For polishing ad copy before launch
@@ -2,7 +2,7 @@
 name: ai-seo
 description: "When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for Perplexity,' 'AI citations,' 'AI visibility,' 'zero-click search,' 'how do I show up in AI answers,' 'LLM mentions,' or 'optimize for Claude/Gemini.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional technical and on-page SEO audits, see seo-audit. For structured data implementation, see schema-markup."
 metadata:
-  version: 1.1.0
+  version: 1.2.0
 ---

 # AI SEO
@@ -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
@@ -333,7 +377,7 @@ Monthly manual check:
 - Fair and balanced (AI penalizes obviously biased comparisons)
 - Specific criteria with ratings or scores
 - Updated pricing and feature data
- Cite the competitors skill for building these pages
+- Cite the competitor-alternatives skill for building these pages

 ### Documentation / Help Content

@@ -358,6 +402,7 @@ Monthly manual check:
 - **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
@@ -393,6 +438,6 @@ For implementation, see the [tools registry](../../tools/REGISTRY.md).
 - **seo-audit**: For traditional technical and on-page SEO audits
 - **schema-markup**: For implementing structured data that helps AI understand your content
 - **content-strategy**: For planning what content to create
- **competitors**: For building comparison pages that get cited
+- **competitor-alternatives**: For building comparison pages that get cited
 - **programmatic-seo**: For building SEO pages at scale
 - **copywriting**: For writing content that's both human-readable and AI-extractable
@@ -1,6 +1,6 @@
 ---
-name: analytics
-description: When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "track conversions," "attribution," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For A/B test measurement, see ab-testing.
+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," "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.1.0
 ---
@@ -303,7 +303,7 @@ For implementation, see the [tools registry](../../tools/REGISTRY.md). Key analy

 ## Related Skills

- **ab-testing**: For experiment tracking
+- **ab-test-setup**: For experiment tracking
 - **seo-audit**: For organic traffic analysis
- **cro**: For conversion optimization (uses this data)
+- **page-cro**: For conversion optimization (uses this data)
 - **revops**: For pipeline metrics, CRM tracking, and revenue attribution
@@ -1,299 +0,0 @@
---
-name: aso-audit
-description: >
-  Use when auditing an App Store or Google Play listing for optimization.
-  Triggers: "ASO audit", "app store optimization", "optimize my app listing",
-  "improve app visibility", "app store ranking", "audit my listing", or when
-  user shares an App Store / Google Play URL and wants to improve it. Also
-  triggers on: "why aren't people downloading my app", "improve my app
-  conversion", "keyword optimization for app", "compare my app to competitors".
-metadata:
-  version: 1.0.0
---
-
-# ASO Audit
-
-Analyze App Store and Google Play listings against ASO best practices. Fetches
-live listing data, scores metadata, visuals, and ratings, then produces a
-prioritized action plan.
-
-## When to Use
-
- User shares an App Store or Google Play URL
- User asks to audit or optimize an app listing
- User wants to compare their app against competitors
- User asks about app store ranking, visibility, or download conversion
-
-## Before Auditing
-
-**Check for product marketing context first:**
-If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
-
-## Phase 1 — Identify Store & Fetch
-
-### Detect store type from URL
-
-```
-Apple:  apps.apple.com/{country}/app/{name}/id{digits}
-Google: play.google.com/store/apps/details?id={package}
-```
-
-If the user gives an app name instead of a URL, search the web for:
-`site:apps.apple.com "{app name}"` or `site:play.google.com "{app name}"`
-
-### Fetch the listing
-
-Use WebFetch to retrieve the listing page. Extract every available field:
-
-**Apple App Store fields:**
-
- App name (title) — 30 char limit
- Subtitle — 30 char limit
- Description (long) — not indexed for search, but matters for conversion
- Promotional text — 170 chars, updatable without new release
- Category (primary + secondary)
- Screenshots (count, order, caption text)
- Preview video (presence, duration)
- Rating (average + count)
- Recent reviews (visible ones)
- Price / in-app purchases
- Developer name
- Last updated date
- Version history notes
- Age rating
- Size
- Languages / localizations listed
- In-app events (if any visible)
-
-**Google Play fields:**
-
- App name (title) — 30 char limit
- Short description — 80 char limit
- Full description — 4,000 char limit, IS indexed for search
- Category + tags
- Feature graphic (presence)
- Screenshots (count, order)
- Preview video (presence)
- Rating (average + count)
- Recent reviews (visible ones)
- Price / in-app purchases
- Developer name
- Last updated date
- What's new text
- Downloads range
- Content rating
- Data safety section
- Languages listed
-
-If WebFetch returns incomplete data (stores render client-side), note gaps and
-work with what's available. Ask the user to paste missing fields if critical.
-
-### Visual asset assessment
-
-WebFetch cannot extract screenshot images or caption text. **Always use the
-Playwright browser tool** to get visual data:
-
-1. Navigate to the listing URL with `browser_navigate`
-2. Take a full-page screenshot with `browser_take_screenshot`
-3. Read the screenshot image to assess: icon, screenshot count, caption text,
-   messaging quality, preview video presence, feature graphic (Google Play)
-4. If Playwright is unavailable, ask the user to share a screenshot of the
-   listing page
-
-**Promotional text (Apple):** This 170-char field appears above the description
-but is often indistinguishable from it in scraped HTML. If you cannot confirm
-its presence, note this and recommend the user check App Store Connect.
-
---
-
-## Phase 1.5 — Assess Brand Maturity
-
-Before scoring, classify the app into one of three tiers. This determines how
-you interpret "textbook ASO" deviations — a deliberate brand choice by a
-household name is not the same as a missed opportunity by an unknown app.
-
-### Tier definitions
-
-| Tier            | Signals                                                                                                                              | Examples                                    |
-| --------------- | ------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------- |
-| **Dominant**    | Household name, 1M+ ratings, top-10 in category, near-universal brand recognition. Users search by brand name, not generic keywords. | Instagram, Uber, Spotify, WhatsApp, Netflix |
-| **Established** | Well-known in their category, 100K+ ratings, strong organic installs, recognized brand but not universally known.                    | Strava, Notion, Duolingo, Cash App, Calm    |
-| **Challenger**  | Building awareness, <100K ratings, needs discovery through keywords and ASO tactics. Most apps fall here.                            | Your app, most indie/startup apps           |
-
-### How tier affects scoring
-
-**Dominant apps** get adjusted scoring in these areas:
-
- **Title:** Brand-only or brand-first titles are valid (score 8+ if brand is the keyword). These apps don't need generic keyword discovery.
- **Description:** Score purely on conversion quality, not keyword presence. If the app is a household name, a well-crafted brand description beats a keyword-stuffed one.
- **Visual Assets:** Lifestyle/brand photography instead of UI demos is a legitimate conversion strategy. No video is acceptable if the product is hard to demo in 30s or brand awareness is near-universal.
- **What's New:** Generic release notes at weekly+ cadence are acceptable (score 8+). At scale, detailed changelogs have minimal ROI and risk backlash.
- **In-app events:** Missing events for utility apps with massive install bases (Uber, WhatsApp) is not a penalty. These apps don't need discovery help.
- **Localization:** Score relative to actual market, not absolute count. A US-only fintech with 2 languages (English + Spanish) is appropriately localized.
-
-**Established apps** get partial adjustment:
-
- Brand-first titles are fine but should still include 1-2 keywords
- Strategic description choices get benefit of the doubt
- Other dimensions scored normally
-
-**Challenger apps** are scored strictly against textbook ASO best practices — every character, screenshot, and keyword matters.
-
-**Key principle:** Before docking points, ask: "Is this a mistake or a deliberate
-choice by a team that has data I don't?" If the app has 1M+ ratings and a
-dedicated ASO team, assume their choices are data-informed unless clearly wrong.
-
---
-
-## Phase 2 — Score Each Dimension
-
-Score each dimension 0-10 using the criteria in `references/scoring-criteria.md`.
-Apply the brand maturity tier adjustments from Phase 1.5.
-
-Reference files for platform specs and benchmarks:
-
- `references/apple-specs.md` — Official Apple character limits, screenshot/video specs, CPP/PPO rules, rejection triggers
- `references/google-play-specs.md` — Official Google Play limits, screenshot specs, Android Vitals thresholds, policies
- `references/benchmarks.md` — Conversion data, rating impact, video lift, screenshot behavior, CPP/event benchmarks
-
-### Dimensions and Weights
-
-| #   | Dimension            | Weight | What It Covers                                                            |
-| --- | -------------------- | ------ | ------------------------------------------------------------------------- |
-| 1   | Title & Subtitle     | 20%    | Character usage, keyword presence, clarity, brand + keyword balance       |
-| 2   | Description          | 15%    | First 3 lines, keyword density (Google), CTA, structure, promotional text |
-| 3   | Visual Assets        | 25%    | Screenshot count/quality/messaging, video, icon, feature graphic          |
-| 4   | Ratings & Reviews    | 20%    | Average rating, volume, recency, developer responses                      |
-| 5   | Metadata & Freshness | 10%    | Category choice, update recency, localization count, data safety          |
-| 6   | Conversion Signals   | 10%    | Price positioning, IAP transparency, social proof, download range         |
-
-**Final score** = weighted sum, out of 100.
-
-### Score interpretation
-
-| Score  | Grade | Meaning                                                   |
-| ------ | ----- | --------------------------------------------------------- |
-| 85-100 | A     | Well-optimized; focus on A/B testing and iteration        |
-| 70-84  | B     | Good foundation; clear opportunities to improve           |
-| 50-69  | C     | Significant gaps; prioritized fixes will have high impact |
-| 30-49  | D     | Major optimization needed across multiple dimensions      |
-| 0-29   | F     | Listing needs a complete overhaul                         |
-
---
-
-## Phase 3 — Competitor Comparison (Optional)
-
-If the user provides competitor URLs or asks for comparison:
-
-1. Fetch 2-3 top competitors in the same category
-2. Run the same scoring on each
-3. Build a comparison table highlighting where the user's app is weaker/stronger
-4. Identify keyword gaps — terms competitors rank for that the user's app doesn't target
-
-If no competitors are specified, suggest the user provide 2-3 or offer to search
-for top apps in their category.
-
---
-
-## Phase 4 — Generate Report
-
-Use the template in `references/report-template.md` to structure the output.
-
-The report must include:
-
-1. **Score card** — table with all 6 dimensions, scores, and grade
-2. **Top 3 quick wins** — changes that take <1 hour and have highest impact
-3. **Detailed findings** — per-dimension breakdown with specific issues and fixes
-4. **Keyword suggestions** — based on title/description analysis and competitor gaps
-5. **Visual asset recommendations** — specific screenshot/video improvements
-6. **Priority action plan** — ordered list of changes by impact vs effort
-
-### Report rules
-
- Every recommendation must be **specific and actionable** ("Change subtitle from X to Y" not "Improve subtitle")
- Include character counts for all text recommendations
- Flag platform-specific differences (Apple vs Google) when relevant
- Note what CANNOT be assessed without paid tools (search volume, exact rankings)
- When suggesting keyword changes, explain WHY each keyword matters
-
---
-
-## Platform-Specific Rules
-
-### Apple App Store — Key Facts
-
- Title (30 chars) + Subtitle (30 chars) + Keyword field (100 **bytes**, hidden) = indexed text
- Keywords field is bytes not chars — Arabic/CJK use 2-3 bytes per char
- Long description is NOT indexed for search — optimize for conversion only
- Promotional text (170 chars) does NOT affect search (Apple confirmed)
- Never repeat words across title/subtitle/keyword field (Apple indexes each word once)
- Keyword field: commas, no spaces ("photo,editor,filter" not "photo, editor, filter")
- Screenshots: up to 10 per device. First 3 visible in search — 90% never scroll past 3rd
- Screenshot captions indexed since June 2025 (AI extraction)
- In-app events: max 10 published at once, max 31 days each. Indexed and appear in search
- Custom Product Pages (up to 70) in organic search since July 2025. +5.9% avg conversion lift
- App preview video: up to 3, 15-30s each. Autoplays muted — +20-40% conversion lift
- SKStoreReviewController: max 3 prompts per 365 days
- Apple has human editorial curation — quality and design matter more
- See `references/apple-specs.md` for full specs, dimensions, and rejection triggers
-
-### Google Play — Key Facts
-
- Title (30 chars) + Short description (80 chars) + Full description (4,000 chars) = indexed text
- Full description IS indexed — target 2-3% keyword density naturally
- No hidden keyword field — all keywords must be in visible text
- Google NLP/semantic understanding — keyword stuffing detected and penalized
- Prohibited in title: emojis, ALL CAPS, "best"/"#1"/"free", CTAs (enforced since 2021)
- Screenshots: min 2, **max 8** per device (not 10 like Apple)
- Feature graphic (1024x500, exact) required for featured placements
- Video does NOT autoplay — only ~6% of users tap play (low ROI vs iOS)
- Android Vitals directly affect ranking: crash >1.09% or ANR >0.47% = reduced visibility
- Promotional Content: submit 14 days early for featuring. Apps see 2x explore acquisitions
- Custom Store Listings: up to 50 (can target churned users, specific countries, ad campaigns)
- Store Listing Experiments: test up to 3 variants, run 7+ days, 1 experiment at a time
- See `references/google-play-specs.md` for full specs and policy details
-
-### What Apple Indexes vs What Google Indexes
-
-| Field                 | Apple Indexed?   | Google Indexed?        |
-| --------------------- | ---------------- | ---------------------- |
-| Title                 | Yes              | Yes (strongest signal) |
-| Subtitle / Short desc | Yes              | Yes                    |
-| Keyword field         | Yes (hidden)     | Does not exist         |
-| Long description      | No               | Yes (heavily)          |
-| Screenshot captions   | Yes (since 2025) | No                     |
-| In-app events         | Yes              | N/A (LiveOps instead)  |
-| Developer name        | No               | Partial                |
-| IAP names             | Yes              | Yes                    |
-
---
-
-## Common Issues Checklist
-
-Flag these if found. Items marked _(tier-dependent)_ should be evaluated against
-the app's brand maturity tier — they may be deliberate choices for Dominant apps.
-
-**Always flag (all tiers):**
-
- [ ] Rating below 4.0
- [ ] Last update > 3 months ago
- [ ] Google Play description has no keyword strategy (under 1% density)
- [ ] Google Play missing feature graphic
- [ ] Apple keyword field likely has repeated words (inferred from title+subtitle)
- [ ] Category mismatch — app would face less competition in a different category
- [ ] Fewer than 5 screenshots
-
-**Flag for Challenger/Established only** _(not mistakes for Dominant apps):_
-
- [ ] Title wastes characters on brand name only (no keywords) _(Dominant: brand IS the keyword)_
- [ ] Subtitle/short description duplicates title keywords
- [ ] Description first 3 lines are generic _(Dominant: may be brand-voice choice)_
- [ ] No preview video _(Dominant: may be rational if product is hard to demo)_
- [ ] Screenshots are just UI dumps with no messaging/captions _(Dominant: lifestyle/brand shots may convert better)_
- [ ] Only 1-2 localizations _(score relative to actual market, not absolute count)_
- [ ] No in-app events or promotional content _(Dominant utility apps may not need discovery help)_
-
-**Flag for all tiers but note context:**
-
- [ ] No developer responses to negative reviews _(note volume — responding at 10M+ reviews is a different challenge than at 1K)_
- [ ] Generic "What's New" text _(acceptable at weekly+ release cadence for Established/Dominant)_
@@ -1,107 +0,0 @@
-# Apple App Store — Official Specs & Guidelines
-
-All data from developer.apple.com as of March 2026.
-
-## Character Limits
-
-| Field                   | Limit            | Indexed for Search?      | Notes                                                    |
-| ----------------------- | ---------------- | ------------------------ | -------------------------------------------------------- |
-| App Name                | 30 chars (min 2) | Yes                      | Must be unique; no trademarks, competitor names, pricing |
-| Subtitle                | 30 chars         | Yes                      | No unverifiable claims                                   |
-| Keywords                | 100 bytes        | Yes (hidden)             | Commas, no spaces between terms                          |
-| Description             | 4,000 chars      | **No**                   | Plain text only, no HTML                                 |
-| Promotional Text        | 170 chars        | **No** (Apple confirmed) | Updatable without new version                            |
-| What's New              | 4,000 chars      | No                       | Required for all versions after first                    |
-| IAP Name                | 35 chars         | Yes                      | Appears in search                                        |
-| IAP Description         | 55 chars         | No                       |                                                          |
-| In-App Event Name       | 30 chars         | Yes                      | Title case required                                      |
-| In-App Event Short Desc | 50 chars         | Yes                      | Sentence case                                            |
-| In-App Event Long Desc  | 120 chars        | No                       | Sentence case                                            |
-
-**Keywords field is 100 bytes, not 100 characters.** Non-Latin scripts (Arabic,
-Chinese, Japanese, Korean) use 2-3 bytes per character, reducing effective
-keyword count significantly.
-
-## Screenshot Specs
-
-| Device           | Required?     | Count | Dimensions (portrait)      |
-| ---------------- | ------------- | ----- | -------------------------- |
-| 6.9" iPhone      | **Required**  | 1-10  | 1260 x 2736                |
-| 13" iPad         | **Required**  | 1-10  | 2064 x 2752                |
-| Mac              | If applicable | 1-10  | Up to 2880 x 1800 (16:10)  |
-| Apple Watch      | If applicable | 1-10  | Varies by model            |
-| Apple TV         | If applicable | 1-10  | 1920 x 1080 or 3840 x 2160 |
-| Apple Vision Pro | If applicable | 1-10  | 3840 x 2160                |
-
- Formats: JPEG, PNG
- Apple auto-scales from required base sizes to smaller devices
-
-## App Preview Video Specs
-
- **Count:** Up to 3 per app
- **Duration:** 15-30 seconds
- **Max file size:** 500 MB
- **Codecs:** H.264 (10-12 Mbps, up to 30fps) or ProRes 422 HQ
- **Audio:** Stereo, 256 kbps AAC or PCM, 44.1/48 kHz
- **Formats:** .mov, .m4v, .mp4
- **Behavior:** Autoplays muted on product page (iOS 11+)
-
-## Custom Product Pages (CPPs)
-
- **Max:** 70 additional pages (plus 1 default)
- **Customizable:** Screenshots, promotional text, app previews, deep links (iOS 18+)
- **Keywords:** Each keyword combo must be unique to a single CPP
- **Review:** Submitted to App Review independently of app updates
- **Organic search:** CPPs appear in organic search results since July 2025
- **Performance:** +2.5 percentage points higher conversion on average vs default
-
-## Product Page Optimization (A/B Testing)
-
- **Treatments:** Up to 3 vs original
- **Testable:** App icons, screenshots, app preview videos
- **NOT testable:** Title, subtitle, description, keywords
- **Concurrent tests:** 1 per app
- **Max duration:** 90 days
- **Icon constraint:** All icon variants must be in the published app binary
- **Confidence:** Apple recommends 90% threshold (Bayesian method)
- **Cannot modify** a test once started
-
-## In-App Events
-
- **Max approved:** 15 in App Store Connect at once
- **Max published:** 10 on App Store simultaneously
- **Max duration:** 31 days per event
- **Pre-event promotion:** Up to 14 days before start
- **Badge types:** Challenge, Competition, Live Event, Major Update, New Season, Premiere, Special Event
-
-**Event card image:** 16:9, min 1920x1080, max 3840x2160
-**Event details image:** 9:16, min 1080x1920, max 2160x3840
-
-**Not suitable:** Repetitive daily tasks, price promotions without new content, general awareness campaigns.
-
-## Ratings & Reviews
-
- **SKStoreReviewController:** Max 3 prompts per 365-day period
- System controls display frequency (may show fewer than 3)
- Do not use custom buttons to request reviews
- Developers can respond to all reviews in App Store Connect
- Summary rating is territory-specific
-
-## Metadata Rejection Triggers (App Review Guidelines)
-
-| Guideline | Rejection Trigger                                                         |
-| --------- | ------------------------------------------------------------------------- |
-| 2.3.1     | Hidden features, misleading marketing, false pricing                      |
-| 2.3.2     | Not disclosing IAPs in description/screenshots                            |
-| 2.3.3     | Screenshots that don't show app in use (only splash/login)                |
-| 2.3.4     | Preview videos using non-app content                                      |
-| 2.3.5     | Wrong category selected                                                   |
-| 2.3.7     | Keyword stuffing: trademarks, competitor names, pricing, irrelevant terms |
-| 2.3.8     | Metadata not appropriate for all audiences (must be 4+ rated)             |
-| 2.3.10    | Other platform names/imagery (Android, etc.) in metadata                  |
-| 2.3.12    | Generic What's New for significant changes                                |
-| 2.3.13    | Inaccurate in-app event metadata                                          |
-
-Sources: developer.apple.com/app-store/product-page/,
-developer.apple.com/app-store/search/,
-developer.apple.com/app-store/review/guidelines/
@@ -1,129 +0,0 @@
-# ASO Benchmarks & Conversion Data
-
-Industry data from AppTweak, SplitMetrics, Sensor Tower, and others. Updated March 2026.
-
-## Conversion Rate Benchmarks by Category
-
-**Average CVR (page view to install):**
-
- iOS overall: **25.0%**
- Google Play overall: **27.3%**
-
-| Category          | iOS CVR        | Google Play CVR |
-| ----------------- | -------------- | --------------- |
-| Navigation        | 115%\*         | --              |
-| Auto & Vehicles   | --             | 70.5%           |
-| Business          | 66.7%          | --              |
-| Music (Games)     | --             | 45.0%           |
-| Utilities & Tools | --             | 36.8%           |
-| Shopping          | --             | 27.7%           |
-| Health & Fitness  | --             | 23.2%           |
-| Finance           | --             | 19.7%           |
-| Food & Drink      | --             | 13.1%           |
-| Games (Board)     | 1.2%           | 7.3%            |
-| Games (overall)   | 3-5% realistic | --              |
-
-\*Above 100% = some users install from search without visiting product page.
-
-Source: AppTweak 2025 Benchmarks Report (H1 2024 data, US market)
-
-## Rating Impact on Conversion
-
-| Rating Change              | Conversion Impact                       |
-| -------------------------- | --------------------------------------- |
-| 3.0 to 4.0 stars           | **+89%**                                |
-| 4.0 to 4.5 stars           | **+20-30%**                             |
-| 4.3 to 4.6 stars           | **+22-28%** (Finance, Health)           |
-| 0.4-star gap vs competitor | **~25% lost installs** from same search |
-| 3-star vs 5-star app       | **50% fewer conversions** for 3-star    |
-
-**Critical thresholds:**
-
- **4.0 stars** = minimum for Apple featuring, user trust, conversion viability
- **4.5+ stars** = optimal zone. Sweet spot: 4.1-4.9
- **5.0 stars** can look suspicious to users
- **Below 3.5** = sharp visibility drop on both stores
- **79% of users** check ratings before downloading
- **50% reject** apps below 3 stars
-
-Sources: AppFollow, MobileAction, Sensor Tower, Troof.ai
-
-## Preview Video Impact
-
-**iOS:** +20-40% conversion lift (video autoplays on product page)
-**Google Play:** Minimal lift (only ~6% of visitors tap to play)
-
- Autoplay introduced in iOS 11 caused **+47% conversion jump**
- Users who watch video are **2x more likely to install**
- Average watch time: **4-6.5 seconds** (first 5 seconds are critical)
- 50%+ of viewers watch to the end
-
-**Takeaway:** Video is high-ROI on iOS, low-ROI on Google Play.
-
-Sources: StoreMaven, SplitMetrics, Leanplum
-
-## Screenshot Impact
-
- **90% of users** do not scroll past the 3rd screenshot
- Average scroll rate: only **17%**
- Users spend **6-10 seconds** scanning before deciding
- **First screenshot decides everything**
- Well-designed screenshots lift conversion **20-35%**
- A/B test winners see **10-25% improvement**
- **Optimal count:** 4-5 for utility apps, 5-6 for complex apps
- More than 6: diminishing returns, can cause decision paralysis
- Top 200 apps update screenshots **2-4 times/year**
- Top Google Play games update visuals **up to 8x/year**
- **57% of top games** A/B tested screenshots at least 2x in 2024
-
-Sources: AppTweak, ASOMobile, Sensor Tower
-
-## Custom Product Pages (Apple CPPs)
-
- Average conversion lift: **+5.9% for apps**, **+3.5% for games**
- Best cases: up to **+8.6%**
- Organic referral: **+2.5 percentage points** (156% lift vs 1.6% baseline)
- Apple Ads CPP CVR: **55.8% in 2024** (up from 42.1% in 2023)
- **Only 31% of apps** and **26% of games** use CPPs (low adoption = opportunity)
- Screenshot reordering alone produced **+16.6% installs** in one case
-
-Sources: AppTweak, SplitMetrics, MobileAction
-
-## Custom Store Listings (Google Play CSLs)
-
- Up to **50 custom versions** per app
- Case study (Lockwood/Avakin Life): **+57% CVR** over 2 months
- Can target inactive/churned users (28+ days no activity)
-
-Source: Phiture, MobileAction
-
-## In-App Events (Apple)
-
- **55% of top 200 apps** use them regularly
- +**15-20% more impressions** from editorial/browse placements
- One case: **+124% surge** in total impressions
- One case: **+50% impressions AND first-time downloads**
- Search CVR uptick: **+10.3%**
- Re-downloads increase: **+15.5%**
- **Boost is short-lived** -- KPIs drop to baseline when event ends
- Optimal: **2-4 active events per month**
-
-Sources: Phiture, AppTweak, Appalize
-
-## Promotional Content (Google Play)
-
- Apps with featuring see **2x explore acquisitions** (official Google)
- +2% 28-day active users and +4% revenue on average
-
-Source: Google Play Console documentation
-
-## A/B Test Impact Thresholds
-
-| Improvement | Classification                     |
-| ----------- | ---------------------------------- |
-| >10%        | Strong winner -- apply immediately |
-| 5-10%       | Meaningful winner                  |
-| 2-5%        | Marginal winner                    |
-| <2%         | Noise -- not significant           |
-
-Source: SplitMetrics, MobileAction
@@ -1,131 +0,0 @@
-# Google Play Store — Official Specs & Guidelines
-
-All data from support.google.com and developer.android.com as of March 2026.
-
-## Character Limits
-
-| Field             | Limit       | Indexed?               | Notes                                 |
-| ----------------- | ----------- | ---------------------- | ------------------------------------- |
-| App Title         | 30 chars    | Yes (strongest signal) | Reduced from 50 in Sept 2021          |
-| Short Description | 80 chars    | Yes                    | Visible without expanding             |
-| Full Description  | 4,000 chars | **Yes (heavily)**      | Google NLP indexes entire text        |
-| Developer Name    | 64 chars    | Partial                | Same emoji/caps restrictions as title |
-
-## Prohibited in Metadata (enforced since Sept 2021)
-
-**Title, Icon, Developer Name:**
-
- Emojis, emoticons, repeated special characters
- ALL CAPS (unless registered brand)
- Performance claims: "top," "best," "#1," "free," "no ads"
- Misleading store performance or endorsement
- Calls-to-action: "update now," "download now"
-
-**Short Description:**
-
- Same performance claims as title
- Calls-to-action
- Unattributed testimonials
-
-**Screenshots, Feature Graphic, Video:**
-
- Time-sensitive taglines
- Calls-to-action ("Download now," "Play now")
- Must authentically showcase app functionality
-
-## Screenshot Specs
-
-| Device     | Min   | Max   | Aspect Ratio | Min Resolution | Max Long Edge |
-| ---------- | ----- | ----- | ------------ | -------------- | ------------- |
-| Phone      | **2** | **8** | 9:16 or 16:9 | 320px any side | 3,840px       |
-| 7" Tablet  | 4     | 8     | 9:16 or 16:9 | 1,080px short  | 7,680px       |
-| 10" Tablet | 4     | 8     | 9:16 or 16:9 | 1,080px short  | 7,680px       |
-| Chromebook | 4     | 8     | 9:16 or 16:9 | 1,080px short  | 7,680px       |
-| Wear OS    | 1     | 8     | **1:1**      | 384x384        | 3,840px       |
-| Android TV | 1     | 8     | **16:9**     | 1,920x1,080    | 3,840px       |
-
- **Recommended phone size:** 1080x1920 (portrait)
- **Format:** JPEG or 24-bit PNG (no alpha)
- **Max file size:** 8 MB each
-
-**Note:** Google Play max is 8 screenshots per device, not 10 like Apple.
-
-## Feature Graphic
-
- **Dimensions:** 1024 x 500 px (exact, required)
- **Format:** JPEG or 24-bit PNG (no alpha)
- Displayed at top of listing and in featured placements
-
-## App Icon
-
- **Dimensions:** 512 x 512 px
- **Format:** 32-bit PNG (with alpha)
- **Max file size:** 1,024 KB
- **Shape:** Full square (Google applies 30% corner radius automatically)
- **Prohibited:** Ranking claims, download counts, deal text, emoji
-
-## Preview Video
-
- **Format:** YouTube URL (public or unlisted)
- **Duration:** 30 seconds to 2 minutes recommended
- No ads, no monetization, must be embeddable, not age-restricted
- **Does NOT autoplay** (only ~6% of visitors tap to play)
-
-## Store Listing Experiments (A/B Testing)
-
- **Variants:** Up to 3 per experiment (plus control)
- **Testable:** Icon, feature graphic, screenshots, video, short description, full description
- **Concurrent:** Cannot run more than 1 default graphics experiment simultaneously
- **Audience:** Signed-in Google Play users only
- **Metrics:** First-time installers + retained first-time installers (1-day retention)
- **Duration:** Run at least 7 days (weekday/weekend variance)
- **Localized:** Test across up to 5 languages simultaneously
-
-## Custom Store Listings
-
- **Max:** 50 per app (100 for Play partners)
- **Customizable:** Title, short/full description, icon, screenshots, feature graphic, video
- **Targeting:** Country/region, pre-registration, install state, Google Ads campaigns, inactive/churned users (28+ days)
- **2025 addition:** Gemini AI auto-generates text for CSLs in Play Console
-
-## Promotional Content (LiveOps)
-
-| Type              | Description                    | Duration             |
-| ----------------- | ------------------------------ | -------------------- |
-| Offers            | Discounts, free items, bundles | Up to 28 days        |
-| Events            | Time-limited in-app events     | Must have time limit |
-| Major Update      | Significant new features       | Max 1 week           |
-| Crossover (games) | Cross-game/IP collaboration    | Varies               |
-
- Submit **4+ days** before start (standard review)
- Submit **14+ days** before for featuring requests
- **Impact:** "Over twice as many explore acquisitions during featuring" (official Google)
-
-## Android Vitals — Ranking Thresholds
-
-Apps exceeding these thresholds get **reduced visibility** in search and recommendations.
-
-| Metric                       | Overall Threshold | Per-Device Threshold |
-| ---------------------------- | ----------------- | -------------------- |
-| User-Perceived Crash Rate    | **1.09%**         | 8%                   |
-| User-Perceived ANR Rate      | **0.47%**         | 8%                   |
-| Excessive Partial Wake Locks | 5%                | N/A                  |
-
-**Consequences:** Reduced search visibility, warning labels on listing, quality alerts to users before install.
-**Recovery:** Google checks daily using 28-day rolling average.
-
-## Search Ranking — Official Factors
-
-Google confirms these affect ranking:
-
-1. **Metadata relevance** — Title carries most weight. NLP scans title + short desc + full desc.
-2. **App quality** — Android Vitals (crash/ANR rates)
-3. **Ratings and reviews** — Star rating + review text. 85% of featured apps have 4.0+
-4. **Install volume and velocity** — Total installs + daily/weekly frequency
-5. **Engagement and retention** — Session frequency, duration, retention rates
-6. **Update frequency** — Regular updates signal active maintenance
-7. **Localization** — Regional keyword/visual adaptation. 59% of US apps localize titles.
-
-Sources: support.google.com/googleplay/android-developer/answer/4448378,
-support.google.com/googleplay/android-developer/answer/9898842,
-developer.android.com/topic/performance/vitals
@@ -1,213 +0,0 @@
-# ASO Audit Report Template
-
-Use this structure for all ASO audit reports.
-
---
-
-## Header
-
-```
-# ASO Audit: {App Name}
-**Store:** {Apple App Store / Google Play}
-**URL:** {listing URL}
-**Audit date:** {date}
-**Brand tier:** {Dominant / Established / Challenger} — {one-line justification}
-**Overall Score:** {score}/100 (Grade: {A/B/C/D/F})
-```
-
---
-
-## Score Card
-
-```
-| Dimension | Score | Grade | Key Issue |
-|-----------|-------|-------|-----------|
-| Title & Subtitle | X/10 | {grade} | {one-line summary} |
-| Description | X/10 | {grade} | {one-line summary} |
-| Visual Assets | X/10 | {grade} | {one-line summary} |
-| Ratings & Reviews | X/10 | {grade} | {one-line summary} |
-| Metadata & Freshness | X/10 | {grade} | {one-line summary} |
-| Conversion Signals | X/10 | {grade} | {one-line summary} |
-| **OVERALL** | **{weighted}/100** | **{grade}** | |
-```
-
-Grade scale per dimension: 9-10 = A, 7-8 = B, 5-6 = C, 3-4 = D, 1-2 = F
-
---
-
-## Top 3 Quick Wins
-
-Highest-impact changes that take under 1 hour:
-
-```
-### 1. {Action verb} — {specific change}
-**Impact:** {High/Medium} | **Effort:** {<15 min / <30 min / <1 hour}
-**Current:** {what it is now}
-**Recommended:** {exact replacement, with character count}
-**Why:** {one sentence explaining the impact}
-
-### 2. ...
-### 3. ...
-```
-
---
-
-## Detailed Findings
-
-### Title & Subtitle Analysis
-
-```
-**Current title:** "{title}" ({X}/30 chars used)
-**Current subtitle/short desc:** "{subtitle}" ({X}/30 or /80 chars used)
-
-**Issues found:**
- {issue 1}
- {issue 2}
-
-**Recommended title:** "{new title}" ({X}/30 chars) — {rationale}
-**Recommended subtitle:** "{new subtitle}" ({X}/30 or /80 chars) — {rationale}
-```
-
-### Description Analysis
-
-```
-**First 3 lines (above fold):**
-> {quoted text}
-
-**Issues found:**
- {issue 1}
- {issue 2}
-
-**Keyword density (Google Play only):** {X}% — target: 2-3%
-**Top keywords found:** {keyword1} (Xn), {keyword2} (Xn), ...
-**Missing high-value keywords:** {keyword1}, {keyword2}, ...
-
-**Recommended first 3 lines:**
-> {rewritten text}
-```
-
-### Visual Assets Analysis
-
-```
-**Screenshots:** {count} ({store} shows first {3/all} in search)
-**Preview video:** {Yes/No}
-**Icon assessment:** {description}
-**Feature graphic (Google Play):** {Yes/No}
-
-**Screenshot audit:**
-1. {screenshot 1 description} — {pass/issue}
-2. {screenshot 2 description} — {pass/issue}
-...
-
-**Recommendations:**
- {specific visual change 1}
- {specific visual change 2}
-```
-
-### Ratings & Reviews Analysis
-
-```
-**Average rating:** {X.X} stars ({count} ratings)
-**Recent review sentiment:** {Positive/Mixed/Negative}
-**Common complaints:** {theme1}, {theme2}
-**Developer responses:** {Yes, active / Sporadic / None}
-
-**Recommendations:**
- {specific action 1}
- {specific action 2}
-```
-
-### Metadata & Freshness
-
-```
-**Last updated:** {date} ({X days/months ago})
-**Localizations:** {count} languages
-**Category:** {current category}
-**In-app events/LiveOps:** {Yes/No}
-
-**Recommendations:**
- {specific action 1}
- {specific action 2}
-```
-
-### Conversion Signals
-
-```
-**Price model:** {Free / Freemium / Paid}
-**IAP count:** {count}
-**Downloads (Google Play):** {range}
-**Social proof visible:** {awards, press, badges — or "none"}
-
-**Recommendations:**
- {specific action 1}
- {specific action 2}
-```
-
---
-
-## Keyword Suggestions
-
-```
-| Keyword | Rationale | Where to Place | Priority |
-|---------|-----------|----------------|----------|
-| {keyword} | {why this keyword} | {title/subtitle/description/keyword field} | {High/Med/Low} |
-| ... | ... | ... | ... |
-```
-
-Note: Without paid ASO tools, exact search volume is unavailable. These
-suggestions are based on category analysis, competitor metadata, and semantic
-relevance. Validate with AppTweak, Sensor Tower, or MobileAction for volume data.
-
---
-
-## Competitor Comparison (if applicable)
-
-```
-| Metric | {Your App} | {Competitor 1} | {Competitor 2} |
-|--------|-----------|----------------|----------------|
-| Title keywords | ... | ... | ... |
-| Rating | ... | ... | ... |
-| Screenshots | ... | ... | ... |
-| Video | ... | ... | ... |
-| Description keywords | ... | ... | ... |
-| Last updated | ... | ... | ... |
-| Overall ASO score | ... | ... | ... |
-```
-
---
-
-## Priority Action Plan
-
-Ordered by impact (high to low), grouped by effort:
-
-```
-### Do This Week (Quick Wins)
-1. {action} — {expected impact}
-2. {action} — {expected impact}
-
-### Do This Month (Medium Effort)
-3. {action} — {expected impact}
-4. {action} — {expected impact}
-
-### Plan for Next Quarter (High Effort)
-5. {action} — {expected impact}
-6. {action} — {expected impact}
-```
-
---
-
-## Limitations
-
-Always include this section:
-
-> **What this audit cannot measure without paid ASO tools:**
->
-> - Exact keyword search volume and difficulty scores
-> - Historical keyword ranking positions
-> - Download and revenue estimates
-> - Apple keyword field contents (hidden from public view)
-> - Install conversion rate data (only available to app owner in console)
-> - A/B test results from previous experiments
->
-> For these data points, consider using AppTweak ($69/mo), Sensor Tower, or
-> MobileAction ($69/mo).
@@ -1,213 +0,0 @@
-# ASO Scoring Criteria
-
-Score each dimension 0-10 using the rubrics below.
-**Apply brand maturity tier adjustments** from Phase 1.5 of the main skill.
-
---
-
-## Brand Maturity Adjustments (apply to all dimensions)
-
-Before scoring, determine the app's tier: **Dominant**, **Established**, or **Challenger**.
-
-**Dominant apps (Instagram, Uber, Spotify, WhatsApp, Netflix):**
-
- Brand-only titles score 8+ (the brand IS the keyword)
- Lifestyle/brand screenshots score same as captioned UI screenshots
- Generic What's New at weekly+ cadence scores 8+
- Missing in-app events for utility apps is not a penalty
- Description scored on conversion quality only, not keyword presence
- Localization scored relative to actual market footprint
- Missing preview video is acceptable if brand awareness is near-universal
-
-**Established apps (Duolingo, Strava, Notion, Calm, Cash App):**
-
- Brand-first titles with 1-2 keywords score normally
- Strategic description/visual choices get benefit of the doubt
- All other dimensions scored normally
-
-**Challenger apps (most apps):**
-
- Scored strictly against textbook ASO — every character and feature matters
-
-**Key principle:** Before docking points, ask: "Is this a mistake or a data-informed
-choice by a team with more information than I have?"
-
---
-
-## 1. Title & Subtitle (Weight: 20%)
-
-**Challenger rubric:**
-
-| Score | Criteria                                                                                                                                                                |
-| ----- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| 9-10  | Brand + high-value keyword in title, complementary keywords in subtitle, no word repetition across fields, near max character usage, instantly communicates app purpose |
-| 7-8   | Good keyword presence, minor character waste (5+ unused chars), clear purpose                                                                                           |
-| 5-6   | Has keywords but poor placement, some repetition between fields, purpose somewhat clear                                                                                 |
-| 3-4   | Title is brand-only or generic, subtitle missing or weak, poor character usage                                                                                          |
-| 1-2   | No keyword strategy, title doesn't communicate purpose, major character waste                                                                                           |
-| 0     | Cannot assess (data unavailable)                                                                                                                                        |
-
-**Dominant/Established adjustment:** Brand-only titles (e.g., "Instagram") are
-valid if the brand has high search volume. Score 8+ for Dominant apps where
-brand recognition eliminates the need for generic keywords. Evaluate whether
-unused characters represent waste or intentional simplicity.
-
-**Check for:**
-
- Characters used vs limit (title: 30, subtitle/short desc: 30/80). "Near max" = within 3 chars of the limit (27+/30, 77+/80)
- Primary keyword in title
- Keyword duplication between title and subtitle
- Whether app purpose is immediately clear
- Unnecessary words (articles, prepositions) consuming space
- Special characters or claims ("#1", "best") that risk rejection (Apple)
-
---
-
-## 2. Description (Weight: 15%)
-
-### Apple App Store
-
-| Score | Criteria                                                                                                                                               |
-| ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| 9-10  | First 3 lines hook with clear value prop, structured with features/benefits/social proof/CTA, promotional text actively used, compelling and scannable |
-| 7-8   | Good opening, decent structure, could improve scannability or CTA                                                                                      |
-| 5-6   | Generic opening ("Welcome to..."), some structure, missing CTA or social proof                                                                         |
-| 3-4   | Wall of text, no clear value prop above fold, no promotional text                                                                                      |
-| 1-2   | Minimal or boilerplate description, no effort                                                                                                          |
-| 0     | Cannot assess                                                                                                                                          |
-
-### Google Play
-
-| Score | Criteria                                                                                                                                     |
-| ----- | -------------------------------------------------------------------------------------------------------------------------------------------- |
-| 9-10  | Keywords in first 3 sentences, 2-3% natural density throughout, HTML formatting used, structured sections, strong CTA, keywords feel natural |
-| 7-8   | Good keyword presence, some structure, density slightly off (1-2% or 3-4%)                                                                   |
-| 5-6   | Keywords present but sparse (<1%) or stuffed (>5%), weak structure                                                                           |
-| 3-4   | No keyword strategy visible, poor formatting, wall of text                                                                                   |
-| 1-2   | Minimal description, no keywords, no structure                                                                                               |
-| 0     | Cannot assess                                                                                                                                |
-
-**Check for:**
-
- First 3 lines quality (visible before "Read More")
- Feature-benefit framing (not just feature lists)
- Social proof (downloads, awards, press mentions)
- Call to action
- Keyword density (Google Play only - count target keywords / total words)
- HTML formatting usage (Google Play)
- Promotional text presence and quality (Apple)
-
---
-
-## 3. Visual Assets (Weight: 25%)
-
-| Score | Criteria                                                                                                                                                                      |
-| ----- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| 9-10  | 8-10 screenshots with clear messaging/captions, preview video present, screenshots tell a story in sequence, each communicates one benefit, icon is distinctive and memorable |
-| 7-8   | 6-7 screenshots with captions, good icon, no video OR good video but some screenshot messaging unclear                                                                        |
-| 5-6   | 5+ screenshots but weak/no captions, basic icon, no video, screenshots are UI dumps                                                                                           |
-| 3-4   | 3-4 screenshots, no captions, generic icon, no storytelling                                                                                                                   |
-| 1-2   | Fewer than 3 screenshots, or screenshots are raw unedited UI, poor icon                                                                                                       |
-| 0     | Cannot assess                                                                                                                                                                 |
-
-**Check for:**
-
- Screenshot count (minimum 5, ideal 8-10)
- Caption/overlay text on screenshots (one message per screen, 5-7 words max)
- First 3 screenshots (highest conversion impact on Apple)
- Preview video presence and quality
- Icon distinctiveness (no text in icon, bold shapes, stands out)
- Feature graphic presence (Google Play - mandatory for featured placements)
- Screenshot storytelling flow (do they tell a coherent story?)
- Localized visual assets (for non-English markets)
- Caption keywords (Apple - indexed since June 2025)
-
---
-
-## 4. Ratings & Reviews (Weight: 20%)
-
-| Score | Criteria                                                                                               |
-| ----- | ------------------------------------------------------------------------------------------------------ |
-| 9-10  | 4.5+ stars, 10K+ ratings, recent reviews positive, developer responds to negatives, steady review flow |
-| 7-8   | 4.0-4.4 stars, 1K+ ratings, mostly positive recent reviews, some developer responses                   |
-| 5-6   | 3.5-3.9 stars, 500+ ratings, mixed recent reviews, no developer responses                              |
-| 3-4   | 3.0-3.4 stars, <500 ratings, negative themes in recent reviews                                         |
-| 1-2   | Below 3.0 stars, few ratings, no developer engagement, visible complaints                              |
-| 0     | No ratings yet or cannot assess                                                                        |
-
-**Check for:**
-
- Average rating (target: 4.0+ minimum, 4.5+ ideal)
- Total rating count
- Recent review sentiment (last 5-10 visible reviews)
- Common complaint themes (bugs, crashes, pricing, UX)
- Developer response presence and quality
- Rating trend (improving or declining, if visible)
- Review recency (fresh reviews signal active user base)
-
---
-
-## 5. Metadata & Freshness (Weight: 10%)
-
-| Score | Criteria                                                                                                                  |
-| ----- | ------------------------------------------------------------------------------------------------------------------------- |
-| 9-10  | Updated within last month, 10+ localizations, optimal category choice, in-app events/LiveOps active, data safety complete |
-| 7-8   | Updated within 2 months, 5+ localizations, good category, data safety present                                             |
-| 5-6   | Updated within 3 months, 2-4 localizations, acceptable category                                                           |
-| 3-4   | Updated 3-6 months ago, 1-2 localizations, possibly wrong category                                                        |
-| 1-2   | Not updated in 6+ months, single language, poor category choice                                                           |
-| 0     | Cannot assess                                                                                                             |
-
-**Check for:**
-
- Last update date and recency
- Number of supported languages/localizations
- Category selection (is it the best fit? less competitive alternative?)
- In-app events (Apple) or promotional content (Google) presence
- Data safety / privacy nutrition label completeness
- Age rating appropriateness
- Version history quality (do release notes communicate value?)
- What's New text quality
-
---
-
-## 6. Conversion Signals (Weight: 10%)
-
-| Score | Criteria                                                                                                                                                          |
-| ----- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| 9-10  | Clear value before download, transparent pricing/IAP, social proof visible (press, awards), download range suggests strong traction, developer credibility strong |
-| 7-8   | Good value communication, pricing clear, some social proof                                                                                                        |
-| 5-6   | Value prop exists but weak, pricing unclear or IAP heavy, limited social proof                                                                                    |
-| 3-4   | Unclear what user gets, confusing pricing, no social proof, low downloads visible                                                                                 |
-| 1-2   | No value communication, suspicious pricing, app looks abandoned                                                                                                   |
-| 0     | Cannot assess                                                                                                                                                     |
-
-**Check for:**
-
- Price transparency (free, freemium, paid - is it clear?)
- In-app purchase list quality (do IAP names communicate value?)
- Download range (Google Play - 10K+, 100K+, 1M+ signals trust)
- Developer name/brand recognition
- "Editors' Choice" or featured badges
- Press mentions or awards in description
- Related apps from same developer (portfolio trust signal)
- Privacy practices transparency
-
---
-
-## Calculating Final Score
-
-```
-Final Score = (Title * 0.20) + (Description * 0.15) + (Visuals * 0.25)
-            + (Ratings * 0.20) + (Metadata * 0.10) + (Conversion * 0.10)
-
-Scale to 100: Final Score * 10
-```
-
-**Example:** Title: 7, Description: 6, Visuals: 8, Ratings: 9, Metadata: 5, Conversion: 7
-
-```
-(7 * 0.20) + (6 * 0.15) + (8 * 0.25) + (9 * 0.20) + (5 * 0.10) + (7 * 0.10)
-= 1.4 + 0.9 + 2.0 + 1.8 + 0.5 + 0.7
-= 7.3 → 73/100 → Grade: B
-```
@@ -1,6 +1,6 @@
 ---
 name: churn-prevention
-description: "When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers or wants to build systems to prevent it. For post-cancel win-back email sequences, see emails. For in-app upgrade paywalls, see paywalls."
+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.1.0
 ---
@@ -252,7 +252,7 @@ Health Score = (
 | Trigger | Intervention |
 |---------|-------------|
 | Usage drop >50% for 2 weeks | "We noticed you haven't used [feature]. Need help?" email |
-| Approaching plan limit | Upgrade nudge (not a wall — paywalls handles this) |
+| Approaching plan limit | Upgrade nudge (not a wall — paywall-upgrade-cro handles this) |
 | No login for 14 days | Re-engagement email with recent product updates |
 | NPS detractor (0-6) | Personal follow-up within 24 hours |
 | Support ticket unresolved >48h | Escalation + proactive status update |
@@ -360,7 +360,7 @@ Test one variable at a time:
 | Offer presentation (modal vs full page) | Full page gets more attention | Save rate |
 | Copy tone (empathetic vs direct) | Empathetic reduces friction | Save rate |

-**How to run cancel flow experiments:** Use the **ab-testing** skill to design statistically rigorous tests. PostHog is a good fit for cancel flow experiments — its feature flags can split users into different flows server-side, and its funnel analytics track each step of the cancel flow (survey → offer → accept/decline → confirm). See the [PostHog integration guide](../../tools/integrations/posthog.md) for setup.
+**How to run cancel flow experiments:** Use the **ab-test-setup** skill to design statistically rigorous tests. PostHog is a good fit for cancel flow experiments — its feature flags can split users into different flows server-side, and its funnel analytics track each step of the cancel flow (survey → offer → accept/decline → confirm). See the [PostHog integration guide](../../tools/integrations/posthog.md) for setup.

 ---

@@ -416,9 +416,9 @@ For implementation, see the [tools registry](../../tools/REGISTRY.md).

 ## Related Skills

- **emails**: For win-back email sequences after cancellation
- **paywalls**: For in-app upgrade moments and trial expiration
- **pricing**: For plan structure and annual discount strategy
- **onboarding**: For activation to prevent early churn
- **analytics**: For setting up churn signal events
- **ab-testing**: For testing cancel flow variations with statistical rigor
+- **email-sequence**: For win-back email sequences after cancellation
+- **paywall-upgrade-cro**: For in-app upgrade moments and trial expiration
+- **pricing-strategy**: For plan structure and annual discount strategy
+- **onboarding-cro**: For activation to prevent early churn
+- **analytics-tracking**: For setting up churn signal events
+- **ab-test-setup**: For testing cancel flow variations with statistical rigor
@@ -184,7 +184,7 @@ For multi-plan products, downgrade is the strongest save:
 When the cancel reason is "switching to competitor":

 1. **Ask which competitor** (optional, don't force it)
-2. **Show a comparison** if you have one (see competitors skill)
+2. **Show a comparison** if you have one (see competitor-alternatives skill)
 3. **Offer a migration credit** ("We'll match their price for 3 months")
 4. **Request a feedback call** ("15 minutes to understand what we're missing")

@@ -226,7 +226,7 @@ from customers like you.
 | Day 60 | Address their specific cancel reason if resolved |
 | Day 90 | Final win-back with special offer |

-**For detailed win-back email sequences**: See the emails skill.
+**For detailed win-back email sequences**: See the email-sequence skill.

 ---

@@ -290,7 +290,7 @@ The most effective cancel flows use segmentation to show different offers to dif
 - [ ] Set up proactive intervention triggers
 - [ ] A/B test discount amounts and offer types
 - [ ] Segment flows by plan, tenure, and usage
- [ ] Post-cancel win-back sequence (coordinate with emails skill)
+- [ ] Post-cancel win-back sequence (coordinate with email-sequence skill)
 - [ ] Cohort analysis: churn by channel, plan, tenure

 ---
@@ -1,6 +1,6 @@
 ---
 name: cold-email
-description: Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions "cold outreach," "prospecting email," "outbound email," "email to leads," "reach out to prospects," "sales email," "follow-up email sequence," "nobody's replying to my emails," or "how do I write a cold email." Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences. For warm/lifecycle email sequences, see emails. For sales collateral beyond emails, see sales-enablement.
+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
 ---
@@ -152,7 +152,7 @@ Use this data to inform your writing — not as a checklist to satisfy.
 ## Related Skills

 - **copywriting**: For landing pages and web copy
- **emails**: For lifecycle/nurture email sequences (not cold outreach)
- **social**: For LinkedIn and social posts
+- **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
@@ -1,5 +1,5 @@
 ---
-name: competitors
+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,' 'competitive landing pages,' 'how do we compare to X,' 'battle card,' or 'competitor teardown.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For sales-specific competitor docs, see sales-enablement."
 metadata:
  version: 1.1.0
@@ -1,6 +1,6 @@
 ---
 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," "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.
+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.1.0
 ---
@@ -361,5 +361,5 @@ Visual or structured representation of how content interconnects.
 - **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
- **emails**: For email-based content
- **social**: For social media content
+- **email-sequence**: For email-based content
+- **social-content**: For social media content
@@ -169,7 +169,7 @@ URL structure, navigation hierarchy, and internal linking all depend on how cont

 ### Email Sequences

-Pull CMS content into email templates for consistent messaging across web and email. Case studies, testimonials, and blog posts can feed email nurture sequences. See **emails** skill.
+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.

 ---

@@ -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,' 'copy sweep,' 'tighten this up,' 'this reads awkwardly,' 'clean up this text,' 'too wordy,' or 'sharpen the messaging.' Use this when the user already has copy and wants it improved rather than rewritten from scratch. For writing new copy, see copywriting."
+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.1.0
+  version: 1.3.0
 ---

 # Copy Editing
@@ -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,15 +485,16 @@ 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?

 ---

 ## Related Skills

 - **copywriting**: For writing new copy from scratch (use this skill to edit after your first draft is complete)
- **cro**: For broader page optimization beyond copy
+- **page-cro**: For broader page optimization beyond copy
 - **marketing-psychology**: For understanding why certain edits improve conversion
- **ab-testing**: For testing copy variations
+- **ab-test-setup**: For testing copy variations

 ---

@@ -444,4 +505,4 @@ This iterative process ensures each edit doesn't create new problems while respe
 | Writing new page copy from scratch | copywriting |
 | Reviewing and improving existing copy | copy-editing (this skill) |
 | Editing copy you just wrote | copy-editing (this skill) |
-| Structural or strategic page changes | cro |
+| Structural or strategic page changes | page-cro |
@@ -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,6 +1,6 @@
 ---
 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," "CTA copy," "value proposition," "tagline," "subheadline," "hero section copy," "above the fold," "this copy is weak," "make this more compelling," or "help me describe my product." Use this whenever someone is working on website text that needs to persuade or convert. For email copy, see emails. For popup copy, see popups. For editing existing copy, see copy-editing.
+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.1.0
 ---
@@ -246,7 +246,7 @@ For headlines and CTAs, provide 2-3 options:
 ## Related Skills

 - **copy-editing**: For polishing existing copy (use after your draft)
- **cro**: If page structure/strategy needs work, not just copy
- **emails**: For email copywriting
- **popups**: For popup and modal copy
- **ab-testing**: To test copy variations
+- **page-cro**: If page structure/strategy needs work, not just copy
+- **email-sequence**: For email copywriting
+- **popup-cro**: For popup and modal copy
+- **ab-test-setup**: To test copy variations
@@ -1,68 +0,0 @@
-# Page CRO Reference
-
-Detailed page-level conversion optimization guidance. Use alongside the main CRO skill.
-
-## Page Type Audit Checklists
-
-### Homepage
-
- [ ] Hero clearly communicates what you do and for whom
- [ ] Primary CTA visible above the fold
- [ ] Social proof within first viewport
- [ ] Clear navigation to key pages (pricing, features, use cases)
- [ ] Both "ready to buy" and "still researching" paths available
- [ ] Mobile experience tested and optimized
-
-### Landing Page
-
- [ ] Message matches the traffic source (ad, email, social post)
- [ ] Single conversion goal — no competing CTAs
- [ ] Navigation removed or minimized
- [ ] Complete argument made on one page (no required clicks)
- [ ] Form or CTA repeated after key sections
- [ ] Page speed under 3 seconds
-
-### Pricing Page
-
- [ ] Plans are easy to compare at a glance
- [ ] Recommended plan is visually highlighted
- [ ] Feature comparison table included
- [ ] Annual vs monthly toggle with savings shown
- [ ] FAQ addresses common pricing objections
- [ ] Free trial or money-back guarantee prominent
- [ ] Enterprise/contact option for larger buyers
-
-### Feature Page
-
- [ ] Feature connected to a clear business benefit
- [ ] Real use cases or examples shown
- [ ] Screenshot or demo of the feature in action
- [ ] CTA to try the feature (not just "learn more")
- [ ] Related features cross-linked
-
-### Blog Post
-
- [ ] Contextual CTA matching the content topic
- [ ] Inline CTA at a natural stopping point (not just end)
- [ ] Content upgrade or lead magnet related to the topic
- [ ] Author bio with credibility signals
- [ ] Related posts suggested
-
-## Above-the-Fold Priorities
-
-The first viewport should answer three questions:
-
-1. **What is this?** — Clear headline with the core value proposition
-2. **Why should I care?** — Subheadline connecting to the visitor's problem or desire
-3. **What do I do next?** — Visible primary CTA
-
-If a visitor can't answer all three within 5 seconds, the above-the-fold content needs work.
-
-## Mobile CRO Considerations
-
- Thumb-friendly CTA buttons (min 44x44px)
- Sticky CTA bar for long pages
- Simplified forms (consider progressive disclosure)
- Test with real devices, not just browser resize
- Prioritize speed — mobile users are less patient
- Consider mobile-specific CTAs (click-to-call, app deep links)
@@ -1,6 +1,6 @@
 ---
 name: customer-research
-description: When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," or "find out why customers churn/convert/buy." Use for both analyzing existing research assets AND gathering new research from online sources. For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.
+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
 ---
@@ -121,17 +121,18 @@ Choose sources based on your ICP type — then read `references/source-guides.md

 | ICP Type | Primary Sources |
 |----------|----------------|
-| B2B SaaS / technical buyers | Reddit (role-specific subs), G2/Capterra, Hacker News, LinkedIn, Indie Hackers |
-| SMB / founders | Reddit (r/entrepreneur, r/smallbusiness), Indie Hackers, Product Hunt, Facebook Groups |
+| 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 |
+| 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
+- Need competitive intel? → Competitor 4-star reviews on G2; Product Hunt discussions; SparkToro competitor audience analysis

 ### What to Extract from Each Source

@@ -261,8 +262,8 @@ Don't ask all five at once — lead with #1 and #2, then follow up as needed.
 | When to hand off | Skill |
 |-----------------|-------|
 | Writing copy informed by the research | `copywriting` |
-| Optimizing a page using VOC insights | `cro` |
-| Building a competitor comparison page | `competitors` |
+| 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` |
@@ -282,6 +282,61 @@ Comments on review videos are especially valuable — these are people actively

 ---

+## 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:
@@ -319,6 +374,7 @@ Not all sources carry equal weight. Use this guide when assigning confidence lab
 | 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
@@ -1,6 +1,6 @@
 ---
-name: emails
-description: When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding.
+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," "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.1.0
 ---
@@ -304,8 +304,8 @@ For implementation, see the [tools registry](../../tools/REGISTRY.md). Key email

 - **lead-magnets**: For planning lead magnets that feed into nurture sequences
 - **churn-prevention**: For cancel flows, save offers, and dunning strategy (email supports this)
- **onboarding**: For in-app onboarding (email supports this)
+- **onboarding-cro**: For in-app onboarding (email supports this)
 - **copywriting**: For landing pages emails link to
- **ab-testing**: For testing email elements
- **popups**: For email capture popups
+- **ab-test-setup**: For testing email elements
+- **popup-cro**: For email capture popups
 - **revops**: For lifecycle stages that trigger email sequences
@@ -1,6 +1,13 @@
-# Form CRO Reference
+---
+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," "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.1.0
+---

-Detailed form optimization guidance. Use alongside the main CRO skill.
+# Form CRO
+
+You are an expert in form optimization. Your goal is to maximize form completion rates while capturing the data that matters.

 ## Initial Assessment

@@ -416,6 +423,7 @@ Ideas to A/B test with expected outcomes

 ## Related Skills

- **signup**: For account creation forms
- **popups**: For forms inside popups/modals
- **ab-testing**: For testing form changes
+- **signup-flow-cro**: For account creation forms
+- **popup-cro**: For forms inside popups/modals
+- **page-cro**: For the page containing the form
+- **ab-test-setup**: For testing form changes
@@ -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,5 +1,5 @@
 ---
-name: free-tools
+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," "free resource," "ROI calculator," "grader tool," "audit tool," "should I build a free tool," or "tools for lead gen." Use this whenever someone wants to build something useful and give it away to attract leads or earn links. For downloadable content lead magnets (ebooks, checklists, templates), see lead-magnets.
 metadata:
  version: 1.1.0
@@ -173,7 +173,7 @@ Rate each factor 1-5:
 ## Related Skills

 - **lead-magnets**: For downloadable content lead magnets (ebooks, checklists, templates)
- **cro**: For optimizing the tool's landing page
+- **page-cro**: For optimizing the tool's landing page
 - **seo-audit**: For SEO-optimizing the tool
- **analytics**: For measuring tool usage
- **emails**: For nurturing leads from the tool
+- **analytics-tracking**: For measuring tool usage
+- **email-sequence**: For nurturing leads from the tool
@@ -77,10 +77,10 @@
    {
      "id": 6,
      "prompt": "How do I optimize the landing page for our free tool to get more signups? The tool itself is great but nobody finds it.",
-      "expected_output": "Should recognize this is a landing page conversion optimization task, not a free tool strategy task. Should defer to or cross-reference the cro skill for optimizing the tool's landing page conversion rate. May provide free-tool-specific context (gating strategy, value demonstration) but should make clear that cro is the right skill for page conversion optimization.",
+      "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 cro skill",
+        "References or defers to page-cro skill",
        "May provide free-tool-specific context",
        "Does not attempt full page CRO using free tool strategy patterns"
      ],
@@ -1,5 +1,5 @@
 ---
-name: launch
+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,' 'product update,' 'how do I launch this,' 'launch checklist,' 'GTM plan,' or 'we're about to ship.' Use this whenever someone is preparing to release something publicly. For ongoing marketing after launch, see marketing-ideas."
 metadata:
  version: 1.1.0
@@ -346,8 +346,8 @@ Even small changelog updates remind customers your product is evolving. This bui
 ## Related Skills

 - **marketing-ideas**: For additional launch tactics (#22 Product Hunt, #23 Early Access Referrals)
- **emails**: For launch and onboarding email sequences
- **cro**: For optimizing launch landing pages
+- **email-sequence**: For launch and onboarding email sequences
+- **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
@@ -1,6 +1,6 @@
 ---
 name: lead-magnets
-description: When the user wants to create, plan, or optimize a lead magnet for email capture or lead generation. Also use when the user mentions "lead magnet," "gated content," "content upgrade," "downloadable," "ebook," "cheat sheet," "checklist," "template download," "opt-in," "freebie," "PDF download," "resource library," "content offer," "email capture content," "Notion template," "spreadsheet template," or "what should I give away for emails." Use this for planning what to create and how to distribute it. For interactive tools as lead magnets, see free-tools. For writing the actual content, see copywriting. For the email sequence after capture, see emails.
+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
 ---
@@ -116,7 +116,7 @@ Goal: Help implement. Remove friction to purchase.
 | Template | "Ready-to-Use Sales Email Templates" |
 | Free trial | "14-Day Free Trial" |
 | Implementation guide | "Migration Checklist: Switch in 30 Minutes" |
-| ROI calculator | "Calculate Your Savings" (→ see **free-tools**) |
+| ROI calculator | "Calculate Your Savings" (→ see **free-tool-strategy**) |

 ---

@@ -147,8 +147,8 @@ Rule of thumb: Ask for the minimum needed. Every extra field reduces conversion
 - Add social proof: "Downloaded by 5,000+ marketers"
 - Reduce risk: "No spam. Unsubscribe anytime."

-**For form optimization**: See **cro** skill
-**For popup implementation**: See **popups** skill
+**For form optimization**: See **form-cro** skill
+**For popup implementation**: See **popup-cro** skill

 ---

@@ -163,7 +163,7 @@ Rule of thumb: Ask for the minimum needed. Every extra field reduces conversion
 5. **Form** — Minimal fields, clear CTA button
 6. **FAQ** — Address hesitations (Is it really free? What format?)

-**For landing page optimization**: See **cro** skill
+**For landing page optimization**: See **page-cro** skill

 ### Delivery Methods

@@ -196,14 +196,14 @@ Don't waste the thank you page. After they've converted:

 - Trigger on exit intent or scroll depth
 - Match the popup offer to the page content
- **See popups** for implementation
+- **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** for social strategy
+- **See social-content** for social strategy

 ### Paid Promotion

@@ -298,13 +298,13 @@ When creating a lead magnet strategy, provide:

 ## Related Skills

- **free-tools**: For interactive tools as lead magnets (calculators, graders, quizzes)
+- **free-tool-strategy**: For interactive tools as lead magnets (calculators, graders, quizzes)
 - **copywriting**: For writing the lead magnet content itself
- **emails**: For nurture sequences after lead capture
- **cro**: For optimizing lead magnet landing pages
- **popups**: For popup-based lead capture
- **cro**: For optimizing capture forms
+- **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**: For measuring lead magnet performance
+- **analytics-tracking**: For measuring lead magnet performance
 - **paid-ads**: For paid promotion of lead magnets
- **social**: For social media promotion
+- **social-content**: For social media promotion
@@ -171,7 +171,7 @@ Detailed creation guidance for each lead magnet format.

 **Implementation**: Gate results behind email capture. The quiz itself is ungated — the personalized results require an email.

-**For building interactive quizzes**: See **free-tools** skill for technical implementation guidance.
+**For building interactive quizzes**: See **free-tool-strategy** skill for technical implementation guidance.

 ---

@@ -1,6 +1,6 @@
 ---
 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,' 'ideas to grow,' 'what else can I try,' 'I don't know how to market this,' 'brainstorm marketing,' or 'what marketing should I do.' Use this as a starting point whenever someone is stuck or looking for inspiration on how to grow. For specific channel execution, see the relevant skill (paid-ads, social, emails, etc.)."
+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.1.0
 ---
@@ -161,7 +161,7 @@ When recommending ideas, provide for each:
 ## Related Skills

 - **programmatic-seo**: For scaling SEO content (#4)
- **competitors**: For comparison pages (#11)
- **emails**: For email marketing tactics
- **free-tools**: For engineering as marketing (#15)
+- **competitor-alternatives**: For comparison pages (#11)
+- **email-sequence**: For email marketing tactics
+- **free-tool-strategy**: For engineering as marketing (#15)
 - **referral-program**: For viral growth (#93)
@@ -448,8 +448,8 @@ When facing a marketing challenge, consider:

 ## Related Skills

- **cro**: Apply psychology to page optimization
+- **page-cro**: Apply psychology to page optimization
 - **copywriting**: Write copy using psychological principles
- **popups**: Use triggers and psychology in popups
- **pricing-page optimization**: See cro for pricing psychology
- **ab-testing**: Test psychological hypotheses
+- **popup-cro**: Use triggers and psychology in popups
+- **pricing-page optimization**: See page-cro for pricing psychology
+- **ab-test-setup**: Test psychological hypotheses
@@ -1,6 +1,6 @@
 ---
-name: onboarding
-description: When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," "new user experience," "users aren't activating," "nobody completes setup," "low activation rate," "users sign up but don't use the product," "time to value," or "first session experience." Use this whenever users are signing up but not sticking around. For signup/registration optimization, see signup. For ongoing email sequences, see emails.
+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," "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.1.0
 ---
@@ -214,7 +214,7 @@ When recommending experiments, consider tests for:

 ## Related Skills

- **signup**: For optimizing the signup before onboarding
- **emails**: For onboarding email series
- **paywalls**: For converting to paid during/after onboarding
- **ab-testing**: For testing onboarding changes
+- **signup-flow-cro**: For optimizing the signup before onboarding
+- **email-sequence**: For onboarding email series
+- **paywall-upgrade-cro**: For converting to paid during/after onboarding
+- **ab-test-setup**: For testing onboarding changes
@@ -1,13 +1,13 @@
 ---
-name: cro
-description: "When the user wants to optimize, improve, or increase conversions on any marketing page or form. Also use when the user says 'CRO,' 'conversion rate optimization,' 'this page isn't converting,' 'improve conversions,' 'why isn't this page working,' 'my landing page sucks,' 'nobody's converting,' 'low conversion rate,' 'bounce rate is too high,' 'form optimization,' 'lead form conversions,' 'form friction,' 'nobody fills out our form,' 'form abandonment,' or 'too many fields.' Use this for any conversion optimization on pages or forms. For signup/registration flows, see signup. For post-signup activation, see onboarding. For popups/modals, see popups. For paywalls, see paywalls."
+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," "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
 ---

-# Conversion Rate Optimization (CRO)
+# Page Conversion Rate Optimization (CRO)

-You are a conversion rate optimization expert. Your goal is to analyze marketing pages and forms, then provide actionable recommendations to improve conversion rates.
+You are a conversion rate optimization expert. Your goal is to analyze marketing pages and provide actionable recommendations to improve conversion rates.

 ## Initial Assessment

@@ -16,21 +16,15 @@ If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-

 Before providing recommendations, identify:

-1. **What needs optimization?** — A page, a form, or both
-2. **Page Type** (if page): Homepage, landing page, pricing, feature, blog, about
-3. **Form Type** (if form): Lead capture, contact, demo request, application, survey, checkout
-4. **Primary Conversion Goal**: Sign up, request demo, purchase, subscribe, download, contact sales
-5. **Traffic Context**: Where are visitors coming from? (organic, paid, email, social)
-
-**For page optimization**: See [references/page.md](references/page.md)
-
-**For form optimization**: See [references/form.md](references/form.md)
+1. **Page Type**: Homepage, landing page, pricing, feature, blog, about, other
+2. **Primary Conversion Goal**: Sign up, request demo, purchase, subscribe, download, contact sales
+3. **Traffic Context**: Where are visitors coming from? (organic, paid, email, social)

 ---

 ## CRO Analysis Framework

-Analyze across these dimensions, in order of impact:
+Analyze the page across these dimensions, in order of impact:

 ### 1. Value Proposition Clarity (Highest Impact)

@@ -176,14 +170,13 @@ When recommending experiments, consider tests for:
 3. What does your signup/purchase flow look like after this page?
 4. Do you have user research, heatmaps, or session recordings?
 5. What have you already tried?
-6. What type of form are you optimizing (if applicable)?

 ---

 ## Related Skills

- **signup**: If the issue is in the signup process itself
- **popups**: If considering popups as part of the strategy
- **paywalls**: For in-app upgrade moments and trial expiration
+- **signup-flow-cro**: If the issue is in the signup process itself
+- **form-cro**: If forms on the page need optimization
+- **popup-cro**: If considering popups as part of the strategy
 - **copywriting**: If the page needs a complete copy rewrite
- **ab-testing**: To properly test recommended changes
+- **ab-test-setup**: To properly test recommended changes
@@ -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,6 +1,6 @@
 ---
 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,' 'audience targeting,' 'Google Ads,' 'Facebook ads,' 'LinkedIn ads,' 'ad budget,' 'cost per click,' 'ad spend,' or 'should I run ads.' Use this for campaign strategy, audience targeting, bidding, and optimization. For bulk ad creative generation and iteration, see ad-creative. For landing page optimization, see cro."
+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.1.0
 ---
@@ -310,6 +310,6 @@ For tracking, see also: [ga4.md](../../tools/integrations/ga4.md), [segment.md](

 - **ad-creative**: For generating and iterating ad headlines, descriptions, and creative at scale
 - **copywriting**: For landing page copy that converts ad traffic
- **analytics**: For proper conversion tracking setup
- **ab-testing**: For landing page testing to improve ROAS
- **cro**: For optimizing post-click conversion rates
+- **analytics-tracking**: For proper conversion tracking setup
+- **ab-test-setup**: For landing page testing to improve ROAS
+- **page-cro**: For optimizing post-click conversion rates
@@ -1,6 +1,6 @@
 ---
-name: paywalls
-description: When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," "in-app pricing," "free users won't upgrade," "trial to paid conversion," or "how do I get users to pay." Use this for any in-product moment where you're asking users to upgrade. Distinct from public pricing pages (see cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see pricing.
+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," "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.1.0
 ---
@@ -222,6 +222,6 @@ What you've accomplished:
 ## Related Skills

 - **churn-prevention**: For cancel flows, save offers, and reducing churn post-upgrade
- **cro**: For public pricing page optimization
- **onboarding**: For driving to aha moment before upgrade
- **ab-testing**: For testing paywall variations
+- **page-cro**: For public pricing page optimization
+- **onboarding-cro**: For driving to aha moment before upgrade
+- **ab-test-setup**: For testing paywall variations
@@ -80,10 +80,10 @@
    {
      "id": 6,
      "prompt": "Can you help me optimize our public pricing page? We want more visitors to choose the Pro plan over the Basic plan.",
-      "expected_output": "Should recognize this is a public pricing page optimization task, not an in-app paywall task. Should defer to or cross-reference the cro skill for pricing page CRO. Paywall-upgrade-cro specifically handles in-app upgrade prompts for existing users, not public-facing pricing pages.",
+      "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 cro skill",
+        "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"
      ],
@@ -1,6 +1,6 @@
 ---
-name: popups
-description: When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," "overlay," "collect emails with a popup," "exit popup," "scroll trigger," "sticky bar," or "notification bar." Use this for any overlay or interrupt-style conversion element. For forms outside of popups, see cro. For general page conversion optimization, see cro.
+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," "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.1.0
 ---
@@ -448,7 +448,7 @@ Ideas to A/B test with expected outcomes
 ## Related Skills

 - **lead-magnets**: For planning lead magnets to promote via popups
- **cro**: For optimizing the form inside the popup
- **cro**: For the page context around popups
- **emails**: For what happens after popup conversion
- **ab-testing**: For testing popup variations
+- **form-cro**: For optimizing the form inside the popup
+- **page-cro**: For the page context around popups
+- **email-sequence**: For what happens after popup conversion
+- **ab-test-setup**: For testing popup variations
@@ -81,10 +81,10 @@
    {
      "id": 6,
      "prompt": "We need to optimize the lead capture form inside our popup. It currently asks for name, email, company, and phone number. Too many fields?",
-      "expected_output": "Should recognize this overlaps with form optimization. Should defer to or cross-reference the cro skill, which handles form field optimization, layout, and conversion. May provide popup-specific context (popups need minimal fields due to fleeting attention) but should make clear that cro is the right skill for detailed form optimization.",
+      "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 cro skill",
+        "References or defers to form-cro skill",
        "Notes popups need minimal fields due to context",
        "Does not attempt detailed form redesign"
      ],
@@ -1,6 +1,6 @@
 ---
-name: pricing
-description: "When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' or 'should I offer a free plan.' Use this whenever someone is figuring out what to charge or how to structure their plans. For in-app upgrade screens, see paywalls."
+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,' '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.1.0
 ---
@@ -223,9 +223,9 @@ Identifies which features customers value most:
 ## Related Skills

 - **churn-prevention**: For cancel flows, save offers, and reducing revenue churn
- **cro**: For optimizing pricing page conversion
+- **page-cro**: For optimizing pricing page conversion
 - **copywriting**: For pricing page copy
 - **marketing-psychology**: For pricing psychology principles
- **ab-testing**: For testing pricing changes
+- **ab-test-setup**: For testing pricing changes
 - **revops**: For deal desk processes and pipeline pricing
 - **sales-enablement**: For proposal templates and pricing presentations
@@ -63,24 +63,24 @@
    {
      "id": 5,
      "prompt": "What pricing psychology tactics should we use on our pricing page? We want the $79 plan to be the most popular.",
-      "expected_output": "Should apply the pricing psychology section: anchoring (show the $79 plan next to a higher-priced plan), decoy effect (make the lower plan look less valuable), visual emphasis (highlight or 'recommend' the $79 plan), charm pricing ($79 vs $80), Rule of 100 (percentage discounts below $100, dollar discounts above), loss framing (show what lower plans miss). Should provide specific pricing page design recommendations. Should cross-reference cro for broader pricing page optimization.",
+      "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 cro or marketing-psychology"
+        "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 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.",
+      "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 cro skill",
+        "References or defers to page-cro skill",
        "Explains that pricing-strategy is about pricing decisions",
        "Does not attempt full page CRO audit"
      ],
@@ -1,5 +1,5 @@
 ---
-name: product-marketing
+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,' 'who is my target audience,' 'describe my product,' 'ICP,' 'ideal customer profile,' or wants to avoid repeating foundational information across marketing tasks. Use this at the start of any new project before using other marketing skills — it creates `.agents/product-marketing-context.md` that all other skills reference for product, audience, and positioning context."
 metadata:
  version: 1.1.0
@@ -59,7 +59,7 @@
    {
      "id": 5,
      "prompt": "Do we have a product marketing context set up? I want to make sure the other marketing skills have context about our product.",
-      "expected_output": "Should check for .agents/product-marketing-context.md (and the older .claude/product-marketing-context.md location). Should report whether it exists and summarize its contents if found. If it doesn't exist, should offer to create one and explain why it's valuable (other skills like copywriting, cro, seo-audit check for it first). Should explain how other skills use this context document.",
+      "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",
@@ -235,4 +235,4 @@ 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
- **competitors**: For comparison page frameworks
+- **competitor-alternatives**: For comparison page frameworks
@@ -103,7 +103,7 @@ Beyond mixing and matching data point permutations, these are the proven playboo

 **URL structure**: `/compare/[x]-vs-[y]/` or `/[x]-vs-[y]/`

-*See also: competitors skill for detailed frameworks*
+*See also: competitor-alternatives skill for detailed frameworks*

 ---

@@ -1,6 +1,6 @@
 ---
-name: referrals
-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."
+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,' '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.1.0
 ---
@@ -251,7 +251,7 @@ For implementation, see the [tools registry](../../tools/REGISTRY.md). Key tools

 ## Related Skills

- **launch**: For launching referral program effectively
- **emails**: For referral nurture campaigns
+- **launch-strategy**: For launching referral program effectively
+- **email-sequence**: For referral nurture campaigns
 - **marketing-psychology**: For understanding referral motivation
- **analytics**: For tracking referral attribution
+- **analytics-tracking**: For tracking referral attribution
@@ -1,6 +1,6 @@
 ---
 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 emails. For pricing decisions, see pricing."
+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
 ---
@@ -338,8 +338,8 @@ For implementation, see the [tools registry](../../tools/REGISTRY.md). Key RevOp
 ## Related Skills

 - **cold-email**: For outbound prospecting emails
- **emails**: For lifecycle and nurture email flows
- **pricing**: For pricing decisions and packaging
- **analytics**: For tracking pipeline metrics and attribution
- **launch**: For go-to-market launch planning
+- **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
@@ -1,6 +1,6 @@
 ---
 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 competitors. For marketing website copy, see copywriting. For cold outreach emails, see cold-email."
+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
 ---
@@ -351,9 +351,9 @@ For partner sales enablement, see the [tools registry](../../tools/REGISTRY.md):

 ## Related Skills

- **competitors**: For public-facing comparison and alternative pages
+- **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**: For pricing decisions and packaging
+- **pricing-strategy**: For pricing decisions and packaging
 - **product-marketing-context**: For foundational positioning and messaging
@@ -1,5 +1,5 @@
 ---
-name: schema
+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," "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.1.0
@@ -408,5 +408,5 @@ Same format as above
 - **programmatic-seo**: For building SEO pages at scale
 - **site-architecture**: For page hierarchy, navigation design, and URL structure
 - **schema-markup**: For implementing structured data
- **cro**: For optimizing pages for conversion (not just ranking)
- **analytics**: For measuring SEO performance
+- **page-cro**: For optimizing pages for conversion (not just ranking)
+- **analytics-tracking**: For measuring SEO performance
@@ -1,6 +1,6 @@
 ---
-name: signup
-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. For lead capture forms (not account creation), see cro.
+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," "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.1.0
 ---
@@ -353,7 +353,7 @@ Organized by:

 ## Related Skills

- **onboarding**: For optimizing what happens after signup
- **cro**: For non-signup forms (lead capture, contact)
- **cro**: For the landing page leading to signup
- **ab-testing**: For testing signup flow changes
+- **onboarding-cro**: For optimizing what happens after signup
+- **form-cro**: For non-signup forms (lead capture, contact)
+- **page-cro**: For the landing page leading to signup
+- **ab-test-setup**: For testing signup flow changes
@@ -33,7 +33,7 @@
    {
      "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 cro). Should provide diagnostic checklist and recommendations.",
+      "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",
@@ -352,6 +352,6 @@ Mermaid diagram showing page relationships and navigation zones. Use `graph TD`
 - **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
- **cro**: For optimizing individual pages for conversion
+- **page-cro**: For optimizing individual pages for conversion
 - **schema-markup**: For implementing breadcrumb and site navigation structured data
- **competitors**: For comparison page frameworks and URL patterns
+- **competitor-alternatives**: For comparison page frameworks and URL patterns
@@ -1,8 +1,8 @@
 ---
-name: social
+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,' '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.1.0
+  version: 1.2.0
 ---

 # Social Content
@@ -108,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

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

 ---

@@ -274,6 +322,6 @@ Instead of guessing, analyze what's working for top creators in your niche:
 ## Related Skills

 - **copywriting**: For longer-form content that feeds social
- **launch**: For coordinating social with launches
- **emails**: For nurturing social audience via email
+- **launch-strategy**: For coordinating social with launches
+- **email-sequence**: For nurturing social audience via email
 - **marketing-psychology**: For understanding what drives engagement
@@ -74,6 +74,9 @@ Quick reference for AI agents to discover tool capabilities and integration meth
 | 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) |
@@ -340,6 +343,36 @@ Traffic analytics, competitor benchmarking, and market research.

 **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.
@@ -330,7 +330,7 @@ ActiveCampaign uses REST with resource wrapping (e.g., `{ "contact": {...} }`).

 ## Relevant Skills

- emails
+- email-sequence
 - lifecycle-marketing
 - crm-integration
 - sales-pipeline
@@ -151,6 +151,6 @@ s.tl(this, 'o', 'Button Click');

 ## Relevant Skills

- analytics
- ab-testing
+- analytics-tracking
+- ab-test-setup
 - paid-ads
@@ -139,4 +139,4 @@ Authorization: Bearer {api_token}

 - seo-audit
 - content-strategy
- competitors
+- competitor-alternatives
@@ -130,6 +130,6 @@ amplitude.track('Feature Used', {

 ## Relevant Skills

- analytics
- ab-testing
- onboarding
+- analytics-tracking
+- ab-test-setup
+- onboarding-cro
@@ -145,4 +145,4 @@ POST https://api.apollo.io/api/v1/organizations/enrich
 - lead-enrichment
 - lead-scoring
 - cold-email
- competitors
+- competitor-alternatives
@@ -151,7 +151,7 @@ All endpoints are scoped to a publication. The publication ID is a required path

 ## Relevant Skills

- emails
+- email-sequence
 - newsletter-growth
- referrals
+- referral-program
 - content-strategy
@@ -261,7 +261,7 @@ Brevo uses standard REST with offset-based pagination (`limit` and `offset` para

 ## Relevant Skills

- emails
+- email-sequence
 - sms-marketing
 - transactional-email
 - lifecycle-marketing
@@ -146,4 +146,4 @@ POST https://api.clay.com/v3/companies/enrich
 - cold-email
 - revops
 - sales-enablement
- competitors
+- competitor-alternatives
--- a/Show More
+++ b/Show More
Author	SHA1	Message	Date
Corey Haines	fe670959f7	Merge pull request #220 from coreyhaines31/release/v1.6.0 release: v1.6.0 — community-marketing skill, 3 new tools, skill enhancements	2026-04-06 11:33:38 -07:00
Corey Haines	4874fe8979	Merge pull request #214 from coreyhaines31/feature/copy-editing-content-refresh feat: add content refresh editing to copy-editing	2026-04-03 17:02:17 -07:00
Corey Haines	d88009d1a4	Merge pull request #213 from coreyhaines31/feature/copy-editing-expert-panel feat: add expert panel scoring to copy-editing	2026-04-03 17:02:17 -07:00
Corey Haines	78da95de86	Merge pull request #212 from coreyhaines31/feature/social-content-repurposing feat: expand content repurposing in social-content	2026-04-03 17:02:17 -07:00
Corey Haines	7c2e29c526	Merge pull request #211 from coreyhaines31/feature/ab-test-growth-experiments feat: add growth experimentation program to ab-test-setup	2026-04-03 17:02:17 -07:00
Corey Haines	49f520f4eb	Merge pull request #210 from coreyhaines31/feature/add-rb2b-tool feat: add RB2B and Gong to tools registry	2026-04-03 17:02:17 -07:00
Corey Haines	ef8e08ffd2	Merge pull request #209 from coreyhaines31/feature/add-sparktoro feat: add SparkToro audience research tool	2026-04-03 17:02:17 -07:00
Corey Haines	e10c33406c	Merge pull request #208 from coreyhaines31/feature/ai-seo-pricing-md feat: add pricing.md guidance to ai-seo skill	2026-04-03 17:02:17 -07:00
Corey Haines	c31adfe89e	Merge pull request #207 from MarianoGarciaGz/feat/platform-limits-reference feat: add platform limits reference for social-content skill	2026-04-03 17:02:12 -07:00
Corey Haines	1f295fa5c8	Merge pull request #78 from pangerlkr/feature/new-skill-community-marketing feat: add community-marketing skill	2026-04-03 17:02:07 -07:00