@opendirectory.dev/skills 0.1.65 → 0.1.67

package/skills/npm-downloads-to-leads/README.md

@@ -1,4 +1,4 @@
-# npm-downloads-to-leads
+# npm-downloads-to-leads
 
 Give this skill a list of npm packages. It fetches 12 weeks of download data, scores each package by growth velocity, maps maintainers to GitHub and Twitter, and outputs a ranked lead brief per breakout package: who built it, how to reach them, and what to say.
 
@@ -9,19 +9,138 @@ npx "@opendirectory.dev/skills" install npm-downloads-to-leads --target claude
 ```
 
 ### Video Tutorial
-Watch this quick video to see how it's done:
 
 https://github.com/user-attachments/assets/cea8b565-2002-4a87-8857-d902bfcfdc1c
 
-### Step 1: Download the skill from GitHub
-1. Copy the URL of this specific skill folder from your browser's address bar.
-2. Go to [download-directory.github.io](https://download-directory.github.io/).
-3. Paste the URL and click **Enter** to download.
+### Step 1: Download from GitHub
+1. Click the **Code** button on this repo's GitHub page.
+2. Select **Download ZIP**.
+3. Extract the ZIP on your computer.
 
-### Step 2: Install the Skill in Claude
-1. Open your **Claude desktop app**.
-2. Go to the sidebar on the left side and click on the **Customize** section.
-3. Click on the **Skills** tab, then click on the **+** (plus) icon button to create a new skill.
-4. Choose the option to **Upload a skill**, and drag and drop the `.zip` file (or you can extract it and drop the folder, both work).
+### Step 2: Install in Claude
+1. Open the **Claude desktop app**.
+2. Go to **Customize** in the sidebar.
+3. Click the **Skills** tab, then the **+** button.
+4. Choose **Upload a skill** and drop the folder or ZIP file.
 
-> **Note:** For some skills (like `position-me`), the `SKILL.md` file might be located inside a subfolder. Always make sure you are uploading the specific folder that contains the `SKILL.md` file!
+Note: Upload the folder that contains the `SKILL.md` file.
+
+## What It Does
+
+- Fetches 12 weeks of daily download data per package from the npm Downloads API
+- Aggregates to weekly buckets and computes a velocity score: recent growth x acceleration x sweet-spot multiplier
+- Classifies each package as BREAKOUT, WATCHING, steady, established, or too early
+- Fetches maintainer profiles from the npm registry and GitHub API
+- Extracts GitHub followers, Twitter handle, bio, and company from each maintainer's GitHub profile
+- Generates a lead brief per breakout package: growth story, contact signals, why to reach out now, and a suggested first message
+- Saves output to `docs/npm-leads/[date].md`
+
+## Requirements
+
+| Requirement | Purpose | How to Set Up |
+|---|---|---|
+| GitHub token | Raises rate limit from 60/hr to 5000/hr for maintainer profile lookups | github.com/settings/tokens (no scopes needed for public user profiles) |
+
+No external AI API key needed. The npm and npm registry APIs are fully public with no auth. GitHub token is optional but recommended for lists larger than 10 packages.
+
+## Setup
+
+```bash
+cp .env.example .env
+# Add GITHUB_TOKEN (optional, recommended for larger package lists)
+```
+
+## How to Use
+
+```
+"Find leads from these npm packages: esbuild, vite, @hono/hono, zod"
+"Track download trends for competitor packages: turbo, nx, lerna"
+"Who maintains these breakout npm packages? bun, oxc-parser, biome"
+"Find evangelists before they are famous: @effect-ts/core, fp-ts, zod"
+"Analyze npm momentum for my space: my-package, competitor-a, competitor-b"
+"Map npm maintainers to Twitter for these packages: ..."
+```
+
+Include a short description of your product and the skill will tailor the outreach message to your context.
+
+## Why Velocity Score, Not Raw Downloads
+
+React gets 50 million downloads a week. Its maintainers are already famous, already inundated with outreach, and already aligned with a framework you are likely building on.
+
+The velocity score finds the package going from 1K to 8K weekly downloads over 8 weeks. That maintainer just crossed a growth inflection. They are building an audience, they are not yet overwhelmed, and they are in a phase where your product makes a difference to their workflow.
+
+The formula: `velocity_score = growth_ratio x acceleration x sweet_spot_multiplier`
+
+- `growth_ratio`: recent 4-week average divided by prior 4-week average
+- `acceleration`: last 2 weeks vs mid 2 weeks (is growth speeding up?)
+- `sweet_spot_multiplier`: 1.0 for 500 to 500K weekly downloads, lower for noise floor or established giants
+
+Breakout threshold: velocity score above 80 AND 500 to 500K weekly downloads.
+
+## The Lead Brief
+
+For each breakout and watching package:
+
+- **Growth story**: exact download numbers, 8-week comparison, weekly trend
+- **Maintainer profile**: GitHub handle, Twitter, bio, company, follower count
+- **Why reach out now**: specific to this package's growth inflection point
+- **Suggested first message**: names the package, its growth, and connects to your product context
+
+## Cost Per Run
+
+- npm Downloads API: free, no auth, no rate limit concerns
+- npm Registry API: free, no auth
+- GitHub API: free (60 req/hr unauthenticated, 5000/hr with token)
+- AI analysis: uses the model already running the skill; no additional cost
+- Total: free
+
+## Standalone Script
+
+Run the data fetching step directly from the terminal without Claude. Useful for scheduled jobs, CI pipelines, or exploring data before generating lead briefs.
+
+```bash
+# Basic usage
+python3 scripts/fetch.py esbuild zod @hono/hono
+
+# With product context
+python3 scripts/fetch.py esbuild zod --context "We build a TypeScript DX platform"
+
+# From a file (one package per line)
+python3 scripts/fetch.py --file packages.txt --output results.json
+
+# Print to stdout
+python3 scripts/fetch.py esbuild zod --stdout | jq '.summary'
+```
+
+The script handles Steps 3 to 5 (download fetch, velocity scoring, maintainer enrichment) and writes a JSON file. Open that file with Claude and ask: "Generate lead briefs from this npm data."
+
+```bash
+GITHUB_TOKEN=your_token python3 scripts/fetch.py esbuild zod @hono/hono
+```
+
+Script output fields per package:
+
+- `velocity_score`, `growth_pct`, `recent_4_avg`, `prior_4_avg`, `tier`
+- `weeks`: array of 12 weekly download counts, oldest to newest
+- `profile.description`, `profile.keywords`, `profile.npm_maintainers`
+- `profile.github_users`: array with `username`, `twitter_username`, `followers`, `bio`, `company`
+
+## Project Structure
+
+```
+npm-downloads-to-leads/
+├── SKILL.md
+├── README.md
+├── .env.example
+├── scripts/
+│   └── fetch.py           standalone data fetcher (Steps 3 to 5, no Claude needed)
+├── evals/
+│   └── evals.json
+└── references/
+    ├── velocity-scoring.md
+    └── outreach-timing.md
+```
+
+## License
+
+MIT

package/skills/oss-launch-kit/README.md

@@ -25,24 +25,3 @@ Unlike single-channel generators, `oss-launch-kit` acts as the **Root Strategy L
 1. It tells you **if and where** you should launch.
 2. It provides a **timed checklist** for coordination.
 3. It hands off to **specialized skills** for channel-specific drafting.
-
-
-## Install
-
-### Video Tutorial
-Watch this quick video to see how it's done:
-
-https://github.com/user-attachments/assets/cea8b565-2002-4a87-8857-d902bfcfdc1c
-
-### Step 1: Download the skill from GitHub
-1. Copy the URL of this specific skill folder from your browser's address bar.
-2. Go to [download-directory.github.io](https://download-directory.github.io/).
-3. Paste the URL and click **Enter** to download.
-
-### Step 2: Install the Skill in Claude
-1. Open your **Claude desktop app**.
-2. Go to the sidebar on the left side and click on the **Customize** section.
-3. Click on the **Skills** tab, then click on the **+** (plus) icon button to create a new skill.
-4. Choose the option to **Upload a skill**, and drag and drop the `.zip` file (or you can extract it and drop the folder, both work).
-
-> **Note:** For some skills (like `position-me`), the `SKILL.md` file might be located inside a subfolder. Always make sure you are uploading the specific folder that contains the `SKILL.md` file!

package/skills/outreach-sequence-builder/README.md

@@ -1,4 +1,4 @@
-# outreach-sequence-builder
+# outreach-sequence-builder
 
 <img width="1280" height="640" alt="outreach-sequence-builder" src="https://github.com/user-attachments/assets/3d73358a-52ca-48e7-b34e-b1ba33246d6e" />
 
@@ -28,3 +28,105 @@ https://github.com/user-attachments/assets/cea8b565-2002-4a87-8857-d902bfcfdc1c
 4. Choose the option to **Upload a skill**, and drag and drop the `.zip` file (or you can extract it and drop the folder, both work).
 
 > **Note:** For some skills (like `position-me`), the `SKILL.md` file might be located inside a subfolder. Always make sure you are uploading the specific folder that contains the `SKILL.md` file!
+
+## What It Does
+
+- Identifies the signal type from 7 categories: Post-Fundraise, Hiring Signal, Competitor Displacement, Product Launch, Content Engagement, Event Follow-up, Job Change
+- Loads your ICP from docs/icp.md or asks 4 questions to define target persona and pain points
+- Develops the Insight, Bridge, Opener, and Ask for the specific signal
+- Plans a 4-6 touchpoint channel sequence over 10-14 days
+- Generates all messages with Gemini, enforcing hard limits (100-word emails, 300-character LinkedIn notes, 20-word phone openers)
+- Pre-empts 2-4 objections woven into existing touchpoints
+- Runs a 13-point QA pass before presenting the sequence
+- Saves the sequence to docs/sequences/ and optionally drafts emails in Gmail via Composio
+
+## Requirements
+
+| Requirement | Purpose | How to Set Up |
+|------------|---------|--------------|
+| Gemini API key | Sequence generation | aistudio.google.com, Get API key |
+| Composio API key (optional) | Gmail draft creation | app.composio.dev, API Keys |
+
+## Setup
+
+```bash
+cp .env.example .env
+```
+
+Fill in:
+- `GEMINI_API_KEY` (required)
+- `COMPOSIO_API_KEY` (optional, for Gmail draft creation)
+
+Optional: create `docs/icp.md` with your target personas, company profile, pain points, and differentiators. If the file does not exist, the skill asks 4 questions before generating.
+
+## How to Use
+
+Basic sequence from a signal:
+
+```
+"Build an outreach sequence for a prospect who just raised a Series B"
+"They're hiring 8 engineers — write me a sequence"
+"Create outreach based on this signal: they just launched a new product"
+```
+
+With contact context:
+
+```
+"Build an outreach sequence for Sarah Chen, VP Sales at Momentum CRM — they just raised $22M Series B"
+"They switched from Salesforce and posted a frustrated LinkedIn comment. Write a competitor displacement sequence."
+```
+
+With Gmail drafting:
+
+```
+"Build a post-fundraise sequence and draft the emails in Gmail"
+```
+
+## Signal Types
+
+| Signal | Definition | Window |
+|--------|-----------|--------|
+| Post-Fundraise | Company raised a round in the last 30 days | 48 hours from announcement |
+| Hiring Signal | Company posted 5 or more roles in a function you serve | Within the week posts appear |
+| Competitor Displacement | Contact is using a competitor and showing frustration | Within 24 hours |
+| Product Launch | Company launched a new product or major feature | 2-4 weeks after launch |
+| Content Engagement | Contact liked, commented, or shared your content | Start on LinkedIn first |
+| Event Follow-up | You met at a conference or webinar | Within 48 hours of event |
+| Job Change | Contact moved to a new company in the last 60 days | Within 2 weeks of announcement |
+
+## Message Rules
+
+- Only `{{first_name}}` is allowed as a variable. All other details must be filled in from context.
+- Email bodies: 100 words maximum.
+- LinkedIn notes: 300 characters maximum.
+- Phone openers: 20 words maximum.
+- No placeholders like `[Company Name]` or `[INSERT PAIN POINT]`. If the information is not available, the skill asks before writing.
+
+## Output
+
+The sequence is saved to `docs/sequences/{signal-type}.md`. Each touchpoint includes:
+
+- Channel and day number
+- Two subject line variants (email)
+- Message body
+- Word count (email) or character count (LinkedIn)
+- Phone talk track with voicemail script
+
+## Project Structure
+
+```
+outreach-sequence-builder/
+├── SKILL.md
+├── README.md
+├── .env.example
+├── evals/
+│   └── evals.json
+└── references/
+    ├── signal-playbook.md
+    ├── sequence-format.md
+    └── output-template.md
+```
+
+## License
+
+MIT

package/skills/position-me/README.md

@@ -1,4 +1,4 @@
-# Position-Me
+# Position-Me
 
 <img width="1376" height="768" alt="generated-image" src="https://github.com/user-attachments/assets/118fcd1f-1efc-4eca-b0b0-366a6f9ff5da" />
 
@@ -29,3 +29,67 @@ https://github.com/user-attachments/assets/cea8b565-2002-4a87-8857-d902bfcfdc1c
 4. Choose the option to **Upload a skill**, and drag and drop the `.zip` file (or you can extract it and drop the folder, both work).
 
 > **Note:** For some skills (like `position-me`), the `SKILL.md` file might be located inside a subfolder. Always make sure you are uploading the specific folder that contains the `SKILL.md` file!
+
+## Core Capabilities
+
+When invoked, the skill commands the AI agent to conduct an exhaustive teardown of the target website through a rigid protocol:
+
+* Autonomous Navigation: Crawl the homepage, about, pricing, and blog pages.
+* Visual Psychology: Take full page screenshots and analyze visual friction, layout flow, and cognitive load using the LIFT model.
+* Copywriting Critique: Rewrite generic text using the PAS (Problem, Agitation, Solution) framework.
+* Deep Content Audits: Read actual blog posts to identify fluff, grade technical depth, and offer new content strategies.
+* Technical Readiness: Verify the presence of llms.txt, sitemap.xml, and semantic JSON-LD Schema (FAQPage, SoftwareApplication, etc) for generative search optimization.
+
+## Requirements
+
+The host AI agent must have access to:
+1. A multimodal LLM capable of analyzing screenshots natively.
+2. Chrome DevTools MCP Server (https://github.com/ChromeDevTools/chrome-devtools-mcp).
+3. Chrome CDP Skill (https://github.com/pasky/chrome-cdp-skill).
+4. Terminal access to run fallback Python scripts if browser automation fails.
+
+To set up the required Chrome automation:
+* Install and configure the Chrome DevTools MCP server in the agent MCP settings.
+* Add the Chrome CDP skill to the agent skills directory.
+* Ensure Chrome is running with remote debugging enabled (e.g., `chrome --remote-debugging-port=9222`).
+
+## Installation Instructions
+
+### For Developers (Manual Setup)
+
+1. Clone or download the `position-me` repository.
+2. Copy the `position-me/` directory into the agent designated skills directory.
+3. Alternatively, extract the raw `SKILL.md` and `references/` folder into the agent custom prompt configuration.
+
+### For AI Agents (Automated Setup)
+
+1. Clone or download the `position-me` repository into the active project workspace.
+2. Read directly from the `position-me/` source folder.
+3. Add the `SKILL.md` file to the active context window or skill registry.
+4. Verify access to the `references/EVALUATION_SOP.md` and `references/REPORT_TEMPLATE.md` files.
+
+## Execution Protocol for Agents
+
+Once loaded, the AI agent must strictly follow this execution loop:
+
+1. Data Gathering: Prompt the user for the target URL.
+2. Connect to Browser: Use the Chrome DevTools MCP combined with the Chrome CDP skill.
+3. Multi-Page Crawl: Navigate to the homepage, pricing page, about page, and at least one blog post.
+4. Capture Vision Context: Take screenshots of every visited page and load them into memory.
+5. Extract DOM Context: Pull the accessibility tree, search for `llms.txt`, and verify JSON-LD schemas.
+6. Analyze: Apply the frameworks specified in `references/EVALUATION_SOP.md`.
+7. Report: Generate a scored, highly structured teardown using exactly the format in `references/REPORT_TEMPLATE.md`.
+
+## Project Structure
+
+```text
+position-me/
+├── README.md                        # Documentation
+└── position-me/                     # Raw skill source code
+    ├── SKILL.md                     # Master protocol
+    ├── scripts/
+    │   └── extract_links.py         # Fallback crawler script
+    └── references/
+        ├── EVALUATION_SOP.md        # Evaluation frameworks
+        └── REPORT_TEMPLATE.md       # Teardown report template
+```

package/skills/pr-description-writer/README.md

@@ -1,4 +1,4 @@
-# pr-description-writer
+# pr-description-writer
 
 <img width="1280" height="640" alt="pr-description-writer" src="https://github.com/user-attachments/assets/485f5846-b621-40ac-8a99-2b50243fb454" />
 
@@ -28,3 +28,78 @@ https://github.com/user-attachments/assets/cea8b565-2002-4a87-8857-d902bfcfdc1c
 4. Choose the option to **Upload a skill**, and drag and drop the `.zip` file (or you can extract it and drop the folder, both work).
 
 > **Note:** For some skills (like `position-me`), the `SKILL.md` file might be located inside a subfolder. Always make sure you are uploading the specific folder that contains the `SKILL.md` file!
+
+## What It Does
+
+- Reads `git diff main...HEAD` to understand what changed
+- Reads commit messages for context on why it changed
+- Generates a structured PR description following a consistent format
+- Creates a new PR with `gh pr create` or updates an existing one with `gh pr edit`
+
+## Requirements
+
+| Requirement | Purpose | How to Set Up |
+|------------|---------|--------------|
+| `gh` CLI | Creating and updating PRs | https://cli.github.com, then run `gh auth login` |
+| Git repo with a branch | Source diff | Run from inside the repo |
+
+No API keys needed. The agent reads the diff directly and writes the description.
+
+## How to Use
+
+Write a description for the current branch:
+
+```
+"Write a PR description for my current branch"
+"Draft my PR"
+"Generate a PR description"
+```
+
+Create the PR at the same time:
+
+```
+"Create a PR for this branch with a good description"
+"Open a PR and write the description"
+```
+
+Update an existing PR's description:
+
+```
+"Update my PR description"
+"Rewrite the PR body based on the latest changes"
+```
+
+Output only, no gh commands:
+
+```
+"Write a PR description but just give me the text"
+"Draft the PR description, I'll paste it myself"
+```
+
+## Output Format
+
+Every generated description includes:
+
+| Section | Content |
+|---------|---------|
+| Summary | 1-2 sentences on what this PR does and why |
+| Changes | Specific bullets, one per logical change, starting with a verb |
+| Testing | Actionable steps to verify the change works |
+| Screenshots | Only for UI changes |
+| Linked Issues | Only if the branch fixes a tracked issue |
+
+## Project Structure
+
+```
+pr-description-writer/
+├── SKILL.md
+├── README.md
+├── evals/
+│   └── evals.json
+└── references/
+    └── pr-format-guide.md
+```
+
+## License
+
+MIT

package/skills/pricing-finder/README.md

@@ -1,4 +1,4 @@
-# pricing-finder
+# pricing-finder
 
 Tell it what your product is (URL or description). It finds 5 competitors globally, fetches their actual pricing pages, and returns a complete pricing intelligence report: the dominant pricing model in your space, a benchmark price table, feature gate analysis, a competitive positioning map, and a concrete recommended pricing strategy for your product.
 
@@ -27,3 +27,116 @@ https://github.com/user-attachments/assets/cea8b565-2002-4a87-8857-d902bfcfdc1c
 4. Choose the option to **Upload a skill**, and drag and drop the `.zip` file (or you can extract it and drop the folder, both work).
 
 > **Note:** For some skills (like `position-me`), the `SKILL.md` file might be located inside a subfolder. Always make sure you are uploading the specific folder that contains the `SKILL.md` file!
+
+## Setup
+
+```bash
+# Install free Python dependencies (required)
+pip install ddgs requests beautifulsoup4 html2text
+```
+
+No API keys needed. Optionally add keys to `.env` for better quality:
+
+```bash
+cp .env.example .env
+# Uncomment TAVILY_API_KEY or FIRECRAWL_API_KEY if you have them
+```
+
+## Usage
+
+```
+Find pricing benchmarks for my startup: https://yourstartup.com
+```
+
+Or paste a description if you don't have a live URL:
+
+```
+Find pricing benchmarks. We build [what you do] for [who]. [Stage], [geography].
+```
+
+## What It Does
+
+1. Fetches your product page to understand what you're building
+2. Analyzes your product: category, differentiators, ICP
+3. Discovers 5 competitors in your space via DuckDuckGo search
+4. **Asks you to confirm the competitor list** before fetching any data
+5. Fetches each competitor's pricing page (3-tier fallback: direct fetch → Google cache → search snippet)
+6. Extracts structured pricing data: tiers, prices, limits, feature gates
+7. Analyzes patterns across all 5 competitors
+8. Maps competitive positioning and identifies underserved gaps
+9. Recommends a concrete pricing strategy for your product
+
+## Output
+
+A pricing intel report saved to `docs/pricing-intel/[product-slug]-[date].md` containing:
+
+- **Pricing Model Analysis** -- dominant model in your space (per-seat / flat-rate / usage-based / freemium) and why
+- **Price Point Benchmark Table** -- every competitor's tiers with exact prices, free tier, free trial
+- **Market ranges** -- entry tier median, mid tier median, enterprise floor
+- **Feature Gate Analysis** -- what's always free, what's always paid, what varies
+- **Competitive Positioning Map** -- who owns cheap+simple, middle market, enterprise, and where the gap is
+- **Recommended Pricing Strategy** -- model, entry price, mid price, top price, free tier decision, annual discount, what to gate behind paid
+
+## Cost
+
+**$0.00.** Entirely free using pip dependencies.
+
+Optional API upgrades:
+- Tavily API (free tier: 1000 credits/month) -- better search results
+- Firecrawl API (free tier: 500 credits/month) -- better JS-heavy page rendering
+
+## Zero-Hallucination Policy
+
+Every price in the output traces to fetched pricing page content or a search snippet. "Contact Sales" is recorded exactly -- never estimated. Fields that could not be sourced are labeled "not found in page data." Low-quality data (search snippets) is explicitly flagged so you know which competitors to verify manually.
+
+## How Pricing Page Fetching Works
+
+The script tries three methods per competitor, in order:
+
+1. **Direct fetch** (`requests` + `beautifulsoup4` + `html2text`) -- works for most pricing pages since companies make them SEO-friendly and server-rendered
+2. **Google cache** -- fallback for recently-changed pages or soft blocks
+3. **Search snippet** -- last resort; marks data quality as "low" in the output
+
+If you have a Firecrawl API key, it replaces step 1 with a fully JS-rendered fetch.
+
+## Project Structure
+
+```
+pricing-finder/
+├── SKILL.md                        -- 10-step workflow for Claude Code
+├── README.md                       -- this file
+├── .env.example                    -- optional API key template
+├── requirements.txt                -- free pip dependencies
+├── scripts/
+│   └── research.py                 -- two-phase data collector
+├── evals/
+│   └── evals.json                  -- 5 test cases
+└── references/
+    ├── pricing-models.md           -- per-seat, flat, usage, freemium definitions + signals
+    ├── extraction-guide.md         -- how to read a pricing page
+    └── positioning-guide.md        -- how to map competitors and find gaps
+```
+
+## Standalone Script Usage
+
+```bash
+# Phase 1: competitor discovery
+python3 scripts/research.py \
+    --phase discover \
+    --product-analysis /tmp/pf-product-analysis.json \
+    --output /tmp/pf-competitors-raw.json
+
+# Phase 2: fetch pricing pages
+python3 scripts/research.py \
+    --phase fetch-pricing \
+    --competitors /tmp/pf-competitors-confirmed.json \
+    --output /tmp/pf-pricing-raw.json
+
+# With optional API key upgrades
+python3 scripts/research.py \
+    --phase fetch-pricing \
+    --competitors /tmp/pf-competitors-confirmed.json \
+    --firecrawl-key "$FIRECRAWL_API_KEY" \
+    --tavily-key "$TAVILY_API_KEY" \
+    --output /tmp/pf-pricing-raw.json
+```

package/skills/pricing-page-psychology-audit/README.md

@@ -1,4 +1,4 @@
-<img src="https://images.unsplash.com/photo-1551288049-bebda4e38f71?w=1280&h=640&fit=crop&q=80" width="100%" alt="cover" />
+<img src="https://images.unsplash.com/photo-1551288049-bebda4e38f71?w=1280&h=640&fit=crop&q=80" width="100%" alt="cover" />
 
 # pricing-page-psychology-audit
 
@@ -98,3 +98,87 @@ https://github.com/user-attachments/assets/cea8b565-2002-4a87-8857-d902bfcfdc1c
 4. Choose the option to **Upload a skill**, and drag and drop the `.zip` file (or you can extract it and drop the folder, both work).
 
 > **Note:** For some skills (like `position-me`), the `SKILL.md` file might be located inside a subfolder. Always make sure you are uploading the specific folder that contains the `SKILL.md` file!
+
+---
+
+## Usage
+
+### Basic audit:
+```
+"Use pricing-page-psychology-audit to audit https://linear.app/pricing"
+```
+
+### More examples:
+```
+"Audit the pricing page at https://notion.so/pricing"
+"Run a psychology audit on https://vercel.com/pricing"
+"What's wrong with https://stripe.com/pricing from a psychology perspective?"
+```
+
+---
+
+## Example Output
+
+```markdown
+# Pricing Page Psychology Audit
+**URL:** https://linear.app/pricing
+**Audited on:** 2026-04-18
+**Overall Score:** 9/12 principles passing
+
+---
+
+## Audit Results
+
+### 1. Anchoring — ✅ Pass
+**What we found:** Enterprise plan is listed last but priced highest at
+custom pricing, creating an anchor that makes the $16/seat Business plan
+feel accessible.
+**Suggestion:** Consider moving Enterprise to first position for stronger
+anchoring effect.
+
+### 2. Decoy Effect — ⚠️ Needs Work
+**What we found:** The Business tier exists between Free and Enterprise
+but is not clearly positioned as the "sweet spot."
+**Suggestion:** Add a "Most Popular" badge to Business and increase visual
+size to activate the decoy effect.
+
+[... 10 more principles ...]
+
+---
+
+## 🏆 Top 3 Quick Wins
+
+**Quick Win #1 — CTA Button Copy**
+Current: "Get started"
+Rewrite to: "Start shipping faster — free"
+Why: Action-outcome CTAs convert 14% higher than generic "Get started" copy.
+
+**Quick Win #2 — Social Proof Placement**
+Current: Logos shown on a separate /customers page
+Rewrite to: Add 3 customer logos directly below the pricing tiers
+Why: Social proof near the decision point reduces purchase anxiety.
+
+**Quick Win #3 — Guarantee / Trust Signal**
+Current: No guarantee mentioned on pricing page
+Rewrite to: Add "30-day money-back guarantee. No questions asked." below CTAs
+Why: Guarantees have been shown to increase conversion by up to 21%.
+```
+
+---
+
+## Project Structure
+
+```
+pricing-page-psychology-audit/
+├── SKILL.md              ← AI instructions (the brain)
+├── README.md             ← This file
+├── .env.example          ← No API keys required
+└── scripts/
+    └── scrape_pricing.py ← Python scraper (requests + BeautifulSoup)
+```
+
+---
+
+## License
+
+MIT — Built by [@ajaycodesitbetter](https://github.com/ajaycodesitbetter)