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 well-structured description with excellent trigger term coverage and clear 'when to use' guidance. Its main weakness is that the 'what it does' portion is somewhat high-level, listing topic areas rather than specific concrete actions the skill performs. Despite this, the description would perform well in skill selection due to its comprehensive trigger terms and explicit usage guidance.
Suggestions
Replace the general topic areas ('pricing research, tier structure, and packaging strategy') with specific concrete actions, e.g., 'Designs pricing tier structures, conducts Van Westendorp analysis, models freemium conversion, evaluates value metrics, and recommends price increase strategies.'
| 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 things the skill does (e.g., 'designs pricing tiers,' 'runs Van Westendorp analysis,' 'models revenue impact'). | 2 / 3 |
Completeness | Clearly answers both 'what' (pricing research, tier structure, packaging strategy, monetization) and 'when' (explicit 'Use when' clause with a comprehensive list of trigger terms and scenarios). The 'when' guidance is particularly strong. | 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,' 'monetization.' These are terms users would naturally use when seeking help with pricing decisions. | 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 well-structured strategic skill that covers pricing comprehensively with good progressive disclosure and organization. Its main weaknesses are moderate verbosity in explaining concepts Claude already understands (value-based pricing, what value metrics are) and a lack of concrete, executable outputs—there are no templates, sample deliverables, or specific analytical frameworks with worked examples. The workflow could benefit from explicit validation steps and decision-tree logic.
Suggestions
Add concrete output templates or examples—e.g., a sample tier structure table, a sample Van Westendorp analysis summary, or a pricing recommendation deliverable format that Claude should produce.
Remove explanatory content Claude already knows (e.g., 'Price should be based on value delivered, not cost to serve' and the definition of value metrics) and replace with specific decision rules or heuristics unique to this skill.
Add explicit validation/feedback steps to the workflow—e.g., 'After proposing tier structure, verify: Does each tier map to a distinct persona? Is there clear upgrade motivation between tiers? If not, restructure.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary explanations of concepts Claude already knows (e.g., explaining what value-based pricing is, defining what a value metric is). The tables and frameworks are useful reference material but some sections like 'Pricing Fundamentals' and 'Value-Based Pricing' explain well-known concepts verbosely. However, it's not egregiously padded. | 2 / 3 |
Actionability | The skill provides structured frameworks and checklists which are somewhat actionable, but lacks concrete executable examples. There are no code snippets, specific templates, or copy-paste-ready outputs. The guidance is more conceptual/strategic than concrete—e.g., 'Analyze intersections to find optimal pricing zone' without showing how. | 2 / 3 |
Workflow Clarity | The 'Before Starting' section provides a clear information-gathering sequence, and the checklist at the end provides a reasonable workflow. However, there are no validation checkpoints or feedback loops—no guidance on how to verify pricing decisions are sound, no iteration steps, and no explicit 'if X then Y' decision points beyond the value metric test. | 2 / 3 |
Progressive Disclosure | The skill appropriately references external files for detailed content (references/tier-structure.md, references/research-methods.md) and links to related skills. The main document serves as a clear overview with well-signaled one-level-deep references, and content is organized into logical sections with clear headers. | 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
2c6f6e8
- 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.