Skip to main content
Agent skill

Pricing Page

A standalone pricing page — header, plan tiers, feature comparison table, and an FAQ. Use when the brief asks for "pricing", "plans", "subscription tiers", or a "compare plans" page.

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Pricing Page when an AI agent needs a reusable SKILL.md workflow for this job: A standalone pricing page — header, plan tiers, feature comparison table, and an FAQ. Use when the brief asks for "pricing", "plans", "subscription tiers", or a "compare plans" page.

When not to use it

Skip Pricing Page when the task is outside the creativity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/pricing-page
# Save SKILL.md to ~/.claude/skills/pricing-page/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/pricing-page/SKILL.md. For a shared project, commit the folder at .claude/skills/pricing-page/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Pricing Page skill for this task: Read the active DESIGN.md (injected above). Use only its colors, type. Confirm any required inputs or files before making changes.

What supports this recommendation?

74/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
82/100
Practical detail
74/100
Source evidence
63/100
Source signals
72/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# Pricing Page Skill

Produce a single-screen pricing page that respects the active DESIGN.md.

## Workflow

1. **Read the active DESIGN.md** (injected above). Use only its colors, type tokens, and component patterns. 2. **Classify** the product from the brief and pick a tier shape: - 3-tier (most common): Free / Pro / Team or Starter / Growth / Enterprise. - 4-tier when the brief says "scale" or "enterprise plus". - 2-tier when it says "individual / business" or "personal / pro". 3. **Sections**, in order: 1. **Hero** — page title (e.g. "Pricing"), one-line subhead, optional monthly/annual toggle. 2. **Plan cards** — one card per tier. Each card: tier name, price (use the display font + larger scale for the number), 1-line positioning, 4–6 bullet features, primary CTA. Mark the recommended tier with the DS accent border or a small badge. 3. **Comparison table** — feature rows × tier columns, ✓ / — / value cells. Group features into 2–3 logical sections (Core, Collaboration, Support, Security…). Sticky header. 4. **FAQ** — 4–6 collapsible Q&A items. Use `<details><summary>` for the collapse — no JS. 5. **Footer CTA** — single line + button, accent band sparingly. 4. **Write** one self-contained HTML document: - `<!doctype html>` through `</html>`, CSS in one inline `<style>`. - CSS Grid for the plan-card row; CSS Grid for the comparison table. - `data-od-id` on each tier card and each table row. 5. **Money rendering**: use the display font for the big number, body for the currency and "/mo" — sizes per DESIGN.md scale. 6. **Self-check**: - Prices are plausible for the product (not "$X / month"). - Accent is on the recommended tier and one CTA only. - Comparison table renders cleanly at 1024px and stacks readably below 768px (rotate column headers or scroll-x). - No fake feature names — every row reads as something a real product would actually offer.

## Output contract

Emit between `<artifact>` tags:

``` <artifact identifier="pricing-slug" type="text/html" title="Pricing — Product Name"> <!doctype html> <html>...</html> </artifact> ```

One sentence before the artifact, nothing after.

Intended uses

  • Read the active DESIGN.md (injected above). Use only its colors, type
  • Classify the product from the brief and pick a tier shape:
  • 3-tier (most common): Free / Pro / Team or Starter / Growth / Enterprise.
  • 4-tier when the brief says "scale" or "enterprise plus".
  • 2-tier when it says "individual / business" or "personal / pro".
  • Sections, in order:
  • Hero — page title (e.g. "Pricing"), one-line subhead, optional
  • Plan cards — one card per tier. Each card: tier name, price (use the
  • Comparison table — feature rows × tier columns, ✓ / — / value cells.
  • FAQ — 4–6 collapsible Q&A items. Use <details><summary> for the
  • Footer CTA — single line + button, accent band sparingly.
  • Write one self-contained HTML document:
  • <!doctype html> through </html>, CSS in one inline <style>.
  • CSS Grid for the plan-card row; CSS Grid for the comparison table.
  • data-od-id on each tier card and each table row.
  • Money rendering: use the display font for the big number, body for the
  • Self-check:
  • Prices are plausible for the product (not "$X / month").
  • Accent is on the recommended tier and one CTA only.
  • Comparison table renders cleanly at 1024px and stacks readably below

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.