CtrlK
BlogDocsLog inGet started
Tessl Logo

paywall-optimization

When the user wants to design, test, or optimize their app's paywall — layout, copy, pricing display, trial offers, plan structure, hard vs soft paywall, paywall placement, or paywall A/B tests. Use when the user mentions "paywall", "paywall design", "paywall conversion", "trial-to-paid", "soft paywall", "hard paywall", "paywall A/B test", "paywall copy", "plan picker", "annual vs monthly display", "best paywall", "RevenueCat paywall", "Superwall", "Adapty", or "my paywall isn't converting". For overall pricing strategy and monetization model choice, see monetization-strategy. For trial nurture, dunning, and churn, see subscription-lifecycle. For where in the onboarding the paywall fires, see onboarding-optimization.

76

Quality

93%

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

87%

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

The body is a tight, domain-specific playbook that assumes Claude's intelligence and delivers concrete scoring rubrics, numeric benchmarks, and a copy-paste output template rather than filler. Its main weakness is workflow clarity: the diagnose-before-redesign sequence would benefit from explicit validation checkpoints before proceeding to redesign or test.

Suggestions

Add explicit validation checkpoints to the diagnostic flow — e.g., 'Do not redesign until you have confirmed the weakest funnel stage with at least 30 days of data; if data is missing, stop and ask for it.'

Add a verify-then-proceed gate to the A/B Testing section stating the exact stopping condition (sample size reached + p<0.05) before declaring a winner, since 'Common Mistakes' flags false positives in low-traffic apps.

Insert a quick cross-check step after pulling RevenueCat/asc-metrics noting what to do if the two trial-count sources disagree (e.g., trust asc-metrics and note the discrepancy in the diagnostic).

DimensionReasoningScore

Conciseness

Lean and efficient: every section (funnel, audit, placement, pricing, A/B playbook, output template, mistakes) earns its place and assumes Claude's competence, with no padding explaining what a paywall or A/B test is.

3 / 3

Actionability

Provides concrete, executable guidance — numeric healthy/red-flag funnel ranges, a 1–5 scoring audit, sample-size floors by baseline conversion, a copy-paste output template, and named tools (Superwall, RevenueCat Experiments, Adapty).

3 / 3

Workflow Clarity

Has a clear sequence (Initial Assessment → Diagnose → 7-Element Audit → Placement → A/B Testing → Output) but validation checkpoints are implicit rather than explicit verify-then-proceed gates; e.g. 'Identify the weakest stage' is a soft gate, not a required verification loop.

2 / 3

Progressive Disclosure

A single self-contained file with well-organized, clearly headed sections and easy navigation; no external references are needed for this analysis-oriented skill, consistent with the simple-skill scoring note. No bundle files exist to verify against.

3 / 3

Total

11

/

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 dense and complete, naming concrete paywall optimization actions, an explicit 'Use when' trigger clause, and broad natural trigger terms. Its distinctiveness is reinforced by explicit cross-skill routing that scopes it narrowly. It is slightly verbose but well within rubric tolerance and uses consistent third-person voice.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions such as 'design, test, or optimize their app's paywall — layout, copy, pricing display, trial offers, plan structure, hard vs soft paywall, paywall placement, or paywall A/B tests'.

3 / 3

Completeness

Clearly answers both 'what' (design, test, optimize paywalls) and 'when' via an explicit 'Use when the user mentions...' clause with concrete triggers.

3 / 3

Trigger Term Quality

Excellent coverage of natural terms a user would actually say, including 'paywall', 'soft paywall', 'hard paywall', 'plan picker', 'annual vs monthly display', 'RevenueCat paywall', 'Superwall', 'Adapty', and 'my paywall isn't converting'.

3 / 3

Distinctiveness Conflict Risk

Clear niche with distinct triggers plus explicit routing to adjacent skills ('see monetization-strategy', 'see subscription-lifecycle', 'see onboarding-optimization'), making it unlikely to trigger for the wrong skill.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Eronred/aso-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.