Name: pricing-strategist
Rating: 69.6 (1 reviews)
Author: alirezarezvani

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.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

The canonical home for this skill is pricing-strategist in alirezarezvani/claude-skills

Quality

Content

78%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.

An actionable, well-sequenced skill body with concrete CLI commands and strong guardrails, weakened mainly by the absence of the referenced bundle files and some repetition of the 'range not number' message.

Suggestions

Ship the referenced bundle files (scripts/pricing_model_picker.py, scripts/wtp_analyzer.py, scripts/packaging_designer.py, references/*.md, assets/pricing_brief_template.md) so the signaled progressive-disclosure structure actually exists.

Consolidate the repeated 'model + range, never a single number' statement into a single authoritative spot (Purpose or Anti-patterns) and reference it rather than restating it in Step 5, Assumptions, and Anti-patterns.

Add an explicit validate→fix→retry loop for the PSM sample-size warning (e.g. 'if N<30, expand the sample or fall back to a conjoint/qualitative range; do not proceed on a noisy range') to lift workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, but the 'model + range, never a single number' message recurs across Purpose, Step 5, Assumptions, and Anti-patterns, which could be consolidated to trim tokens.	4 / 5
Actionability	Every step gives a copy-pasteable, fully-flagged command (e.g. `scripts/wtp_analyzer.py --input survey.json --output markdown`) with the expected output artifacts described, covering the common cases.	5 / 5
Workflow Clarity	A clear five-step sequence with a depth-first forcing-question ordering and a sample-size guardrail (N<30 warning) is present; it falls short of 5 only because explicit validate→fix→retry feedback loops are implied rather than spelled out.	4 / 5
Progressive Disclosure	References to assets/, scripts/, and references/ paths are clearly signaled one level deep in prose, but the referenced bundle directories do not exist, so the structure is not actually materialized for navigation.	3 / 5
	Total	16 / 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.

A precise, third-person description that explicitly covers what it does, when to use it, and what it deliberately avoids. The only minor gap is slightly jargon-heavy trigger vocabulary that misses a few lay synonyms.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — selecting among five named pricing models, running Van Westendorp PSM on WTP data, and designing Good/Better/Best tiers — plus the explicit 'recommends a model and a price range with trade-offs, never a single number' output behavior, giving comprehensive coverage.	5 / 5
Completeness	An explicit 'Use when...' clause gives the trigger, the 'Recommends a model and a price range' clause gives the what, and the 'For Commercial leads... at the pricing-design moment — not deal-by-deal discounting, not brand positioning' clause pins the audience and boundaries.	5 / 5
Trigger Term Quality	Natural terms like 'designing or revisiting product pricing', 'pricing model', 'Good/Better/Best packaging tiers', and 'Van Westendorp' map well to what a pricing-design user would say, though it leans specialized and omits a few lay synonyms like 'how much to charge' or 'price points'.	4 / 5
Distinctiveness Conflict Risk	A narrow niche (pricing-model selection, PSM, tier packaging) combined with explicit negative boundaries against deal-desk, brand positioning, and revenue strategy keeps conflict risk minimal.	5 / 5
	Total	19 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 12 missing	Warning

	Total	14 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: .gemini/skills/pricing-strategist/SKILL.md
Commit: 19392f7

Reviewed: ~12 hours 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.