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

pricing-strategy

Design, optimize, and communicate SaaS pricing — tier structure, value metrics, pricing pages, and price increase strategy. Use when building a pricing model from scratch, redesigning existing pricing, planning a price increase, or improving a pricing page. Trigger keywords: pricing tiers, pricing page, price increase, packaging, value metric, per seat pricing, usage-based pricing, freemium, good-better-best, pricing strategy, monetization, pricing page conversion, Van Westendorp. NOT for broader product strategy — use product-strategist for that. NOT for customer success or renewals — use customer-success-manager for expansion revenue.

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-strategy in alirezarezvani/claude-skills

Quality

Content

71%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 well-structured, actionable strategy skill with clear modes, concrete tables, and useful verification checkpoints, but it loses points because the referenced bundle files (references/pricing-models.md, references/pricing-page-playbook.md, scripts/pricing_modeler.py) are missing, breaking the progressive-disclosure navigation it promises.

Suggestions

Create the referenced bundle files (references/pricing-models.md, references/pricing-page-playbook.md, scripts/pricing_modeler.py) or remove the links so navigation does not dead-end.

Move the detailed tier feature grids and pricing-page copy/FAQ templates into the references and keep SKILL.md as a tighter overview to reduce inline bulk.

Add an explicit validate→fix→retry loop to the price-increase execution checklist (e.g., re-check churn/downgrade metrics weekly and roll back or adjust if net revenue impact turns negative).

Dimension	Reasoning	Score
Conciseness	Mostly efficient — concrete tables, heuristics, and specific numbers ("40% trial-to-paid", "5-15% churn", "60-90 days notice") with no padding of basics Claude already knows — but the ASCII packaging diagram and a few positioning aphorisms could be trimmed. Not a 5 because a handful of decorative/narrative tokens don't fully earn their place.	4 / 5
Actionability	Provides concrete, copy-paste-ready guidance: literal Van Westendorp survey questions, a tier feature grid, a pricing-page layout spec, and a numbered execution checklist. Not a 5 because the modeling workflow delegates to a referenced script that is not shown inline, leaving a minor gap in executable detail.	4 / 5
Workflow Clarity	Three modes are clearly framed and the price-increase flow has a sequenced 7-step Execution Checklist with verification/monitoring ("Monitor for 60 days: Churn rate, downgrade rate, support ticket volume") and a decision gate ("If your net revenue impact is positive, proceed"). Not a 5 because there is no explicit validate→fix→retry feedback loop for the batch customer-impacting operation.	4 / 5
Progressive Disclosure	Section structure and in-context reference signaling are good ("See [references/pricing-models.md] for model deep dives"), but the referenced bundle files and script do not exist — the links are dead ends — and substantial detail that could live in those files is inlined in one monolithic body.	3 / 5
	Total	15 / 20 Passed

Description

100%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 model description: it states concrete capabilities, gives explicit 'Use when' triggers with a rich keyword list, and disambiguates from neighboring skills with clear 'NOT for' boundaries. Voice is appropriately third-person/imperative with no first- or second-person drift.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("Design, optimize, and communicate SaaS pricing") tied to specific objects ("tier structure, value metrics, pricing pages, and price increase strategy"), giving comprehensive coverage of what the skill does.	5 / 5
Completeness	Explicitly answers both what ("Design, optimize, and communicate SaaS pricing...") and when ("Use when building a pricing model from scratch, redesigning existing pricing, planning a price increase, or improving a pricing page") with concrete trigger phrases.	5 / 5
Trigger Term Quality	An explicit, extensive keyword list ("pricing tiers, pricing page, price increase, packaging, value metric, per seat pricing, usage-based pricing, freemium, good-better-best, ... Van Westendorp") covers natural user phrases plus synonyms and jargon variants.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (SaaS pricing) and draws explicit boundaries with named alternatives ("NOT for broader product strategy — use product-strategist"; "NOT for customer success or renewals — use customer-success-manager"), minimizing wrong-skill triggering.	5 / 5
	Total	20 / 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
relative_links	Relative link issues: 2 missing	Warning
referenced_paths_exist	Referenced path issues: 5 missing	Warning

	Total	14 / 16 Passed

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

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