SkillAgentSearch skills...

pricing-page

Use when designing or rewriting a high-converting SaaS pricing page (structure, plan design, copywriting, SEO/AEO, FAQs, layout patterns, experiments). Includes checklists, templates, and common pitfalls.

Install / Use

npx skills add MengTo/Skills --skill pricing-page

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

85/100

Supported Platforms

Universal

Our assessment of pricing-page

pricing-page scores 85/100 on our quality scale, 782nd of 1,153 Content & Media skills we index.

Its SKILL.md is 5.6 KB long, well organised into 33 sections and no code examples: a solid amount of guidance for an agent.

With 6,252 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
13/20
Description
15/15
Adoption
16/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so pricing-page is actively maintained.
  • Our last check on 2026-11-04 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-28. Automated pattern scan on 2026-09-28. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

pricing-page compared with similar skills

All 4 of these similar skills score higher than pricing-page; compare them before choosing.

SkillScoreStarsUpdatedFormat
pricing-page (this skill)by MengTo856.3k54d agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md
siyuanby siyuan-note10047.3ktodayMCP Server
x402by browser-use100121.0k3d agoSKILL.md

Frequently asked questions

How do I install pricing-page?
Run npx skills add MengTo/Skills --skill pricing-page. The install tabs above show the steps for each supported agent.
Which AI agents does pricing-page work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is pricing-page safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is pricing-page still maintained?
The repository was last updated about 2 months ago, so pricing-page is actively maintained.

name: pricing-page description: Use when designing or rewriting a high-converting SaaS pricing page (structure, plan design, copywriting, SEO/AEO, FAQs, layout patterns, experiments). Includes checklists, templates, and common pitfalls.

Pricing Page (High‑Conversion) — Web Design Skill

Design a pricing page that helps visitors choose and feel good about it. Your job is not to “show prices.” Your job is to reduce uncertainty.

Before you design/write

Gather (ask if missing):

1) Offer + audience

  • What are you selling? (category)
  • Who is it for? (ICP + primary use case)
  • What’s the main value metric? (seat, usage, project, revenue, etc.)

2) Plans

  • Plan names + prices (monthly/annual)
  • Limits per plan (the 3–6 limits that matter)
  • What’s the upgrade trigger? (what causes people to move up?)

3) Objections + risk

  • Top 3 reasons people don’t buy today
  • Security/compliance needs? (SOC2, GDPR, etc.)
  • Can you offer: free trial, free plan, money-back, demo?

4) Proof

  • Testimonials, logos, results, case studies, metrics

5) Traffic context

  • Are visitors coming from: homepage, feature pages, ads, comparison pages?
  • What do they already know?

Core structure (what a pricing page should have)

Above the fold (must)

  • Clear value headline (what outcome, for who)
  • Monthly/Annual toggle with annual savings callout
  • 3‑plan pricing table (most common) or 2‑plan (simple product)
  • Primary CTA per plan (consistent verbs)

Below the fold (high leverage)

  • Plan comparison (feature matrix or “what you get” bullets)
  • FAQ (objection handling)
  • Social proof near decision points
  • Security / compliance / procurement section (if B2B)
  • Final CTA + contact sales

Layout types (pick one)

A) Classic 3‑card

Best when:

  • you have 3 natural tiers (Starter / Pro / Business)
  • pricing is simple

Rules:

  • 1 plan labeled Recommended
  • show “most popular” without yelling

B) Value metric slider

Best when:

  • pricing scales with usage (seats, events, credits)

Rules:

  • keep math obvious
  • keep a safe default (median customer)

C) “Pick your path” (two columns)

Best when:

  • different audiences (Individuals vs Teams)

Rules:

  • separate by persona first, then price

D) Enterprise last mile

Best when:

  • you have a self-serve path + sales-led path

Rules:

  • Enterprise should read like procurement reassurance

High‑conversion strategies (practical)

1) Make the decision easy

  • 3 plans max (unless you have a strong reason)
  • One recommended plan
  • Bullets describe outcomes, not internal features

2) Anchor value (without being shady)

  • Annual toggle with “Save X%”
  • Show “Starting at” only if your pricing is truly variable
  • Avoid surprise fees

3) Reduce risk

Choose at least one:

  • Free trial
  • Free plan
  • Money‑back guarantee
  • “Talk to sales” with a clear promise (response time, demo)

4) Handle objections before they bounce

Most effective FAQ topics:

  • “Can I cancel anytime?”
  • “What happens if I hit limits?”
  • “Do you offer discounts?”
  • “Is this for freelancers/teams?”
  • “Security / data / compliance”

5) Provide a comparison that’s readable

  • Avoid huge spreadsheets
  • Group by: Core, Collaboration, Admin/Security, Support
  • Highlight what changes at each tier

Copywriting (templates)

Headlines (choose a formula)

  • “{Outcome} for {audience}—without {pain}”
  • “Plans that scale from {small} to {big}”
  • “Start small. Upgrade when {trigger}.”

Plan description (2 lines)

  • Who it’s for
  • What it unlocks

Example:

  • Pro — For designers shipping weekly. Better components, faster iteration.

CTA buttons

Rules:

  • Use verbs that match the motion:
    • “Start free trial”
    • “Buy Pro”
    • “Contact sales”
  • Keep CTAs consistent across plans (don’t mix “Get started” / “Try now” / “Sign up”).

Feature bullets (write like outcomes)

  • ❌ “Unlimited projects”
  • ✅ “Ship unlimited client sites without extra fees”

Pricing table checklist (UI)

  • Visible monthly/annual toggle
  • “Save X%” callout on annual
  • Recommended plan styling (subtle)
  • Key limits visible (3–6 max)
  • Included items visible (3–6 max)
  • Clear next step under each plan (trial/buy/contact)
  • Link: “Compare plans” (scrolls to matrix)
  • Mobile: table becomes stacked cards (not a horizontal scroll nightmare)

SEO + AEO (AI answers) checklist

SEO basics

  • Title: “Pricing — {Product}” + outcome keyword
  • Meta description: 1 sentence on value + 1 sentence on pricing starting point
  • Clean URL: /pricing
  • Internal links from:
    • homepage CTA
    • feature pages
    • comparison pages

AEO (answer engines)

  • Add an FAQ section that answers:
    • refund policy
    • trial length
    • cancellation
    • what counts as a seat/usage
    • enterprise procurement
  • Write FAQs in plain Q/A format.
  • Optional: FAQ schema (if your stack supports it).

Common pitfalls

  • Too many plans (analysis paralysis)
  • Features listed with no context (why it matters)
  • Pricing hidden behind “Contact sales” for everything
  • Switching value metric mid-page (confusing)
  • Over-designed table that harms readability

Output format (when generating a pricing page)

Return:

  1. Page outline (sections + order)
  2. Pricing table spec (plans, bullets, limits, CTA)
  3. FAQ list (6–12 Q/A)
  4. SEO/AEO (title + meta + FAQ schema suggestion)
  5. Layout recommendation (A/B/C/D + why)

Quick questions (if user gives you only “make a pricing page”)

  • Free plan or trial?
  • Monthly/annual pricing numbers?
  • Value metric?
  • Recommended plan (which one and why)?
  • Top 3 objections?

Related Skills

View on GitHub
GitHub Stars6.3k
CategoryContent
Updated1mo ago
Forks741

Languages

HTML

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions