feat: consolidate page-cro and form-cro into unified cro skill
- Create skills/cro/ with shared CRO analysis framework - Move page-specific content to references/page.md - Move form-specific content to references/form.md - Copy experiments reference from page-cro - Remove skills/page-cro/ and skills/form-cro/ - Update all cross-references across skills, tools, README, AGENTS.md BREAKING: page-cro and form-cro are replaced by cro. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Corey Haines
@@ -29,15 +29,14 @@
|
||||
"./skills/copy-editing",
|
||||
"./skills/copywriting",
|
||||
"./skills/customer-research",
|
||||
"./skills/cro",
|
||||
"./skills/emails",
|
||||
"./skills/form-cro",
|
||||
"./skills/free-tools",
|
||||
"./skills/launch",
|
||||
"./skills/lead-magnets",
|
||||
"./skills/marketing-ideas",
|
||||
"./skills/marketing-psychology",
|
||||
"./skills/onboarding",
|
||||
"./skills/page-cro",
|
||||
"./skills/paid-ads",
|
||||
"./skills/paywalls",
|
||||
"./skills/popups",
|
||||
|
||||
@@ -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**: `page-cro`, `emails`, `ab-testing`
|
||||
**Valid**: `cro`, `emails`, `ab-testing`
|
||||
**Invalid**: `Page-CRO`, `-page`, `page--cro`
|
||||
|
||||
### Optional Skill Directories
|
||||
@@ -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 page-cro`
|
||||
- `fix: improve clarity in cro`
|
||||
- `docs: update README`
|
||||
|
||||
### Pull Request Checklist
|
||||
|
||||
@@ -30,10 +30,10 @@ 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 │ │page-cro │ │copywritng│ │paid-ads │ │referral │ │revops │ │mktg-ideas │
|
||||
│seo-audit │ │cro │ │copywritng│ │paid-ads │ │referral │ │revops │ │mktg-ideas │
|
||||
│ai-seo │ │signup-cro│ │copy-edit │ │ad-creative │ │free-tool │ │sales-enable │ │mktg-psych │
|
||||
│site-arch │ │onboard │ │cold-email│ │ab-test │ │churn- │ │launch │ │customer- │
|
||||
│programm │ │form-cro │ │email-seq │ │analytics │ │ prevent │ │pricing │ │research │
|
||||
│programm │ │cro │ │email-seq │ │analytics │ │ prevent │ │pricing │ │research │
|
||||
│schema │ │popups │ │social │ │ │ │ │ │competitor │ │ │
|
||||
│content │ │paywall │ │ │ │ │ │ │ │ │ │ │
|
||||
└────┬─────┘ └────┬─────┘ └────┬─────┘ └─────┬──────┘ └────┬─────┘ └──────┬──────┘ └─────┬─────┘
|
||||
@@ -41,10 +41,10 @@ Skills reference each other and build on shared context. The `product-marketing-
|
||||
└────────────┴─────┬──────┴──────────────┴─────────────┴──────────────┴──────────────┘
|
||||
│
|
||||
Skills cross-reference each other:
|
||||
copywriting ↔ page-cro ↔ ab-testing
|
||||
copywriting ↔ cro ↔ ab-testing
|
||||
revops ↔ sales-enablement ↔ cold-email
|
||||
seo-audit ↔ schema ↔ ai-seo
|
||||
customer-research → copywriting, page-cro, competitors
|
||||
customer-research → copywriting, cro, competitors
|
||||
```
|
||||
|
||||
See each skill's **Related Skills** section for the full dependency map.
|
||||
@@ -66,14 +66,14 @@ See each skill's **Related Skills** section for the full dependency map.
|
||||
| [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... |
|
||||
| [form-cro](skills/form-cro/) | When the user wants to optimize any form that is NOT signup/registration — including lead capture forms, contact forms,... |
|
||||
| [cro](skills/cro/) | When the user wants to optimize any form that is NOT signup/registration — including lead capture forms, contact forms,... |
|
||||
| [free-tools](skills/free-tools/) | When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or... |
|
||||
| [launch](skills/launch/) | When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user... |
|
||||
| [lead-magnets](skills/lead-magnets/) | When the user wants to create, plan, or optimize a lead magnet for email capture or lead generation. Also use when the... |
|
||||
| [marketing-ideas](skills/marketing-ideas/) | When the user needs marketing ideas, inspiration, or strategies for their SaaS or software product. Also use when the... |
|
||||
| [marketing-psychology](skills/marketing-psychology/) | When the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when... |
|
||||
| [onboarding](skills/onboarding/) | 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... |
|
||||
| [cro](skills/cro/) | When the user wants to optimize, improve, or increase conversions on any marketing page — including homepage, landing... |
|
||||
| [paid-ads](skills/paid-ads/) | When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X,... |
|
||||
| [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... |
|
||||
@@ -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 page-cro copywriting
|
||||
npx skills add coreyhaines31/marketingskills --skill 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 page-cro copywriting
|
||||
npx skillkit install coreyhaines31/marketingskills --skill cro copywriting
|
||||
|
||||
# List available skills
|
||||
npx skillkit install coreyhaines31/marketingskills --list
|
||||
@@ -178,7 +178,7 @@ Once installed, just ask your agent to help with marketing tasks:
|
||||
|
||||
```
|
||||
"Help me optimize this landing page for conversions"
|
||||
→ Uses page-cro skill
|
||||
→ Uses cro skill
|
||||
|
||||
"Write homepage copy for my SaaS"
|
||||
→ Uses copywriting skill
|
||||
@@ -193,7 +193,7 @@ Once installed, just ask your agent to help with marketing tasks:
|
||||
You can also invoke skills directly:
|
||||
|
||||
```
|
||||
/page-cro
|
||||
/cro
|
||||
/emails
|
||||
/seo-audit
|
||||
```
|
||||
@@ -201,10 +201,10 @@ You can also invoke skills directly:
|
||||
## Skill Categories
|
||||
|
||||
### Conversion Optimization
|
||||
- `page-cro` - Any marketing page
|
||||
- `cro` - Any marketing page
|
||||
- `signup` - Registration flows
|
||||
- `onboarding` - Post-signup activation
|
||||
- `form-cro` - Lead capture forms
|
||||
- `cro` - Lead capture forms
|
||||
- `popups` - Modals and overlays
|
||||
- `paywalls` - In-app upgrade moments
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
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 page-cro.
|
||||
description: When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," or "how long should I run this test." Use this whenever someone is comparing two approaches and wants to measure which performs better. For tracking implementation, see analytics. For page-level conversion optimization, see cro.
|
||||
metadata:
|
||||
version: 1.1.0
|
||||
---
|
||||
@@ -261,6 +261,6 @@ Document every test with:
|
||||
|
||||
## Related Skills
|
||||
|
||||
- **page-cro**: For generating test ideas based on CRO principles
|
||||
- **cro**: For generating test ideas based on CRO principles
|
||||
- **analytics**: For setting up test measurement
|
||||
- **copywriting**: For creating variant copy
|
||||
|
||||
@@ -305,5 +305,5 @@ For implementation, see the [tools registry](../../tools/REGISTRY.md). Key analy
|
||||
|
||||
- **ab-testing**: For experiment tracking
|
||||
- **seo-audit**: For organic traffic analysis
|
||||
- **page-cro**: For conversion optimization (uses this data)
|
||||
- **cro**: For conversion optimization (uses this data)
|
||||
- **revops**: For pipeline metrics, CRM tracking, and revenue attribution
|
||||
|
||||
@@ -431,7 +431,7 @@ This iterative process ensures each edit doesn't create new problems while respe
|
||||
## Related Skills
|
||||
|
||||
- **copywriting**: For writing new copy from scratch (use this skill to edit after your first draft is complete)
|
||||
- **page-cro**: For broader page optimization beyond copy
|
||||
- **cro**: For broader page optimization beyond copy
|
||||
- **marketing-psychology**: For understanding why certain edits improve conversion
|
||||
- **ab-testing**: For testing copy variations
|
||||
|
||||
@@ -444,4 +444,4 @@ This iterative process ensures each edit doesn't create new problems while respe
|
||||
| Writing new page copy from scratch | copywriting |
|
||||
| Reviewing and improving existing copy | copy-editing (this skill) |
|
||||
| Editing copy you just wrote | copy-editing (this skill) |
|
||||
| Structural or strategic page changes | page-cro |
|
||||
| Structural or strategic page changes | cro |
|
||||
|
||||
@@ -246,7 +246,7 @@ For headlines and CTAs, provide 2-3 options:
|
||||
## Related Skills
|
||||
|
||||
- **copy-editing**: For polishing existing copy (use after your draft)
|
||||
- **page-cro**: If page structure/strategy needs work, not just copy
|
||||
- **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
|
||||
|
||||
@@ -1,13 +1,13 @@
|
||||
---
|
||||
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. For post-signup activation, see onboarding. For forms outside of signup, see form-cro. For popups/modals, see popups.
|
||||
name: cro
|
||||
description: "When the user wants to optimize, improve, or increase conversions on any marketing page or form. Also use when the user says 'CRO,' 'conversion rate optimization,' 'this page isn't converting,' 'improve conversions,' 'why isn't this page working,' 'my landing page sucks,' 'nobody's converting,' 'low conversion rate,' 'bounce rate is too high,' 'form optimization,' 'lead form conversions,' 'form friction,' 'nobody fills out our form,' 'form abandonment,' or 'too many fields.' Use this for any conversion optimization on pages or forms. For signup/registration flows, see signup. For post-signup activation, see onboarding. For popups/modals, see popups. For paywalls, see paywalls."
|
||||
metadata:
|
||||
version: 1.1.0
|
||||
version: 1.0.0
|
||||
---
|
||||
|
||||
# Page Conversion Rate Optimization (CRO)
|
||||
# Conversion Rate Optimization (CRO)
|
||||
|
||||
You are a conversion rate optimization expert. Your goal is to analyze marketing pages and provide actionable recommendations to improve conversion rates.
|
||||
You are a conversion rate optimization expert. Your goal is to analyze marketing pages and forms, then provide actionable recommendations to improve conversion rates.
|
||||
|
||||
## Initial Assessment
|
||||
|
||||
@@ -16,15 +16,21 @@ If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-
|
||||
|
||||
Before providing recommendations, identify:
|
||||
|
||||
1. **Page Type**: Homepage, landing page, pricing, feature, blog, about, other
|
||||
2. **Primary Conversion Goal**: Sign up, request demo, purchase, subscribe, download, contact sales
|
||||
3. **Traffic Context**: Where are visitors coming from? (organic, paid, email, social)
|
||||
1. **What needs optimization?** — A page, a form, or both
|
||||
2. **Page Type** (if page): Homepage, landing page, pricing, feature, blog, about
|
||||
3. **Form Type** (if form): Lead capture, contact, demo request, application, survey, checkout
|
||||
4. **Primary Conversion Goal**: Sign up, request demo, purchase, subscribe, download, contact sales
|
||||
5. **Traffic Context**: Where are visitors coming from? (organic, paid, email, social)
|
||||
|
||||
**For page optimization**: See [references/page.md](references/page.md)
|
||||
|
||||
**For form optimization**: See [references/form.md](references/form.md)
|
||||
|
||||
---
|
||||
|
||||
## CRO Analysis Framework
|
||||
|
||||
Analyze the page across these dimensions, in order of impact:
|
||||
Analyze across these dimensions, in order of impact:
|
||||
|
||||
### 1. Value Proposition Clarity (Highest Impact)
|
||||
|
||||
@@ -170,13 +176,14 @@ When recommending experiments, consider tests for:
|
||||
3. What does your signup/purchase flow look like after this page?
|
||||
4. Do you have user research, heatmaps, or session recordings?
|
||||
5. What have you already tried?
|
||||
6. What type of form are you optimizing (if applicable)?
|
||||
|
||||
---
|
||||
|
||||
## Related Skills
|
||||
|
||||
- **signup**: If the issue is in the signup process itself
|
||||
- **form-cro**: If forms on the page need optimization
|
||||
- **popups**: If considering popups as part of the strategy
|
||||
- **paywalls**: For in-app upgrade moments and trial expiration
|
||||
- **copywriting**: If the page needs a complete copy rewrite
|
||||
- **ab-testing**: To properly test recommended changes
|
||||
@@ -1,13 +1,6 @@
|
||||
---
|
||||
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. For popups containing forms, see popups.
|
||||
metadata:
|
||||
version: 1.1.0
|
||||
---
|
||||
# Form CRO Reference
|
||||
|
||||
# Form CRO
|
||||
|
||||
You are an expert in form optimization. Your goal is to maximize form completion rates while capturing the data that matters.
|
||||
Detailed form optimization guidance. Use alongside the main CRO skill.
|
||||
|
||||
## Initial Assessment
|
||||
|
||||
@@ -425,5 +418,4 @@ Ideas to A/B test with expected outcomes
|
||||
|
||||
- **signup**: For account creation forms
|
||||
- **popups**: For forms inside popups/modals
|
||||
- **page-cro**: For the page containing the form
|
||||
- **ab-testing**: For testing form changes
|
||||
@@ -0,0 +1,68 @@
|
||||
# Page CRO Reference
|
||||
|
||||
Detailed page-level conversion optimization guidance. Use alongside the main CRO skill.
|
||||
|
||||
## Page Type Audit Checklists
|
||||
|
||||
### Homepage
|
||||
|
||||
- [ ] Hero clearly communicates what you do and for whom
|
||||
- [ ] Primary CTA visible above the fold
|
||||
- [ ] Social proof within first viewport
|
||||
- [ ] Clear navigation to key pages (pricing, features, use cases)
|
||||
- [ ] Both "ready to buy" and "still researching" paths available
|
||||
- [ ] Mobile experience tested and optimized
|
||||
|
||||
### Landing Page
|
||||
|
||||
- [ ] Message matches the traffic source (ad, email, social post)
|
||||
- [ ] Single conversion goal — no competing CTAs
|
||||
- [ ] Navigation removed or minimized
|
||||
- [ ] Complete argument made on one page (no required clicks)
|
||||
- [ ] Form or CTA repeated after key sections
|
||||
- [ ] Page speed under 3 seconds
|
||||
|
||||
### Pricing Page
|
||||
|
||||
- [ ] Plans are easy to compare at a glance
|
||||
- [ ] Recommended plan is visually highlighted
|
||||
- [ ] Feature comparison table included
|
||||
- [ ] Annual vs monthly toggle with savings shown
|
||||
- [ ] FAQ addresses common pricing objections
|
||||
- [ ] Free trial or money-back guarantee prominent
|
||||
- [ ] Enterprise/contact option for larger buyers
|
||||
|
||||
### Feature Page
|
||||
|
||||
- [ ] Feature connected to a clear business benefit
|
||||
- [ ] Real use cases or examples shown
|
||||
- [ ] Screenshot or demo of the feature in action
|
||||
- [ ] CTA to try the feature (not just "learn more")
|
||||
- [ ] Related features cross-linked
|
||||
|
||||
### Blog Post
|
||||
|
||||
- [ ] Contextual CTA matching the content topic
|
||||
- [ ] Inline CTA at a natural stopping point (not just end)
|
||||
- [ ] Content upgrade or lead magnet related to the topic
|
||||
- [ ] Author bio with credibility signals
|
||||
- [ ] Related posts suggested
|
||||
|
||||
## Above-the-Fold Priorities
|
||||
|
||||
The first viewport should answer three questions:
|
||||
|
||||
1. **What is this?** — Clear headline with the core value proposition
|
||||
2. **Why should I care?** — Subheadline connecting to the visitor's problem or desire
|
||||
3. **What do I do next?** — Visible primary CTA
|
||||
|
||||
If a visitor can't answer all three within 5 seconds, the above-the-fold content needs work.
|
||||
|
||||
## Mobile CRO Considerations
|
||||
|
||||
- Thumb-friendly CTA buttons (min 44x44px)
|
||||
- Sticky CTA bar for long pages
|
||||
- Simplified forms (consider progressive disclosure)
|
||||
- Test with real devices, not just browser resize
|
||||
- Prioritize speed — mobile users are less patient
|
||||
- Consider mobile-specific CTAs (click-to-call, app deep links)
|
||||
@@ -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 page-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 cro.
|
||||
metadata:
|
||||
version: 1.0.0
|
||||
---
|
||||
@@ -261,7 +261,7 @@ 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 | `page-cro` |
|
||||
| Optimizing a page using VOC insights | `cro` |
|
||||
| Building a competitor comparison page | `competitors` |
|
||||
| Creating a churn prevention strategy from churn research | `churn-prevention` |
|
||||
| Planning paid ads informed by research | `paid-ads` |
|
||||
|
||||
@@ -1,90 +0,0 @@
|
||||
{
|
||||
"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": []
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -173,7 +173,7 @@ Rate each factor 1-5:
|
||||
## Related Skills
|
||||
|
||||
- **lead-magnets**: For downloadable content lead magnets (ebooks, checklists, templates)
|
||||
- **page-cro**: For optimizing the tool's landing page
|
||||
- **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
|
||||
|
||||
@@ -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 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.",
|
||||
"expected_output": "Should recognize this is a landing page conversion optimization task, not a free tool strategy task. Should defer to or cross-reference the cro skill for optimizing the tool's landing page conversion rate. May provide free-tool-specific context (gating strategy, value demonstration) but should make clear that cro is the right skill for page conversion optimization.",
|
||||
"assertions": [
|
||||
"Recognizes this as page CRO, not free tool strategy",
|
||||
"References or defers to page-cro skill",
|
||||
"References or defers to cro skill",
|
||||
"May provide free-tool-specific context",
|
||||
"Does not attempt full page CRO using free tool strategy patterns"
|
||||
],
|
||||
|
||||
@@ -347,7 +347,7 @@ Even small changelog updates remind customers your product is evolving. This bui
|
||||
|
||||
- **marketing-ideas**: For additional launch tactics (#22 Product Hunt, #23 Early Access Referrals)
|
||||
- **emails**: For launch and onboarding email sequences
|
||||
- **page-cro**: For optimizing launch landing pages
|
||||
- **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
|
||||
|
||||
@@ -147,7 +147,7 @@ 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 **form-cro** skill
|
||||
**For form optimization**: See **cro** skill
|
||||
**For popup implementation**: See **popups** 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 **page-cro** skill
|
||||
**For landing page optimization**: See **cro** skill
|
||||
|
||||
### Delivery Methods
|
||||
|
||||
@@ -301,9 +301,9 @@ When creating a lead magnet strategy, provide:
|
||||
- **free-tools**: For interactive tools as lead magnets (calculators, graders, quizzes)
|
||||
- **copywriting**: For writing the lead magnet content itself
|
||||
- **emails**: For nurture sequences after lead capture
|
||||
- **page-cro**: For optimizing lead magnet landing pages
|
||||
- **cro**: For optimizing lead magnet landing pages
|
||||
- **popups**: For popup-based lead capture
|
||||
- **form-cro**: For optimizing capture forms
|
||||
- **cro**: For optimizing capture forms
|
||||
- **content-strategy**: For content planning and topic selection
|
||||
- **analytics**: For measuring lead magnet performance
|
||||
- **paid-ads**: For paid promotion of lead magnets
|
||||
|
||||
@@ -448,8 +448,8 @@ When facing a marketing challenge, consider:
|
||||
|
||||
## Related Skills
|
||||
|
||||
- **page-cro**: Apply psychology to page optimization
|
||||
- **cro**: Apply psychology to page optimization
|
||||
- **copywriting**: Write copy using psychological principles
|
||||
- **popups**: Use triggers and psychology in popups
|
||||
- **pricing-page optimization**: See page-cro for pricing psychology
|
||||
- **pricing-page optimization**: See cro for pricing psychology
|
||||
- **ab-testing**: Test psychological hypotheses
|
||||
|
||||
@@ -1,111 +0,0 @@
|
||||
{
|
||||
"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 page-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 cro."
|
||||
metadata:
|
||||
version: 1.1.0
|
||||
---
|
||||
@@ -312,4 +312,4 @@ For tracking, see also: [ga4.md](../../tools/integrations/ga4.md), [segment.md](
|
||||
- **copywriting**: For landing page copy that converts ad traffic
|
||||
- **analytics**: For proper conversion tracking setup
|
||||
- **ab-testing**: For landing page testing to improve ROAS
|
||||
- **page-cro**: For optimizing post-click conversion rates
|
||||
- **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 page-cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see pricing.
|
||||
description: When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," "in-app pricing," "free users won't upgrade," "trial to paid conversion," or "how do I get users to pay." Use this for any in-product moment where you're asking users to upgrade. Distinct from public pricing pages (see cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see pricing.
|
||||
metadata:
|
||||
version: 1.1.0
|
||||
---
|
||||
@@ -222,6 +222,6 @@ What you've accomplished:
|
||||
## Related Skills
|
||||
|
||||
- **churn-prevention**: For cancel flows, save offers, and reducing churn post-upgrade
|
||||
- **page-cro**: For public pricing page optimization
|
||||
- **cro**: For public pricing page optimization
|
||||
- **onboarding**: For driving to aha moment before upgrade
|
||||
- **ab-testing**: 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 page-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 cro skill for pricing page CRO. Paywall-upgrade-cro specifically handles in-app upgrade prompts for existing users, not public-facing pricing pages.",
|
||||
"assertions": [
|
||||
"Recognizes this as public pricing page optimization",
|
||||
"References or defers to page-cro skill",
|
||||
"References or defers to 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 form-cro. For general page conversion optimization, see page-cro.
|
||||
description: When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," "overlay," "collect emails with a popup," "exit popup," "scroll trigger," "sticky bar," or "notification bar." Use this for any overlay or interrupt-style conversion element. For forms outside of popups, see cro. For general page conversion optimization, see 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
|
||||
- **form-cro**: For optimizing the form inside the popup
|
||||
- **page-cro**: For the page context around 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
|
||||
|
||||
@@ -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 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.",
|
||||
"expected_output": "Should recognize this overlaps with form optimization. Should defer to or cross-reference the cro skill, which handles form field optimization, layout, and conversion. May provide popup-specific context (popups need minimal fields due to fleeting attention) but should make clear that cro is the right skill for detailed form optimization.",
|
||||
"assertions": [
|
||||
"Recognizes overlap with form optimization",
|
||||
"References or defers to form-cro skill",
|
||||
"References or defers to cro skill",
|
||||
"Notes popups need minimal fields due to context",
|
||||
"Does not attempt detailed form redesign"
|
||||
],
|
||||
|
||||
@@ -223,7 +223,7 @@ Identifies which features customers value most:
|
||||
## Related Skills
|
||||
|
||||
- **churn-prevention**: For cancel flows, save offers, and reducing revenue churn
|
||||
- **page-cro**: For optimizing pricing page conversion
|
||||
- **cro**: For optimizing pricing page conversion
|
||||
- **copywriting**: For pricing page copy
|
||||
- **marketing-psychology**: For pricing psychology principles
|
||||
- **ab-testing**: For testing pricing changes
|
||||
|
||||
@@ -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 page-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 cro for broader pricing page optimization.",
|
||||
"assertions": [
|
||||
"Applies pricing psychology tactics",
|
||||
"Applies anchoring effect",
|
||||
"Applies decoy effect or visual emphasis",
|
||||
"Applies charm pricing or Rule of 100",
|
||||
"Provides specific pricing page recommendations",
|
||||
"Cross-references page-cro or marketing-psychology"
|
||||
"Cross-references cro or marketing-psychology"
|
||||
],
|
||||
"files": []
|
||||
},
|
||||
{
|
||||
"id": 6,
|
||||
"prompt": "Our pricing page conversion rate is only 1.5%. Can you review the page and suggest improvements?",
|
||||
"expected_output": "Should recognize this is a pricing page conversion optimization task, not a pricing strategy task. Should defer to or cross-reference the 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.",
|
||||
"expected_output": "Should recognize this is a pricing page conversion optimization task, not a pricing strategy task. Should defer to or cross-reference the cro skill, which handles pricing page conversion rate optimization including plan comparison clarity, CTA optimization, and trust signals. Pricing-strategy focuses on the actual pricing decisions (what to charge, how to package), not the page design.",
|
||||
"assertions": [
|
||||
"Recognizes this as pricing page CRO, not pricing strategy",
|
||||
"References or defers to page-cro skill",
|
||||
"References or defers to cro skill",
|
||||
"Explains that pricing-strategy is about pricing decisions",
|
||||
"Does not attempt full page CRO audit"
|
||||
],
|
||||
|
||||
@@ -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, page-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, 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",
|
||||
|
||||
@@ -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
|
||||
- **page-cro**: For optimizing pages for conversion (not just ranking)
|
||||
- **cro**: For optimizing pages for conversion (not just ranking)
|
||||
- **analytics**: 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 form-cro.
|
||||
description: When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions "signup conversions," "registration friction," "signup form optimization," "free trial signup," "reduce signup dropoff," "account creation flow," "people aren't signing up," "signup abandonment," "trial conversion rate," "nobody completes registration," "too many steps to sign up," or "simplify our signup." Use this whenever the user has a signup or registration flow that isn't performing. For post-signup onboarding, see onboarding. For lead capture forms (not account creation), see cro.
|
||||
metadata:
|
||||
version: 1.1.0
|
||||
---
|
||||
@@ -354,6 +354,6 @@ Organized by:
|
||||
## Related Skills
|
||||
|
||||
- **onboarding**: For optimizing what happens after signup
|
||||
- **form-cro**: For non-signup forms (lead capture, contact)
|
||||
- **page-cro**: For the landing page leading to signup
|
||||
- **cro**: For non-signup forms (lead capture, contact)
|
||||
- **cro**: For the landing page leading to signup
|
||||
- **ab-testing**: 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 page-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 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
|
||||
- **page-cro**: For optimizing individual pages for conversion
|
||||
- **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
|
||||
|
||||
@@ -123,4 +123,4 @@ POST https://www.google-analytics.com/mp/collect?measurement_id={measurement_id}
|
||||
- analytics
|
||||
- ab-testing
|
||||
- seo-audit
|
||||
- page-cro
|
||||
- cro
|
||||
|
||||
@@ -156,4 +156,4 @@ LIMIT 10
|
||||
|
||||
- paid-ads
|
||||
- analytics
|
||||
- page-cro
|
||||
- cro
|
||||
|
||||
@@ -140,7 +140,7 @@ Authorization: Bearer {access_token}
|
||||
|
||||
## Relevant Skills
|
||||
|
||||
- page-cro
|
||||
- cro
|
||||
- ab-testing
|
||||
- analytics
|
||||
- ux-audit
|
||||
|
||||
@@ -144,4 +144,4 @@ access_token={access_token}
|
||||
|
||||
- paid-ads
|
||||
- analytics
|
||||
- page-cro
|
||||
- cro
|
||||
|
||||
@@ -165,7 +165,7 @@ GET https://api.optimizely.com/v2/pages?project_id={project_id}
|
||||
## Relevant Skills
|
||||
|
||||
- ab-testing
|
||||
- page-cro
|
||||
- cro
|
||||
- landing-page
|
||||
- personalization
|
||||
- analytics
|
||||
|
||||
@@ -173,5 +173,5 @@ GET https://plausible.io/api/v1/sites
|
||||
- analytics
|
||||
- content-strategy
|
||||
- programmatic-seo
|
||||
- page-cro
|
||||
- cro
|
||||
- utm-tracking
|
||||
|
||||
@@ -185,6 +185,6 @@ GET https://api.typeform.com/workspaces/{workspace_id}
|
||||
|
||||
- lead-generation
|
||||
- customer-research
|
||||
- page-cro
|
||||
- cro
|
||||
- signup
|
||||
- customer-feedback
|
||||
|
||||
@@ -195,4 +195,4 @@ webflow devlink sync
|
||||
|
||||
- programmatic-seo
|
||||
- content-strategy
|
||||
- page-cro
|
||||
- cro
|
||||
|
||||
Reference in New Issue
Block a user