Source profileQuality 73/100

nexu-io/open-design/design-templates/pricing-page/SKILL.md

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.

Source repository stars
82,073
Declared platforms
0
Static risk flags
0
Last source update
2026-07-28
Source checked
2026-07-28

Decision brief

What it does—and where it fits

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

Best for

  • Use when the brief asks for "pricing", "plans", "subscription tiers", or a "compare plans" page.

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/nexu-io/open-design --skill "design-templates/pricing-page"
Safe inspection promptEditorial

Inspect the Agent Skill "pricing-page" from https://github.com/nexu-io/open-design/blob/89d6d4ef21baf80f871595abdf6f7de6e941dd44/design-templates/pricing-page/SKILL.md at commit 89d6d4ef21baf80f871595abdf6f7de6e941dd44. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    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"…

    Read the active DESIGN.md (injected above). Use only its colors, typeClassify the product from the brief and pick a tier shape:3-tier (most common): Free / Pro / Team or Starter / Growth / Enterprise.
  2. 02

    Output contract

    One sentence before the artifact, nothing after.

    One sentence before the artifact, nothing after.

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score73/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars82,073SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
nexu-io/open-design
Skill path
design-templates/pricing-page/SKILL.md
Commit
89d6d4ef21baf80f871595abdf6f7de6e941dd44
License
Apache-2.0
Collected
2026-07-28
Default branch
main
View the original SKILL.md

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.

Alternatives

Compare before choosing