pricing-strategy
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' or 'monetization.' This skill covers pricing research, tier structure, and packaging strategy.
78
73%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./config/claude/skills/pricing-strategy/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description with excellent trigger term coverage and completeness, clearly answering both what the skill does and when to use it. Its main weakness is that the 'what' portion could be more specific about concrete actions rather than listing topic areas. The trigger terms are well-chosen and span both common and specialized pricing vocabulary.
Suggestions
Replace the general topic areas ('pricing research, tier structure, and packaging strategy') with more specific concrete actions, e.g., 'Conducts Van Westendorp analyses, designs pricing tier structures, evaluates freemium vs. free trial models, recommends value metrics.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (pricing/monetization) and mentions some actions like 'pricing research, tier structure, and packaging strategy,' but these are more like topic areas than concrete actions. It doesn't list specific deliverables like 'build pricing tier comparisons, conduct Van Westendorp analysis, design freemium models.' | 2 / 3 |
Completeness | Clearly answers both 'what' (pricing research, tier structure, packaging strategy, monetization) and 'when' with an explicit 'Use when' clause listing specific trigger terms and scenarios. Both dimensions are well-covered. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' and 'monetization.' These span both common and specialized terms a user might naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche around pricing and monetization strategy with highly specific trigger terms like 'Van Westendorp,' 'value metric,' and 'willingness to pay' that are unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a reasonably well-structured pricing strategy skill that covers the key topics comprehensively and uses good progressive disclosure. Its main weaknesses are verbosity in explaining concepts Claude already understands (pricing psychology basics, what value metrics are) and a lack of concrete worked examples showing what a pricing analysis output should look like. The workflow could be strengthened with a clearer end-to-end process and validation steps.
Suggestions
Add a worked example showing a complete pricing analysis output (e.g., 'Given this SaaS product context, here's the recommended tier structure with rationale') so Claude knows what deliverable to produce.
Remove definitional content Claude already knows (e.g., 'What is a Value Metric?' section, basic pricing psychology definitions) and replace with decision rules or heuristics specific to this skill's approach.
Add an explicit end-to-end workflow: gather context → analyze value metric → design tiers → set price points → validate with research data → present recommendation, with checkpoints between steps.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary explanations of concepts Claude already knows (e.g., defining what a value metric is, explaining basic pricing psychology concepts like anchoring and decoy effect). However, the tables and checklists are reasonably efficient. Could be tightened by removing definitional content and focusing on decision frameworks. | 2 / 3 |
Actionability | The skill provides structured frameworks (Good-Better-Best, Van Westendorp questions, checklists) which give concrete guidance, but lacks executable examples—no sample pricing analyses, no template outputs, no example of what a completed pricing recommendation looks like. It describes approaches rather than demonstrating them with worked examples. | 2 / 3 |
Workflow Clarity | The 'Before Starting' section establishes a clear information-gathering sequence, and the checklists provide some structure. However, there's no clear end-to-end workflow for how to go from gathering context to delivering a pricing recommendation. The sections read more like a reference guide than a sequenced process, and there are no validation checkpoints (e.g., 'validate assumptions with customer data before finalizing tiers'). | 2 / 3 |
Progressive Disclosure | The skill appropriately references deeper content via one-level-deep links (references/tier-structure.md, references/research-methods.md) and keeps the main file as an overview. Related skills are clearly listed at the bottom. The section structure is well-organized with clear headers for navigation. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- freekmurze/dotfiles
- Commit
05d40bb
- 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.