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.

68

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

72%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, actionable CRO skill body: lean bullet sections, concrete paywall templates, and a clean single-reference progressive-disclosure pattern. The main weakness is workflow clarity — the discovery flow lacks explicit validation checkpoints that would confirm context is sufficient before producing recommendations.

Suggestions

Add an explicit validation checkpoint to the Initial Assessment (e.g., "Before recommending, confirm you have: conversion rate, paywall trigger, gated features, aha moment, and pricing model — if any are missing, ask"), turning the discovery flow into a verify-then-proceed loop.

Tighten the timing material by merging "When to Show," "When NOT to Show," and "Frequency Rules" into a single consolidated section to remove restated principles and improve token efficiency.

Fill in one fully-worked paywall copy example (headline + value demo + CTA + escape hatch) alongside the scaffolds so the templates are immediately usable rather than requiring Claude to draft from scratch.

DimensionReasoningScore

Conciseness

Lean and bullet-driven with no filler explaining concepts Claude already knows; the ASCII paywall templates and component lists earn their tokens. A few sections (timing principles restated across "When to Show"/"When NOT to Show"/"Frequency Rules") could be tightened, keeping it just below a 5.

4 / 5

Actionability

Provides concrete, copy-pasteable structure via the Feature Lock, Usage Limit, and Trial Expiration paywall templates plus specific component lists, metrics, and A/B dimensions. Templates are scaffolds rather than filled-in copy, leaving minor gaps that hold it at 4.

4 / 5

Workflow Clarity

The Initial Assessment lays out a sequenced discovery process (read product-marketing-context → ask remaining questions → assess context/model/journey → recommend), but there are no explicit validation checkpoints or feedback loops; sequence is present but checkpoints are implicit.

3 / 5

Progressive Disclosure

Well-organized overview body with a single clearly signaled one-level-deep reference ("For comprehensive experiment ideas: See references/experiments.md", verified to exist), keeping the main skill lean while offloading depth appropriately.

5 / 5

Total

16

/

20

Passed

Description

95%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.

A strong, well-crafted description: it states concrete capabilities, provides exhaustive natural trigger terms with synonyms, answers both what and when explicitly, and draws a sharp boundary against a sibling skill. Only minor specificity gaps keep it from a perfect score across every dimension.

DimensionReasoningScore

Specificity

Names several concrete targets — "create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates" — giving multiple specific actions with only minor coverage gaps; not the exhaustive single-skill list of a 5.

4 / 5

Completeness

Explicitly answers both what (create/optimize in-product upgrade moments) and when ("When the user wants to..." and "Also use when the user mentions..." with concrete trigger phrases).

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage including synonyms and phrasings users actually say ("paywall," "upsell," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," "in-app pricing").

5 / 5

Distinctiveness Conflict Risk

Explicit boundary disambiguation — "Distinct from public pricing pages (see page-cro) — this skill focuses on in-product upgrade moments where the user has already experienced value" — gives a clear niche with minimal conflict risk.

5 / 5

Total

19

/

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.

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.