@opendirectory.dev/skills 0.1.0

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

@@ -0,0 +1,303 @@
+---
+name: reddit-post-engine
+description: Writes and optionally posts a Reddit post for any subreddit, following that subreddit's specific culture and rules. Drafts a title, body, and first comment using the 90/10 rule. Uses Composio Reddit MCP for optional direct posting. Use when asked to post on Reddit, draft a Reddit post, share a project on Reddit, write a subreddit post, or launch something on Reddit. Trigger when a user says "post this on Reddit", "write a Reddit post for r/...", "help me launch on Reddit", "draft something for Reddit", or "how do I share this on Reddit without getting banned".
+compatibility: [claude-code, gemini-cli, github-copilot]
+author: OpenDirectory
+version: 1.0.0
+---
+
+# Reddit Post Engine
+
+Draft a Reddit post that fits the subreddit's culture. Optionally post it via Composio.
+
+---
+
+**Critical rule:** Never post without confirming subreddit rules. Never include product links in the body: put them in the first comment only if appropriate. Follow the 90/10 rule: your post should add value independent of any product mention.
+
+**Anti-spam rule:** Posts that are primarily promotional will be removed and may get the account banned. The goal is to contribute to the community first. Product mentions go in the first comment, and only if the subreddit allows self-promotion.
+
+---
+
+## Step 1: Setup Check
+
+```bash
+echo "GEMINI_API_KEY: ${GEMINI_API_KEY:+set}"
+# Check if Composio Reddit MCP is connected
+claude mcp list 2>/dev/null | grep -i reddit || echo "Composio Reddit MCP: not connected"
+```
+
+**If GEMINI_API_KEY is missing:**
+Stop. Tell the user: "GEMINI_API_KEY is required. Get it at aistudio.google.com. Add it to your .env file."
+
+**If Composio Reddit MCP is not connected:**
+Continue. The skill will draft posts but skip the posting step. Inform the user: "Composio Reddit MCP not connected: I'll draft your post for manual submission. To enable direct posting, see the setup instructions in README.md."
+
+---
+
+## Step 2: Gather Context
+
+You need:
+- Target subreddit (e.g., r/devops, r/startups, r/SideProject)
+- What you are sharing (project, article, question, discussion, tool)
+- One-sentence description of what it does
+- Why it's relevant to this specific subreddit's community
+- Whether you want a self-post (text) or link post
+
+If any of these are missing, ask in one message:
+
+"To draft your Reddit post, I need:
+1. Which subreddit? (e.g., r/devops, r/startups)
+2. What are you sharing? (project, article, tool, question)
+3. What does it do? (one sentence, technical)
+4. Why does this subreddit care about it specifically?"
+
+---
+
+## Step 3: Fetch Subreddit Rules and Culture
+
+**Fetch the subreddit's rules:**
+```bash
+curl -s \
+  -H "User-Agent: varnan-skills/1.0" \
+  "https://www.reddit.com/r/{SUBREDDIT}/about/rules.json" \
+  | python3 -c "
+import sys, json
+d = json.load(sys.stdin)
+rules = d.get('rules', [])
+for r in rules:
+    print(f'Rule: {r.get(\"short_name\", \"\")}')
+    print(f'Detail: {r.get(\"description\", \"\")[:200]}')
+    print()
+"
+```
+
+**Fetch recent top posts to understand tone and style:**
+```bash
+curl -s \
+  -H "User-Agent: varnan-skills/1.0" \
+  "https://www.reddit.com/r/{SUBREDDIT}/top.json?t=week&limit=10" \
+  | python3 -c "
+import sys, json
+d = json.load(sys.stdin)
+for p in d['data']['children'][:10]:
+    pd = p['data']
+    print(f'Score: {pd[\"score\"]} | Title: {pd[\"title\"][:100]}')
+"
+```
+
+Note patterns in the top posts:
+- Are titles questions or statements?
+- Do they lead with the technology or the outcome?
+- Are they personal ("I built...") or impersonal ("Tool for...")?
+- What format gets the most engagement in this subreddit?
+
+**Check subreddit sidebar for posting rules:**
+```bash
+curl -s \
+  -H "User-Agent: varnan-skills/1.0" \
+  "https://www.reddit.com/r/{SUBREDDIT}/about.json" \
+  | python3 -c "
+import sys, json
+d = json.load(sys.stdin)
+data = d.get('data', {})
+print('Public description:', data.get('public_description', '')[:300])
+print('Subscribers:', data.get('subscribers', 0))
+"
+```
+
+**Identify the subreddit type:**
+
+| Type | Examples | Post style |
+|------|----------|-----------|
+| Technical practitioner | r/devops, r/sysadmin, r/ExperiencedDevs | Technical specifics, no fluff, "I did X and learned Y" |
+| Startup/builder | r/startups, r/SideProject, r/indiehackers | Personal story, metrics, lessons learned |
+| General tech | r/programming, r/technology | News angle, discussion hook, controversial take |
+| Career | r/cscareerquestions, r/ITCareerQuestions | Question format, specific scenario, ask for experience |
+| Niche tool | r/vim, r/rust, r/golang | Deep technical content, code examples, benchmarks |
+
+Use the fetched rules and top posts to determine which style applies.
+
+---
+
+## Step 4: Draft the Post with Gemini
+
+Write the post content to a temp file and call Gemini:
+
+```bash
+cat > /tmp/reddit-post-request.json << 'ENDJSON'
+{
+  "system_instruction": {
+    "parts": [{
+      "text": "You are a developer who is active in the {SUBREDDIT} community. Write a Reddit post that fits this subreddit's culture. Rules: (1) Write in first person if it is a project or experience post. (2) Do NOT include any product links in the body: links go in the first comment only. (3) The post must add genuine value to the community independent of any product being shared. (4) Match the tone of top posts in this subreddit: {SUBREDDIT_TONE_NOTES}. (5) Title max 300 characters. (6) Body 150-400 words for text posts. (7) No marketing language: no 'game-changing', 'powerful', 'robust', 'seamless', 'innovative'. (8) If the post is about a tool the user built, use the 'I made...' or 'I built...' opener: it performs best on Reddit. (9) Output: title on first line, blank line, then body. No labels, no commentary. Do not use em dashes."
+    }]
+  },
+  "contents": [{
+    "parts": [{
+      "text": "POST_DETAILS_HERE"
+    }]
+  }],
+  "generationConfig": {
+    "temperature": 0.7,
+    "maxOutputTokens": 1024
+  }
+}
+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/reddit-post-request.json \
+  | python3 -c "import sys,json; d=json.load(sys.stdin); print(d['candidates'][0]['content']['parts'][0]['text'])"
+```
+
+Replace `POST_DETAILS_HERE` with:
+- Subreddit name and type
+- Top post patterns observed
+- What is being shared and why it's relevant
+- Key technical details
+- Builder's honest motivation
+
+---
+
+## Step 5: Draft the First Comment
+
+If the user has a product link or additional context to share, draft a first comment to post immediately after the post goes live.
+
+The first comment serves two purposes:
+1. Provide the link (which keeps the body link-free and feels less promotional)
+2. Add context that would be too promotional in the post body
+
+**First comment rules:**
+- Post this as the first reply to your own post, immediately after it goes live
+- Keep it under 100 words
+- Example format: "Link for those who want to check it out: [URL]: also happy to answer questions about [specific technical thing mentioned in the post]."
+- Only include the first comment if the subreddit allows self-promotion in comments
+- If the subreddit has a "No self-promotion" rule, omit the link entirely
+
+---
+
+## Step 6: Self-QA
+
+Check the draft before presenting:
+
+**Structure:**
+- [ ] Title does not exceed 300 characters
+- [ ] No links appear in the post body
+- [ ] Post opens in first person (for project/experience posts)
+- [ ] At least one specific technical detail or concrete number included
+- [ ] Post matches the tone of top posts observed in this subreddit (noted in Step 3)
+- [ ] Subreddit rules from Step 3 are not violated
+
+**Claude-ism detection: scan for these vocabulary categories and remove all instances:**
+
+| Category | Words to remove |
+|----------|----------------|
+| Filler intensifiers | incredibly, absolutely, certainly, definitely, essentially, fundamentally, literally, particularly, quite, rather, really, significantly, simply, truly, ultimately, very |
+| AI hedging | I should note, it's worth noting, it's important to note, as mentioned, as I noted |
+| Hype descriptors | game-changing, revolutionary, powerful, robust, seamless, innovative, best-in-class, cutting-edge, groundbreaking, remarkable |
+| Throat-clearing | In conclusion, in summary, to summarize, overall, first and foremost, last but not least |
+| Unnecessary connectors | Furthermore, moreover, additionally, however (at sentence start), thus, hence, thereby |
+| AI tells | This ensures that, This allows for, This helps to, This enables, delve, utilize, leverage, foster |
+
+If any appear: replace with a specific noun, verb, or number. "Very fast" becomes "runs in 12ms". "Powerful tool" becomes what it actually does.
+
+**Instant-delete phrase check: these patterns trigger Reddit spam filters or moderator removal:**
+
+- Any sentence that reads as an advertisement ("Try [Product] today", "Sign up now", "Get started free")
+- Phrases that imply you are not the builder ("I came across this great tool", "I found this amazing product")
+- First-person possession of users ("our users", "our customers") in subreddits where you have not established community presence
+- "I made X and you can use it to..." followed immediately by a link (promotional structure)
+- Superlatives without qualification ("the best way to...", "the only tool that...")
+- External links in post body (use first comment only)
+
+If any instant-delete phrases appear: revise the sentence entirely, not just swap words.
+
+---
+
+## Step 7: Adversarial Review
+
+Before presenting the final draft, run a 3-persona review. Each persona reads the post and finds ONE specific problem, quoting the exact text that triggers it.
+
+**Persona 1: The Skeptical Practitioner**
+This person has been in r/{SUBREDDIT} for years and has seen hundreds of product launches disguised as posts. Their read:
+- Does any sentence feel promotional even if not explicitly selling?
+- Does the post reveal genuine knowledge of the community's problems, or does it just talk about the product?
+- Is there any claim that a practitioner would roll their eyes at?
+
+State the one specific line they would flag and why.
+
+**Persona 2: The Moderator**
+This person enforces the rules fetched in Step 3. Their read:
+- Does the post technically comply with subreddit rules?
+- Is the ratio of self-promotion to community contribution acceptable?
+- Would they have seen this exact post structure removed before?
+
+State the one specific rule that is at risk of violation, or confirm it is clean.
+
+**Persona 3: The Target Reader**
+This is a non-builder community member who matches the subreddit's demographic. Their read:
+- Would they upvote this post even if they never use the product?
+- Is there a takeaway they can apply even if they skip the link in the first comment?
+- Does the opening sentence make them want to keep reading?
+
+State the one thing they would stop reading at, or confirm the post holds their attention.
+
+After all three personas report: apply any fixes. If no persona found a problem, state "Adversarial review: clean."
+
+---
+
+## Step 8: Post via Composio (Optional)
+
+If Composio Reddit MCP is connected and the user confirms they want to post:
+
+```
+Use the reddit-composio MCP tool REDDIT_CREATE_REDDIT_POST with:
+- subreddit: {SUBREDDIT_WITHOUT_r/}
+- title: {TITLE}
+- kind: "self"
+- text: {BODY}
+```
+
+**Before posting, confirm with the user:**
+"Ready to post to r/{SUBREDDIT}. Post title: '{TITLE}'. Shall I go ahead?"
+
+Only proceed after explicit confirmation.
+
+**After posting:**
+1. Note the post URL from the response
+2. If a first comment was drafted, post it immediately using the same MCP with the returned post ID
+
+**If posting fails (403, 429, or other error):**
+Present the draft for manual submission. Tell the user: "Direct posting failed ([error code]). Here is your post for manual submission. Copy-paste the title and body at reddit.com/r/{SUBREDDIT}/submit."
+
+---
+
+## Step 9: Present Output
+
+```
+## Reddit Post: r/{SUBREDDIT}
+
+### Title
+{title}
+
+### Body
+{body}
+
+### First Comment (post immediately after)
+{first comment, if applicable}
+
+---
+
+### Submission Notes
+- Post type: {self/link}
+- Best time to post: {peak hours for this subreddit: weekday mornings US time for most tech subreddits}
+- After posting: Reply to every comment in the first hour: early engagement signals quality to the algorithm
+- Karma note: {If account is new, note that some subreddits require minimum karma before posting}
+```
+
+If the post was already submitted via Composio, replace the output block with:
+```
+Post submitted: {reddit_post_url}
+```
+
+

