mcpField
P
pricing-page-critique

pricing-page-critique

github.com/sylphxaiMarketing & growth153 installsUpdated today
Repository

About pricing-page-critique

A marketing skill for evaluating pricing-page communication, including plan structure, comparisons, cancellation, and trust details. It helps teams clarify how pricing is presented and produces prioritized fixes and experiments, while keeping pricing strategy distinct from page communication.

Key features

  1. 01Review plan structure and comparisons
  2. 02Assess upgrade and cancellation paths
  3. 03Check limits and renewal disclosures
  4. 04Identify trust and risk reducers
  5. 05Prioritize fixes and experiments

Use cases

  1. 01Critique a pricing page before launch
  2. 02Clarify plan differences and restrictions
  3. 03Plan pricing-page improvement experiments

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill pricing-page-critique

After installing, type/pricing-page-critiquein Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/pricing-page-patterns.md

Details

From the project README

Pricing Page Critique

Use this skill to make pricing understandable, trustworthy, and commercially effective.

Workflow

  1. Identify buyer, value metric, sales motion, and product maturity.
  2. Read references/pricing-page-patterns.md.
  3. Review plan architecture, comparison table, risk reducers, upgrade path, cancellation, and trust details.
  4. Check whether the pricing page supports the business model without confusing users.
  5. Produce prioritized fixes and experiments.

When not to use

  • Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Guardrails

  • Do not hide renewal, limits, cancellation, or material restrictions.
  • Do not recommend dark-pattern urgency or fake scarcity.
  • Separate pricing strategy from pricing-page communication.

Output format

Buyer and value metric:
Pricing-page diagnosis:

Fixes:
- <rule id> <fix>

Experiment backlog:
- Hypothesis: <hypothesis>
  Change: <change>
  Guardrail: <metric or trust check>

Comments

Markdown supported