@opendirectory.dev/skills 0.1.0

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

@@ -0,0 +1,380 @@
+---
+name: producthunt-launch-kit
+description: ''
+compatibility: [claude-code, gemini-cli, github-copilot]
+author: OpenDirectory
+version: 1.0.0
+---
+
+# Product Hunt Launch Kit
+
+Generate every asset you need for a Product Hunt launch: listing copy, maker comment, and day-one social posts.
+
+---
+
+**Critical rule:** Product Hunt taglines are maximum 60 characters. Descriptions are maximum 500 characters. Never make factual claims that cannot be verified. Never mention competitor names. Never say "free" unless the product is permanently free (not just a trial).
+
+---
+
+## Step 1: Gather Product Details
+
+You need:
+
+- Product name
+- What it does (technical description, one sentence)
+- Primary use case and target user
+- Key differentiator from existing tools
+- Pricing: free, freemium, paid (starting price)
+- Open source: yes/no
+- Launch date (for scheduling context)
+- Any credentials, launch discount, or promo code to offer
+- 2-3 things that make it worth upvoting (honest reasons, not marketing)
+
+If any of these are missing, ask in one message before proceeding.
+
+Also check for project context files:
+
+```bash
+ls README.md 2>/dev/null && echo "README found"
+ls package.json 2>/dev/null && echo "package.json found"
+```
+
+If README.md exists, read the first 80 lines to extract product description and key features before asking questions.
+
+---
+
+## Step 2: Gallery Strategy
+
+Product Hunt requires screenshots. Most listings fail because of weak or missing gallery images. Plan these before writing copy.
+
+**Spec:** 1270×760px, PNG or JPG, max 8 images. The first image is the hero: it appears in feeds and cards.
+
+**Five-position framework:**
+
+| Position | Purpose | What to show |
+|----------|---------|-------------|
+| 1 (Hero) | First impression in feeds | Product in use, clean UI or terminal output, no text overlays |
+| 2 (Feature demo) | Show the core action | The thing that makes the product click: the "aha" moment |
+| 3 (Before/After) | Show the problem being solved | Split screen: messy/slow state vs. clean/fast state |
+| 4 (Social proof) | Build credibility | A real quote, a stat, or a before/after metric from a real user |
+| 5 (Technical differentiator) | Address skeptics | Architecture diagram, benchmark, or the unusual technical decision |
+
+If the product is a CLI tool or library, screenshots of terminal output work well. Annotate with arrows pointing to the important part.
+
+**Video (optional but high-impact):** A 60-90 second demo. Under 2 minutes. No voiceover required: screen capture with captions works.
+
+Tell the user: "Plan [N] gallery images before launch day. The hero image (position 1) is the most important. Here's what to capture for each position: [list above, customized for this product]."
+
+---
+
+## Step 3: Generate Tagline Variants
+
+The tagline appears directly under the product name on Product Hunt. It is the most read copy on your listing.
+
+**Hard limits:**
+- Maximum 60 characters (including spaces)
+- No period at the end
+- No hashtags
+- Do not start with the product name
+- No superlatives: "best", "fastest", "easiest", "most powerful"
+- No questions
+
+**Tagline formula:** `[Action verb] + [what it does] + [key differentiator]`
+
+Generate five tagline variants:
+
+1. **Outcome-first:** What the user achieves ("Ship docs without leaving your codebase")
+2. **Problem-first:** Names the pain that is solved ("No more copy-pasting between Figma and code")
+3. **Technical-angle:** For developer tools, lead with the tech ("SQLite to shareable web app in one command")
+4. **Comparison-free alternative:** Positions without naming competitors ("Git-native code review that works inside VS Code")
+5. **Plain-English:** No jargon, widest possible audience ("Turns any RSS feed into a daily email digest")
+
+After generating, count characters for each. Flag any that exceed 60 characters and revise.
+
+---
+
+## Step 4: Write the Listing Description
+
+The description appears below the tagline. Maximum 500 characters. It displays in search results and link previews.
+
+**Structure:**
+- Sentence 1: What it does and who it's for (specific)
+- Sentence 2: The key feature or technical approach that makes it work
+- Sentence 3 (optional): Pricing or availability
+
+**Description rules:**
+- 280-500 characters (shorter is fine; longer is truncated in previews)
+- Present tense throughout
+- No hype adjectives
+- No "I": write in third person or imperative ("Turns your...", "Connects to...", not "I built...")
+- No links (they do not render)
+- If open source, say so: "Open source and self-hostable."
+
+---
+
+## Step 5: Write the Maker Comment
+
+The maker comment is the most important driver of Product Hunt success. It is your first reply to your own post, posted within 60 seconds of launch.
+
+**Hard limits:**
+- 300-400 words
+- Must be posted within 60 seconds of the product going live
+- First-person, conversational
+- Tell the origin story
+- Acknowledge the obvious alternative and explain why you built this anyway
+- End with a specific question to invite comments
+
+**Structure:**
+
+**Opening (2-3 sentences):** Why you built this. The real story: what frustrated you, what gap you noticed, what problem you kept hitting. No "I'm thrilled to announce."
+
+**What it does (3-5 sentences):** Explain the core mechanic. What happens when someone uses it for the first time. Include one specific technical detail that shows you thought hard about the problem.
+
+**Who it's for (2-3 sentences):** Describe the specific person who will get the most value. Not "everyone who needs X": a specific persona: "If you're a solo dev who deploys on Friday afternoons and dreads..." or "If you've ever spent 20 minutes explaining the same PR context to three different reviewers..."
+
+**Honest caveat (1-2 sentences):** What it does NOT do. What is still rough. This builds trust and filters in the right early users.
+
+**Call for feedback (1-2 sentences):** Ask a specific question. "We haven't figured out the right approach for [specific edge case]: would love to know how you've handled it." or "The thing I'm most unsure about is [X]: does that matter to you?"
+
+---
+
+## Step 6: Generate All Assets with Gemini
+
+Write all assets in one Gemini call:
+
+```bash
+cat > /tmp/ph-launch-request.json << 'ENDJSON'
+{
+  "system_instruction": {
+    "parts": [{
+      "text": "You are writing Product Hunt launch copy. Generate all assets in sequence, clearly labeled. Rules: taglines max 60 chars, description max 500 chars, maker comment 300-400 words first-person. No marketing words: 'revolutionary', 'game-changing', 'powerful', 'robust', 'seamless', 'innovative', 'best-in-class', 'streamline'. No competitor names. No superlatives in taglines. Do not use em dashes. For social posts: tweets max 280 chars, no hashtags in tweet threads (they reduce signal quality on technical posts). LinkedIn post 150-300 words, professional but not stiff. Email sequence: 4 emails, each under 150 words, subject line under 50 chars. Output each asset with a clear header. No commentary between sections."
+    }]
+  },
+  "contents": [{
+    "parts": [{
+      "text": "PRODUCT_DETAILS_HERE"
+    }]
+  }],
+  "generationConfig": {
+    "temperature": 0.7,
+    "maxOutputTokens": 4096
+  }
+}
+ENDJSON
+
+curl -s -X POST \
+  "https://generativelanguage.googleapis.com/v1beta/models/gemini-2.0-flash:generateContent?key=$GEMINI_API_KEY" \
+  -H "Content-Type: application/json" \
+  -d @/tmp/ph-launch-request.json \
+  | python3 -c "import sys,json; d=json.load(sys.stdin); print(d['candidates'][0]['content']['parts'][0]['text'])"
+```
+
+Replace `PRODUCT_DETAILS_HERE` with all gathered context: product name, description, use case, differentiator, pricing, and any maker notes from Step 1.
+
+Request these assets in the prompt:
+1. Five tagline variants (with character counts)
+2. Listing description (with character count)
+3. Maker comment (300-400 words)
+4. Tweet thread for launch day (5-7 tweets, 280 chars each)
+5. LinkedIn post (150-300 words)
+6. Email sequence (4 emails: existing users, newsletter, day-of reminder, follow-up)
+
+---
+
+## Step 7: Self-QA
+
+Before presenting:
+
+**Taglines:**
+- [ ] All under 60 characters (count each)
+- [ ] None start with the product name
+- [ ] None contain superlatives
+- [ ] None contain marketing words
+
+**Description:**
+- [ ] Under 500 characters (count)
+- [ ] Third person or imperative voice (no "I")
+- [ ] No links
+
+**Maker comment:**
+- [ ] 300-400 words (count)
+- [ ] Opens with the real origin story (not "I'm excited to...")
+- [ ] Includes one honest caveat
+- [ ] Ends with a specific question
+- [ ] No marketing language
+- [ ] No em dashes
+
+**Tweet thread:**
+- [ ] Each tweet under 280 characters (count)
+- [ ] No hashtags
+- [ ] First tweet is the hook: most compelling thing about the product
+
+If any item fails, revise before presenting. Do not present drafts with QA failures.
+
+---
+
+## Step 8: Present the Full Launch Kit
+
+Present in this exact order:
+
+```
+## Product Hunt Launch Kit: [Product Name]
+
+---
+
+### Taglines (choose one)
+1. [tagline]: [char count]
+2. [tagline]: [char count]
+3. [tagline]: [char count]
+4. [tagline]: [char count]
+5. [tagline]: [char count]
+
+**Recommendation:** [one-sentence reason to prefer tagline X]
+
+---
+
+### Listing Description
+[description text]
+[char count] / 500
+
+---
+
+### Maker Comment (post within 60 seconds of launch)
+[maker comment text]
+
+---
+
+### Launch Day Tweets
+Tweet 1/6: [text]
+Tweet 2/6: [text]
+...
+
+---
+
+### LinkedIn Post
+[post text]
+
+---
+
+### Email Sequence
+
+**Email 1: Existing Users (send 1 week before)**
+Subject: [subject]
+[body]
+
+**Email 2: Newsletter / Audience (send day before)**
+Subject: [subject]
+[body]
+
+**Email 3: Day-of Reminder (send at 12:01 AM PST)**
+Subject: [subject]
+[body]
+
+**Email 4: Follow-up (send 48 hours after launch)**
+Subject: [subject]
+[body]
+
+---
+
+### Self-Hunt vs. Top Hunter Decision
+
+Answer these questions to decide:
+
+| Question | Self-Hunt | Get a Hunter |
+|----------|-----------|--------------|
+| Do you have 500+ Twitter/LinkedIn followers in your target audience? | Yes | No |
+| Does your product have an existing user base to rally? | Yes | No |
+| Is your product technical and you have a personal brand in dev communities? | Yes | No |
+| Is this your first launch with no audience yet? | No | Yes |
+| Does a top hunter (500+ followers on PH) already use your product? | No | Yes |
+
+If 3+ answers point to "Get a Hunter": reach out to hunters at least 2 weeks before launch day. Frame the ask as sharing something you built that they would genuinely want to know about: not asking for a favor.
+
+---
+
+### 30-Day Pre-Launch Preparation
+
+**Day 30-21: Teaser Phase**
+- [ ] Post a "building in public" update on Twitter/LinkedIn: what problem you are solving and why
+- [ ] Identify 3-5 hunters with 500+ PH followers who match your product category
+- [ ] Start building a supporter list (everyone who would upvote on launch day): team, users, investors, friends in tech
+- [ ] Set up a simple "notify me on launch" page (even a TypeForm or Google Form)
+
+**Day 20-8: Asset Phase**
+- [ ] Capture all 5 gallery images at 1270×760px (see gallery strategy above)
+- [ ] Record 60-90 second demo video if applicable
+- [ ] Draft all copy from this kit: tagline, description, maker comment, social posts, emails
+- [ ] Send Email 1 (existing users) at Day 8
+
+**Day 7-2: Final Prep**
+- [ ] Send Email 2 (newsletter) at Day 2
+- [ ] Message your supporter list directly (Slack, DM, email): not a mass blast, personal messages
+- [ ] Schedule tweet thread and LinkedIn post
+- [ ] Do a dry run: check PH listing preview, verify all gallery images display correctly
+- [ ] Confirm maker comment is under 400 words and saved somewhere you can paste instantly
+
+**Day 1: Launch Day**
+- [ ] Post goes live at 12:01 AM PST
+- [ ] Send Email 3 (day-of reminder) immediately after going live
+- [ ] Maker comment posted within 60 seconds of launch
+- [ ] Tweet thread posted in the first 30 minutes
+- [ ] LinkedIn post published
+- [ ] Reply to every comment within 2 hours: PH algorithm rewards active makers
+- [ ] Do not ask for upvotes directly: ask people to "check it out" or "share feedback"
+- [ ] DM your supporter list with a direct link: not "go upvote" but "we just launched, would love your thoughts"
+- [ ] First comment with any promo code posted within 5 minutes of launch
+
+**Day 2: Follow-Up**
+- [ ] Send Email 4 (48-hour follow-up) with results and thank-you
+- [ ] Post a results update on Twitter/LinkedIn: upvotes, comments, lessons
+- [ ] Reply to any overnight comments you missed
+
+---
+
+### Upvote Benchmarks
+
+| Upvotes | Outcome |
+|---------|---------|
+| 50-100 | Listed but not front page |
+| 200-400 | Competitive front page placement |
+| 500-800 | Top 5 of the day |
+| 800+ | Product of the Day |
+| 1500+ | Product of the Week contender |
+
+First-hour velocity matters more than final count. 100 upvotes in the first hour beats 400 spread over 24 hours.
+
+---
+
+### Hour-by-Hour Launch Day Timeline
+
+| Time (PST) | Action |
+|------------|--------|
+| 12:01 AM | Post goes live. Do not schedule: be awake and click manually. |
+| 12:02 AM | Maker comment posted (have it in clipboard, paste and submit immediately) |
+| 12:05 AM | First comment (promo code or context) posted |
+| 12:15 AM | Tweet thread live |
+| 12:30 AM | LinkedIn post live |
+| 12:30 AM | Personal DMs to your 10 most-engaged supporters |
+| 1:00 AM | Check for first comments, reply to all |
+| 7:00 AM | Morning US traffic peak. Check ranking. Reply to overnight comments. |
+| 9:00 AM | Send Email 3 (day-of reminder) if you held it for morning send |
+| 12:00 PM | Midday check. Reply to all comments. Post a "midday update" tweet if trending. |
+| 5:00 PM | Evening US traffic peak. Final push to supporter list if needed. |
+| 11:59 PM | Results final. Screenshot your placement. |
+
+---
+
+### Launch Checklist
+- [ ] Post goes live at 12:01 AM PST on launch day (manual click, not scheduled)
+- [ ] Maker comment copied to clipboard, posted within 60 seconds of launch
+- [ ] Supporter list of 200+ people ready to message personally on launch day
+- [ ] Gallery images and video (if any) uploaded and previewed before launch
+- [ ] All 4 emails drafted and scheduled
+- [ ] Reply to every comment on launch day: PH rewards active makers
+- [ ] Do not ask for upvotes directly: ask people to "check it out" or "share feedback"
+- [ ] First comment (with any promo code) posted within 5 minutes of launch
+```
+
+
+
+

