skills/pages/marketing/pricing/SKILL.md
When the user wants to create, optimize, or audit pricing page content and structure. Also use when the user mentions "pricing page," "pricing table," "plans," "subscription," "pricing plans," "pricing tiers," "pricing comparison," "SaaS pricing," "enterprise pricing," "API pricing," "contact sales," "pricing in nav," "public pricing," "hide pricing," or "pricing objection handling." For pricing strategy, use pricing-strategy.
npx skillsauth add kostja94/marketing-skills pricing-page-generatorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Guides pricing page content, structure, and conversion optimization. Covers self-serve plans, enterprise/contact sales, API/usage-based pricing, and special programs (startups, education).
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for product, audience, and pricing strategy.
Identify:
| Show public pricing | Hide (contact sales only) | |--------------------|---------------------------| | Self-serve / SMB; standard tiers | Enterprise; highly customized | | Competitive market; transparency differentiates | Premium positioning; consultative sales | | Simple pricing model | New category; value exceeds cost in prospect's mind | | 86% of B2B buyers want transparency; hidden pricing is a top deterrent | Custom deployments, SLA, volume; fixed price misleading |
Middle ground: "Starting from," price ranges, or calculator—clarity without rigid commitment.
| Location | Audience | Purpose | |----------|----------|---------| | Marketing site | Unlogged visitors | Acquisition; standalone /pricing page; main nav or footer | | In-app / Dashboard | Logged-in users | Subscription management; Settings → Billing/Subscription in sidebar; upgrade/downgrade, payment |
Marketing site = conversion; In-app billing = retention and plan management. Not all sites need public pricing in nav—enterprise-only products may use "Contact sales" as primary CTA.
| Model | Use | |-------|-----| | Subscription | Recurring; monthly/annual; most SaaS | | Freemium | Free tier + paid; adoption then conversion | | Usage-based | Pay per use; API calls, tokens, credits | | One-time | Perpetual license; some tools | | Hybrid | Base + usage; tiered + overage |
| Section | Purpose | |---------|---------| | Headline | Value-focused; "Simple pricing" or benefit-led | | Pricing model selector | Monthly/annual toggle; show annual savings (15–25%); usage-based calculator if applicable | | Plan comparison | Clear table or cards; feature comparison; "Best for" per tier | | Enterprise / Contact sales | Separate tier; "Contact us," "Custom pricing"; SLA, dedicated support; volume discount | | API / Usage pricing | If API product: token/request pricing; tiers (Standard/Flex/Batch); overage; link to /api or docs | | Special programs | Startups, education, nonprofit; link to startups-page or embed block | | FAQ | Billing, cancellation, refunds, API limits, enterprise | | Social proof | Testimonials, logos, "X companies trust us" | | CTA | Per plan or unified "Get started"; "Contact sales" for enterprise | | Guarantee | Money-back, free trial, no credit card | | Comparison | Brief price vs alternatives; link to alternatives-page |
| Scenario | Use | |----------|-----| | Enterprise | Separate tier; "Contact sales," "Custom pricing"; SLA, dedicated support, volume discount | | API / Usage-based | Token/request pricing; tier (Standard/Flex/Batch); overage; link to api-page or docs | | Hybrid | Base subscription + usage; show base + overage clearly |
data-ai
When the user wants to add or optimize Twitter Card metadata for X (Twitter) link previews. Also use when the user mentions "Twitter Card," "twitter:card," "twitter:image," "twitter:title," "X preview," or "tweet preview." For Facebook/LinkedIn previews, use open-graph.
testing
When the user wants to add or optimize Open Graph metadata for social sharing. Also use when the user mentions "Open Graph," "og:tags," "og:title," "og:image," "og:description," "Facebook preview," "LinkedIn preview," or "social share preview." For X (Twitter) link previews, use twitter-cards. For SERP title/description, use title-tag and meta-description.
tools
When the user wants to create, optimize, or structure Terms of Service page. Also use when the user mentions "terms of service," "terms and conditions," "terms of use," "user agreement," "ToS," "legal terms," "service agreement," or "terms page." For legal overview page, use legal-page-generator.
development
When the user wants to create or optimize a shipping or delivery information page. Also use when the user mentions "shipping," "delivery," "shipping policy," "delivery times," "shipping page," "free shipping," "shipping rates," "delivery options," "shipping info," "cross-border shipping," "international delivery," or "order tracking." For legal overview, use legal-page-generator.