@opendirectory.dev/skills 0.1.65 → 0.1.67

package/skills/sdk-adoption-tracker/README.md

@@ -1,4 +1,4 @@
-# sdk-adoption-tracker
+# sdk-adoption-tracker
 
 Give this skill an SDK or library name. It searches GitHub for public repos that import it, scores each repo by company signal and activity, identifies who is building on you in production, and outputs a ranked adoption report with outreach context for high-signal company repos.
 
@@ -25,3 +25,129 @@ 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!
+
+Note: Upload the folder that contains the `SKILL.md` file.
+
+## What It Does
+
+- Searches GitHub code for all public repos that import or require the SDK
+- Supports npm, Python, Go, Ruby, and generic import patterns -- auto-detected from the SDK name
+- Filters forks, tutorials, examples, and archived repos from results
+- Classifies each repo: company org, affiliated developer, solo developer, or tutorial noise
+- Scores by adoption signal: org type, company field, stars, recency, fork status
+- Fetches owner profile and top contributor for each high-signal repo
+- Tracks adoption velocity: new repos in last 7, 14, and 30 days
+- Compares to previous snapshot for exact new-adopter count on repeat runs
+- Generates an outreach brief per high-signal company repo: what they are building, who introduced the SDK, and what to say
+- Saves output to `docs/sdk-adopters/[sdk-name]-[date].md`
+
+## Requirements
+
+| Requirement | Purpose | How to Set Up |
+|---|---|---|
+| GitHub token | Required for code search (unauthenticated limit is 3 req/min, too low to run) | github.com/settings/tokens (no scopes needed for public repos) |
+
+## Setup
+
+```bash
+cp .env.example .env
+# Add GITHUB_TOKEN
+```
+
+## How to Use
+
+```
+"Who is using my SDK on GitHub? @company/my-sdk"
+"Find companies building on my library: stripe"
+"Track adoption of my Python package: requests"
+"Which orgs import my SDK: @clerk/nextjs"
+"Show me who uses my library and rank by company signal"
+"Find warm leads from SDK adopters: my-package"
+```
+
+Include a short description of your product and the skill will tailor the outreach message to your context.
+
+## Why Score Instead of Just List
+
+A raw GitHub code search for a popular SDK returns tutorials, forks, abandoned side projects, and examples mixed in with real production users. The adoption score separates them:
+
+- A company org repo with recent commits and 200 stars scores 130+
+- A tutorial named "learn-stripe-payments" scores below 20 and is excluded
+
+The person who added the import in a company repo is the warmest possible lead. They chose the SDK, they understand what it does, and they have an active production use case.
+
+## The Adoption Score
+
+`score = org_signal + company_field + stars_capped + recency + quality_flags`
+
+- Org type (50 points): GitHub Organization accounts are almost always a company or serious team
+- Company field (20 points): user has a company listed on their GitHub profile
+- Stars (up to 50 points): capped at 500 stars to prevent established open-source from dominating
+- Recency (up to 50 points): pushed in last 7 or 30 days
+- Quality (up to 40 points): not a fork, not archived, not a tutorial
+
+Score >= 80: full outreach brief generated. Score 40-79: listed in report. Score < 40: counted in breakdown only.
+
+## Velocity Tracking
+
+Run the skill weekly and save the JSON snapshot. On each subsequent run, the skill compares the current repo list to the previous snapshot and tells you exactly how many new teams adopted the SDK since last time.
+
+```
+New repos last 7 days: 3
+New repos last 30 days: 11
+New since last run (7 days ago): 3
+```
+
+## Cost Per Run
+
+- GitHub Code Search API: free with token
+- GitHub User, Org, Contributors API: free 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 or CI pipelines.
+
+```bash
+# Basic usage
+python3 scripts/fetch.py stripe
+
+# Python SDK
+python3 scripts/fetch.py requests --ecosystem python
+
+# With product context for outreach
+python3 scripts/fetch.py @company/my-sdk --context "We build observability for DevTools"
+
+# Exclude the SDK publisher's own repos
+python3 scripts/fetch.py stripe --exclude stripe
+
+# Print to stdout
+python3 scripts/fetch.py stripe --stdout | jq '.summary'
+```
+
+The script handles Steps 3-5 (code search, scoring, enrichment) and writes a JSON file. Open that file with Claude and ask: "Generate adoption briefs from this SDK data."
+
+```bash
+GITHUB_TOKEN=your_token python3 scripts/fetch.py stripe --output results.json
+```
+
+## Project Structure
+
+```
+sdk-adoption-tracker/
+├── SKILL.md
+├── README.md
+├── .env.example
+├── scripts/
+│   └── fetch.py           standalone fetcher (Steps 3-5, no Claude needed)
+├── evals/
+│   └── evals.json
+└── references/
+    ├── import-patterns.md
+    └── scoring-guide.md
+```
+
+## License
+
+MIT