package/skills/producthunt-launch-kit/evals/evals.json

@@ -0,0 +1,35 @@
+{
+  "skill_name": "producthunt-launch-kit",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Generate a Product Hunt launch kit for my product: Replyflow. It drafts personalized cold email replies using AI. Target user: sales reps who get 50+ emails a day. Freemium: free for 10 replies/month, $29/month unlimited. I'm launching next Tuesday.",
+      "expected_output": "Agent gathers all required context (has enough from the prompt). Generates: 5 tagline variants all under 60 characters with character counts shown, listing description under 500 characters, maker comment 300-400 words opening with origin story not 'Hi PH!', tweet thread of 5-7 tweets each under 280 characters with no hashtags, LinkedIn post 150-300 words, 4-email sequence with subject lines under 50 chars. All copy avoids marketing adjectives. Maker comment includes honest caveat and ends with specific question. Launch checklist included at end.",
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "Write my Product Hunt tagline. Product: Doppler: a secrets manager that syncs env vars across environments.",
+      "expected_output": "Agent generates 5 tagline variants. All are under 60 characters (agent counts each one). None start with 'Doppler'. None contain adjectives like 'powerful', 'simple', 'easy'. Each follows a different formula: outcome-first, problem-first, technical-angle, comparison-free alternative, plain-English. Agent recommends one with a one-sentence reason. All variants describe what Doppler does, not what it is.",
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "Write my maker comment for Product Hunt. My product is Raycast, a launcher app for Mac.",
+      "expected_output": "Agent writes maker comment that is 300-400 words. Does NOT open with 'Hi Product Hunt!' or 'Thrilled to announce'. Opens with origin story or personal motivation. Includes at least one technical detail about how it works. Identifies who should NOT use it or what it does not do. Ends with a specific question for the community. No marketing language. No em dashes. Reads like a thoughtful HN-style comment, not a press release.",
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "Generate a Product Hunt kit. My README is attached.",
+      "expected_output": "Agent reads README.md to extract: product name, what it does, key features, pricing, tech stack. Asks only for information not found in the README (typically: personal motivation/origin story, launch discount if any, specific launch date). Does not re-ask for information visible in the file. Generates full kit using README + user answers. All copy respects the 60/500 char limits.",
+      "files": ["README.md"]
+    },
+    {
+      "id": 5,
+      "prompt": "Write a Product Hunt description that says our tool is free.",
+      "expected_output": "Agent checks what 'free' means in context. If the product has paid tiers, flags this: 'You mentioned free: does the product have paid plans too? If so, I'll use \"Free to start\" instead of \"free\" to avoid misleading PH visitors.' If the product is genuinely permanently free, writes 'Free and open source' or similar. Never writes 'free' when the context indicates freemium. Explains the reason for the distinction.",
+      "files": []
+    }
+  ]
+}

