pricing-page-psychology-audit

$npx mdskill add Varnan-Tech/opendirectory/pricing-page-psychology-audit

Automatically audits SaaS pricing pages for 12 psychology principles and provides a ranked improvement report

  • Users can input a URL to audit their SaaS pricing page against psychological pricing principles.
  • Deploys a scraper script using Python to extract relevant information from the pricing page.
  • Analyzes extracted data against 12 proven pricing psychology principles, assigning each principle a score of Pass, Needs Work, or Missing.
  • Generates a ranked improvement report with specific rewrite suggestions and quick wins for the user.

SKILL.md

.github/skills/pricing-page-psychology-auditView on GitHub ↗
---
name: pricing-page-psychology-audit
description: Audits any SaaS pricing page URL against 12 pricing psychology principles and outputs a ranked improvement report with specific rewrite suggestions and quick wins.
author: ajaycodesitbetter
version: 1.0.0
---

# Pricing Page Psychology Audit

Scrape any SaaS pricing page and audit it against 12 proven pricing psychology
principles. Get a scored Markdown report with specific rewrite suggestions per
tier and a "Top 3 Quick Wins" section.

---

## Step 1: Get the Target URL

Ask the user:
"Which SaaS pricing page should I audit? Share the full URL
(e.g. https://linear.app/pricing)"

If no URL is provided, stop and ask. Do not proceed without a valid URL
starting with http:// or https://.

---

## Step 2: Run the Scraper

Run the scraper script with the URL:

```bash
python scripts/scrape_pricing.py "URL_HERE"
```

The script outputs structured text to stdout. Capture the output — it contains:
- Page title
- All visible text content
- Button labels (CTAs)
- Plan names and prices
- Feature list items

If the script fails (timeout, blocked, invalid URL), tell the user:
"The page could not be scraped: [error]. Try a different URL or check
if the site blocks bots."

---

## Step 3: Evaluate Against 12 Psychology Principles

Analyze the scraped content against each principle. For each, assign:
- ✅ Pass — clearly present and well-executed
- ⚠️ Needs Work — present but weak or could be improved
- ❌ Missing — not present at all

### The 12 Principles:

1. **Anchoring** — Is there a high-priced plan shown first or prominently to
   make others feel cheaper?

2. **Decoy Effect** — Is there a middle-tier plan designed to make the top
   tier look like better value?

3. **Loss Aversion Framing** — Does copy use "don't miss out", "limited",
   "you'll lose access" rather than purely gain language?

4. **Feature-vs-Value Naming** — Do plan names/descriptions highlight
   outcomes ("Close more deals") vs just features ("10 seats")?

5. **Social Proof Placement** — Are testimonials, logos, or user counts
   shown near pricing tiers (not just on a separate page)?

6. **Urgency / Scarcity Signals** — Is there a countdown timer, limited
   spots badge, or "offer ends" language?

7. **Plan Naming Psychology** — Are plan names aspirational
   (Starter/Growth/Scale) vs generic (Basic/Pro/Enterprise)?

8. **CTA Button Copy** — Do CTAs say action-outcome ("Start growing free")
   vs generic ("Sign up" or "Get started")?

9. **Free Trial vs Freemium Framing** — Is the free offer framed clearly?
   Does it reduce friction or create confusion?

10. **Price Ending Tactics** — Do prices end in 9 ($49, $99) for perceived
    value, or round numbers ($50, $100) for premium feel?

11. **Visual Hierarchy of Tiers** — Is the recommended/popular plan visually
    highlighted (badge, border, size difference)?

12. **Guarantee / Trust Signal Presence** — Is there a money-back guarantee,
    "no credit card required", or security badge near the CTA?

---

## Step 4: Generate the Audit Report

Output the report in this exact Markdown structure:

```
# Pricing Page Psychology Audit
**URL:** [URL]
**Audited on:** [today's date]
**Overall Score:** X/12 principles passing

---

## Audit Results

### 1. Anchoring — ✅ Pass / ⚠️ Needs Work / ❌ Missing
**What we found:** [1-2 sentences from the page]
**Suggestion:** [Specific rewrite or change to make]

[Repeat for all 12 principles]

---

## 🏆 Top 3 Quick Wins

These are your highest-leverage changes, prioritized by impact vs effort:

**Quick Win #1 — [Principle name]**
Current: "[exact copy from page]"
Rewrite to: "[your improved version]"
Why: [1 sentence on the psychological mechanism]

**Quick Win #2 — [Principle name]**
...

**Quick Win #3 — [Principle name]**
...
```

---

## Step 5: Self-QA Before Output

Check before presenting the report:
- [ ] All 12 principles are scored (none skipped)
- [ ] Each "Suggestion" is specific — no generic advice like "add social proof"
- [ ] Quick Wins cite actual copy from the page (not invented)
- [ ] Scores reflect what is literally present in the scraped content
- [ ] Date is today's actual date

Fix any violation before output.

---

## Step 6: Offer Follow-ups

After presenting the report, offer:
1. "Export this as a PDF-ready Markdown file"
2. "Generate rewrite copy for all CTAs on this page"
3. "Compare against a competitor's pricing page"
4. "Build a prioritized action plan for the dev team"

More from Varnan-Tech/opendirectory

SkillDescription
app-store-review-arbitrageFetches low-star App Store and Google Play reviews, clusters them into broken-promise patterns, and generates a ranked copy brief with positioning opportunities.
blog-cover-generatorUse when the user asks to generate a blog cover image, thumbnail, or article header. Automatically uses modern typography, brand logos, and Google Search grounding to create beautiful 16:9 images with Gemini 3.1 Flash Image Preview.
brand-alchemyWorld-class brand strategist and naming expert. Uses an interrogation-led discovery phase to extract your brand's DNA, then applies scientific naming frameworks (Phonosemantics) and automated multi-TLD domain checking.
claude-md-generatorUse when the user asks to generate or update a project's CLAUDE or AGENTS context file from a codebase scan. Writes a focused file under 100 lines containing only the non-obvious build commands, conventions, and gotchas Claude Code needs.
cold-email-verifierUse when the user wants to verify cold emails, enrich a lead list, or autonomously guess email addresses from a CSV using ValidEmail.co or the open-source Reacher engine.
company-radarCompetitive intelligence orchestrator tracking companies across 8+ platforms (GitHub, Twitter, Reddit, HN, PH, YC Jobs) with heat scores and AI briefings.
competitor-pr-finderGive it your product URL or description. It finds your top 5 competitors, runs three-track PR research across all of them (editorial, podcasts, communities), identifies which channels appear most frequently, looks up the journalist or host for each, and returns a tiered outreach list with story angles and ready-to-send cold pitch drafts tailored to your product. Use when asked to find PR opportunities, discover where competitors got featured, build a media outreach list, find which journalists cover my space, or get pitch templates for press coverage.
cook-the-blogGenerate high-converting, deep-dive growth case studies in MDX format. Use this skill when asked to write a case study or blog post about a company's growth, tech stack, or product-led strategy. It handles the full pipeline (researching the company via Tavily, generating a 16:9 cover image, quality checking the draft, uploading assets to cloud storage, and pushing directly to the target repository).
dependency-update-botScans your project for outdated npm, pip, Cargo, Go, or Ruby packages. Runs a CVE security audit. Fetches changelogs, summarizes breaking changes with Gemini, and opens one PR per risk group (patch, minor, major). Includes Diagnosis Mode for install conflicts. Use when asked to update dependencies, check for outdated packages, open dependency PRs, scan for package updates, audit for CVEs, or flag breaking changes in upgrades. Trigger when a user says "check for outdated packages", "update my dependencies", "open PRs for dependency updates", "scan for CVEs", or "which packages need upgrading".
docs-from-codeGenerates and updates README.md and API reference docs by reading your codebase's functions, routes, types, schemas, and architecture. Uses graphify to build a knowledge graph first, then writes accurate docs from it. Use when asked to write docs, generate a README, document an API, update stale docs, create an API reference from code, add an architecture section, or document a project in any language. Trigger when a user says their docs are missing, outdated, or wants to document their codebase without writing it manually.