package/skills/reddit-post-engine/evals/evals.json

@@ -0,0 +1,35 @@
+{
+  "skill_name": "reddit-post-engine",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Help me post my open source tool on r/devops. It's called Kargo: a Kubernetes deployment pipeline manager. Written in Go. It solves the problem of managing sequential deployments across multiple clusters without writing custom Argo CD app-of-apps configs.",
+      "expected_output": "Agent fetches r/devops subreddit rules and top posts. Notes the technical tone of the subreddit. Drafts a self-post with a title like 'I built Kargo – a deployment pipeline manager for Kubernetes without the app-of-apps complexity'. Body is technical, explains the problem, the approach, a specific tradeoff made. No links in body: link in first comment. Self-QA passes. Post fits r/devops practitioner tone (no marketing language, technical specifics included).",
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "Write a Reddit post for r/SideProject for my project: a Raycast extension that generates shell aliases from natural language descriptions. Built it because I kept forgetting my own aliases.",
+      "expected_output": "Agent fetches r/SideProject top posts. Notes the personal/build-story tone. Drafts post opening with 'I built...' opener. Story includes: why (kept forgetting aliases), what it does (natural language to shell alias), current state (Raycast extension, works for zsh/bash). No product links in body. First comment drafted with link. Post is 150-300 words. Conversational tone.",
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "Post to Reddit. Here is my project.",
+      "expected_output": "Agent recognizes missing required context: target subreddit, what the project does, why it is relevant to that community. Asks all four required questions in a single message before proceeding. Does not draft a post without knowing the target subreddit.",
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "I want to post on r/startups and r/SideProject and r/indiehackers at the same time. My SaaS just hit $1k MRR and I want to share the story.",
+      "expected_output": "Agent drafts three separate posts, one per subreddit, each adapted to the community's tone: r/startups version focuses on the business lessons and what drove MRR growth; r/SideProject version is more personal and celebrates the milestone; r/indiehackers version includes specific numbers and metrics (revenue, users, time to $1k MRR) because that community expects transparency. Advises staggering the posts (not same-day cross-posting) to avoid spam detection.",
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "Draft a Reddit post for my project and post it to r/devops via Composio.",
+      "expected_output": "Agent checks if Composio Reddit MCP is connected. If not connected: drafts the post and informs user how to set up Composio for direct posting (README instructions), presents post for manual submission. If connected: drafts post, shows preview, asks for explicit confirmation before posting. After confirmation, calls REDDIT_CREATE_REDDIT_POST with subreddit (without r/ prefix), title, kind='self', and text body. If posting succeeds, presents the post URL. If posting fails with 403/429, falls back to manual submission instructions.",
+      "files": []
+    }
+  ]
+}