package/skills/show-hn-writer/README.md

@@ -1,4 +1,4 @@
-# show-hn-writer
+# show-hn-writer
 
 <img width="1280" height="640" alt="show-hn-writer" src="https://github.com/user-attachments/assets/224030e0-c3e0-499c-98d4-a049d7dddc51" />
 
@@ -28,3 +28,85 @@ 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 your project context (from README or your answers)
+- Drafts three Show HN title variants in different formats
+- Writes a 150-350 word body following HN community norms
+- Uses Gemini to flag marketing language, vague descriptions, or other HN anti-patterns
+- Runs a self-QA checklist before presenting output
+- Includes submission notes (timing, first-comment strategy, resubmission rules)
+
+## Requirements
+
+| Requirement | Purpose | How to Set Up |
+|------------|---------|--------------|
+| Gemini API key (optional) | Automated draft review for HN anti-patterns | aistudio.google.com, Get API key |
+
+The skill works without Gemini: it runs the manual self-QA checklist instead.
+
+## Setup
+
+```bash
+cp .env.example .env
+# Add GEMINI_API_KEY if you want automated review (optional)
+```
+
+## How to Use
+
+From a README:
+```
+"Write a Show HN post for my project"
+"Help me launch on Hacker News"
+"Draft a Show HN for the project in this repo"
+```
+
+With explicit context:
+```
+"Write a Show HN post for [project name]: [what it does]. I built it because [reason]."
+```
+
+For a specific title format:
+```
+"Write a Show HN title for my CLI tool that converts JSON to TypeScript interfaces"
+```
+
+## Show HN Title Formats
+
+| Format | Example | Best For |
+|--------|---------|----------|
+| Product-First | `Show HN: Datasette – Instantly publish SQLite databases to the web` | Single-function tools |
+| Outcome-Focused | `Show HN: Jitsi – Group video calls without an account` | Tools replacing something painful |
+| Technical-Angle | `Show HN: Bun – JavaScript runtime built in Zig` | Dev tools where the implementation matters |
+| Experiment | `Show HN: Ink – React for command-line apps` | Projects challenging a convention |
+
+## What Makes a Good Show HN Post
+
+**Title:** 60-80 characters. Starts with "Show HN:". En dash separator. No adjectives.
+
+**Body:** First-person. 150-350 words. At least one technical detail. Honest about limitations. Ends with an invitation for feedback, not a CTA.
+
+**What kills HN posts:**
+- Vague titles ("Show HN: I built a thing for developers")
+- Marketing adjectives ("fast", "simple", "powerful")
+- Asking for upvotes
+- Body that reads like a product page
+
+## Project Structure
+
+```
+show-hn-writer/
+├── SKILL.md
+├── README.md
+├── .env.example
+├── evals/
+│   └── evals.json
+└── references/
+    ├── hn-rules.md
+    └── title-formulas.md
+```
+
+## License
+
+MIT

package/skills/stargazer/README.md

@@ -77,24 +77,3 @@ Generate a final CSV file for use in other applications.
 ```bash
 python stargazer-skill/scripts/convert_to_csv.py
 ```
-
-
-## 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/tweet-thread-from-blog/README.md

@@ -1,4 +1,4 @@
-# tweet-thread-from-blog
+# tweet-thread-from-blog
 
 <img width="1280" height="640" alt="tweet-thread-from-blog" src="https://github.com/user-attachments/assets/18b96a6b-9477-444d-b169-ea14a63e9fdf" />
 
