@opendirectory.dev/skills 0.1.65 → 0.1.67

package/skills/luma-attendees-scraper/README.md

@@ -168,24 +168,3 @@ Some browsers block downloads from DevTools-triggered scripts until user interac
 ## Disclaimer
 
 Use this responsibly and only for events and attendee lists your account is authorized to access.
-
-
-## 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/map-your-market/README.md

@@ -1,4 +1,4 @@
-# map-your-market
+# map-your-market
 
 Give this skill a product description, category keywords, or competitor names. It searches Reddit, Hacker News, GitHub Issues, G2, and Google Trends for real pain signals from your market -- then builds a complete positioning framework: who your ICP is, what they say out loud, and how to talk to them.
 
@@ -25,3 +25,123 @@ 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 any combination of: product description, category keywords, competitor names
+- Auto-detects relevant subreddits from the category
+- Searches Reddit public JSON API for pain posts (top posts, last 12 months)
+- Searches Hacker News Algolia API for stories and Ask HN threads
+- Searches GitHub Issues on competitor repos for high-reaction complaints
+- Scrapes G2 category pages for vendor count and top products
+- Fetches Google Trends direction (up / flat / down) for the category
+- Scores every signal by source weight and recency (GitHub issues score 3x Reddit -- more deliberate signal)
+- Clusters top 60 signals into 5-7 named pain themes
+- Extracts ICP from subreddit and post metadata (not just content)
+- Generates a positioning framework with messaging angles using verbatim market language
+- Saves output to `docs/market-maps/[category]-[date].md` + JSON snapshot
+
+## Requirements
+
+| Requirement | Purpose | How to Set Up |
+|---|---|---|
+| GITHUB_TOKEN | Optional -- improves GitHub Issues rate limit from 60/hr to 5000/hr | github.com/settings/tokens (no scopes needed for public repos) |
+
+No other API keys required.
+
+## Setup
+
+```bash
+cp .env.example .env
+# Add GITHUB_TOKEN if you want higher GitHub rate limits
+```
+
+## How to Use
+
+```
+"Map my market: I build developer observability tools"
+"Who is my ICP? Competitors: Datadog, Grafana, New Relic"
+"What are the top pains in the HR software market?"
+"Find messaging angles for my B2B analytics tool"
+"Map the CRM market. What are people complaining about?"
+"I build payment APIs. Who should I be selling to?"
+```
+
+Include competitor names for richer GitHub Issues data. Include a product description for tailored messaging angles.
+
+## Why This Instead of Manual Research
+
+A founder doing this manually would spend 2-3 days:
+- Reading Reddit threads, taking notes
+- Scrolling HN "Ask HN" posts
+- Checking G2 review counts per vendor
+- Looking up Google Trends
+- Synthesizing into a document
+
+This skill does the same sweep in 3 minutes and returns verbatim quotes, not paraphrased summaries. The messaging framework uses the exact language your market uses -- not marketing copy you invented.
+
+## The Pain Score
+
+`pain_score = base * recency_factor`
+
+- GitHub issue reactions: `reactions * 3` -- a developer deliberately clicking +1 is the strongest signal
+- Reddit: `upvotes + (comments * 0.3)` -- upvotes count more than comments (comments include noise)
+- HN: `points + (comments * 0.3)` -- same structure
+
+Score tiers: critical (200+), high (50-199), medium (10-49), noise (<10, filtered out).
+
+## Velocity Tracking
+
+Run the skill every quarter. JSON snapshots in `docs/market-maps/` let you compare pain cluster rankings over time. A pain that was #3 last quarter and is #1 this quarter is accelerating -- a stronger positioning bet.
+
+## Cost Per Run
+
+- Reddit, HN, Google Trends: free, no auth
+- GitHub Issues: free with optional token
+- G2 scrape: free HTML fetch
+- AI analysis: uses the model already running the skill
+- Total: free
+
+## Standalone Script
+
+Run data collection without Claude. Useful when you want the raw signals first, then bring them to any AI for analysis.
+
+```bash
+# Basic usage
+python3 scripts/fetch.py "developer observability"
+
+# With competitors
+python3 scripts/fetch.py "developer observability" --competitors "Datadog,Grafana,New Relic"
+
+# With product context
+python3 scripts/fetch.py "B2B analytics" --context "We help ops teams track spend"
+
+# Print to stdout
+python3 scripts/fetch.py "devops tooling" --stdout | jq '.summary'
+
+# With GitHub token for higher rate limits
+GITHUB_TOKEN=your_token python3 scripts/fetch.py "CRM software" --competitors "Salesforce,HubSpot" --output results.json
+```
+
+The script writes a JSON file with all raw signals. Open that file with Claude and ask: "Generate a market map and positioning framework from this data."
+
+## Project Structure
+
+```
+map-your-market/
+├── SKILL.md
+├── README.md
+├── .env.example
+├── scripts/
+│   └── fetch.py           standalone data collector
+├── evals/
+│   └── evals.json
+└── references/
+    ├── subreddit-map.md   category to subreddit mapping
+    ├── pain-scoring.md    scoring formula and tier thresholds
+    └── icp-signals.md     how to extract ICP from post metadata
+```
+
+## License
+
+MIT