package/skills/reddit-post-engine/references/subreddit-playbook.md

@@ -0,0 +1,156 @@
+# Subreddit Playbook
+
+Rules, tone, and post patterns for commonly used subreddits.
+
+---
+
+## r/SideProject
+
+**Audience:** Indie builders, hobbyist developers, side project enthusiasts
+
+**What works:**
+- "I built X in [timeframe]" opener
+- Share the build story, not just the product
+- Be honest about usage numbers and what is still rough
+- Mention if it is open source or free
+
+**What gets removed:**
+- Pure self-promotion with no story
+- Posts that feel like product pages
+- Repeated posts for the same project
+
+**Post format:** Self-post. Lead with the build story. Link in first comment.
+
+**Karma requirement:** None typically, but very new accounts get flagged
+
+---
+
+## r/startups
+
+**Audience:** Early-stage founders, VCs, operator types
+
+**What works:**
+- Share a lesson, not just a product
+- Questions about strategy, GTM, or fundraising do well
+- "We tried X and learned Y" posts outperform pure announcement posts
+- Traction numbers signal credibility
+
+**What gets removed:**
+- "I launched my startup" posts without a specific hook
+- Soliciting investment
+- Posts that are thinly veiled ads
+
+**Post format:** Self-post, 200-400 words. Lead with the non-obvious insight.
+
+---
+
+## r/devops
+
+**Audience:** SREs, platform engineers, DevOps practitioners
+
+**What works:**
+- Specific technical problem and how you solved it
+- Benchmark numbers, architecture diagrams
+- "How we reduced X by Y%" posts
+- Tool comparisons with real data
+
+**What gets removed:**
+- "Check out my tool" without technical depth
+- Posts that read like product marketing
+- Vague questions answerable by googling
+
+**Post format:** Self-post with technical depth. Code snippets encouraged.
+
+**Post tone:** Very direct. No fluff. Engineers here have low patience for marketing language.
+
+---
+
+## r/programming
+
+**Audience:** General developer community, CS nerds, broad technical interest
+
+**What works:**
+- Blog post or article link with an interesting angle in the title
+- Show posts for technically novel projects
+- Technical deep-dives
+- Controversial/contrarian takes on tech decisions
+
+**What gets removed:**
+- Job posts
+- Tutorial spam
+- Low-effort link posts without discussion value
+
+**Post format:** Link post for articles, self-post for discussion. Title should name the technical topic, not just the product.
+
+---
+
+## r/ExperiencedDevs
+
+**Audience:** Senior engineers and staff+ level developers
+
+**What works:**
+- Nuanced takes on engineering tradeoffs
+- "Career at X level looks like..." experience posts
+- Architecture decision retrospectives
+- Anything that shows you have been burned and learned
+
+**What gets removed:**
+- Beginner questions
+- "I just got my first job" posts
+- Pure self-promotion
+
+**Tone:** Skeptical audience. They will poke holes in your reasoning. Write defensively: acknowledge weaknesses before commenters do.
+
+---
+
+## r/indiehackers
+
+**Audience:** Solo founders, bootstrappers, people building profitable businesses without VC
+
+**What works:**
+- Revenue numbers (they love transparency)
+- "Month 6 update" style posts showing growth
+- Failed experiments and what you learned
+- "I quit my job to build X, here is where I am at" stories
+
+**What does not work:**
+- VC-backed startups positioning as indie
+- Posts without personal context
+- Generic business advice
+
+**Post format:** Self-post. Personal and honest. Numbers matter here.
+
+---
+
+## r/webdev
+
+**Audience:** Frontend and full-stack web developers
+
+**What works:**
+- Portfolio pieces with technical explanation
+- "I built X, here is how" posts
+- CSS tricks, JS patterns, performance wins
+- Tools that solve a specific web dev pain
+
+**Post tone:** Friendly and curious, less intense than r/programming
+
+---
+
+## The 90/10 Rule
+
+For any subreddit where you plan to share your own project:
+
+Before you post, check your account's recent post history. At least 90% of your posts should be genuine contributions: answering questions, sharing interesting links, participating in discussions. At most 10% should be posts about your own work.
+
+If you are posting about your project in multiple subreddits on the same day, stagger the posts. Identical posts across subreddits on the same day trigger spam detection.
+
+---
+
+## Anti-Patterns That Get Posts Removed
+
+1. **Cross-posting the exact same post to 5 subreddits simultaneously**: post one at a time, wait for results
+2. **Asking friends to upvote**: vote manipulation gets posts and accounts banned
+3. **Replying to your own post with a second account**: obvious and penalized
+4. **Using your product URL as the post URL**: for self-posts, keep the link in the first comment
+5. **"I need feedback" when you want users**: moderators read this correctly
+6. **Flair violations**: some subreddits require flair; missing it gets the post auto-removed

