CtrlK
BlogDocsLog inGet started
Tessl Logo

monetization-strategy

When the user wants to design or optimize their app's monetization — pricing, paywalls, subscriptions, or in-app purchases. Also use when the user mentions "pricing", "paywall", "subscription", "IAP", "how to monetize", "revenue optimization", "free trial", or "conversion to paid". For retention impact, see retention-optimization. For competitive pricing, see competitor-analysis.

72

Quality

88%

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 dense, actionable monetization reference with strong concrete guidance and clean sectioning. Its weaknesses are moderate: inlined reference data and the absence of explicit validation/feedback checkpoints in the workflow.

Suggestions

Move the category benchmark and pricing-tier reference tables into a separate references/ file (e.g., BENCHMARKS.md) and link to it from SKILL.md to reduce inline token load and improve progressive disclosure.

Add an explicit validation checkpoint in the Initial Assessment (confirm the user's current model and goals before recommending changes) and a measure-then-iterate feedback loop after the recommendation.

Tighten the Pricing Psychology and 'What converts' bullet lists, condensing widely-known heuristics to preserve token budget.

DimensionReasoningScore

Conciseness

Largely efficient, table-dense reference material that avoids explaining concepts Claude already knows, but the sheer volume (~170 lines) of inlined benchmark and psychology bullets could be trimmed or moved to keep every token earning its place.

4 / 5

Actionability

Highly concrete guidance with specific pricing benchmarks, conversion rates by paywall timing, a copy-paste output-format template, metric formulas with targets, and a sequenced implementation roadmap — fully actionable for an instruction-only skill.

5 / 5

Workflow Clarity

The Initial Assessment gives a clear sequenced intake and the roadmap is ordered, but there are no explicit validation checkpoints or feedback loops (e.g., confirm assumptions before recommending, measure-then-iterate).

4 / 5

Progressive Disclosure

Well-organized into clear sections with a Related Skills list, but no bundle files exist and substantial reference tables (category benchmarks, pricing tiers) are inlined rather than split into linked reference files.

4 / 5

Total

17

/

20

Passed

Description

95%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, third-person description that clearly states the skill's purpose, provides comprehensive natural trigger phrases, and actively disambiguates from related skills. The only minor gap is the limited number of distinct action verbs versus the comprehensive-coverage anchor.

DimensionReasoningScore

Specificity

Names the monetization domain plus several concrete sub-areas ("pricing, paywalls, subscriptions, or in-app purchases") and the actions "design or optimize", but the action verbs are limited relative to the comprehensive anchor.

4 / 5

Completeness

Explicitly answers both what ("design or optimize their app's monetization") and when ("Also use when the user mentions ...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural trigger coverage including synonyms and abbreviations ("pricing", "paywall", "subscription", "IAP", "how to monetize", "revenue optimization", "free trial", "conversion to paid").

5 / 5

Distinctiveness Conflict Risk

Clear monetization niche with distinct triggers and explicit sibling disambiguation ("For retention impact, see retention-optimization. For competitive pricing, see competitor-analysis.") minimizing conflict risk.

5 / 5

Total

19

/

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.