CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pricing-strategy

Analyze and design pricing strategies including pricing models, competitive pricing analysis, willingness-to-pay estimation, and price elasticity. Use when setting prices, evaluating pricing models, preparing for a pricing change, or comparing freemium vs paid approaches.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 solid, well-structured instruction skill: concrete examples, specific numbers, and a clear sequenced workflow ending in a structured output template. It is consistently one notch from excellent — a little filler, a couple of vague fallbacks, and validation that is implied by the output format rather than built into the process.

Suggestions

Remove 'Think step by step.' and trim the Van Westendorp price-point ladder to just the method name — Claude already knows how the Price Sensitivity Meter works.

Make step 5's fallback concrete: replace 'estimate based on competitor pricing and value delivered' with a specific heuristic (e.g., benchmark against the closest competitor's mid-tier and test 0.5x/1x/2x value-delivered price points).

Convert the closing 'Flag any assumptions' instruction into an explicit final workflow step (e.g., 'Step 8: List each assumption with a test') so validation is a checkpoint in the sequence rather than a closing remark.

DimensionReasoningScore

Conciseness

The body is mostly efficient — a tight model-comparison table and specific numbers ("15-20% off monthly pricing") — but "Think step by step." is filler and the Van Westendorp price-point ladder ("Too cheap → quality concerns...") re-explains a methodology Claude already knows. Minor over-explanation, not pervasive padding.

4 / 5

Actionability

Guidance is concrete and executable for an instruction-only skill: a pricing-model table with real exemplars (Basecamp $99/mo, Slack, AWS), specific parameters ("2-4 tiers", "Annual discount: Typically 15-20%"), a named method (Van Westendorp PSM), and a copy-paste output template. Minor gaps remain: step 1 is a list of questions rather than a method, and step 5's fallback ("estimate based on competitor pricing and value delivered") is vague.

4 / 5

Workflow Clarity

The 7-step sequence (value → model selection → competitive analysis → structure → sensitivity → experiments → output) is clear and logically ordered, and validation appears via "[Assumption] → [How to test]" and "Flag any assumptions that need validation before launch". However, checkpoints are embedded in the output template rather than explicit mid-process validation steps, and there are no feedback loops.

4 / 5

Progressive Disclosure

Sections (Context / Instructions / Further Reading) are well organized and the Further Reading links are clearly signaled, with all content appropriately inline at ~80 lines and no bundle files to misplace. It falls short of the top anchor because the skill exceeds the under-50-lines simple-skill threshold and the model-comparison table plus PSM detail could arguably live in a reference file.

4 / 5

Total

16

/

20

Passed

Description

87%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: it states concrete capabilities in third person and pairs them with an explicit, well-phrased 'Use when...' trigger clause covering several natural use cases. The only weaknesses are a few missing natural synonyms and slightly generic verbs.

DimensionReasoningScore

Specificity

The description lists four concrete capability areas ("pricing models, competitive pricing analysis, willingness-to-pay estimation, and price elasticity"), but the verbs remain generic ("Analyze and design") and adjacent areas like tiering, packaging, and discount design are absent — minor gaps rather than comprehensive coverage.

4 / 5

Completeness

It explicitly answers both what ("Analyze and design pricing strategies including pricing models, competitive pricing analysis, willingness-to-pay estimation, and price elasticity") and when ("Use when setting prices, evaluating pricing models, preparing for a pricing change, or comparing freemium vs paid approaches") with concrete trigger phrases, matching the top anchor's pattern.

5 / 5

Trigger Term Quality

"setting prices", "preparing for a pricing change", and "comparing freemium vs paid approaches" are phrases users would naturally say, but common synonyms such as "monetization", "how much should I charge", and "subscription tiers" are missing.

4 / 5

Distinctiveness Conflict Risk

Pricing strategy is a clear niche with distinct, pricing-specific triggers ("setting prices", "freemium vs paid", "pricing change") that are unlikely to fire for unrelated skills.

5 / 5

Total

18

/

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

phuryn/pm-skills

Path

pm-product-strategy/skills/pricing-strategy/SKILL.md

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.