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

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Quality

Content

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

The body is a well-structured, highly actionable pricing playbook that makes good use of progressive disclosure via real reference files and a script. The main weakness is mild verbosity in the introductory framing and a decorative diagram, plus the absence of explicit validation checkpoints in the design and optimize modes.

Suggestions

Trim the editorializing intro paragraph and the ASCII 'Three Pricing Axes' diagram; replace with a one-line framing so the body leads with actionable content.

Add explicit validation/gate checkpoints to Mode 1 (Design) and Mode 2 (Optimize) — e.g., a 'sanity-check the metric against the 4 red flags before locking packaging' step — mirroring the go/no-go gate already present in Mode 3.

Specify how to invoke scripts/pricing_modeler.py (expected inputs/flags and a sample invocation) so the 'Model pricing scenarios' artifact is copy-paste ready rather than directional.

Dimension	Reasoning	Score
Conciseness	The body is dense with scannable tables and checklists and assumes Claude's baseline knowledge (no 'what is SaaS' padding), but the editorializing intro ('Pricing is not math — it's positioning…') and the decorative ASCII axes diagram are tokens that don't each earn their place.	4 / 5
Actionability	Concrete, specific guidance throughout — numeric thresholds ('60-90 days notice', '20-30% price increase → 5-15% churn'), copy-paste Van Westendorp questions, pricing-page must-haves, an output-artifacts request→deliverable map, and a referenced executable script — fully actionable for an instruction-only skill.	5 / 5
Workflow Clarity	The price-increase mode has an explicit 7-step checklist with a go/no-go gate ('If your net revenue impact is positive, proceed') and a 60-day monitoring feedback loop, but the design-from-scratch and optimize modes are topic orderings without explicit validation checkpoints, leaving a minor gap.	4 / 5
Progressive Disclosure	The body is an overview that points to verified, clearly-signaled one-level-deep bundle files — references/pricing-models.md, references/pricing-page-playbook.md, and scripts/pricing_modeler.py — each introduced with its purpose, with detail appropriately split out.	5 / 5
	Total	18 / 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.

The description is exemplary: it states concrete capabilities, supplies a rich set of natural trigger keywords, answers both what and when explicitly, and carves out a distinct niche with explicit negative boundary guidance. No meaningful improvements needed.

Dimension	Reasoning	Score
Specificity	Three concrete verbs ('Design, optimize, and communicate') paired with four named sub-domains (tier structure, value metrics, pricing pages, price increase strategy) give comprehensive, non-abstract coverage; third-person imperative voice avoids any person penalty.	5 / 5
Completeness	The first sentence answers 'what' concretely and the 'Use when building… redesigning… planning… improving…' clause answers 'when' with concrete trigger phrases, satisfying both halves explicitly.	5 / 5
Trigger Term Quality	An explicit 'Trigger keywords:' list supplies ~13 natural terms a user would actually say, including synonyms and variants (per seat pricing, usage-based pricing, freemium, good-better-best, Van Westendorp).	5 / 5
Distinctiveness Conflict Risk	A clear SaaS-pricing niche is reinforced by two explicit boundary clauses ('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

100%

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

Validation for skill structure

No warnings or errors.

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

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