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?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./config/claude/skills/pricing-strategy/SKILL.md
SKILL.md
Quality
Evals
Security

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 clear 'when to use' guidance. Its main weakness is that the 'what it does' portion is somewhat high-level, describing topic areas rather than specific concrete actions the skill performs. The extensive list of trigger terms and explicit use-when clause make it highly effective for skill selection.

Suggestions

Replace the general topic summary ('pricing research, tier structure, and packaging strategy') with specific concrete actions like 'Designs pricing tiers, conducts Van Westendorp analysis, recommends value metrics, evaluates freemium vs. free trial models, and plans price increase strategies.'

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,' 'conducts Van Westendorp analysis,' 'recommends value metrics').

2 / 3

Completeness

Clearly answers both 'what' (pricing research, tier structure, packaging strategy, monetization) and 'when' (explicit 'Use when' clause with detailed trigger terms and scenarios). The 'when' guidance is particularly strong with its enumerated trigger terms.

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,' 'willingness to pay,' and 'freemium' that are unlikely to conflict with other skills.

3 / 3

Total

11

/

12

Passed

Implementation

50%

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 verbosity and lack of concrete deliverables. It explains many concepts Claude already knows (pricing psychology, value metrics basics) rather than focusing on novel, actionable frameworks. The referenced bundle files don't exist, weakening the progressive disclosure structure.

Suggestions

Add concrete example outputs—e.g., a sample tier structure table, a sample pricing recommendation memo, or a completed Van Westendorp analysis—so Claude knows exactly what deliverable to produce.

Remove explanations of well-known concepts (anchoring, decoy effect, what a value metric is) and replace with terse decision rules or heuristics that add novel value.

Add explicit validation steps to the workflow, such as 'Cross-check proposed price points against competitor data and willingness-to-pay research before recommending' with a feedback loop.

Either provide the referenced bundle files (references/tier-structure.md, references/research-methods.md) or inline the critical content and remove the broken references.

DimensionReasoningScore

Conciseness

The skill contains some unnecessary explanations of concepts Claude already knows (e.g., explaining what a value metric is, defining 'Good-Better-Best' framework basics, explaining pricing psychology concepts like anchoring and decoy effect). However, the tables and checklists are reasonably efficient. Could be tightened significantly.

2 / 3

Actionability

The skill provides structured frameworks, checklists, and tables which are useful, but lacks concrete executable examples—no sample pricing models, no template outputs, no example deliverables showing what a completed pricing analysis looks like. It describes concepts rather than providing copy-paste-ready artifacts.

2 / 3

Workflow Clarity

There's a logical flow from gathering context → fundamentals → research → implementation, and the checklist provides sequencing. However, there are no explicit validation checkpoints or feedback loops—e.g., no step to validate pricing against research data before finalizing, no iteration cycle for testing assumptions.

2 / 3

Progressive Disclosure

References to 'references/tier-structure.md' and 'references/research-methods.md' are well-signaled, but no bundle files were provided, so these references are broken. The main file itself is quite long (~200 lines) with content that could be offloaded (e.g., the full Van Westendorp explanation, pricing page best practices, pricing psychology).

2 / 3

Total

8

/

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.

Validation10 / 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
freekmurze/dotfiles
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.