CtrlK
BlogDocsLog inGet started
Tessl Logo

paywall-upgrade-cro

You are an expert in in-app paywalls and upgrade flows. Your goal is to convert free users to paid, or upgrade users to higher tiers, at moments when they've experienced enough value to justify the commitment.

44

Quality

45%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/paywall-upgrade-cro/SKILL.md

The canonical home for this skill is paywall-upgrade-cro in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is well-structured and offers concrete paywall templates plus a clear output spec, but it is markedly verbose with heavy inline content and limited executable specificity. It scores mid-range across most dimensions.

Suggestions

Move the large 'Experiment Ideas' and 'Common Patterns by Business Model' sections into reference files (e.g. references/experiments.md, references/business-models.md) and link to them from SKILL.md to improve both conciseness and progressive disclosure.

Trim generic advisory bullets into concrete defaults — replace 'Show security signals' with specific examples of what to show and where.

Replace the filler 'When to Use' sentence with a concrete trigger list of when this skill applies (in-app paywall design, upgrade-flow optimization, trial-conversion work).

DimensionReasoningScore

Conciseness

The ~575-line body is noticeably verbose: the enormous 'Experiment Ideas' section and many bullet lists read as padding Claude could generate, and the closing 'When to Use' line is filler, matching the 'noticeably verbose' anchor.

2 / 5

Actionability

Provides genuinely concrete ASCII paywall templates with copy and a specified Output Format, but a large portion is abstract bullet advice ('Minimize steps', 'Show security signals') that lacks the specifics needed to execute directly.

3 / 5

Workflow Clarity

The advisory flow (Initial Assessment → apply principles/components → produce the specified output) is sequenced, but as a non-destructive advisory skill it has no explicit validation checkpoints, matching the 'steps present but checkpoints missing' anchor.

3 / 5

Progressive Disclosure

No bundle files exist and everything is inlined into one ~575-line SKILL.md; headers are clear, but content that belongs in separate references (experiment catalog, business-model patterns) is inline, so it does not meet the simple-skill exception.

3 / 5

Total

11

/

20

Passed

Description

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

The description conveys a clear purpose and a recognizable niche, but is held back by second-person voice, the absence of an explicit 'Use when' trigger clause, and limited keyword synonyms. It lands in the middle of the scale.

Suggestions

Rewrite in third person (e.g. 'Converts free users to paid and upgrades users to higher tiers...') to satisfy the voice requirement and recover specificity.

Add an explicit 'Use when...' clause naming natural trigger phrases such as paywalls, subscription conversion, in-app purchase prompts, trial expiration, and upgrade flows.

Broaden trigger-term coverage with synonyms users actually say — monetization, IAP, free-to-paid conversion, plan upgrade.

DimensionReasoningScore

Specificity

Names the domain and two concrete actions ('convert free users to paid, or upgrade users to higher tiers'), matching anchor 3, but the description is written in second person ('You are an expert', 'Your goal'), which the rubric penalizes by reducing specificity by 1.

2 / 5

Completeness

Clearly states what the skill does, but offers no explicit 'Use when...' trigger guidance — the phrase 'at moments when they've experienced enough value' refers to paywall timing, not when to invoke the skill, capping completeness at 3.

3 / 5

Trigger Term Quality

Includes relevant natural terms ('paywalls', 'upgrade flows', 'free users to paid', 'higher tiers') but misses common variations a user might say such as subscription, monetization, in-app purchase, or trial conversion.

3 / 5

Distinctiveness Conflict Risk

In-app paywalls and upgrade flows is a fairly distinct niche with only minor overlap risk against closely related skills like page-cro, matching the 'mostly distinct' anchor.

4 / 5

Total

12

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (577 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-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.