@@ -28,3 +28,106 @@ 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!
+
+## Thread Styles
+
+| Style | Use When | Example Input |
+|-------|----------|---------------|
+| Data/Insight | Evidence-based article with stats or research findings | Engineering blog post with benchmark numbers |
+| How-To | Tutorial or step-by-step guide | "How to set up X in 10 minutes" post |
+| Story/Journey | Personal experience, build log, lessons learned | Indie hacker retrospective |
+| Hot Take | Opinion piece, contrarian argument | "Why X is wrong" editorial |
+
+The agent auto-detects the right style. Override it by specifying the style in your prompt.
+
+## Requirements
+
+No LLM API key needed. The agent reads the page and writes the thread.
+
+**Note on X/Twitter posting:** Twitter's API v2 now requires a paid developer account (Basic tier, $100/month minimum). As a result, the Composio Twitter integration returns a 403 error for most users. The skill still generates complete, ready-to-post threads — just copy-paste them manually. Direct posting via Composio is documented below but is only viable if you have a paid Twitter developer account connected.
+
+## Setup
+
+### 1. Configure environment variables (optional)
+
+```bash
+cp .env.example .env
+# Add COMPOSIO_API_KEY if you want direct posting to X
+```
+
+### 2. Connect X/Twitter via Composio (optional, requires paid Twitter developer account)
+
+Twitter's API v2 now requires a paid developer account before Composio can post on your behalf. If you get a 403 error, this is why. Skip this step and use copy-paste output instead.
+
+1. Sign up for Twitter Developer Portal (Basic tier, ~$100/month): https://developer.twitter.com/en/portal/products
+2. Get your Composio API key at: https://app.composio.dev/settings
+3. Connect your X/Twitter account at: https://app.composio.dev/app/twitter
+4. Complete the OAuth flow
+
+## How to Use
+
+From a URL:
+
+```
+"Turn this into a tweet thread: https://example.com/blog/post"
+"Create a Twitter thread from this article: https://example.com/post"
+"Write a tweet thread about this blog post: https://example.com/tutorial"
+```
+
+From pasted content:
+
+```
+"Make a thread from this: [paste article text]"
+"Turn this into a Twitter thread: [paste blog post]"
+```
+
+With a style override:
+
+```
+"Turn this into a How-To thread: https://example.com/data-article"
+"Write a Hot Take thread from this: https://example.com/opinion"
+```
+
+With direct posting (requires paid Twitter developer account + Composio setup):
+
+```
+"Post this blog post as a Twitter thread: https://example.com/post"
+```
+
+## Output
+
+| Output | Description |
+|--------|-------------|
+| Full thread | 7-10 numbered tweets, each under 280 characters |
+| Alternative hook | A second hook tweet in a different format |
+| Posted confirmation | If COMPOSIO_API_KEY is set and you confirm, the thread posts as a reply chain on X |
+
+## How Threads Are Formatted
+
+Hook first. Tweet 1 leads with the most surprising insight or a curiosity gap. It never announces the thread.
+
+One idea per tweet. If a tweet can be split, it gets split. Each tweet stands alone.
+
+Numbered throughout. Every tweet starts with its position: "1/8", "2/8", etc.
+
+CTA last. The final tweet is the only one with a URL or call to action.
+
+No hashtags. Hashtags reduce the quality signal of technical threads.
+
+## Project Structure
+
+```
+tweet-thread-from-blog/
+├── SKILL.md
+├── README.md
+├── .env.example
+├── evals/
+│   └── evals.json
+└── references/
+    ├── thread-format.md
+    └── output-template.md
+```
+
+## License
+
+MIT

package/skills/twitter-GTM-find-skill/README.md

@@ -1,4 +1,4 @@
-# Twitter GTM Find Skill
+# Twitter GTM Find Skill
 
 <img width="1280" height="640" alt="Generated_chart__twitter-gtm-find-cover-bw png" src="https://github.com/user-attachments/assets/618b0abe-34fc-4c3e-a345-1a3eaeb3d20b" />
 
@@ -29,3 +29,39 @@ 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!
+
+## The Skill Directory
+
+All executable code and documentation are packaged cleanly inside the `twitter-GTM-find/` folder. This is designed to be directly imported and read by AI agents (like OpenClaw or Claude) so they understand how to use the tool.
+
+```text
+twitter-GTM-find/
+├── SKILL.md             <-- The AI entry point and documentation
+├── references/          
+│   └── icp-checklist.md <-- The strict evaluation criteria (Dev-first + $100K+ funded)
+└── scripts/
+    ├── run_pipeline.sh  <-- The executable shell script
+    └── src/             <-- The TypeScript pipeline source code
+```
+
+## Usage
+
+To run the pipeline manually or via an agent:
+
+1. Create a `.env` file at the root of the repository:
+   ```env
+   APIFY_API_TOKEN=your_apify_token
+   GEMINI_API_KEY=your_gemini_api_key
+   MAX_POSTS=20
+   ```
+2. Run the shell script:
+   ```bash
+   cd twitter-GTM-find/scripts
+   bash run_pipeline.sh
+   ```
+
+## Output
+
+The pipeline generates two temporary files at the root of the repository (which are `.gitignore`d to prevent leaking data):
+- `radar-jobs.json`: The initial raw batch of scraped tech jobs.
+- `openclaw-icp-jobs.json`: The final, strict ICP-validated list of highly funded, developer-first startups hiring right now.

