@opendirectory.dev/skills 0.1.65 → 0.1.66

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

@@ -14,7 +14,7 @@ npx "@opendirectory.dev/skills" install pr-description-writer --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
+https://github.com/user-attachments/assets/ee98a1b5-ebc4-452f-bbfb-c434f2935067
 
 ### Step 1: Download the skill from GitHub
 1. Copy the URL of this specific skill folder from your browser's address bar.
@@ -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

@@ -13,7 +13,7 @@ npx "@opendirectory.dev/skills" install pricing-finder --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
+https://github.com/user-attachments/assets/ee98a1b5-ebc4-452f-bbfb-c434f2935067
 
 ### Step 1: Download the skill from GitHub
 1. Copy the URL of this specific skill folder from your browser's address bar.
@@ -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

@@ -84,7 +84,7 @@ npx @opendirectory.dev/skills install pricing-page-psychology-audit
 ### Video Tutorial
 Watch this quick video to see how it's done:
 
-https://github.com/user-attachments/assets/cea8b565-2002-4a87-8857-d902bfcfdc1c
+https://github.com/user-attachments/assets/ee98a1b5-ebc4-452f-bbfb-c434f2935067
 
 ### Step 1: Download the skill from GitHub
 1. Copy the URL of this specific skill folder from your browser's address bar.
@@ -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)

package/skills/product-update-logger/README.md

@@ -13,12 +13,12 @@ npx "@opendirectory.dev/skills" install product-update-logger --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
+https://github.com/user-attachments/assets/ee98a1b5-ebc4-452f-bbfb-c434f2935067
 
 ### 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.
+1. Click the **Code** button on this repo's GitHub page.
+2. Select **Download ZIP** to download the repository.
+3. Extract the ZIP file on your computer.
 
 ### Step 2: Install the Skill in Claude
 1. Open your **Claude desktop app**.
@@ -27,3 +27,171 @@ 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
+
+- Accepts: free text items, git commits (auto-read), GitHub PRs -- any combination
+- Filters noise: merge commits, version bumps, CI/CD, typos excluded automatically
+- Transforms: technical commit language -> user-facing benefit language
+- Categorizes: New / Improved / Fixed / Under the hood
+- Generates a content package: one-liner, tweet thread, LinkedIn post, email snippet
+- Appends a new dated entry to `docs/changelog.md` (living log, newest entry first)
+- Saves the content package to `docs/product-updates/[date]-content.md`
+
+## Requirements
+
+| Requirement | Purpose | How to Set Up |
+|---|---|---|
+| GITHUB_TOKEN | Optional -- enables GitHub PR fetching for richer context | github.com/settings/tokens (no scopes needed) |
+
+No other API keys required. Free text + git auto-read work with no configuration.
+
+## Setup
+
+```bash
+cp .env.example .env
+# Add GITHUB_TOKEN if you want to pull from GitHub PRs
+```
+
+## How to Use
+
+```
+"We shipped dark mode and fixed the export bug this week."
+"Log my product updates. I'm in a git repo."
+"We launched 3 things: dark mode, faster search, fixed mobile login."
+"Log updates from last 14 days. Repo: acme/dashboard"
+"We shipped the onboarding redesign. Version: v2.1.0"
+```
+
+Include competitor names for richer channel discovery. Include ICP role + pain for accurate signal-tracing.
+
+## What Gets Generated
+
+### docs/changelog.md (living log)
+
+```markdown
+# Changelog
+
+## Week of April 23, 2026
+
+### New
+- **Dark mode** -- Toggle in Settings > Appearance. Works across all views.
+
+### Improved
+- **Search** -- Results now load in under half a second.
+
+### Fixed
+- **CSV export** -- Exports no longer drop the last row.
+
+---
+
+## Week of April 14, 2026
+...
+```
+
+### docs/product-updates/[date]-content.md (content package)
+
+```
+## One-liner
+Dark mode, faster search, and a fix for the export bug.
+
+## Tweet Thread
+[1/4] We shipped 3 things this week.
+[2/4] Dark mode is live. Toggle it in Settings > Appearance.
+...
+
+## LinkedIn Post
+We shipped 3 updates this week.
+...
+
+## Email Snippet
+Subject: What shipped this week: dark mode + faster search
+...
+```
+
+## Input Sources
+
+The skill pulls from all three sources automatically:
+
+| Source | When used | How to trigger |
+|---|---|---|
+| Free text | Always first | Just describe what shipped in your message |
+| Git commits | Auto-read when in a git repo | Run the skill from your project directory |
+| GitHub PRs | When GITHUB_TOKEN + repo provided | Mention "repo: owner/repo" in your message |
+
+All three can be combined. Overlapping items are deduplicated.
+
+## Changelog Entry Format
+
+Each entry follows a consistent structure:
+
+```
+## [Version label]
+
+### New
+- **Feature** -- Benefit sentence.
+
+### Improved
+- **Feature** -- Benefit sentence.
+
+### Fixed
+- **Feature** -- What was broken, now fixed.
+
+### Under the hood
+- **Component** -- Developer-relevant change only.
+```
+
+Version labels default to `Week of [Month Day, Year]`. Detected semver format is preserved and incremented automatically.
+
+## Content Rules
+
+- **Tweets**: Under 280 chars each, no hashtags, no em dashes, active voice
+- **LinkedIn**: No markdown formatting, no hashtags, founder voice ("We shipped" not "We are excited to announce")
+- **Email**: 50-100 word body, subject line formula, casual and direct
+- **One-liner**: Max 20 words, covers top 1-2 items
+
+## Standalone Script
+
+Run data collection without Claude. Useful for raw item discovery before analysis.
+
+```bash
+# Git auto-read
+python3 scripts/gather.py --since 7 --output /tmp/pul-raw.json
+
+# Free text items
+python3 scripts/gather.py --items "Add dark mode|Fix CSV bug" --output /tmp/pul-raw.json
+
+# With GitHub PRs
+GITHUB_TOKEN=your_token python3 scripts/gather.py --repo owner/repo --since 14
+
+# Print to stdout
+python3 scripts/gather.py --since 7 --stdout | jq '.items'
+```
+
+## Project Structure
+
+```
+product-update-logger/
+├── SKILL.md
+├── README.md
+├── .env.example
+├── scripts/
+│   └── gather.py               git + GitHub + free text collector
+├── evals/
+│   └── evals.json              5 test cases
+└── references/
+    ├── changelog-format.md     entry structure, category rules, transformation examples
+    ├── content-rules.md        tweet/LinkedIn/email writing rules + banned words
+    └── noise-filter.md         git commit patterns to skip
+```
+
+## Cost Per Run
+
+- Git, free text: free, no auth
+- GitHub PRs: free with optional token
+- AI analysis: uses the model running the skill
+- Total: free
+
+## License
+
+MIT

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

