CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

66

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

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

A well-structured advisory skill with strong concrete templates and clean progressive disclosure, weakened mainly by generic CRO principle sections that add tokens without adding knowledge Claude lacks. The assessment-first workflow is clear, though the feedback loop is implicit rather than explicit.

Suggestions

Compress the "Core Principles" and "Paywall Screen Components" sections, which restate general conversion-marketing knowledge, and keep only the parts specific to in-product upgrade moments.

Add an explicit iterate-and-validate step after recommendations (e.g., pair each recommendation with a metric from the A/B Testing section and a re-check with the user on current conversion data).

Replace abstract bullets like "Highlight key differences" and "Social Proof - Customer quotes" with one-line concrete examples matching the quality of the wireframe templates.

DimensionReasoningScore

Conciseness

The body is mostly terse lists, but sections like "Core Principles" ("Respect the No - Don't trap or pressure") and "Paywall Screen Components" restate general CRO knowledge Claude already has; roughly a quarter of the content could be tightened or cut.

3 / 5

Actionability

Three copy-ready wireframe templates (Feature Lock, Usage Limit, Trial Expiration), concrete copy formulas ("Unlock [Feature] to [Benefit]"), specific timing values (7, 3, 1 day), and a question checklist give mostly executable guidance. Not 5 because some bullets like "Highlight key differences" remain abstract direction.

4 / 5

Workflow Clarity

The Initial Assessment section establishes a clear sequence (check for product marketing context, understand upgrade context/product model/user journey, then apply principles and templates), and the A/B Testing metrics serve as the validation checkpoint. Not 5 because there is no explicit validate-and-iterate loop after recommendations are drafted.

4 / 5

Progressive Disclosure

SKILL.md is a well-sectioned overview with exactly one clearly signaled, one-level-deep reference — "For comprehensive experiment ideas: See [references/experiments.md](references/experiments.md)" — which is a real file with substantive matching content.

5 / 5

Total

16

/

20

Passed

Description

90%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An excellent description: explicit what/when, rich natural trigger terms, and explicit boundary demarcation against the sibling public-pricing skill. The only weakness is that the capability verbs are limited to "create or optimize," which slightly undersells the range of actions the body actually covers.

DimensionReasoningScore

Specificity

It names the domain precisely ("in-app paywalls, upgrade screens, upsell modals, or feature gates") but offers only two actions — "create or optimize" — rather than several specific concrete actions, so it matches anchor 3 rather than anchor 4.

3 / 5

Completeness

Explicitly answers both "what" (create or optimize in-app paywalls, upgrade screens, upsell modals, feature gates) and "when" ("When the user wants to... Also use when the user mentions...") with a full list of concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage including synonyms and phrasings users would actually say: "paywall," "upgrade screen," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," "in-app pricing."

5 / 5

Distinctiveness Conflict Risk

A clear niche with an explicit boundary statement — "Distinct from public pricing pages (see page-cro) — this skill focuses on in-product upgrade moments" — that minimizes overlap with the sibling pricing-page skill.

5 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

freekmurze/dotfiles

Path

config/claude/skills/marketing/skills/paywall-upgrade-cro/SKILL.md

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.