paywall-upgrade-cro
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.
85
81%
Does it follow best practices?
Impact
88%
1.04xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description with excellent trigger term coverage and clear differentiation from related skills. The main weakness is that it focuses heavily on 'when' to use the skill but is somewhat vague about the specific actions or outputs it produces - it says 'create or optimize' but doesn't detail what that entails (copywriting, design patterns, conversion tactics, etc.).
Suggestions
Add specific concrete actions the skill performs, e.g., 'Designs paywall layouts, writes upgrade copy, recommends conversion tactics, and structures value propositions for in-app upgrade moments.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (in-app paywalls, upgrade screens) and lists types of screens (upsell modals, feature gates), but doesn't describe concrete actions like 'design', 'write copy for', 'optimize conversion rates', or 'A/B test'. | 2 / 3 |
Completeness | Clearly answers both what (create/optimize paywalls, upgrade screens, upsell modals, feature gates) and when (explicit 'Use when' clause with extensive trigger terms and user phrases). Also distinguishes from related skills (page-cro, pricing-strategy). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural user terms including 'paywall', 'upgrade screen', 'upsell', 'freemium conversion', 'trial expiration screen', 'free users won't upgrade', and 'how do I get users to pay' - these match how users would naturally phrase requests. | 3 / 3 |
Distinctiveness Conflict Risk | Explicitly distinguishes itself from 'page-cro' (public pricing pages) and 'pricing-strategy', clearly defining its niche as 'in-product upgrade moments where the user has already experienced value' - very low conflict risk. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with excellent structure and concrete templates for different paywall scenarios. The main weaknesses are some unnecessary explanatory content that Claude already understands and a lack of explicit validation/iteration workflows for measuring and improving paywall effectiveness. The templates and component breakdowns are particularly strong.
Suggestions
Add explicit validation steps: how to measure if a paywall is working, what metrics indicate success/failure, and when to iterate
Remove or condense the 'Core Principles' section - these are concepts Claude understands; instead, embed them as constraints in the templates
Add a concrete workflow for post-A/B-test iteration: 'If CTR < X%, try Y; if completion rate drops, check Z'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary explanation (e.g., 'Your goal is to convert free users to paid' is obvious from context). Some sections like 'Core Principles' explain concepts Claude likely understands, though the overall structure is fairly lean. | 2 / 3 |
Actionability | Provides concrete, copy-paste ready templates for different paywall types (feature lock, usage limit, trial expiration). Includes specific component structures, timing rules, and clear examples that Claude can directly implement. | 3 / 3 |
Workflow Clarity | The skill covers multiple scenarios but lacks explicit validation checkpoints. The 'From Paywall to Payment' section is vague ('Minimize steps'). No feedback loops for testing whether paywalls are working or iteration process after A/B tests. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections, appropriate use of headers, and good cross-references to related skills and external references (experiments.md). Content is appropriately structured without being monolithic or requiring deep navigation. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- coreyhaines31/marketingskills
- Commit
9d4d29a
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.