@@ -14,7 +14,7 @@ npx "@opendirectory.dev/skills" install producthunt-launch-kit --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
+https://github.com/user-attachments/assets/ee98a1b5-ebc4-452f-bbfb-c434f2935067
 
 ### Step 1: Download the skill from GitHub
 1. Copy the URL of this specific skill folder from your browser's address bar.
@@ -28,3 +28,92 @@ 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
+
+- Generates 5 tagline variants with character counts (all under 60 chars)
+- Writes a listing description under 500 characters
+- Drafts a maker comment (300-400 words) that opens with the builder story, not "Hi PH!"
+- Creates a launch day tweet thread (5-7 tweets, no hashtags)
+- Writes a LinkedIn post for launch day
+- Generates a 4-email sequence: existing users, newsletter, day-of reminder, follow-up
+- Includes a launch checklist with timing and community guidelines
+
+## Requirements
+
+| Requirement | Purpose | How to Set Up |
+|------------|---------|--------------|
+| Gemini API key | All copy generation | aistudio.google.com, Get API key |
+
+## Setup
+
+```bash
+cp .env.example .env
+# Add GEMINI_API_KEY
+```
+
+## How to Use
+
+Full launch kit:
+```
+"Generate a Product Hunt launch kit for my product"
+"Prepare my PH listing and launch copy"
+"Help me launch on Product Hunt"
+```
+
+Specific assets:
+```
+"Write my Product Hunt tagline for [product description]"
+"Draft a maker comment for my PH launch"
+"Write PH launch tweets"
+```
+
+From README:
+```
+"Generate a Product Hunt kit: my README is in this repo"
+```
+
+## Copy Constraints
+
+| Asset | Limit | Notes |
+|-------|-------|-------|
+| Tagline | 60 chars | Hard limit, enforced by PH form |
+| Description | 500 chars | Appears in search and email digests |
+| Maker comment | 300-400 words | Post within 60 seconds of launch |
+| Tweets | 280 chars each | No hashtags on technical threads |
+
+## Maker Comment Strategy
+
+The maker comment drives more PH success than any other single action. It should:
+
+- Open with the real builder story (not "Hi PH! We're excited to announce...")
+- Include at least one technical detail about how it works
+- Acknowledge what the product does NOT do
+- End with a specific question that invites comments
+
+The comment goes live as your first reply to your own listing, within 60 seconds of the product going live at 12:01 AM PST.
+
+## Launch Timing
+
+Best days: Tuesday, Wednesday, Thursday
+
+Avoid: Friday afternoons, holiday weeks, major tech conference days
+
+The first 4 hours determine front page placement. Notify your audience before midnight PST on launch day so they are ready.
+
+## Project Structure
+
+```
+producthunt-launch-kit/
+├── SKILL.md
+├── README.md
+├── .env.example
+├── evals/
+│   └── evals.json
+└── references/
+    └── copy-rules.md
+```
+
+## License
+
+MIT