@opendirectory.dev/skills 0.1.65 → 0.1.67

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

@@ -1,4 +1,4 @@
-# product-update-logger
+# product-update-logger
 
 Tell the skill what your product shipped. It writes a polished, living `docs/changelog.md` entry and hands you a ready-to-use content package: tweet thread, LinkedIn post, email snippet, and one-liner.
 
@@ -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**.
@@ -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

@@ -1,4 +1,4 @@
-# producthunt-launch-kit
+# producthunt-launch-kit
 
 <img width="1280" height="640" alt="producthunt-launch-kit" src="https://github.com/user-attachments/assets/dc16bde9-9bc4-4022-94a8-a4db024cbd95" />
 
@@ -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

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

@@ -1,4 +1,4 @@
-# reddit-icp-monitor
+# reddit-icp-monitor
 
 <img width="1280" height="640" alt="reddit-icp-monitor" src="https://github.com/user-attachments/assets/8182b73f-1f8d-4812-9061-165fd8aeb0e8" />
 
@@ -28,3 +28,114 @@ 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 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

package/skills/reddit-post-engine/README.md

@@ -1,4 +1,4 @@
-# reddit-post-engine
+# reddit-post-engine
 
 <img width="1280" height="640" alt="reddit-post-engine" src="https://github.com/user-attachments/assets/2706f326-5fb9-46fc-851a-ec54ccf53f74" />
 
@@ -28,3 +28,100 @@ 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
+
+- Fetches the target subreddit's rules and top posts from Reddit's public API
+- Identifies the subreddit's tone and posting conventions
+- Drafts a title and body that match the community's style
+- Keeps product links out of the body (puts them in the first comment)
+- Optionally posts directly via Composio
+- Covers 7 common subreddits with specific playbooks
+
+## Requirements
+
+| Requirement | Purpose | How to Set Up |
+|------------|---------|--------------|
+| Gemini API key | Post drafting and tone matching | aistudio.google.com, Get API key |
+| Composio Reddit MCP (optional) | Direct posting | app.composio.dev |
+
+## Setup
+
+### 1. Configure environment variables
+
+```bash
+cp .env.example .env
+# Add GEMINI_API_KEY (required)
+# Add COMPOSIO_API_KEY if you want direct posting
+```
+
+### 2. Connect Reddit via Composio (optional)
+
+Direct posting requires a Composio account connected to Reddit OAuth:
+
+1. Get your Composio API key at app.composio.dev/settings
+2. Connect Reddit at app.composio.dev/app/reddit
+3. Add the MCP server to Claude Code:
+
+```bash
+claude mcp add --transport http reddit-composio \
+  "https://mcp.composio.dev/reddit/YOUR_COMPOSIO_API_KEY"
+```
+
+4. Verify: `claude mcp list` should show `reddit-composio`
+
+Without Composio, the skill drafts posts for manual copy-paste submission.
+
+## How to Use
+
+Draft a post for a specific subreddit:
+```
+"Help me post my project on r/SideProject"
+"Write a Reddit post for r/devops about my Kubernetes tool"
+"Draft something for r/startups: we hit $1k MRR"
+```
+
+With direct posting:
+```
+"Post my project to r/SideProject via Composio"
+```
+
+Multi-subreddit drafts:
+```
+"Draft posts for r/SideProject and r/indiehackers for my launch"
+```
+
+## Subreddit Playbook Summary
+
+| Subreddit | Tone | What Works |
+|-----------|------|------------|
+| r/devops | Technical, direct | Problem + solution + specific numbers |
+| r/SideProject | Personal, builder | Build story + honest state + link in comment |
+| r/startups | Business-focused | Lessons learned + metrics |
+| r/programming | Technical, skeptical | Novel approach + code examples |
+| r/ExperiencedDevs | Senior-level | Nuanced tradeoffs, no hand-holding |
+| r/indiehackers | Transparent | Revenue numbers, real story |
+| r/webdev | Friendly | What you built + how it works |
+
+## The 90/10 Rule
+
+Reddit detects promotional patterns. For your posts to land well, 90% of your Reddit activity should be genuine community contribution: answering questions, discussing topics, sharing interesting links. At most 10% should be posts about your own work.
+
+This skill drafts high-quality posts, but the underlying account reputation matters. New accounts with no history posting self-promotional content often get filtered.
+
+## Project Structure
+
+```
+reddit-post-engine/
+├── SKILL.md
+├── README.md
+├── .env.example
+├── evals/
+│   └── evals.json
+└── references/
+    └── subreddit-playbook.md
+```
+
+## License
+
+MIT

