agentsclimarketplace

Pricing page

Skill swd3k/skills/agent-skills/web-design/pricing-page

Portable agent skills for desktop apps, programming, UI, and web design - Codex, Claude, Cursor, Grok. English SKILL.md playbooks (Photino, Inno, CI, landings).

Install
npx -y skills add swd3k/skills --skill pricing-page

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 19 days oldThe repository was created 19 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Structure pricing pages with clear tiers, comparison, FAQs, and conversion-focused layout. Use when designing SaaS pricing or plan comparison sections.

SKILL.md

0.9 KB, as published. Nobody here has run it

Pricing Page

Goals

  • Help the buyer self-select a plan fast
  • Make the recommended plan obvious
  • Answer billing objections without sales call

Structure

  1. Headline + billing period toggle (monthly/yearly)
  2. 2–4 tiers max (most teams: Free/Pro/Business)
  3. Feature comparison table (progressive disclosure on mobile)
  4. FAQ (seats, taxes, refunds, limits)
  5. Final CTA

Tier cards

  • Name, price, who it's for
  • 4–7 bullets max on card; rest in table
  • Highlight one recommended tier
  • Primary CTA per card, same verb family

Honesty

  • No fake "most popular" without data intent
  • Limits clear (not only in ToS)

Acceptance

  • User can answer "which plan for me?" in 30 seconds

Gives 0 of the 12 instructions most pricing monetisation skills give

Counted across 366 of the 366 authors here whose files we hold, read 2026-08-06

  • verify webhook signaturesin 23 of 366, across 19 files
  • differentiate tiers using features, limits, or supportin 15 of 366, across 4 files
  • read product marketing context before asking questionsin 14 of 366, across 6 files
  • base price on perceived value, not costin 14 of 366, across 3 files
  • use Van Westendorp to find acceptable price rangein 14 of 366, across 3 files
  • use MaxDiff to identify highly valued featuresin 14 of 366, across 3 files
  • choose a value metric that scales with customer valuein 14 of 366, across 9 files
  • handle webhook events idempotentlyin 12 of 366, across 6 files
  • understand the upgrade context before recommendingin 11 of 366, across 4 files
  • align the pricing metric with delivered valuein 10 of 366, across 4 files
  • install stripe packagein 10 of 366, across 5 files
  • calculate unit economics metricsin 10 of 366, across 5 files

Said here and by no other author read

  • create two to four pricing tiers
  • add a billing FAQ section
  • list four to seven bullets per card
  • use consistent verbs for CTAs
  • state limits clearly outside the ToS

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.