CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pricing-strategist

Use when designing or revisiting product pricing — selecting a pricing model (subscription seat-based, usage-based, value-based, freemium, or hybrid), running Van Westendorp Price Sensitivity Meter analysis on WTP survey data, or designing Good/Better/Best packaging tiers. Recommends a model and a price range with trade-offs, never a single number. For Commercial leads, Product Marketing, and CMOs at the pricing-design moment — not deal-by-deal discounting, not brand positioning.

71

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

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

A strong, highly actionable skill body with executable commands, deterministic decision logic, and a well-organized bundle whose referenced files all exist. The main improvements are consolidating the repeatedly restated guardrails and moving the forcing-question library into a reference file, plus adding explicit validation checkpoints between workflow steps.

Suggestions

State the 'model + range, never a single number' guardrail once (e.g., in Assumptions) and remove its repetitions in Purpose, Step 3, and Step 5; likewise merge the deal-dek/distinct-from disambiguation into a single section.

Move the forcing-question library to a reference file (e.g., references/forcing_questions.md) and keep a one-line pointer plus the walk discipline in SKILL.md, mirroring how the other references are handled.

Add explicit validation checkpoints after Steps 2–4 (e.g., 'if the top two model fit scores are within 10 points, revisit the brief's consumption-pattern data before proceeding' or 'if the PSM range is degenerate or N < 30, flag and stop').

DimensionReasoningScore

Conciseness

The body is dense and actionable with no filler explaining concepts Claude already knows, but the core guardrail ('model + range, never the number') is repeated in Purpose, Step 3, Step 5, and Assumptions, and the deal-desk distinction appears three times ('Do not use for', 'Anti-patterns', 'Distinct from') — slightly more trimming opportunity than the 'minor instances' of anchor 4, yet well short of the padding of anchor 3.

4 / 5

Actionability

Fully executable guidance throughout: exact CLI invocations with flags for all three scripts ('scripts/pricing_model_picker.py --input brief.json --profile saas --output markdown'), explicit input requirements ('≥ 4 questions per respondent: too cheap / bargain / getting expensive / too expensive'), and a copy-paste-ready '--sample' quick example covering the common case.

5 / 5

Workflow Clarity

A clear 5-step sequence with exact commands and ordering discipline ('Run pricing_model_picker first', 'Lock 1-3 before opening 4-6'), and script warnings are surfaced ('Below 30, the script emits a sample-size warning' — 'respect the warning'). It falls short of anchor 5 because there are no explicit validate-and-branch checkpoints after each step (e.g., what to do if fit scores are close or PSM range is degenerate).

4 / 5

Progressive Disclosure

Good structure: a dedicated Scripts section, a References section with one-line descriptions, contextual citations in the workflow, and all seven bundle files (3 scripts, 3 references, 1 asset) exist and are one level deep. Minor gaps: the ~30-line forcing-question library and parts of the anti-pattern list duplicate content belonging in references/packaging_anti_patterns.md and could be split out.

4 / 5

Total

17

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: concrete capabilities, an explicit 'Use when' trigger clause, third-person voice, a stated output contract, and explicit boundary exclusions. The only gap is a few natural layperson synonyms that would improve trigger recall.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'selecting a pricing model (subscription seat-based, usage-based, value-based, freemium, or hybrid)', 'running Van Westendorp Price Sensitivity Meter analysis on WTP survey data', 'designing Good/Better/Best packaging tiers' — plus an explicit output contract ('Recommends a model and a price range with trade-offs, never a single number') in third-person voice, giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

It explicitly answers 'when' ('Use when designing or revisiting product pricing') with concrete trigger conditions and answers 'what' ('Recommends a model and a price range with trade-offs, never a single number'), plus audience and explicit exclusions — matching the top anchor rather than the weaker-'when' anchor 4.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('product pricing', 'pricing model', 'WTP survey data', 'packaging tiers', 'discounting'), but common layperson phrasings like 'how much should we charge', 'monetization', or 'price points' are missing, so it falls just short of the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

A clear niche is staked out ('the pricing-design moment — not deal-by-deal discounting, not brand positioning') with named neighboring skills excluded, minimizing risk of triggering the wrong skill.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

Total

15

/

16

Passed

Repository

alirezarezvani/claude-skills

Path

commercial/skills/pricing-strategist/SKILL.md

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.