package/skills/schema-markup-generator/README.md

@@ -1,4 +1,4 @@
-# schema-markup-generator
+# schema-markup-generator
 
 ![schema-markup-generator](https://github.com/user-attachments/assets/4b5e5bfb-3c33-4a20-afff-59fda19196b4)
 
@@ -28,3 +28,111 @@ 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!
+
+## Schema Types Supported
+
+| Type | Use When |
+|------|----------|
+| FAQPage | Page has 2 or more visible question/answer pairs |
+| Article / BlogPosting | Page is a blog post or editorial article |
+| Organization | Page represents a company or institution |
+| Product | Page sells or describes a product with pricing |
+| WebSite | Homepage schema with optional sitelinks search |
+| HowTo | Page is a step-by-step guide with numbered steps |
+| BreadcrumbList | Page has visible breadcrumb navigation |
+| SoftwareApplication | Page describes a software tool or app |
+| LocalBusiness | Page represents a physical business location |
+
+The agent detects the right type automatically. A single page often gets multiple types (a blog post gets Article and BreadcrumbList, a homepage gets WebSite and Organization).
+
+## Requirements
+
+No LLM API key needed. The agent reads the page and generates the markup.
+
+Chrome is needed for JavaScript-rendered pages. For static HTML pages or when you paste HTML directly, Chrome is not required.
+
+A GitHub token is optional. Without it, the agent outputs the markup as text for you to paste manually.
+
+## Setup
+
+### 1. Start Chrome with remote debugging (for live URLs)
+
+```bash
+# macOS
+open -a "Google Chrome" --args --remote-debugging-port=9222
+
+# Linux
+google-chrome --remote-debugging-port=9222
+```
+
+### 2. Configure environment variables (optional)
+
+```bash
+cp .env.example .env
+# Add GITHUB_TOKEN if you want auto-PR support
+```
+
+## How to Use
+
+From a live URL:
+
+```
+"Generate schema markup for https://example.com/faq"
+"Add structured data to https://example.com/blog/my-post"
+"What schema markup does this page need? https://example.com/about"
+```
+
+From pasted HTML:
+
+```
+"Generate schema markup for this page: [paste HTML]"
+"Add JSON-LD to this HTML: [paste HTML]"
+```
+
+Targeting a specific type:
+
+```
+"Generate FAQPage schema for https://example.com/support"
+"Add Organization schema to our about page: https://example.com/about"
+"Generate Product schema for this page: https://example.com/products/pro"
+```
+
+With auto-PR:
+
+```
+"Generate schema markup for https://example.com/blog/post and open a GitHub PR"
+```
+
+## Output
+
+| Output | Description |
+|--------|-------------|
+| JSON-LD script block | One `<script type="application/ld+json">` block per schema type |
+| Placement instructions | Where to insert the block in your HTML or framework |
+| MISSING field list | Required fields not found on the page that you need to fill in |
+| GitHub PR | If GITHUB_TOKEN and GITHUB_REPO are configured and you confirm |
+
+## Validate Your Markup
+
+After applying the markup, validate it at:
+
+- Google Rich Results Test: https://search.google.com/test/rich-results
+- Schema.org Validator: https://validator.schema.org
+
+## Project Structure
+
+```
+schema-markup-generator/
+├── SKILL.md
+├── README.md
+├── .env.example
+├── evals/
+│   └── evals.json
+└── references/
+    ├── json-ld-spec.md
+    └── output-template.md
+```
+
+## License
+
+MIT