package/skills/producthunt-launch-kit/references/copy-rules.md

@@ -0,0 +1,124 @@
+# Product Hunt Copy Rules
+
+## Tagline
+
+**The tagline is the second thing people read after the product name.**
+
+It appears:
+- Under the product name on the listing
+- In Twitter/X cards when the listing is shared
+- In email digests Product Hunt sends to subscribers
+
+**Hard constraints:**
+- 60 characters maximum (enforced by PH)
+- No period at the end
+- Do not start with the product name (it appears just above already)
+- No hashtags
+
+**What makes a tagline work:**
+
+It names a specific action or outcome. Not what the product IS: what it DOES.
+
+Good:
+- "Turn changelogs into product announcements" (60 chars)
+- "Open source Heroku alternative built on Kubernetes" (51 chars)
+- "Ship faster by keeping your docs next to your code" (52 chars)
+
+Bad:
+- "The best tool for developer productivity" (adjective, vague)
+- "A powerful platform for modern teams" (filler words, no specifics)
+- "Your new favorite way to manage tasks" (second-person, sounds like an ad)
+
+**Formula:** `[Active verb] + [specific object] + [optional context or differentiator]`
+
+Count characters before submitting. The submission form will reject anything over 60.
+
+---
+
+## Description
+
+**The description appears below the tagline. Maximum 500 characters.**
+
+This is your elevator pitch. It has to work in the notification email, in search results, and on the listing page.
+
+**Structure:**
+1. What it does and who it's for (specific)
+2. Key capability or technical differentiator
+3. Pricing or availability (optional but helpful)
+
+**Rules:**
+- Third person or imperative voice
+- No "I" or "we" (save that for the maker comment)
+- No links (they do not render in the description field)
+- No list formatting (it does not render well in all contexts)
+- 280-500 characters is the ideal range
+- Present tense
+
+Good example (312 chars):
+> Datasette is a tool for exploring and publishing data. It helps data journalists, scientists, and developers share SQLite databases as interactive websites. Open source. Works with any SQLite file. Deploy to any server in minutes.
+
+Bad example:
+> We built this amazing tool that will completely change how you work with data! Our powerful platform makes it easy for anyone to share data in a beautiful, seamless, innovative way!
+
+---
+
+## Maker Comment
+
+**The maker comment is the single highest-leverage action on launch day.**
+
+PH ranks products partly on engagement. A maker who responds to every comment in the first two hours sends a strong signal.
+
+**Mechanics:**
+- Post it as a comment on your own listing, within 60 seconds of launch
+- This is not the time for polished marketing copy: write like a human
+- It will be the first comment on the listing
+
+**What the comment should contain:**
+
+1. Why you built it (the honest version, not the press release version)
+2. The core mechanic: what happens when someone uses it
+3. A specific technical decision or tradeoff you made
+4. Who should NOT use it (or what it does not do): this builds trust
+5. A specific question for the community
+
+**What kills maker comments:**
+- "Hi PH! Thrilled to share..." (sounds like an announcement, not a human)
+- "Our product is the best solution for..." (sounds like marketing)
+- Not responding to any comments for the first 2 hours
+- Asking people to upvote ("if you like this, please upvote!")
+
+**Tone reference:** Think of the tone of a thoughtful comment on Hacker News. Not a pitch. Not a tutorial. A practitioner talking to peers.
+
+---
+
+## Promo Codes
+
+If you have a promo code for PH users:
+- Post it in a separate comment after the maker comment (not in the maker comment itself)
+- Format: "Product Hunt special: use [CODE] for [discount/free tier/extended trial]"
+- Include expiry date if there is one
+- Lifetime deals tend to perform well on PH
+
+---
+
+## What NOT to Do
+
+**Vote ring:** Do not ask friends, Discord members, Slack groups, or anyone else to upvote your launch. PH detects coordinated voting. It will bury your product. "Vote rings" are the fastest way to get your listing penalized.
+
+**Correct ask:** "We launched on PH today: would love your feedback" or "Check it out if it's relevant to you." That is fine. Asking specifically for upvotes is not.
+
+**Hashtags:** Product Hunt does not use hashtags. Do not include them in copy.
+
+**Competitor naming:** Do not name competitors in your listing. Focus on what you do, not what you are not.
+
+**Free vs freemium:** If it has a free tier but also paid plans, say "Free to start" or "Free tier available." Do not say "free" unless it is permanently, completely free.
+
+---
+
+## Launch Timing
+
+- Products launch at 12:01 AM Pacific Time on the selected day
+- The first 4 hours determine front page placement
+- Tuesday, Wednesday, Thursday are the highest-traffic days
+- Avoid holiday weeks and major tech conference days (everyone is heads-down)
+- Notify your audience the night before so they are ready at launch time

