Generates a complete Product Hunt launch kit from your product description: tagline variants (60 chars max), listing description, maker comment, launch day tweet thread, LinkedIn post, and a 4-email sequence.
No global install. Always runs the latest version.
npx "@opendirectory.dev/skills" install producthunt-launch-kit --target claudenpx skills add Varnan-Tech/opendirectory --skill producthunt-launch-kitRequires Node.js. Add --global to install to ~/.claude/skills/ instead of the current project.
install-skill-on-claude-compressed.mp4
Step 1: Download the skill from GitHub
- Copy the URL of this specific skill folder from your browser's address bar.
- Go to download-directory.github.io.
- Paste the URL and click Enter to download.
Step 2: Install in Claude
- Open your Claude desktop app.
- Go to the sidebar on the left side and click on the Customize section.
- Click on the Skills tab, then click on the + button to create a new skill.
- Choose Upload a skill, then drag and drop the
.zipfile or extracted folder.
Note: For some skills, the
SKILL.mdfile might be located inside a subfolder. Always upload the specific folder that contains theSKILL.mdfile.
Run these commands inside Claude Code:
/plugin marketplace add Varnan-Tech/opendirectory
/plugin install opendirectory-gtm-skills@opendirectory-marketplaceManusAI-one-click-installation-demo-compressed.mp4
Manus AI users can import a skill directly from its OpenDirectory skill page. This is the easiest path when you want Manus to pull the skill from GitHub for you.
- Open the skill you want from the opendirectory homepage.
- In the install panel, select the Manus AI tab.
- Click Install in Manus AI - this opens Manus with the skill GitHub URL already attached.
- Confirm the import inside Manus AI.
If your Manus workspace prefers file uploads, use the Download tab instead and upload the downloaded
.skill.zipfile inside Manus.
- 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
| Requirement | Purpose | How to Set Up |
|---|---|---|
| Gemini API key | All copy generation | aistudio.google.com, Get API key |
cp .env.example .env
# Add GEMINI_API_KEYFull 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"
| 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 |
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.
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.
producthunt-launch-kit/
├── SKILL.md
├── README.md
├── .env.example
├── evals/
│ └── evals.json
└── references/
└── copy-rules.md
MIT