package/skills/schema-markup-generator/.env.example

@@ -0,0 +1,19 @@
+# schema-markup-generator -- Environment Variables
+# ==================================================
+# Most pages work without any API keys.
+# Chrome is needed for JavaScript-rendered pages.
+# GitHub token is needed only for auto-PR support.
+
+# Chrome remote debugging port (default: 9222)
+# Start Chrome with: google-chrome --remote-debugging-port=9222
+# On macOS: open -a "Google Chrome" --args --remote-debugging-port=9222
+CHROME_DEBUGGING_PORT=9222
+
+# Optional: GitHub personal access token for opening PRs
+# Scopes needed: repo (read + write)
+# Get one at: https://github.com/settings/tokens
+GITHUB_TOKEN=your_github_token_here
+
+# Optional: Target GitHub repo slug (e.g. "yourorg/your-site")
+# If set, the agent offers to open a PR automatically
+GITHUB_REPO=your-org/your-repo

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

@@ -0,0 +1,114 @@
+# schema-markup-generator
+
+![schema-markup-generator](https://github.com/user-attachments/assets/4b5e5bfb-3c33-4a20-afff-59fda19196b4)
+
+
+Generate valid JSON-LD structured data for any webpage. The agent crawls the page, detects which schema types apply, and outputs a script tag ready to paste into your HTML. Optionally opens a GitHub PR with the markup injected.
+
+## 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