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.

63

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/pricing-strategist/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

60%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-organized, operational body with a clear five-step workflow, but it is a storefront for a bundle that is not there: every script, reference, and template the workflow depends on is missing, which breaks both navigation and actual executability. The written guidance is otherwise concrete and mostly token-efficient, aside from repeated boundary mantras.

Suggestions

Ship the bundle or remove the dependencies: the three scripts, the three references/*.md files, and assets/pricing_brief_template.md referenced throughout do not exist in the skill directory — either include them or drop the references (progressive_disclosure).

Add a script-free fallback for Steps 2-4: the workflow is entirely script-driven, so inline the deterministic decision rules already present in the forcing-question library (e.g., "variance > 10x → usage-based wins; variance < 3x → subscription wins") so the workflow survives a missing script (actionability).

De-duplicate the boundary mantras: the "recommends a range, never a single number" principle appears in Purpose, Step 3, Step 5, Assumptions, and Anti-patterns, and the deal-desk distinction appears three times — consolidate each into a single section (conciseness).

DimensionReasoningScore

Conciseness

The body is operational and skill-specific (script invocations, "variance > 10x → usage-based wins" heuristics, an anti-pattern catalog) with no explanation of concepts Claude already knows. Not 5: the "range, not a single number" principle is repeated in Purpose, Step 3, Step 5, Assumptions, and Anti-patterns, and the deal-desk boundary appears three times (When to use, Anti-patterns, Distinct from) — trimmable redundancy.

4 / 5

Actionability

Commands are concrete with full flags ("pricing_model_picker.py --input brief.json --profile saas --output markdown", "--help and --sample work on all three") plus deterministic decision logic. However, the executable core is absent from the bundle: none of the referenced scripts, reference docs, or the brief template exist, so no command can actually run — complete as written but missing the implementation it depends on, which is the anchor-3 condition.

3 / 5

Workflow Clarity

Five clearly sequenced steps with per-step inputs/outputs, a conditional branch ("If you have survey data"), and script-emitted checkpoints ("Below 30, the script emits a sample-size warning", anti-pattern flags). Not 5: there is no fix/retry guidance when a checkpoint fires, and the sequence cannot be executed end-to-end because the scripts are missing. Not 3: checkpoints are explicit, not implicit.

4 / 5

Progressive Disclosure

The body signals references well (Scripts and References sections with one-line descriptions, one level deep), but the bundle contains only SKILL.md — scripts/pricing_model_picker.py, scripts/wtp_analyzer.py, scripts/packaging_designer.py, references/saas_pricing_canon.md, references/van_westendorp_methodology.md, references/packaging_anti_patterns.md, and assets/pricing_brief_template.md all do not exist. Navigation to every referenced path fails, so the disclosure structure is nominal and the skill ships as an incomplete monolith. Not 1: the SKILL.md itself is well-sectioned and references are clearly signaled, not buried.

2 / 5

Total

13

/

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.

Strong description: explicit use-when triggers, enumerated concrete capabilities in third person, and explicit negative triggers that bound the niche against adjacent skills. The only weakness is a few missing natural synonyms (e.g., monetization, tiered pricing) in the trigger vocabulary.

DimensionReasoningScore

Specificity

Quotes: "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", "Recommends a model and a price range with trade-offs, never a single number". Multiple concrete actions comprehensively cover the skill's three functions, in third-person voice. Not 4: coverage spans model selection, WTP analysis, and packaging with no gaps.

5 / 5

Completeness

"Use when designing or revisiting product pricing" explicitly answers when, and the enumerated action list (model selection, PSM analysis, tier design, "Recommends a model and a price range") explicitly answers what; negative triggers ("not deal-by-deal discounting, not brand positioning") sharpen the when. Both present with concrete trigger phrases, matching the anchor-5 example structure.

5 / 5

Trigger Term Quality

Natural terms present: "product pricing", "pricing model", "freemium", "usage-based", "WTP survey data", "packaging tiers", "Good/Better/Best". Not 5: a few natural phrases users would say are missing ("monetization", "how much should we charge", "tiered pricing", "price increase"). Not 3: coverage goes beyond generic domain terms into enumerated model names and packaging vocabulary.

4 / 5

Distinctiveness Conflict Risk

Clear niche (pricing-model design "at the pricing-design moment") with distinct technical triggers (Van Westendorp PSM, WTP, Good/Better/Best) and explicit carve-outs from adjacent functions. Not 4: the description itself names what it is not ("not deal-by-deal discounting, not brand positioning"), minimizing overlap risk with the closest neighboring skills.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

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

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.