package/skills/vc-curated-match/README.md

@@ -40,24 +40,3 @@ python scripts/run.py \
 - **Taxonomy Constraints**: The scoring engine relies on a fixed taxonomy. Extremely niche or highly unusual product descriptions may not trigger specific industry tags and will default to a "Generalist" view.
 - **Human Review Required**: These outputs are best-effort algorithmic matches. They serve as a research starting point and **must be reviewed by a human** before starting outreach.
 - **No Financial Advice**: This tool does not provide financial or investment advice.
-
-
-## 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/vc-finder/README.md

@@ -1,4 +1,4 @@
-# vc-finder
+# vc-finder
 
 Give the skill a product URL or description. It detects the industry and funding stage, identifies 5 comparable funded companies, searches who backed those companies (Track A), finds VCs who publish investment theses about this space (Track B), and returns a ranked sourced investor list with deep-dives and outreach hooks.
 
@@ -14,9 +14,9 @@ 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.
+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**.
@@ -24,4 +24,97 @@ https://github.com/user-attachments/assets/cea8b565-2002-4a87-8857-d902bfcfdc1c
 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!
+> **Note:** Make sure you are uploading the folder that contains the `SKILL.md` file!
+
+## What It Does
+
+- Fetches the product URL via Firecrawl (handles JS-rendered SPAs) or Tavily extract as fallback
+- Detects funding stage from CTA signals on the page (waitlist, free trial, pricing, sales CTAs)
+- Maps a 3-level industry taxonomy (L1 > L2 > L3) from the product page
+- **Curated pre-match (Step 5b):** Scores product against a verified dataset of 25 VC funds (sourced from fund websites) -- instant zero-hallucination matches with no Tavily credits consumed
+- **Discovers comparable companies:** Curated portfolio companies from matched funds + Tavily live search for L3-niche specifics
+- Track A: 5 Tavily searches to find who invested in each comparable company
+- Track B: 3 Tavily searches to find VCs who publish investment theses about this specific niche
+- Synthesizes and ranks all found VCs -- curated matches labeled "verified", Tavily matches labeled by track
+- Produces top 5 deep-dives with fund overview, portfolio evidence, how-to-approach, and outreach hook
+- Generates 3 product-specific outreach hooks (not generic advice)
+- Saves output to `docs/vc-intel/[product]-[date].md`
+
+**Zero-hallucination guarantee:** Every VC name, fund detail, check size, portfolio company, and thesis source in the output must trace to either (a) the curated `data/vc_funds.json` dataset (sourced from fund websites) or (b) a specific Tavily search result. The AI does not draw from training knowledge for any factual claim.
+
+## Requirements
+
+| Requirement | Purpose | How to Set Up |
+|---|---|---|
+| Tavily API key | VC investment research (Track A and Track B) | app.tavily.com, free tier: 1000 credits/month |
+| Firecrawl API key | Fetching JS-rendered product pages (optional) | firecrawl.dev, free tier: 500 credits/month |
+
+Tavily is required. Firecrawl is recommended -- without it, Tavily extract is used as fallback (may miss JS-rendered content).
+
+## Setup
+
+```bash
+cp .env.example .env
+# Add TAVILY_API_KEY (required)
+# Add FIRECRAWL_API_KEY (recommended)
+```
+
+## How to Use
+
+```
+"Find VCs for my startup: https://example.com"
+"Who invests in developer tools at seed stage?"
+"Build me a VC target list for https://example.com"
+"Which funds should I pitch? https://example.com"
+"Find investors for my product: [paste description]"
+"Who backed companies like mine? https://example.com"
+```
+
+Or paste a product description directly if the URL is behind a login or returns no readable content.
+
+## Why Two Tracks
+
+**Track A (portfolio mapping):** VCs who already wrote a check in your space. These investors have proven they understand the category, the risks, and the buyer. They need less convincing than a generalist fund.
+
+**Track B (thesis matching):** VCs who are actively publishing about your space. An investor who wrote a 2,000-word blog post about why they want to invest in CI/CD tooling is actively looking for deals. Your cold email lands in a much warmer inbox.
+
+Generic "VCs in B2B SaaS" lists skip both signals. This skill produces only VCs with named evidence for each entry.
+
+## Output
+
+Each run produces:
+
+1. **Product analysis**: detected industry taxonomy, stage, ICP, comparable companies used
+2. **Track A table**: VCs who backed comparable companies (with evidence)
+3. **Track B table**: VCs with published theses about this space (with source)
+4. **Top 5 deep-dives**: fund overview, why it fits, portfolio in space, how to approach, outreach hook
+5. **3 outreach hooks**: product-specific openers for cold outreach
+
+## Cost per Run
+
+- Firecrawl: ~$0.001 per fetch
+- Tavily: 10 searches at ~$0.01 each = ~$0.10 (2 comparable discovery + 5 Track A + 3 Track B)
+- Curated pre-match (Step 5b): $0.00 -- local scoring against `data/vc_funds.json`, no API calls
+- Total: ~$0.10 per run
+
+## Project Structure
+
+```
+vc-finder/
+├── SKILL.md
+├── README.md
+├── .env.example
+├── data/
+│   └── vc_funds.json          (25 verified funds, sourced from fund websites)
+├── scripts/
+│   └── match_funds.py         (standalone scoring script for testing)
+├── evals/
+│   └── evals.json
+└── references/
+    ├── stage-signals.md
+    └── vc-outreach-guide.md
+```
+
+## License
+
+MIT