package/skills/meeting-brief-generator/README.md

@@ -1,4 +1,4 @@
-# meeting-brief-generator
+# meeting-brief-generator
 
 <img width="1280" height="640" alt="meeting-brief-generator" src="https://github.com/user-attachments/assets/30026bc4-657a-4ce9-8c0e-4dd2654783f8" />
 
@@ -28,3 +28,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!
+
+## What It Does
+
+- Runs 6-8 targeted Tavily searches covering company overview, recent news, tech stack, product, competitors, funding, and contact background
+- Synthesizes results into a structured 1-page brief using Gemini
+- Every claim cites a source URL from the research
+- Optionally saves the brief to a Notion database
+- Handles low-data companies by marking gaps instead of inventing content
+
+## Requirements
+
+| Requirement | Purpose | How to Set Up |
+|------------|---------|--------------|
+| Tavily API key | Company research | app.tavily.com, API Keys |
+| Gemini API key | Brief synthesis | aistudio.google.com, Get API key |
+| Notion token (optional) | Saving briefs | notion.so/my-integrations |
+
+## Setup
+
+```bash
+cp .env.example .env
+```
+
+Fill in:
+- `TAVILY_API_KEY` (required)
+- `GEMINI_API_KEY` (required)
+- `NOTION_TOKEN` and `NOTION_DATABASE_ID` (optional, for saving briefs)
+
+## How to Use
+
+Basic brief with company only:
+
+```
+"Prepare me for a meeting with Stripe next Tuesday"
+"Generate a meeting brief for Vercel"
+"Research Acme Corp before my call tomorrow"
+```
+
+With contact and meeting type:
+
+```
+"Prepare a discovery call brief for Linear. I'm meeting with the VP Engineering, Jordan Lee."
+"Create a pre-call brief for Notion. Demo call on April 20."
+```
+
+Save to Notion:
+
+```
+"Generate a meeting brief for Figma and save it to Notion"
+```
+
+## Brief Sections
+
+| Section | Content |
+|---------|---------|
+| Company Snapshot | What they do, size, funding stage, HQ |
+| Recent News | Last 30 days, source URLs |
+| Decision Maker | Name, title, background (if contact provided) |
+| Tech Stack Signals | Tools spotted in job posts, blog, GitHub |
+| Competitive Context | Who they compete with and how |
+| Talking Points | Because/mention/to formula, 3-5 bullets |
+| Open Questions | Company-specific discovery questions |
+
+## Output Format
+
+One page, under 400 words. Every claim has a source URL. Talking points follow the format: "Because [finding from research], mention [point] to [goal]."
+
+## Project Structure
+
+```
+meeting-brief-generator/
+├── SKILL.md
+├── README.md
+├── .env.example
+├── evals/
+│   └── evals.json
+└── references/
+    ├── brief-format.md
+    └── output-template.md
+```
+
+## License
+
+MIT