package/skills/reddit-icp-monitor/.env.example

@@ -0,0 +1,16 @@
+# reddit-icp-monitor — Environment Variables
+# ============================================
+# Gemini is required. Reddit credentials are optional (higher rate limit).
+
+# Required: Google Gemini API key for relevance scoring and reply drafting
+# Get it: aistudio.google.com, Get API key
+GEMINI_API_KEY=your_gemini_api_key_here
+
+# Optional: Reddit OAuth credentials for 60 RPM (vs 10 RPM with public endpoints)
+# Register a "script"-type app at: reddit.com/prefs/apps
+# Select "script" app type, fill in a redirect URI (http://localhost works)
+# Note: App approval may take several days as of November 2025
+REDDIT_CLIENT_ID=your_reddit_client_id_here
+REDDIT_CLIENT_SECRET=your_reddit_client_secret_here
+REDDIT_USERNAME=your_reddit_username_here
+REDDIT_PASSWORD=your_reddit_password_here

package/skills/reddit-icp-monitor/README.md

@@ -0,0 +1,117 @@
+# reddit-icp-monitor
+
+<img width="1280" height="640" alt="reddit-icp-monitor" src="https://github.com/user-attachments/assets/8182b73f-1f8d-4812-9061-165fd8aeb0e8" />
+
+
+Watch subreddits for people describing the exact problem you solve. Score each post for ICP relevance. Draft a helpful, non-spammy reply for every high-signal match.
+
+## What It Does
+
+- Reads your ICP definition from docs/icp.md (or asks 3 questions to build it)
+- Searches specified subreddits for posts matching your pain point phrases
+- Scores each candidate post 1-5 using Gemini (how clearly does this person have the problem you solve?)
+- Drafts a helpful reply for every post scoring 4 or 5, in the correct mode (vent, how-do-you, or tool recommendation)
+- Enforces a hard rule: replies never name your product unless the post explicitly asks for tool recommendations
+- Saves the full report to docs/reddit-intel/YYYY-MM-DD.md
+
+## Requirements
+
+| Requirement | Purpose | How to Set Up |
+|------------|---------|--------------|
+| Gemini API key | Relevance scoring and reply drafting | aistudio.google.com, Get API key |
+| Reddit credentials (optional) | Higher rate limit (60 RPM vs 10 RPM) | reddit.com/prefs/apps, create a script app |
+
+Reddit credentials are optional. The skill uses Reddit's public JSON endpoints by default, which require no setup and support 10 RPM. That is enough for most monitoring sessions.
+
+## Setup
+
+```bash
+cp .env.example .env
+```
+
+Fill in:
+- `GEMINI_API_KEY` (required)
+- Reddit credentials (optional, see OAuth Upgrade below)
+
+## How to Use
+
+First run (no docs/icp.md yet):
+```
+"Monitor Reddit for my ICP signals"
+"Scan subreddits for people who need my product"
+```
+
+The skill asks 3 questions to build your ICP definition and saves it to docs/icp.md.
+
+Subsequent runs (docs/icp.md exists):
+```
+"Check Reddit for buying signals"
+"Run the Reddit ICP monitor for this week"
+"Find ICP posts from the last month"
+```
+
+Specify a time window:
+```
+"Monitor Reddit for ICP signals from the last 24 hours"
+"Check Reddit for this month's pain point posts"
+```
+
+## Output
+
+Each run produces a report with:
+- All subreddits monitored and time window
+- Each high-signal post: title, URL, upvotes, signal quote, matched keyword, post type
+- A drafted reply for each match (2-5 sentences, mode-appropriate)
+- A list of subreddits that returned 0 results (for tuning)
+
+Reports are saved to `docs/reddit-intel/YYYY-MM-DD.md`.
+
+## Reply Modes
+
+The skill classifies each post and drafts in the appropriate mode:
+
+| Mode | Post Type | Can Name Product? |
+|------|-----------|------------------|
+| Mode 1 | Venting / frustration | Never |
+| Mode 2 | "How do you handle X?" | Never |
+| Mode 3 | "What tool does X?" | Yes, with one alternative |
+
+## Choosing Good Subreddits
+
+**Where to monitor (people describing problems):**
+- r/devops, r/ExperiencedDevs, r/sysadmin: engineers asking operational questions
+- r/startups, r/SaaS, r/EntrepreneurRideAlong: founders and operators venting about scaling
+- r/sales, r/marketing: GTM practitioners asking how others handle things
+
+**Where not to monitor:**
+- Topic subreddits (r/programming, r/MachineLearning): discussions, not pain points
+- Your product's own subreddit: not monitoring your own community
+- Broad consumer subreddits: not your B2B ICP
+
+## OAuth Upgrade
+
+If you need more than 10 RPM (large subreddits or frequent runs):
+
+1. Go to reddit.com/prefs/apps and create a "script" app
+2. Note: app approval may take several days as of late 2025
+3. Fill in REDDIT_CLIENT_ID, REDDIT_CLIENT_SECRET, REDDIT_USERNAME, REDDIT_PASSWORD in .env
+
+With OAuth, the skill fetches a Bearer token at session start and uses the `oauth.reddit.com` endpoint for 60 RPM.
+
+## Project Structure
+
+```
+reddit-icp-monitor/
+├── SKILL.md
+├── README.md
+├── .env.example
+├── evals/
+│   └── evals.json
+└── references/
+    ├── icp-format.md
+    └── reply-rules.md
+```
+
+## License
+
+MIT