package/skills/vid-motion-graphics/README.md

@@ -1,4 +1,4 @@
-# vid-motion-graphics
+# vid-motion-graphics
 
 Generates multi-scene motion graphics as MP4 from a content brief. HTML/CSS animations rendered frame-by-frame in headless Chromium via Playwright, assembled with FFmpeg. No React, no AI APIs, no Python.
 
@@ -16,9 +16,9 @@ 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.
+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**.
@@ -26,4 +26,64 @@ https://github.com/user-attachments/assets/cea8b565-2002-4a87-8857-d902bfcfdc1c
 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!
+> **Note:** Make sure you are uploading the folder that contains the `SKILL.md` file!
+
+## What it does
+
+1. Takes a content brief (what each scene should say) and style params
+2. Generates a multi-scene HTML/CSS animation file
+3. Captures frames via Playwright + Web Animations API seeking
+4. Assembles PNG sequence → H.264 MP4 with FFmpeg
+5. Optionally mixes in background audio
+
+## Output
+
+- Format: H.264 MP4, `-pix_fmt yuv420p` (compatible with QuickTime, iOS, Android, Twitter, LinkedIn, Instagram)
+- Default: 1080×1080px @2× retina (2160×2160 actual)
+- Supports: 1:1, 16:9 (1920×1080), 9:16 (1080×1920)
+- FPS: 24, 30, or 60
+
+## Scene types
+
+| Type | Best for |
+|---|---|
+| `title-card` | Opening hook, brand intro |
+| `stat-reveal` | Single oversized metric |
+| `bullet-list` | 2–4 supporting points |
+| `split-screen` | Before/after, two values |
+| `quote-card` | Testimonial, pull quote |
+| `cta-card` | Final scene, call to action |
+
+## Style presets
+
+| Preset | Feel |
+|---|---|
+| `kinetic-dark` | Dark bg, electric yellow, tight grotesque (default) |
+| `editorial-light` | White bg, serif display, refined |
+| `data-pulse` | Deep navy, mono, terminal/dashboard |
+| `bold-type` | White bg, Bebas Neue, red accent, slam-in |
+| `minimal-clean` | Off-white, Cormorant, gentle rise |
+
+## Requirements
+
+- Node.js (for Playwright frame capture)
+- FFmpeg (for MP4 assembly)
+- Internet access for Google Fonts CDN during capture
+
+## Usage
+
+```
+Create a 9-second motion graphic. Brief: 'Q4 revenue hit $4.2M — 85% growth.
+Three drivers: enterprise deals, churn 1.2%, price increase.
+CTA: acme.com/q4'. Style: data-pulse. Aspect: 1:1.
+```
+
+## Quick export
+
+```bash
+bash scripts/export-video.sh chart/[slug]/video.html --duration 9
+```
+
+## Differentiator vs SkillsMP
+
+All top SkillsMP motion-graphic skills require Remotion (React build step) or AI video APIs (Runway, Kling — cost + rate limits). This skill uses the proven HTML/CSS → Playwright → FFmpeg pipeline from the `graphic-gif` family: zero new dependencies, pixel-perfect output, full CSS control.

package/skills/where-your-customer-lives/README.md

@@ -10,24 +10,6 @@ Stop guessing which communities to post in. Get signal-traced evidence.
 npx "@opendirectory.dev/skills" install where-your-customer-lives --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 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!
-
 ## What It Does
 
 - Accepts: product description + ICP role + ICP pain + competitors (any combination)
@@ -151,4 +133,3 @@ Run both for a complete picture: map-your-market tells you what to say, where-yo
 ## License
 
 MIT
-