diagnose-monetization

Diagnose revenue leaks, analyze willingness-to-pay, evaluate packaging and pricing, and identify expansion revenue opportunities. Use when a PM needs to improve conversion to paid, optimize pricing, reduce revenue churn, or find upsell and expansion opportunities.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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

The body is highly actionable with a clear sequenced workflow and concrete formulas, but it leans verbose in its conceptual framing and is a monolithic inline block with no progressive disclosure into reference files.

Suggestions

Trim the motivational opening paragraph ('You are delivering value but not capturing it proportionally...') to a single sentence so the actionable steps start sooner.

Consider moving the detailed anti-plays and the opportunity-matrix template into a separate reference file linked from the main body to improve progressive disclosure.

Add an explicit data-validation checkpoint early in Step 1 (e.g., 'if any of ARR/ARPU/conversion/churn are missing, ask for them before sizing') to strengthen the workflow's verification feedback loop.

Dimension	Reasoning	Score
Conciseness	Mostly efficient actionable steps, but the opening paragraph ('You are delivering value but not capturing it proportionally... The best monetization improvements come from aligning price with value') frames concepts Claude already knows and could be trimmed.	2 / 3
Actionability	Provides concrete formulas ('Revenue = Users x Conversion Rate x ARPU x (1 - Revenue Churn Rate) + Expansion Revenue'), sizing templates ('X free users use Feature Y weekly... this is $Z/month'), and an output matrix — copy-paste-ready structured guidance for an instruction-only skill.	3 / 3
Workflow Clarity	Clear five-step sequence (Revenue Architecture → Funnel → Packaging → Expansion → Size & Rank) with an explicit seven-item output deliverable checklist and an 'open questions' verification prompt; no destructive/batch ops that would require explicit validate-fix loops.	3 / 3
Progressive Disclosure	Well-organized into labeled sections but presented as one large monolithic inline prompt block over 50 lines with no bundle references to offload detail, so it sits at the some-structure level rather than the clearly-split level 3.	2 / 3
	Total	10 / 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 third-person, concrete, and answers both what and when with natural PM trigger terms. It is a strong, low-conflict description with no padding.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Diagnose revenue leaks, analyze willingness-to-pay, evaluate packaging and pricing, and identify expansion revenue opportunities' — matching the multi-action anchor rather than the single-domain level 2.	3 / 3
Completeness	Explicitly answers both what (the four diagnostic actions) and when ('Use when a PM needs to improve conversion to paid, optimize pricing, reduce revenue churn, or find upsell and expansion opportunities'), matching the level-3 anchor.	3 / 3
Trigger Term Quality	Natural PM vocabulary appears throughout — 'conversion to paid', 'optimize pricing', 'reduce revenue churn', 'upsell and expansion opportunities' — the terms a user would actually say when needing this skill.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear monetization/pricing niche with distinct PM-oriented triggers unlikely to fire for unrelated skills, matching the clear-niche anchor.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: amplitude/builder-skills
Commit: 22b0634

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.