CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

upgrade-flow-design

Designing free-to-paid conversion flows for SaaS products. Trigger moments, paywall design, value demonstration, upsell vs downsell, win-back flows, churn prevention. Honest about paywall-everywhere (gates everything aggressively), free-forever-trap (no upgrade path surfaces), and value-triggered-upgrade (paywall surfaces at moments of demonstrated value) patterns. Triggers on upgrade flow, paywall, free-to-paid, freemium conversion, trial conversion, plan upgrade, subscription upgrade, win-back flow, churn prevention. Also triggers when free-to-paid conversion is low, when paywalls are blocking the wrong moments, or when upgrade flows are being scoped for the first time.

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

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 playbook with excellent progressive disclosure into a real, complete reference bundle and concrete, actionable design guidance. It loses points on conciseness — repeated framing of the three patterns and re-explanations of common SaaS concepts — and lacks an end-to-end worked example that would make the framework fully executable.

Suggestions

Conciseness: state the paywall-everywhere / free-forever-trap / value-triggered-upgrade framing once (in its keystone section) and reference it elsewhere; the intro paragraphs and closing currently repeat it nearly verbatim.

Conciseness: trim sections that define well-known concepts (freemium vs free-trial definitions, upsell/cross-sell/downsell basics) down to only the opinionated decision criteria (when each works, when to avoid).

Actionability: add a short worked example walking one product end-to-end — free-tier choice, trigger moment, paywall copy, plan structure — so the 12-consideration framework can be followed concretely.

DimensionReasoningScore

Conciseness

Mostly efficient opinionated guidance, but padded in places: the paywall-everywhere/free-forever-trap/value-triggered-upgrade framing is restated four times (intro paragraphs, keystone section, framework item 2, closing), and sections restate concepts Claude already knows (freemium vs free-trial definitions, upsell/cross-sell/downsell basics). Fits anchor 3 ('mostly efficient but includes some unnecessary explanation or could be tightened'); not anchor 2 because the bulk is domain-specific opinionated content rather than generic explanation.

3 / 5

Actionability

Concrete guidance throughout for an instruction-only skill: strong/weak trigger-moment lists with reasons, presentation patterns with when-to-use, copy exemplars ("You have used [feature] 50 times. Upgrade to remove the limit and unlock [related capabilities]."), a symptom-to-diagnosis failure table, and a 12-consideration walkthrough. Not anchor 5: there is no end-to-end worked example, and some guidance remains at principle level (e.g., "The upgrade ask is honest about what they get next").

4 / 5

Workflow Clarity

Clear sequenced process — the free-tier decision is explicitly staged first ("Before designing the upgrade flow, decide the free-tier structure"), then the numbered 12-consideration framework — with checkpoints (the litmus test, conversion-as-success-metric as consideration 11). Fits anchor 4 ('clear sequence with most checkpoints present; minor validation gaps'); not anchor 5 because there is no explicit validate-then-proceed feedback loop or measurement guidance in the walkthrough itself.

4 / 5

Progressive Disclosure

The body is an overview with each section signaling 'Detail in [references/X.md]' to real, verified one-level-deep reference files (all 9 cited files exist in references/), plus a consolidated, annotated Reference files list. Matches anchor 5 ('clear overview with well-signaled one-level-deep references; content appropriately split; easy navigation').

5 / 5

Total

16

/

20

Passed

Description

96%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 description: concrete, comprehensive action coverage with explicit and natural trigger terms, plus a distinctive three-pattern framing that aids routing. The only weakness is minor overlap risk on retention-domain terms (churn prevention, win-back flow).

DimensionReasoningScore

Specificity

The description lists multiple specific concrete actions — "Trigger moments, paywall design, value demonstration, upsell vs downsell, win-back flows, churn prevention" — comprehensively covering the free-to-paid conversion domain, analogous to the anchor-5 exemplar ('Extract text and tables from PDF files, fill forms, merge documents'). Not anchor 4: the only unlisted sub-task (plan structure) is a trivial coverage gap.

5 / 5

Completeness

Explicitly answers both 'what' ("Designing free-to-paid conversion flows for SaaS products" plus named sub-tasks) and 'when' ("Triggers on... Also triggers when...") with concrete trigger phrases, structurally matching the anchor-5 example. Not anchor 4: the 'when' clause is explicit and specific, not merely present.

5 / 5

Trigger Term Quality

"Triggers on upgrade flow, paywall, free-to-paid, freemium conversion, trial conversion, plan upgrade, subscription upgrade, win-back flow, churn prevention" provides comprehensive natural-term coverage with synonyms (freemium/trial/plan/subscription conversion), plus situational triggers ("when free-to-paid conversion is low, when paywalls are blocking the wrong moments"). Matches anchor 5; not anchor 4 because no common variation is missing.

5 / 5

Distinctiveness Conflict Risk

The niche is clear and the dominant triggers (paywall, freemium conversion, trial conversion, free-to-paid) are distinct, but "churn prevention" and "win-back flow" are retention-domain terms a closely related lifecycle/retention skill could also claim — a minor overlap risk, placing it at anchor 4 rather than the minimal-conflict anchor 5. Not anchor 3: the description is far more specific than 'Works with document files'.

4 / 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.

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

rampstackco/claude-skills

Path

skills/upgrade-flow-design/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.