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.

1.12x

Quality

73%

Does it follow best practices?

Impact

92%

1.12x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/pricing-strategy/SKILL.md

Quality

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, including an explicit boundary with a related skill. Its main weakness is that it focuses on when to use the skill rather than specifying what concrete actions the skill performs—it tells you the topic but not the deliverables (e.g., pricing analysis, tier recommendations, pricing page design).

Suggestions

Add specific concrete actions the skill performs, e.g., 'Analyzes pricing structures, recommends value metrics, designs pricing tiers, evaluates willingness-to-pay data' to improve specificity.

Dimension	Reasoning	Score
Specificity	The description names the domain (pricing decisions, packaging, monetization strategy) but doesn't list multiple specific concrete actions. It describes the topic area rather than what the skill actually does (e.g., 'analyze pricing tiers', 'recommend value metrics', 'build pricing pages').	2 / 3
Completeness	Clearly answers both 'what' (help with pricing decisions, packaging, monetization strategy) and 'when' with an explicit 'Use when' clause and extensive trigger terms. Also includes a helpful boundary note distinguishing it from the paywall-upgrade-cro skill.	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms users would actually say: 'how much should I charge,' 'my pricing is wrong,' 'freemium,' 'free trial,' 'per seat pricing,' 'should I offer a free plan,' 'annual vs monthly,' 'Van Westendorp,' 'willingness to pay,' and many more. These are highly natural and comprehensive.	3 / 3
Distinctiveness Conflict Risk	The description carves out a clear niche around pricing and monetization strategy with highly specific trigger terms. It even explicitly delineates its boundary from a related skill (paywall-upgrade-cro), reducing conflict risk.	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 pricing strategy skill with good progressive disclosure and organization, but it leans toward being a reference document rather than an actionable guide. It explains concepts Claude likely already knows (pricing psychology, value-based pricing fundamentals) and lacks concrete worked examples showing how to synthesize gathered information into specific pricing recommendations. The checklists and frameworks are useful but would benefit from example outputs.

Suggestions

Add a concrete worked example showing a complete pricing recommendation output—e.g., given a specific SaaS product context, show the recommended tier structure, price points, and rationale.

Remove explanations of well-known concepts (value-based pricing definition, pricing psychology basics like anchoring/charm pricing) and replace with specific heuristics or decision rules Claude wouldn't already know.

Add a clear end-to-end workflow: 'Gather context → Identify value metric → Design tiers → Set price points → Validate against checklist → Present recommendation' with explicit validation steps between stages.

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, listing common pricing psychology concepts like anchoring and charm pricing). However, the tables and checklists are reasonably efficient, and the structure avoids extreme verbosity.	2 / 3
Actionability	The skill provides structured frameworks (Good-Better-Best, Van Westendorp questions, checklists) but lacks concrete, executable examples. There are no specific worked examples showing how to apply these frameworks to a real scenario—e.g., 'Given X product with Y metrics, here's how to structure pricing.' The guidance is more conceptual than copy-paste actionable.	2 / 3
Workflow Clarity	The 'Before Starting' section provides a clear information-gathering sequence, and the checklists provide some structure. However, there's no clear end-to-end workflow showing how to go from gathered context to a pricing recommendation, and no validation checkpoints (e.g., 'validate your tier structure against these criteria before presenting').	2 / 3
Progressive Disclosure	The skill appropriately references deeper content via one-level-deep links (references/tier-structure.md, references/research-methods.md) and includes a well-organized Related Skills section. The main content serves as a clear overview without being monolithic, and navigation is well-signaled.	3 / 3
	Total	9 / 12 Passed

Validation

100%

Warnings & errors only

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.

Repository: coreyhaines31/marketingskills
Commit: 2c7c108

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.