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," or "in-app pricing." Distinct from public pricing pages (see page-cro) — this skill focuses on in-product upgrade moments where the user has already experienced value.
78
73%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./config/claude/skills/paywall-upgrade-cro/SKILL.mdQuality
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 skill description with excellent trigger term coverage and clear disambiguation from related skills. The main weakness is that the 'what' portion could be more specific about the concrete actions the skill performs beyond 'create or optimize.' The explicit boundary-setting with page-cro is a notable strength for reducing conflict risk.
Suggestions
Expand the capabilities section with more specific concrete actions, e.g., 'Designs paywall layouts, writes conversion copy, structures feature comparison tables, builds trial expiration flows, and optimizes upgrade CTAs.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (in-app paywalls, upgrade screens) and some actions ('create or optimize'), but doesn't list multiple specific concrete actions like 'design paywall layouts, write conversion copy, implement feature gates, build trial expiration flows.' | 2 / 3 |
Completeness | Clearly answers both 'what' (create or optimize in-app paywalls, upgrade screens, upsell modals, feature gates) and 'when' with an explicit 'Use when' clause listing numerous trigger terms. Also includes a helpful disambiguation note distinguishing from page-cro. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: '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.' These are highly natural and comprehensive. | 3 / 3 |
Distinctiveness Conflict Risk | Explicitly distinguishes itself from public pricing pages (page-cro) and carves out a clear niche: in-product upgrade moments where the user has already experienced value. The trigger terms are specific to this domain and unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a competent but somewhat generic paywall CRO skill that covers the right topics with decent organization and progressive disclosure. Its main weaknesses are that much of the content reads as general UX best practices Claude likely already knows (e.g., 'respect the no,' 'don't block critical flows'), and the guidance stays at the conceptual/wireframe level rather than providing truly actionable, copy-paste-ready templates or specific implementation instructions.
Suggestions
Replace vague guidance like 'Show what the feature does' with specific, executable examples — e.g., provide actual HTML/React component snippets or detailed copywriting templates with placeholder variables that can be directly adapted.
Trim the Core Principles and Anti-Patterns sections significantly — Claude already understands UX ethics and basic conversion principles. Focus tokens on the unique, non-obvious paywall patterns and specific implementation details.
Add a clear sequential workflow with validation steps, e.g., '1. Identify trigger point → 2. Draft paywall copy using template → 3. Review against checklist → 4. Propose A/B test variants' to give the skill a concrete process rather than a reference-style layout.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably organized but includes some unnecessary framing ('You are an expert...') and sections that could be tightened. The core principles section states things Claude already understands about UX (e.g., 'Don't trap or pressure'). Some bullet points are vague filler rather than actionable content. | 2 / 3 |
Actionability | The wireframe-style templates for feature lock, usage limit, and trial expiration paywalls provide semi-concrete guidance, but they're pseudocode/wireframes rather than executable code or copy-paste-ready components. Many sections are lists of considerations rather than specific instructions (e.g., 'Show what the feature does' without showing how). | 2 / 3 |
Workflow Clarity | There's a logical flow from assessment → principles → trigger points → components → optimization → testing, but the workflow lacks explicit sequencing or validation checkpoints. The 'Initial Assessment' section provides a good starting checklist, but there's no clear 'do step 1, then step 2' process with verification gates for the actual paywall creation workflow. | 2 / 3 |
Progressive Disclosure | The skill is well-structured with clear sections and headers, references related skills at the bottom, and points to a separate experiments file for A/B testing details. Content is appropriately scoped for a SKILL.md overview without being monolithic or deeply nested. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- freekmurze/dotfiles
- Commit
05d40bb
- 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.