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.

74

Quality

91%

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

82%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 tightly written, highly actionable advisory skill body that uses dense tables to stay token-efficient and gives concrete benchmarks, audit criteria, and an output template. Its main gap is the absence of explicit validation/verification checkpoints in the workflow.

Suggestions

Add an explicit verification step after the A/B test runs (e.g., check sample size reached and p-value before declaring a winner) to tighten workflow_clarity toward 5.

Trim minor parenthetical qualifiers like "(depends on placement)" and "(varies by category)" in the funnel table where the ranges already imply the caveat.

Consider splitting the 7-Element Audit or A/B Testing Playbook detail into a reference file to move progressive_disclosure toward a clear one-level-deep structure.

DimensionReasoningScore

Conciseness

Dense, mostly efficient tables that assume Claude's competence without explaining what paywalls or frameworks are; a few parentheticals and the role framing could be trimmed, but nothing rises to padding. Not a clean 5 due to minor tighten-able phrasing.

4 / 5

Actionability

Provides fully concrete, executable guidance: healthy-range funnel benchmarks, a scored 7-element audit, sample-size floors per baseline, a prioritized test order, named tools, and a copy-ready output template — covering the common cases specifically.

5 / 5

Workflow Clarity

The assess → diagnose funnel → audit → choose placement → A/B test sequence is clearly laid out with a "diagnose the weakest stage only" directive, but there are no explicit validation checkpoints; this is advisory rather than destructive/batch, so it lands just below 5.

4 / 5

Progressive Disclosure

Well-organized into clear headed sections with no nested or buried references and self-contained cross-skill handoffs; no bundle files exist to evaluate against, and at >50 lines it sits just short of the simple-skill 5 exception.

4 / 5

Total

17

/

20

Passed

Description

100%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-targeted description that comprehensively states capabilities, lists natural trigger phrases including tool names, and explicitly delineates boundaries against adjacent skills. No meaningful gaps relative to the rubric anchors.

DimensionReasoningScore

Specificity

Lists multiple concrete capability areas — "design, test, or optimize" across "layout, copy, pricing display, trial offers, plan structure, hard vs soft paywall, paywall placement, or paywall A/B tests" — giving comprehensive, non-abstract coverage rather than a single generic verb.

5 / 5

Completeness

Explicitly answers both what (design/test/optimize a paywall with listed sub-tasks) and when (an explicit "Use when the user mentions..." clause with concrete triggers), plus boundary routing to sibling skills.

5 / 5

Trigger Term Quality

Covers natural user phrasings comprehensively, including synonyms ("paywall", "paywall design", "soft paywall", "hard paywall", "plan picker"), tool names (RevenueCat, Superwall, Adapty), and a real complaint phrase ("my paywall isn't converting").

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (paywall conversion) with distinct triggers and explicit cross-skill handoffs to monetization-strategy, subscription-lifecycle, and onboarding-optimization, minimizing overlap risk.

5 / 5

Total

20

/

20

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.