CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

65

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

57%

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

The body is well-structured and uses progressive disclosure effectively with real reference files, but it leans on conceptual prose and abstract direction over concrete, executable guidance and lacks validation checkpoints in its workflow. Tightening the prose and adding actionable artifacts would lift the weaker dimensions.

Suggestions

Replace abstract directives with concrete, copy-paste-ready artifacts: paywall copy templates tied to each trigger type, a trigger-moment scoring rubric, and a worked example flow end-to-end.

Add validation checkpoints to the 12-consideration framework (e.g., 'for each chosen trigger, verify the user can articulate why they should pay before shipping') so the workflow has explicit feedback loops.

Trim repeated restatements of the paywall-everywhere / free-forever-trap / value-triggered-upgrade framing (it appears in the intro, keystone section, failure modes, and closing) to reduce token overhead.

DimensionReasoningScore

Conciseness

The body restates SaaS conversion concepts Claude largely knows and repeats the keystone framing across the intro, dedicated section, failure modes, and closing; organized but padded with unnecessary explanation rather than lean.

2 / 3

Actionability

Guidance is mostly abstract ('Paywalls surface at moments where the user has demonstrated value') with no executable code, commands, or copy templates beyond two illustrative one-liners; it describes rather than instructs.

2 / 3

Workflow Clarity

The 12-consideration framework gives a clear sequence, but there are no validation checkpoints or feedback loops for a consequential design decision, which caps workflow clarity at 2 per the rubric.

2 / 3

Progressive Disclosure

Clear overview with well-signaled one-level-deep references ('Detail in [references/X.md]') that all resolve to real files, plus a consolidated reference list for navigation.

3 / 3

Total

9

/

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.

The description is precise, third-person, and densely packed with natural trigger terms, covering both what the skill does and when to invoke it. It carves a clear, non-overlapping niche among growth skills.

DimensionReasoningScore

Specificity

Names multiple concrete actions ('Trigger moments, paywall design, value demonstration, upsell vs downsell, win-back flows, churn prevention') in third-person voice, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what ('Designing free-to-paid conversion flows...') and when via a dedicated 'Triggers on...' clause plus an 'Also triggers when...' clause.

3 / 3

Trigger Term Quality

Strong natural keyword coverage ('upgrade flow, paywall, free-to-paid, freemium conversion, trial conversion, plan upgrade, subscription upgrade, win-back flow, churn prevention') that a user would actually say.

3 / 3

Distinctiveness Conflict Risk

Clear free-to-paid SaaS niche with distinct triggers and explicit adjacent-pattern distinctions (paywall-everywhere vs free-forever-trap vs value-triggered-upgrade), making conflicts 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
rampstackco/claude-skills
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.