Launch Distribution
amplitude/builder-skills
Plan and execute multi-channel distribution for product launches across X/Twitter, Reddit, LinkedIn, Hacker News, and other platforms.
A skill your agent uses when the user asks to prepare a Product Hunt launch or generate Product Hunt listing assets.
$ npx skills add Varnan-Tech/opendirectory --skill producthunt-launch-kit -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Varnan-Tech/opendirectory producthunt-launch-kit --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Varnan-Tech/opendirectory.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/producthunt-launch-kit .claude/skills/producthunt-launch-kit && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "producthunt-launch-kit" agent skill from https://github.com/Varnan-Tech/opendirectory/tree/main/skills/producthunt-launch-kit into .claude/skills/producthunt-launch-kit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "producthunt-launch-kit", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Varnan-Tech/opendirectory/tree/main/skills/producthunt-launch-kitType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Varnan-Tech/opendirectory --skill producthunt-launch-kit -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Varnan-Tech/opendirectory producthunt-launch-kit --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Varnan-Tech/opendirectory.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/producthunt-launch-kit .agents/skills/producthunt-launch-kit && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "producthunt-launch-kit" agent skill from https://github.com/Varnan-Tech/opendirectory/tree/main/skills/producthunt-launch-kit into .agents/skills/producthunt-launch-kit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "producthunt-launch-kit", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Varnan-Tech/opendirectory --skill producthunt-launch-kit -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Varnan-Tech/opendirectory producthunt-launch-kit --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Varnan-Tech/opendirectory.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/producthunt-launch-kit .cursor/skills/producthunt-launch-kit && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "producthunt-launch-kit" agent skill from https://github.com/Varnan-Tech/opendirectory/tree/main/skills/producthunt-launch-kit into .cursor/skills/producthunt-launch-kit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "producthunt-launch-kit", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Varnan-Tech/opendirectory.git --path skills/producthunt-launch-kit--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Varnan-Tech/opendirectory --skill producthunt-launch-kit -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Varnan-Tech/opendirectory producthunt-launch-kit --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Varnan-Tech/opendirectory.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/producthunt-launch-kit .gemini/skills/producthunt-launch-kit && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "producthunt-launch-kit" agent skill from https://github.com/Varnan-Tech/opendirectory/tree/main/skills/producthunt-launch-kit into .gemini/skills/producthunt-launch-kit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "producthunt-launch-kit", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Varnan-Tech/opendirectory producthunt-launch-kitInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Varnan-Tech/opendirectory --skill producthunt-launch-kit -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Varnan-Tech/opendirectory.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/producthunt-launch-kit .github/skills/producthunt-launch-kit && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "producthunt-launch-kit" agent skill from https://github.com/Varnan-Tech/opendirectory/tree/main/skills/producthunt-launch-kit into .github/skills/producthunt-launch-kit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "producthunt-launch-kit", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Varnan-Tech/opendirectory --skill producthunt-launch-kit -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Varnan-Tech/opendirectory producthunt-launch-kit --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Varnan-Tech/opendirectory.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/producthunt-launch-kit .opencode/skills/producthunt-launch-kit && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "producthunt-launch-kit" agent skill from https://github.com/Varnan-Tech/opendirectory/tree/main/skills/producthunt-launch-kit into .opencode/skills/producthunt-launch-kit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "producthunt-launch-kit", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
producthunt-launch-kitA skill your agent uses when the user asks to prepare a Product Hunt launch or generate Product Hunt listing assets.
Producthunt Launch Kit is an agent skill from Varnan-Tech/opendirectory. Use when the user asks to prepare a Product Hunt launch or generate Product Hunt listing assets. Generates tagline variants under 60 chars, a 500-char description, a maker comment, launch-day tweet thread, LinkedIn post, and a 4-email launch sequence.
Its SKILL.md is about 3.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `README.md`, `evals/evals.json` and `references/copy-rules.md`). Compatibility notes: ["claude-code","gemini-cli","github-copilot"]
It sits in Writing & Content, covering Social media posts, Product launch strategy and Positioning and messaging. It works with LinkedIn. The repository describes itself as: AI Agent Skills built for Founders who hate Marketing. The licence is MIT.
8 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 62e437a. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
curlpython3From the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
generativelanguage.googleapis.comFrom URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
GEMINI_API_KEYFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
["claude-code","gemini-cli","github-copilot"]
From compatibility in the SKILL.md frontmatter.
Producthunt Launch Kit loads about 3.7k tokens when it runs, and up to ~4.9k if it reads all its reference files. Until then it costs about 69 tokens; SKILL.md has 1,068 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from Varnan-Tech/opendirectory at commit 62e437a, republished under its MIT licence (© Varnan-Tech). 1,068 words, ~3,655 tokens.
.claude/skills/producthunt-launch-kit/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.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).
You need:
If any of these are missing, ask in one message before proceeding.
Also check for project context files:
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.
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]."
The tagline appears directly under the product name on Product Hunt. It is the most read copy on your listing.
Hard limits:
Tagline formula: [Action verb] + [what it does] + [key differentiator]
Generate five tagline variants:
After generating, count characters for each. Flag any that exceed 60 characters and revise.
The description appears below the tagline. Maximum 500 characters. It displays in search results and link previews.
Structure:
Description rules:
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:
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?"
Write all assets in one Gemini call:
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:
Before presenting:
Taglines:
Description:
Maker comment:
Tweet thread:
If any item fails, revise before presenting. Do not present drafts with QA failures.
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© Varnan-Tech, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 4 other files (references) in skills/producthunt-launch-kit of Varnan-Tech/opendirectory.
Open the folder on GitHubat commit 62e437a
Producthunt Launch Kit next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Producthunt Launch Kit this skillVarnan-Tech/opendirectory | 674 | — | ~3.7k | Automated safety check: Pass | MIT | |
| Launch Distributionamplitude/builder-skills | 159 | — | ~2.8k | Automated safety check: Pass | None | |
| Content Idea GeneratorBrianRWagner/ai-marketing-claude-code-skills | 441 | — | ~1.7k | Automated safety check: Pass | None | |
| Linkedin Publishereunomia-bpf/eunomia.dev | 236 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Marketing Campaignaffaan-m/ECC | 276k | 1 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Money Socialiamzifei/show-me-the-money | 1k | — | ~2k | Automated safety check: Pass | Custom licence |
amplitude/builder-skills
Plan and execute multi-channel distribution for product launches across X/Twitter, Reddit, LinkedIn, Hacker News, and other platforms.
BrianRWagner/ai-marketing-claude-code-skills
Produces content ideas for LinkedIn, X, newsletters or short video from your positioning statement, in quick, standard or deep planning modes.
eunomia-bpf/eunomia.dev
Prepare or publish eunomia.dev content for LinkedIn posts, articles, carousels, and professional updates.
affaan-m/ECC
End-to-end marketing campaign planning and execution. An agent skill from affaan-m/ECC.
iamzifei/show-me-the-money
Social media management and community building automation. An agent skill from iamzifei/show-me-the-money.
shawnpang/startup-founder-skills
When the user needs to build a LinkedIn authority system, create social content strategy, define content pillars, write posts, or establish thought leadership positioning.
Varnan-Tech/opendirectory
Creates professionally designed B2B SaaS e-books in HTML + CSS, exported as print-ready PDF.
Varnan-Tech/opendirectory
Generates and updates README.md and API reference docs by reading your codebase's functions, routes, types, schemas, and architecture.
Varnan-Tech/opendirectory
Generates data visualization charts (bar, line, area, pie, doughnut, scatter, radar, treemap) as PNG using Apache ECharts v6.
Varnan-Tech/opendirectory
Creates animated looping GIFs from CSS animations (default) or AI image-to-video.
Varnan-Tech/opendirectory
Given a product description, category keywords, or competitor names (any combination), searches Reddit, Hacker News, GitHub Issues, G2, and Google Trends for the real pains your market experiences…
Varnan-Tech/opendirectory
Aggregates RSS feeds from the past week, synthesizes the top stories using Gemini, and publishes a newsletter digest to Ghost CMS.
Works with
Categories
A skill your agent uses when the user asks to prepare a Product Hunt launch or generate Product Hunt listing assets. Producthunt Launch Kit is an agent skill from Varnan-Tech/opendirectory. Use when the user asks to prepare a Product Hunt launch or generate Product Hunt listing assets.
Producthunt Launch Kit fits situations like: the user asks to prepare a Product Hunt launch; generate Product Hunt listing assets.
Run `npx skills add Varnan-Tech/opendirectory --skill producthunt-launch-kit -a claude-code`. Or copy the skill folder (skills/producthunt-launch-kit in Varnan-Tech/opendirectory) into .claude/skills/producthunt-launch-kit in your project. Claude Code loads it when a task matches its description.
Run `npx skills add Varnan-Tech/opendirectory --skill producthunt-launch-kit -a codex`. Or copy the skill folder (skills/producthunt-launch-kit in Varnan-Tech/opendirectory) into .agents/skills/producthunt-launch-kit in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Varnan-Tech/opendirectory --skill producthunt-launch-kit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/producthunt-launch-kit, .gemini/skills/producthunt-launch-kit, .github/skills/producthunt-launch-kit and .opencode/skills/producthunt-launch-kit in your project.
Going by SKILL.md and its folder, Producthunt Launch Kit needs the command-line tools its instructions call (curl and python3) and credentials named GEMINI_API_KEY. Our summary lists: Python 3; A credential in GEMINI_API_KEY. Compatibility (from SKILL.md): ["claude-code","gemini-cli","github-copilot"].
SKILL.md names 1 domain. In commands or code: generativelanguage.googleapis.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Producthunt Launch Kit is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.7k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.2k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Producthunt Launch Kit: Launch Distribution (amplitude/builder-skills, 159 stars), Content Idea Generator (BrianRWagner/ai-marketing-claude-code-skills, 441 stars), Linkedin Publisher (eunomia-bpf/eunomia.dev, 236 stars) and Marketing Campaign (affaan-m/ECC, 276k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Varnan-Tech (a GitHub organization) maintains it in Varnan-Tech/opendirectory, which has 674 GitHub stars. The repository holds 61 skills in this directory. The repository was last updated on August 16, 2026.
Source: Varnan-Tech/opendirectory on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.