CtrlK
BlogDocsLog inGet started
Tessl Logo

finance-based-pricing-advisor

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

66

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

71%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 highly actionable, well-sequenced interactive workflow with strong concrete guidance and worked examples. Its main weaknesses are verbosity from templated fill-in prompts and a monolithic structure with a missing referenced 'examples/' folder.

Suggestions

Externalize the four full recommendation-pattern templates and the ten pitfalls into a reference file (e.g. references/recommendation-patterns.md) to reduce body length and improve progressive disclosure.

Create or remove the referenced 'examples/' folder — the body currently points to a folder that does not exist.

Tighten the fill-in-the-blank prompt templates by collapsing repetitive '$___' placeholder lines into compact parameter lists, cutting padding without losing the adaptive-question structure.

DimensionReasoningScore

Conciseness

The ~770-line body is mostly task-structured rather than teaching basics Claude already knows, but heavy use of fill-in-the-blank prompt templates with many '$___' placeholders and verbose recommendation/pitfall sections adds noticeable padding that could be trimmed.

3 / 5

Actionability

Provides concrete adaptive question flows, enumerated decision options, numbered recommendations with specific thresholds (>10% ARPU lift, <5% churn), and three fully worked examples with real numbers — copy-paste ready guidance for an instruction-only skill.

5 / 5

Workflow Clarity

Steps 0–5 are clearly sequenced with adaptive branches per change type and condition-gated recommendation patterns ('When...'/'Don't roll out if...'); the 'test first' A/B pattern acts as a validation loop, though there is no explicit validate→fix→retry checkpoint elsewhere.

4 / 5

Progressive Disclosure

Section structure is reasonable, but the file is monolithic with no bundle directories (references/, scripts/, assets/ absent), the referenced 'examples/' folder does not exist, and large recommendation templates and pitfalls that could be externalized are inlined.

3 / 5

Total

15

/

20

Passed

Description

92%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, specific description with clear what/when structure and natural trigger phrases. Minor room to add synonyms (price increase, discount, new tier) to round out trigger-term coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete analytic actions — 'using ARPU, conversion, churn risk, NRR, and payback' — covering the domain comprehensively rather than vague abstractions.

5 / 5

Completeness

Explicitly answers both 'what' (evaluate pricing changes using the listed metrics) and 'when' ('Use when deciding whether a pricing move should ship') with a concrete trigger phrase.

5 / 5

Trigger Term Quality

Includes natural terms like 'pricing changes', 'ARPU', 'NRR', 'payback', and the phrase 'whether a pricing move should ship'; a few synonyms (e.g., price increase, discount, new tier) are absent, keeping it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — financial-impact evaluation of a specific pricing change — and is explicitly scoped away from value-based pricing, WTP research, and packaging architecture, minimizing overlap with sibling skills.

5 / 5

Total

19

/

20

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (778 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
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.