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,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' or 'should I offer a free plan.' Use this whenever someone is figuring out what to charge or how to structure their plans. For in-app upgrade screens, see paywall-upgrade-cro.
Install with Tessl CLI
npx tessl i github:coreyhaines31/marketingskills --skill pricing-strategy72
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
72%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 description excels at trigger term coverage and distinctiveness, with an impressive list of natural user phrases and explicit disambiguation from related skills. However, it fails to describe what the skill actually does - it's all 'when' and no 'what.' The description would benefit from leading with specific capabilities like 'Analyzes pricing models, recommends tier structures, evaluates value metrics.'
Suggestions
Add specific capability statements at the beginning describing concrete actions (e.g., 'Analyzes pricing models, recommends tier structures, evaluates willingness to pay, designs packaging strategies').
Restructure to lead with 'what it does' before the extensive 'when to use' section to improve completeness.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (pricing decisions, packaging, monetization strategy) but lacks specific concrete actions. It describes when to use it rather than what specific actions it performs (e.g., 'analyze pricing models', 'create tier structures', 'calculate willingness to pay'). | 2 / 3 |
Completeness | Strong on 'when' with explicit trigger guidance and extensive keyword list, but weak on 'what' - it doesn't clearly explain what the skill actually does beyond vague references to 'help with pricing decisions.' The description focuses almost entirely on triggers rather than capabilities. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'pricing,' 'freemium,' 'free trial,' 'how much should I charge,' 'my pricing is wrong,' 'per seat pricing,' 'should I offer a free plan.' These are highly natural phrases that match real user queries. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche with distinct triggers around pricing and monetization. The explicit callout 'For in-app upgrade screens, see paywall-upgrade-cro' demonstrates awareness of potential conflicts and provides disambiguation guidance. | 3 / 3 |
Total | 10 / 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 skill provides a solid conceptual framework for pricing strategy with good organization and appropriate progressive disclosure to reference materials. However, it leans too heavily on explanatory content rather than actionable guidance, and lacks concrete examples like sample pricing calculations, actual tier structures with numbers, or step-by-step workflows for implementing pricing changes.
Suggestions
Add concrete examples with actual numbers (e.g., 'If your ARPU is $50 and conversion is 45%, consider testing $65-75 range')
Include a step-by-step workflow for creating a pricing strategy from scratch, with validation checkpoints (e.g., 'After competitor research, verify you have at least 3 comparable products before proceeding')
Remove explanatory definitions Claude already knows (e.g., 'What is a Value Metric?' section) and replace with more actionable guidance
Add a concrete pricing page wireframe or structure example rather than just listing 'common elements'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some explanatory text that Claude would already know (e.g., explaining what value-based pricing means, basic definitions). The tables and checklists are well-structured, but sections like 'What is a Value Metric?' explain concepts Claude understands. | 2 / 3 |
Actionability | Provides good frameworks and checklists but lacks concrete, executable examples. No specific pricing calculations, no sample pricing page structures, no actual numbers to work with. The guidance is more conceptual than copy-paste actionable. | 2 / 3 |
Workflow Clarity | The checklist at the end provides some sequence, and the 'Before Starting' section establishes context gathering. However, there's no clear step-by-step workflow for actually creating a pricing strategy, and no validation checkpoints to verify pricing decisions before implementation. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear references to detailed materials (references/tier-structure.md, references/research-methods.md). The main document serves as an overview with well-signaled one-level-deep references. Related skills section provides good navigation to adjacent topics. | 3 / 3 |
Total | 9 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.