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.

68

Quality

81%

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

68%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, domain-specific reference with genuinely useful benchmark data and a concrete output format, mostly respecting token efficiency. Its weaknesses are the lack of an explicitly sequenced decision workflow with validation checkpoints after the initial assessment, and a small amount of common marketing-knowledge padding.

Suggestions

After the Initial Assessment, add an explicit sequenced flow (assess current model → select model via comparison table → set pricing against category benchmarks → design paywall → produce output) so the topical sections read as steps rather than a catalog.

Add validation checkpoints, e.g. verify proposed pricing falls within the category benchmark table and expected conversion is consistent with the paywall-timing table before emitting the recommendation.

Trim widely-known pricing psychology (charm pricing, 3-tier anchoring) and consider moving the category benchmark tables to a references/ file to slim SKILL.md.

DimensionReasoningScore

Conciseness

Mostly lean, table-driven content with no padding or tutorials on basics, but sections like "Pricing Psychology" ("End in .99... still works", "Use 3-tier pricing") restate marketing knowledge Claude already has and could be trimmed, falling short of the every-token-earns-its-place anchor.

4 / 5

Actionability

Concrete, specific guidance throughout — exact tier structures ("40-60% discount vs monthly", "2-3x annual price"), category benchmark ranges, and a fill-in output template — though the template uses placeholders ("$[X.99]", "[model]") rather than fully worked examples, leaving minor gaps.

4 / 5

Workflow Clarity

The numbered "Initial Assessment" steps (1-6) give a clear intake sequence, but the rest is organized as topical reference tables rather than an explicit decision flow, and checkpoints are absent or only implicit (e.g., no step to validate proposed pricing against the category benchmarks it provides).

3 / 5

Progressive Disclosure

Well-organized single-file skill with clear section headers and appropriately inline decision tables that are needed at recommendation time; no bundle files exist and no references are buried. Minor gap: the ~165-line file exceeds the simple-skill threshold and the category benchmark tables could live in a reference file.

4 / 5

Total

15

/

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 description: concrete capability list, explicit what-and-when structure, and comprehensive natural trigger terms including both the IAP abbreviation and its expansion. The explicit deferral to sibling skills for retention and competitive pricing further lowers conflict risk.

DimensionReasoningScore

Specificity

Lists several concrete monetization areas — "pricing, paywalls, subscriptions, or in-app purchases" — plus "free trial" and "conversion to paid", but the governing verbs ("design or optimize") are generic, leaving minor coverage gaps rather than the fully comprehensive action list of a 5.

4 / 5

Completeness

Explicitly answers what ("design or optimize their app's monetization — pricing, paywalls, subscriptions, or in-app purchases") and when ("When the user wants to... Also use when the user mentions...") with concrete trigger phrases, matching the 5 anchor pattern.

5 / 5

Trigger Term Quality

Comprehensive natural trigger coverage: "pricing", "paywall", "subscription", "IAP", "how to monetize", "revenue optimization", "free trial", "conversion to paid" — these are exactly the phrases a user would say, including both the abbreviation and its expansion.

5 / 5

Distinctiveness Conflict Risk

Clear niche (mobile app monetization) with distinct triggers, and it actively reduces overlap risk by routing adjacent intents to sibling skills ("For retention impact, see retention-optimization. For competitive pricing, see competitor-analysis.").

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.

Validation — 16 / 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.