How do I install the Pricing Page skill?

Run npx skillmds@latest add mphinance/pricing-page in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pricing Page safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pricing Page?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pricing Page free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Pricing Page?

mphinance (@mphinance) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pricing Page by mphinance — Agent Skill

Name: Pricing Page
Author: mphinance

File contents

Pricing Page Skill

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

Workflow

Read the active DESIGN.md (injected above). Use only its colors, type tokens, and component patterns.
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:
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.
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 currency and "/mo" — sizes per DESIGN.md scale.
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.

---name: pricing-pagedescription: 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.---# Pricing Page SkillProduce a single-screen pricing page that respects the active DESIGN.md.## Workflow1. **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 contractEmit 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.

Frequently asked questions

Pricing Page