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.

Quality

70%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./config/claude/skills/paywall-upgrade-cro/SKILL.md

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 skill description with excellent trigger term coverage and clear disambiguation from related skills. Its main weakness is that the 'what' portion could be more specific about the concrete actions performed (e.g., writing copy, designing layouts, optimizing conversion flows). Overall it would serve well for skill selection among many candidates.

Suggestions

Add more specific concrete actions beyond 'create or optimize' — e.g., 'design paywall layouts, write upgrade copy, structure feature comparison tables, build trial expiration flows' to improve specificity.

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 the 'page-cro' skill for public pricing pages, and carves out a clear niche focused on 'in-product upgrade moments where the user has already experienced value.' The trigger terms are specific enough to avoid conflicts.	3 / 3
	Total	11 / 12 Passed

Implementation

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a moderately well-structured skill that covers paywall CRO comprehensively but suffers from being more of a knowledge reference than an actionable instruction set. The wireframe templates are a strength, but the skill lacks executable code examples, explicit workflow sequencing with validation steps, and is verbose in areas where Claude already has strong baseline knowledge (dark patterns, general UX principles). It reads more like a best-practices guide than a task-oriented skill.

Suggestions

Add an explicit numbered workflow for creating a paywall (e.g., '1. Identify trigger point → 2. Draft copy using headline formula → 3. Build component structure → 4. Verify escape hatch exists → 5. Set up metrics tracking → 6. Plan A/B test'), with validation checkpoints at key steps.

Replace or supplement the wireframe pseudocode with actual implementable examples (React/HTML components, specific copy formulas with fill-in-the-blank patterns) to increase actionability.

Trim sections that cover knowledge Claude already has (Core Principles, Anti-Patterns) to brief bullet reminders, and move detailed A/B testing guidance and metrics lists to a reference file.

Create the referenced `references/experiments.md` bundle file, and consider splitting timing/frequency rules and post-upgrade flow into separate reference documents to reduce the main file's length.

Dimension	Reasoning	Score
Conciseness	The skill is reasonably organized but includes some unnecessary framing ('You are an expert...'), and several sections like 'Core Principles' and 'Anti-Patterns' cover concepts Claude already understands well. The wireframe-style examples are efficient, but the overall document could be tightened by ~30%.	2 / 3
Actionability	The skill provides wireframe templates for specific paywall types (feature lock, usage limit, trial expiration) which are somewhat actionable, but they're pseudocode/wireframes rather than actual implementable code. The guidance is mostly descriptive ('show what the feature does,' 'clear explanation') rather than providing concrete copy formulas, specific HTML/CSS patterns, or executable examples.	2 / 3
Workflow Clarity	There's a logical flow from assessment → principles → trigger points → components → specific types → testing, but the workflow for actually creating a paywall is implicit rather than explicitly sequenced. There are no validation checkpoints (e.g., 'verify the paywall has an escape hatch before shipping') and no feedback loops for iterating on conversion performance.	2 / 3
Progressive Disclosure	The skill references `references/experiments.md` and related skills (page-cro, onboarding-cro, ab-test-setup), showing awareness of progressive disclosure. However, no bundle files exist to support the reference, and the main document is quite long (~180 lines) with content like A/B testing metrics and anti-patterns that could be split into reference files. The inline content is heavy for a single SKILL.md.	2 / 3
	Total	8 / 12 Passed

Validation

90%

Warnings & errors only

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: 3974caa

Reviewed: 29 days ago

Table of Contents

Discovery Implementation Validation

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.