Source profileQuality 90/100

OpenClaudia/openclaudia-skills/skills/pricing-strategy/SKILL.md

pricing-strategy

Optimize pricing pages, pricing models, and pricing strategy. Use when the user asks about pricing, pricing pages, how to price a product, tiered pricing, freemium vs. paid, price testing, pricing psychology, or pricing page design. Trigger phrases include "pricing", "pricing page", "how to price", "pricing strategy", "freemium", "tiered pricing", "per-seat pricing", "usage-based pricing", "pricing experiment", "price anchoring", "pricing psychology", "pricing optimization".

Source repository stars
662
Declared platforms
0
Static risk flags
0
Last source update
2026-08-24
Source checked
2026-08-25

Decision brief

What it does: where it fits

You are an expert pricing strategist. When the user asks you to design pricing, optimize a pricing page, or advise on pricing decisions, follow this framework.

Best for

  • Use when the user asks about pricing, pricing pages, how to price a product, tiered pricing, freemium vs.

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/OpenClaudia/openclaudia-skills --skill "skills/pricing-strategy"
Safe inspection promptEditorial

Inspect the Agent Skill "pricing-strategy" from https://github.com/OpenClaudia/openclaudia-skills/blob/6b91665a5ab7d36599a605df17dae3e27d5ab242/skills/pricing-strategy/SKILL.md at commit 6b91665a5ab7d36599a605df17dae3e27d5ab242. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    Step 1: Gather Context

    Establish: product/service, target market (B2B/B2C/SMB/enterprise), current pricing, cost structure (COGS, marginal cost), value delivered, competitive pricing, current conversion metrics, revenue model, stage (pre-launch/early/growth/scale).

    Establish: product/service, target market (B2B/B2C/SMB/enterprise), current pricing, cost structure (COGS, marginal cost), value delivered, competitive pricing, current conversion metrics, revenue model, stage (pre-laun…
  2. 02

    Step 2: Pricing Model Selection

    Decision tree: Low marginal cost + viral - Freemium. Needs demo time - Free trial (14d simple, 30d complex). Scales with team - Per-seat. Scales with consumption - Usage-based. Distinct segments - Tiered (3 tiers).

    Decision tree: Low marginal cost + viral - Freemium. Needs demo time - Free trial (14d simple, 30d complex). Scales with team - Per-seat. Scales with consumption - Usage-based. Distinct segments - Tiered (3 tiers).
  3. 03

    Step 3: Pricing Psychology

    Show highest tier first, compare to alternatives ("vs. hiring at $80K/year"), compare to outcome value ("Generates $10K savings. Costs $99/month").

    Show highest tier first, compare to alternatives ("vs. hiring at $80K/year"), compare to outcome value ("Generates $10K savings. Costs $99/month").Add a plan that makes the target plan look obviously better. Example: Basic $9 (5 users), Plus $25 (10 users, DECOY), Pro $29 (25 users, TARGET).$99 feels cheaper than $100. Use .99 for consumer/SMB, round numbers for enterprise/premium.
  4. 04

    4. Center-Stage Effect

    People choose the middle of 3 options. Make your target plan the middle tier and highlight it.

    People choose the middle of 3 options. Make your target plan the middle tier and highlight it.
  5. 05

    Step 4: Tier Design

    1. Core value in all tiers -- never gate the primary use case 2. Gate on scale (seats, storage, API calls), not core features 3. Gate on admin/governance (SSO, RBAC, audit logs) for enterprise 4. Gate on support level (email < chat < priority < dedicated) 5. Never gate basic sec…

    Core value in all tiers -- never gate the primary use caseGate on scale (seats, storage, API calls), not core featuresGate on admin/governance (SSO, RBAC, audit logs) for enterprise

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score90/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars662SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
OpenClaudia/openclaudia-skills
Skill path
skills/pricing-strategy/SKILL.md
Commit
6b91665a5ab7d36599a605df17dae3e27d5ab242
License
MIT
Collected
2026-08-25
Default branch
main
View the original SKILL.md

Pricing Strategy and Page Optimization

You are an expert pricing strategist. When the user asks you to design pricing, optimize a pricing page, or advise on pricing decisions, follow this framework.

Step 1: Gather Context

Establish: product/service, target market (B2B/B2C/SMB/enterprise), current pricing, cost structure (COGS, marginal cost), value delivered, competitive pricing, current conversion metrics, revenue model, stage (pre-launch/early/growth/scale).

Step 2: Pricing Model Selection

ModelBest ForProsCons
FreemiumViral/network effects, low marginal costLarge funnel, PLGLow conversion (2-5%)
Free Trial (time)Products needing time to show valueCreates urgency, 10-25% conversionRequires strong onboarding
Flat RateSimple products, single personaEasy to understandLeaves money on table
Per-SeatCollaboration toolsScales with adoptionDiscourages spreading
Usage-BasedAPI, infrastructureAligns with valueUnpredictable revenue
TieredMost SaaS, distinct segmentsCaptures different WTPCan overwhelm
HybridMature platformsPredictable + upsideComplex

Decision tree: Low marginal cost + viral -> Freemium. Needs demo time -> Free trial (14d simple, 30d complex). Scales with team -> Per-seat. Scales with consumption -> Usage-based. Distinct segments -> Tiered (3 tiers).

Step 3: Pricing Psychology

1. Price Anchoring

Show highest tier first, compare to alternatives ("vs. hiring at $80K/year"), compare to outcome value ("Generates $10K savings. Costs $99/month").

2. Decoy Effect

Add a plan that makes the target plan look obviously better. Example: Basic $9 (5 users), Plus $25 (10 users, DECOY), Pro $29 (25 users, TARGET).

3. Charm Pricing

$99 feels cheaper than $100. Use .99 for consumer/SMB, round numbers for enterprise/premium.

4. Center-Stage Effect

People choose the middle of 3 options. Make your target plan the middle tier and highlight it.

5. Loss Aversion

Frame around what they lose without your product. Use "downgrade" language. Show features they would lose.

6. Endowment Effect

Full-featured trials, then keep. Show personalized data that makes leaving painful.

7. Price-Quality Signal

Premium products should not underprice. Own higher prices: "We cost more because we deliver more."

Step 4: Tier Design

3-Tier Framework

TIER 1 (STARTER): Acquisition. Low/no cost. Enough value to demonstrate product.
  Natural upgrade triggers (usage limits, feature gates).

TIER 2 (PRO - TARGET): Revenue engine. Everything most customers need.
  Best value perception. Highlight "Most Popular." Price: 2-4x Tier 1.

TIER 3 (ENTERPRISE): Capture high WTP. SSO, audit logs, SLAs, dedicated support.
  Custom pricing, sales-assisted. Price: 2-5x Tier 2.

Feature Gating Rules

  1. Core value in all tiers -- never gate the primary use case
  2. Gate on scale (seats, storage, API calls), not core features
  3. Gate on admin/governance (SSO, RBAC, audit logs) for enterprise
  4. Gate on support level (email < chat < priority < dedicated)
  5. Never gate basic security
  6. Create natural upgrade triggers during normal usage

Step 5: Pricing Page Design

3-Column Layout

+------------------+---------------------+------------------+
|    STARTER       |    PROFESSIONAL     |    ENTERPRISE    |
|    $19/mo        |    $49/mo           |    Contact Sales |
|                  |   * MOST POPULAR *  |                  |
|  [Start Free]    |  [Start Free Trial] |  [Talk to Sales] |
|  Feature list    |  Everything in      |  Everything in   |
|                  |  Starter, plus:     |  Pro, plus:      |
+------------------+---------------------+------------------+

Page Elements (Top to Bottom)

  1. Headline: Value-focused ("Simple pricing that scales with you"), not just "Pricing"
  2. Billing toggle: Monthly/Annual with savings shown as % and $
  3. Tier cards: Highlighted middle tier, checkmarks/dashes for features
  4. Feature comparison table: Expandable, grouped by category
  5. Social proof: Logos, testimonials addressing pricing objections
  6. FAQ: Can I switch plans? What happens after trial? Discounts? Refunds? Cancel anytime?
  7. Final CTA: Repeat with value message

Design Rules

Mobile: stack vertically, most popular first. Price font 2-3x larger. Show per-month price even for annual. CTA buttons same style, different weight for target tier.

Step 6: Competitive Pricing Analysis

PREMIUM (10-30% above): Superior product, strong brand. Requires differentiation.
MARKET (within 10%): Feature parity. Requires non-price differentiators.
PENETRATION (20-40% below): New entrant. Risk of low quality perception.
VALUE-BASED (disconnected): Unique category, measurable ROI. Requires proof.

Map competitors: entry price, mid tier, enterprise, model type. Identify gaps and positioning implications.

Step 7: Pricing A/B Tests

Test 1: Price Point -- Raise Pro from $49 to $59. Measure revenue per visitor. Test 2: Annual Default -- Default to annual toggle. Measure 90-day LTV. Test 3: Tier Count -- 4 tiers to 3. Measure conversion rate. Test 4: Feature Gating -- Move feature from Enterprise to Pro. Measure plan distribution + revenue. Test 5: Social Proof -- Add logos/testimonials to pricing page. Measure conversion.

Safety Rules

Never show different prices to same user on repeat visits. Only test on new visitors. Run 30+ days. Track downstream (churn, LTV). Grandfather existing customers.

Step 8: Pricing Page Audit Checklist

Clarity: Plans understood in 30s? Price prominent? Billing period clear? No jargon? Value: Headline communicates value? "Most Popular" indicator? Target plan emphasized? Trust: Logos/testimonials? Guarantee/trial? FAQ covers top objections? Conversion: CTA specific? Low-commitment option? No credit card for trial? Clear upgrade path? Mobile: Tiers stack well? Table usable? CTAs thumb-friendly?

Output Format

PRICING STRATEGY RECOMMENDATION
================================
RECOMMENDED MODEL: [type] | RATIONALE: [why]
TIER STRUCTURE: [names, prices, features, CTAs]
PRICING PAGE WIREFRAME: [section-by-section layout]
PSYCHOLOGY TACTICS: [techniques and placement]
A/B TEST ROADMAP: [prioritized experiments]
COMPETITIVE CONTEXT: [positioning vs. alternatives]
RISKS AND MITIGATIONS: [downsides and how to address]

Show math behind price points when possible. Tie recommendations to specific business context.

Frequently asked questions

What to verify before installation and use

What does the pricing-strategy source document cover?

You are an expert pricing strategist. When the user asks you to design pricing, optimize a pricing page, or advise on pricing decisions, follow this framework.

How do I install pricing-strategy?

The source record exposes this install command: npx skills add https://github.com/OpenClaudia/openclaudia-skills --skill "skills/pricing-strategy". Inspect the command and pinned source before running it.

Alternatives

Compare before choosing

Computed 9224,921

alirezarezvani/claude-skills

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 broade

Computed 10045,511

coreyhaines31/marketingskills

ab-testing

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program

Computed 10014,671

prowler-cloud/prowler

postgresql-indexing

PostgreSQL indexing best practices for Prowler: index design, partial indexes, partitioned table indexing, EXPLAIN ANALYZE validation, concurrent operations, monitoring, and maintenance. Trigger: When creating or modifying PostgreSQL indexes, analyzing query performance with EXPLAIN, debugging slow queries, reviewing index usage statistics, reindexing, dropping indexes, or working with partitioned table indexes. Also trigger when discussing index strategies, partial indexes, or index maintenance

Computed 1008

narrative-io/narrative-skills-marketplace

design-analysis

Translate a fuzzy analytical question into a rigorous investigation plan. Interrogates the ask, grounds the plan in the available data dictionary, applies analytical best practices, and produces a structured brief of query specifications for a downstream query-writing skill. Plans, does not write SQL. Use when: "why did X drop", "is there a relationship between A and B", "who are our highest-value customers", "what's driving the change in Y", "investigate this trend", "design an analysis for", "