package/skills/meta-ads-skill/README.md

@@ -1,4 +1,4 @@
-# Meta Ads Agentic Skill
+# Meta Ads Agentic Skill
 
 <img width="1376" height="768" alt="meta-ads-skill" src="https://github.com/user-attachments/assets/baf2509b-0ee0-41ca-9555-3ad350a6824c" />
 
@@ -25,3 +25,69 @@ 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!
+
+## Overview
+
+The **Meta Ads Skill** is a comprehensive, production-ready  skill designed to give LLMs and AI agents expert-level capabilities to orchestrate the official **Meta Ads Python CLI**.
+
+By using this skill, an agent transforms into an **Expert Media Buyer**. It will know exactly how to explore ad structures, troubleshoot campaign performance (like CPA spikes), discover new audiences, and format massive Meta APIs JSON payloads into beautiful, readable markdown reports.
+
+---
+
+## For Agents: How to Use This Skill Efficiently
+
+This skill is designed using a **Progressive Disclosure (Hub-and-Spoke)** architecture to maximize context window efficiency:
+
+1. **The Hub (`SKILL.md`)**: The primary entry point. It provides strict guardrails, safety protocols, and the authentication troubleshooting workflow.
+2. **The Spokes (`references/`)**: 
+   - When you need to perform a specific task (e.g., investigating a CPA spike), read `references/workflows.md` for the exact step-by-step orchestration strategy.
+   - When presenting data to the user, read `references/report_templates.md` to strictly follow the required Markdown layout.
+
+###  Strict Agent Guardrails
+* **Context Protection**: ALWAYS default to `time_range="last_7d"` for insights. ALWAYS use `limit=10` for listing campaigns/adsets initially.
+* **Safety First**: NEVER execute state-changing tools (`create_campaign`, `update_campaign`) without explicitly showing the parameters to the user and waiting for their affirmative confirmation.
+
+---
+
+## Installation & Setup
+
+To use this skill, you must install the official Meta Ads CLI and configure your credentials.
+
+### 1. Install the CLI
+The skill relies on the `meta-ads` Python package:
+```bash
+pip install meta-ads
+```
+
+### 2. Authentication (System User Token)
+The CLI uses a **System User Access Token** for authentication. 
+1. Generate a System User Token in your [Meta Business Suite](https://business.facebook.com/settings/system-users).
+2. Ensure the token has `ads_management`, `ads_read`, and `read_insights` permissions.
+3. Set the following environment variables on your machine:
+
+```bash
+export ACCESS_TOKEN="your_system_user_access_token"
+export AD_ACCOUNT_ID="act_your_ad_account_id"
+```
+
+---
+
+## Skill Repository Structure
+
+When you deploy this skill, the structure will look like this:
+
+```text
+meta-ads-skill/
+ SKILL.md                          # The core router & guardrails
+ references/
+    report_templates.md           # Standardized markdown report structures
+    workflows.md                  # Orchestration strategies (e.g., CPA troubleshooting)
+```
+
+## Supported Commands
+
+This skill orchestrates the `meta-ads` CLI using a noun-verb structure:
+* **Campaigns**: `meta ads campaign list`, `meta ads campaign create`
+* **Ad Sets**: `meta ads adset list`
+* **Ads**: `meta ads ad list`
+* **Insights**: `meta ads insights get`

package/skills/meta-tribeV2-skill/README.md

@@ -1,4 +1,4 @@
-# Meta Tribe Skill
+# Meta Tribe Skill
 
 AI Skill that uses Meta's TRIBE v2 fMRI Model to analyze the neuroscience of video hooks, reels, and scripts. 
 
@@ -21,8 +21,6 @@ This skill provides the infrastructure to host the massive 80GB TRIBE v2 model p
 
 ## Install
 
-## Install
-
 ### Video Tutorial
 Watch this quick video to see how it's done:
 
@@ -40,3 +38,66 @@ 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!
+
+---
+
+## Deployment Options
+
+Because TRIBE v2 requires a massive amount of VRAM (24GB for text, up to 80GB for video), we offer 3 different deployment options so anyone can use it, regardless of budget or technical expertise.
+
+### 1. Google Colab (Zero Cost, Decoupled)
+Best for users without a cloud budget. Colab provides free T4 GPUs.
+* How it works: We use a decoupled architecture. You run the heavy AI inference in a Colab Notebook, which outputs a preds.npy prediction file. You then run a local script on your laptop to generate the report.
+* Setup:
+  1. Open Google Colab and upload the script from scripts/colab_inference.py into a new Notebook.
+  2. Run the notebook. It will output preds.npy and segments.json.
+  3. Download those files to your machine and run: `python scripts/local_analyze.py --preds preds.npy`. This will output a text report and an ASCII terminal graph showing the engagement peaks and valleys.
+
+### 2. RunPod (Serverless, Pay-per-second)
+Best for production agents and developers. You only pay for the seconds the model is running.
+* How it works: We provide a RunPod Handler and a custom Dockerfile that caches the 80GB model inside the image.
+* Setup:
+  1. Build the Docker image using server/Dockerfile.runpod: docker build -f Dockerfile.runpod -t tribe-runpod .
+  2. Push the image to Docker Hub or GHCR.
+  3. Create a new RunPod Serverless Endpoint using your image URL.
+  4. Point your AI Agent to your RunPod Endpoint URL.
+
+### 3. AWS EC2 Persistent (Enterprise, BYO-Compute)
+Best for heavy, continuous usage. 
+* How it works: Automatically provisions an AWS g5.12xlarge instance (4x A10G GPUs) and runs a FastAPI server.
+* Setup:
+  1. Ensure your AWS account has a vCPU quota limit of at least 48 for "Running On-Demand G and VT instances".
+  2. Run bash scripts/launch_persistent.sh to provision the instance.
+  3. Run export HF_TOKEN="your_token" followed by bash scripts/deploy_to_persistent.sh to build and launch the Docker API.
+
+#### AWS GPU Lifecycle & Estimated Costs
+Running the `g5.12xlarge` instance (4x A10G GPUs) provides incredible speed but costs **$7.09 per hour** on On-Demand pricing. It is crucial to manage this lifecycle.
+1. **Launch:** Run `bash scripts/launch_persistent.sh` (Takes ~3 minutes).
+2. **Analyze:** Run your videos through the API.
+3. **Terminate:** When you are completely finished for the day, you MUST terminate the instance to stop billing.
+   - Run `aws ec2 describe-instances --filters "Name=instance-state-name,Values=running"` to find your Instance ID.
+   - Run `aws ec2 terminate-instances --instance-ids <YOUR_INSTANCE_ID>`.
+   - *Do not just "stop" the instance if you don't want to pay for EBS Volume storage costs overnight. Terminate it.*
+
+---
+
+## HuggingFace Authentication (Required for all methods)
+
+TRIBE v2 relies on meta-llama/Llama-3.2-3B, which is a Gated Model.
+1. Create a HuggingFace account.
+2. Go to the Llama 3.2 3B page and TRIBE v2 page and agree to Meta's license terms.
+3. Generate a HuggingFace Access Token (Read permissions) at huggingface.co/settings/tokens.
+4. Supply this token via the HF_TOKEN environment variable.
+
+---
+
+## The Neuroscience of the Engagement Report
+
+The AI agent will read the raw API output and translate the neuroscience into plain English for you:
+
+* VAN (Ventral Attention Network): Translated to "Is this surprising enough to stop a scroll?". High VAN means the content is novel and creates a pattern interrupt.
+* DMN (Default Mode Network): Translated to "Will people get bored and tune out?". High DMN is bad. It means the brain is wandering. The AI uses this to identify "Cut Candidates" in your video.
+* DAN (Dorsal Attention Network): Translated to "Are people actively following along?". High DAN means strong logical focus.
+* Limbic Network: Translated to "Does this make people feel something?". High Limbic means strong emotional response.
+
+Check out the [Results Showcase](results_showcase.md) for actual examples of Neuro-Marketing reports generated by this skill.

package/skills/newsletter-digest/README.md

@@ -1,4 +1,4 @@
-# newsletter-digest
+# newsletter-digest
 
 <img width="1280" height="640" alt="newsletter-digest" src="https://github.com/user-attachments/assets/cb2879ae-eb5c-4727-a1a2-47b4462a699b" />
 
@@ -28,3 +28,144 @@ 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 RSS/Atom feed list from `feeds.json`
+- Fetches all articles published in the last 7 days (configurable)
+- Deduplicates across feeds and sorts by date
+- Uses Gemini to synthesize a digest in your chosen format
+- Publishes to Ghost as a draft or live post
+- Outputs formatted Markdown for Substack, Notion, or any other platform
+
+## Digest Formats
+
+| Format | Use When | Target Length |
+|--------|----------|---------------|
+| Weekly Roundup | General digest covering top stories across all feeds | 350-500 words |
+| Topic Deep Dive | Focused issue on a single topic (AI, security, etc.) | 450-650 words |
+| Curated Picks | 5 selected articles with editorial context | 250-350 words |
+
+## Requirements
+
+| Requirement | Purpose | Where to Get It |
+|------------|---------|-----------------|
+| GEMINI_API_KEY | Digest synthesis | https://ai.google.dev |
+| GHOST_URL + GHOST_ADMIN_KEY | Ghost publishing (optional) | Ghost Admin, Settings, Integrations |
+| Node.js 20+ | Running scripts | https://nodejs.org |
+
+Tavily is not required. The skill uses article excerpts from RSS feeds directly.
+
+## Setup
+
+### 1. Install dependencies
+
+```bash
+cd /path/to/newsletter-digest
+npm install
+```
+
+### 2. Configure environment variables
+
+```bash
+cp .env.example .env
+# Edit .env with your keys
+```
+
+### 3. Configure your feeds
+
+Edit `feeds.json` with the RSS feeds you want to monitor:
+
+```json
+[
+  { "url": "https://hnrss.org/frontpage", "name": "Hacker News" },
+  { "url": "https://feeds.feedburner.com/TheHackersNews", "name": "The Hacker News" },
+  { "url": "https://changelog.com/feed", "name": "Changelog" }
+]
+```
+
+The file ships with 5 example feeds. Replace them with your own.
+
+### 4. Set up Ghost publishing (optional)
+
+1. Go to Ghost Admin, Settings, Integrations
+2. Click "Add custom integration"
+3. Name it "newsletter-digest"
+4. Copy the Admin API Key (format: `key_id:secret`)
+5. Set `GHOST_ADMIN_KEY=key_id:secret` in `.env`
+6. Set `GHOST_URL=https://your-ghost-site.com` in `.env`
+
+## How to Use
+
+Generate a weekly digest:
+
+```
+"Generate a weekly digest from my RSS feeds"
+"Create this week's newsletter"
+"Summarize my feeds from the last 7 days"
+```
+
+Choose a specific format:
+
+```
+"Create a topic deep dive about AI agents from this week's news"
+"Generate a curated picks digest for this week"
+"Write a weekly roundup newsletter"
+```
+
+Extend the date window:
+
+```
+"Generate a digest from the last 14 days"
+"Not many articles this week, extend the window to 2 weeks"
+```
+
+Publish to Ghost:
+
+```
+"Generate this week's digest and publish it to Ghost as a draft"
+"Create the newsletter and publish it to Ghost"
+```
+
+Output for Substack:
+
+```
+"Generate a newsletter digest for Substack"
+"Create the digest and give me the Markdown version"
+```
+
+## Output
+
+| Output | Description |
+|--------|-------------|
+| HTML | Ready to paste into any CMS |
+| Markdown | For Substack, Notion, Hashnode |
+| Plain text | For email clients |
+| Ghost draft | Published automatically if configured |
+
+## Substack Note
+
+Substack has no public API. The skill outputs a Markdown version of the digest for you to paste directly into the Substack editor.
+
+## Project Structure
+
+```
+newsletter-digest/
+├── SKILL.md
+├── README.md
+├── .env.example
+├── package.json
+├── feeds.json            (your RSS feed list, edit this)
+├── evals/
+│   └── evals.json
+├── references/
+│   ├── digest-format.md  (format rules, length targets, attribution)
+│   └── output-template.md (HTML templates for all 3 formats)
+└── scripts/
+    ├── fetch-feeds.js    (RSS fetching, dedup, date filtering)
+    └── ghost-publish.js  (Ghost Admin API posting)
+```
+
+## License
+
+MIT

package/skills/noise-to-linkedin-carousel/README.md

@@ -79,24 +79,3 @@ Unlike simple text generators, this skill operates as a structured workflow:
 ## Contributing
 
 Pull requests to refine hook patterns, add new slide structures, or include helper scripts that refine raw transcripts are welcome.
-
-
-## 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/noise2blog/README.md

@@ -1,4 +1,4 @@
-# noise2blog
+# noise2blog
 
 <img width="1280" height="640" alt="noise2blog" src="https://github.com/user-attachments/assets/2359cff9-dfd4-4276-bb3e-4b6091ad6983" />
 
@@ -28,3 +28,104 @@ 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 any rough input: bullet points, rough notes, voice transcripts, tweet dumps, short drafts, or a URL
+- Detects the right blog post style automatically (Technical Tutorial, Case Study, Thought Leadership, Explainer)
+- Enriches claims with Tavily research when you set an API key (supporting data, verification)
+- Generates a Markdown post with no AI slop, no em dashes, no banned words
+- Formats frontmatter for Ghost, dev.to, Substack, or Hashnode on request
+
+## Requirements
+
+| Requirement | Purpose | How to Set Up |
+|------------|---------|--------------|
+| Google Gemini API key | Generates the blog post | aistudio.google.com, Get API key |
+| Tavily API key (optional) | Enriches claims with research | app.tavily.com, API Keys |
+
+No LLM backend to run. The agent calls the Gemini API directly.
+
+## Setup
+
+```bash
+cp .env.example .env
+```
+
+Edit `.env` and fill in:
+- `GEMINI_API_KEY` (required)
+- `TAVILY_API_KEY` (optional, enables research enrichment)
+
+## Blog Post Styles
+
+| Style | Use When | Signals in Your Input |
+|-------|----------|----------------------|
+| Technical Tutorial | Step-by-step guide, code walkthrough | Numbered steps, commands, "how to" |
+| Case Study | Build log, before/after story, lessons learned | Specific results, journey narrative |
+| Thought Leadership | Opinion piece, counterintuitive argument | Strong claim, debate framing |
+| Explainer | Explaining a concept or tool to newcomers | Definition-first, comparisons |
+
+The agent detects the style automatically. Override it with: "Use Thought Leadership style" or "Make this a tutorial".
+
+## How to Use
+
+From pasted notes:
+
+```
+"Write a blog post from these notes: [paste your content]"
+"Turn these bullet points into a blog post"
+"Expand this into an article"
+```
+
+From a voice transcript:
+
+```
+"Turn this transcript into a blog post: [paste transcript]"
+"Clean up this voice note and make it publishable"
+```
+
+From a tweet thread:
+
+```
+"Turn this tweet thread into a blog: [paste tweets]"
+"Expand this thread into a full article"
+```
+
+With style override:
+
+```
+"Write a thought leadership post from these notes"
+"Make this a technical tutorial"
+```
+
+With platform formatting:
+
+```
+"Write the post and format it for dev.to"
+"Give me Ghost frontmatter too"
+```
+
+## Output
+
+- Full blog post in Markdown (800-1,800 words)
+- Meta description (1-2 sentences)
+- Alternative title option
+- Platform-specific frontmatter on request
+
+## Project Structure
+
+```
+noise2blog/
+├── SKILL.md
+├── README.md
+├── .env.example
+├── evals/
+│   └── evals.json
+└── references/
+    ├── blog-format.md
+    └── output-template.md
+```
+
+## License
+
+MIT