finance-based-pricing-advisor

Evaluate pricing changes using ARPU, conversion, churn risk, NRR, and payback. Use when deciding whether a pricing move should ship.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

77%

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

A highly actionable, well-sequenced advisory skill with concrete scripts and worked examples. Its weaknesses are length/templating redundancy and a monolithic structure with no bundled reference files to offload detail.

Suggestions

Collapse the four recommendation patterns into one parameterized template keyed by outcome, eliminating the repeated placeholder blocks and cutting length substantially.

Move the worked examples and pitfalls into bundled reference files (e.g. references/examples.md, references/pitfalls.md) referenced one level deep from the body, improving progressive disclosure.

Add a brief input-validation note (flag missing ARPU/churn/conversion baselines before modeling) as a lightweight checkpoint at Step 0.

Dimension	Reasoning	Score
Conciseness	Per-section guidance is reasonably tight and avoids explaining concepts Claude already knows, but the ~775-line body repeats near-identical placeholder template blocks ($___, ___%) across four recommendation patterns, so it could be tightened well below current length.	2 / 3
Actionability	Concrete adaptive question scripts, six explicitly enumerated change-type branches with exact fields to collect, and three worked examples with real arithmetic (e.g. 50 × ($500 − $200) = +$15K MRR) give fully executable, copy-ready guidance.	3 / 3
Workflow Clarity	Steps 0–5 are clearly sequenced with adaptive branching by change type and a final synthesis step; being an advisory (non-destructive) skill, the missing-feedback-loop cap does not apply and the multi-step sequence is unambiguous.	3 / 3
Progressive Disclosure	No references/scripts/assets bundle exists and the body is a single 775-line monolith; an examples/ folder and sibling skills are mentioned but not bundled, so structure is present but most detail that could be split out is inline.	2 / 3
	Total	10 / 12 Passed

Description

85%

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 tight, third-person description that clearly states both capability and trigger. Its main weakness is trigger-term breadth — a single "pricing move" phrasing rather than the concrete change types (price increase, discount, new tier) users actually voice.

Suggestions

Broaden the trigger clause to mirror real user phrasing, e.g. "Use when deciding whether to raise prices, add a tier, introduce an add-on, or offer a discount."

Dimension	Reasoning	Score
Specificity	Names the domain (pricing changes) and lists multiple concrete analytical actions and metrics — "ARPU, conversion, churn risk, NRR, and payback" — matching the multi-action anchor.	3 / 3
Completeness	Explicitly answers both what ("Evaluate pricing changes using ARPU, conversion, churn risk, NRR, and payback") and when ("Use when deciding whether a pricing move should ship"), with a clear explicit trigger clause.	3 / 3
Trigger Term Quality	"Use when deciding whether a pricing move should ship" is a natural trigger, but coverage is thin — it omits common variations users would actually say like "price increase", "discount", "new tier", or "should we raise prices".	2 / 3
Distinctiveness Conflict Risk	The financial-impact-of-pricing niche is distinct, and the trigger centers on pricing-move ship decisions, making overlap with adjacent finance/strategy skills unlikely.	3 / 3
	Total	11 / 12 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (776 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 suspicious	Warning

	Total	13 / 16 Passed

Repository: deanpeters/Product-Manager-Skills
Path: skills/finance-based-pricing-advisor/SKILL.md
Commit: 9971018

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.