CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

—

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/pricing-strategy/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a moderately well-structured pricing strategy skill that covers broad ground but suffers from being too encyclopedic rather than actionable. It explains many concepts Claude already knows (value-based pricing, anchoring, charm pricing) rather than focusing on specific deliverable formats and decision frameworks. The referenced bundle files don't exist, undermining the progressive disclosure structure.

Suggestions

Add concrete output examples — show what a completed pricing recommendation or tier structure deliverable looks like (e.g., a sample markdown output with specific tiers, prices, and rationale).

Remove explanations of concepts Claude already knows (pricing psychology basics, what a value metric is) and replace with decision rules or heuristics specific to this skill's approach.

Create the referenced bundle files (references/tier-structure.md and references/research-methods.md) and move detailed content like the Van Westendorp method explanation and pricing page best practices into them.

Add an explicit workflow with validation steps: e.g., 'After proposing tiers, validate by checking: Does each tier map to a distinct persona? Is there clear upgrade motivation between tiers? Does the value metric scale with usage?'

DimensionReasoningScore

Conciseness

The skill contains some unnecessary explanations of concepts Claude already knows (e.g., explaining what a value metric is, basic pricing psychology concepts like anchoring and decoy effect). The tables and frameworks are useful but could be tightened. Some sections like 'Pricing Fundamentals' explain basic concepts that Claude would already understand.

2 / 3

Actionability

The skill provides frameworks and checklists but lacks concrete, executable outputs. There are no specific examples of deliverables (e.g., a sample pricing recommendation document, a completed tier structure). The guidance is more conceptual/strategic than copy-paste actionable, though the checklists and structured questions add some concreteness.

2 / 3

Workflow Clarity

There's a reasonable sequence implied (gather context → analyze → recommend) and the 'Before Starting' section establishes an initial workflow. However, there's no explicit multi-step process with validation checkpoints. The pricing checklist helps but doesn't define a clear workflow with feedback loops for iterating on pricing decisions.

2 / 3

Progressive Disclosure

The skill references two external files (references/tier-structure.md and references/research-methods.md) which is good progressive disclosure design, but no bundle files were provided, meaning these references are broken. The main file itself is quite long (~180 lines of content) with several sections that could be offloaded to reference files (e.g., pricing psychology, pricing page best practices).

2 / 3

Total

8

/

12

Passed

Description

89%Scale 1-3

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 abstract—listing topic areas rather than 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 willingness-to-pay scenarios, recommends freemium vs. free trial strategies, and evaluates price increase impact.'

DimensionReasoningScore

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

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
TheCraigHewitt/seomachine
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.