CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

70

Quality

86%

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

72%

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

A well-structured, actionable body with strong templates and a clean one-level reference, though it leans on some broadly-known CRO principles and lacks explicit validation checkpoints in its advisory workflow.

Suggestions

Trim or condense the 'Core Principles' section, which restates widely-known conversion concepts Claude already knows, to improve token efficiency.

Add an explicit validation/checklist step in the Initial Assessment flow (e.g. confirm product model and conversion rate are known before recommending) to strengthen workflow clarity.

Tighten the 'Timing and Frequency' and 'Anti-Patterns' sections into fewer bullets where the guidance overlaps common UX knowledge.

DimensionReasoningScore

Conciseness

Mostly efficient with tight bullet lists and templates, but the 'Core Principles' section restates widely-known CRO/UX concepts (e.g. 'Value Before Ask,' 'Show, Don't Just Tell') that Claude already knows, pulling it below the lean/efficient anchor.

2 / 3

Actionability

Provides concrete, copy-paste-ready paywall templates (Feature Lock, Usage Limit, Trial Expiration) plus specific screen-component guidance, A/B-test variables, and named metrics to track, matching the fully-executable anchor.

3 / 3

Workflow Clarity

The Initial Assessment flow (read product-marketing context, then clarify three areas) is sequenced, but checkpoints are implicit and there is no validate/verify feedback loop before issuing recommendations.

2 / 3

Progressive Disclosure

SKILL.md serves as a well-organized overview with a single clearly-signaled one-level-deep reference to references/experiments.md (a real file), matching the clear-overview-with-well-signaled-references anchor.

3 / 3

Total

10

/

12

Passed

Description

100%

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

A strong, third-person description that names concrete actions, supplies rich natural trigger terms, and explicitly separates its niche from a sibling skill. It cleanly satisfies the what/when/completeness criteria.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates' — matching the top anchor for naming several specific actions.

3 / 3

Completeness

Explicitly answers both what (create/optimize in-product upgrade surfaces) and when via a clearly stated 'Also use when the user mentions...' trigger clause, hitting the top anchor.

3 / 3

Trigger Term Quality

Excellent coverage of natural terms users would say: 'paywall,' 'upgrade screen,' 'upsell,' 'feature gate,' 'freemium conversion,' 'trial expiration screen,' matching the good-coverage anchor.

3 / 3

Distinctiveness Conflict Risk

Carves a clear niche ('in-product upgrade moments where the user has already experienced value') and explicitly distinguishes itself from page-cro, making wrong-skill triggering unlikely.

3 / 3

Total

12

/

12

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.

Validation15 / 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
TheCraigHewitt/seomachine
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.