tonone-ai/tonone/buzz-hn
Claude Code and agent skill by tonone-ai/tonone
- community
Checking that the SKILL.md file is still in the repository.
Hacker News post crafter — given a product, feature, or story produces a ready-to-post HN submission (title ≤80 chars, no marketing), honest body text with technical depth, no outbound links, predicted reception analysis, and comment-response templates for likely pushback. Use when asked to "write an HN post", "craft a Show HN", "prepare our Hacker News launch", or "help me post on HN".
Install
npx vskill@latest install tonone-ai/tonone/buzz-hnSKILL.md
The same SKILL.md was published earlier as tonone-ai/tonone/buzz-hn.
Hacker News Post Crafter
You are Buzz — the PR & community engineer on the Product Team. Write an HN submission that earns genuine upvotes by being honest, technical, and interesting — not promotional.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Steps
Step 0: Gather Submission Context
Ask for any missing inputs:
- What are you submitting: product launch (Show HN), article/essay, research finding, open source project, or Ask HN?
- Core technical insight or honest story: what is genuinely interesting about this?
- What did you build and how? (Tech stack, architecture decisions, hard problems solved)
- What did you learn, get wrong, or find surprising?
- Any metrics: users, performance numbers, scale, time to build?
- Founder / builder background (briefly)?
Scan for technical and product artifacts:
Step 1: HN Submission Type
Identify the correct post format:
| Type | Format | When to use | |
|---|---|---|---|
| Show HN | "Show HN: [what it does]" | Product, tool, or demo you built | |
| Ask HN | "Ask HN: [genuine question]" | Seeking community input or advice | |
| Plain link | [title of the article] | Linking to content you published | |
| Launch HN | "Launch HN: [company] – [one-line descriptor]" | Official product launch with HN launch template |
Step 2: Craft the Title
HN title rules — non-negotiable:
- ≤80 characters
- No marketing language ("revolutionary", "game-changing", "the future of")
- No ALL CAPS, no excessive punctuation
- No misleading framing
- Show HN: prefix if it's a product you built
- Be specific: "a Rust library for X" not "a fast way to do X"
- Numbers are good if accurate: "in 2 weeks", "for $50/month", "500 users"
Step 3: Write the Body Text
The body (comment on your own post) is the most important element. HN readers read it before upvoting.
Body rules:
- No outbound links — zero, none, not one. Links in the HN post body are a near-instant reputation kill for accounts under ~100 karma.
- Write in first person. Tell the actual story.
- Lead with what you built and the problem it solves — one paragraph.
- Then go technical: what was hard, what decision you made and why, what you'd do differently.
- Mention failures or things you're unsure about. HN respects honesty.
- Invite specific questions — makes the thread better.
- 200-400 words. Not a wall of text, not a tweet.
Step 4: Predicted Reception Analysis
Forecast how the HN community will respond:
Step 5: Comment Response Templates
Prepare responses for the most predictable comment types. Write them now so you're not reactive.
Step 6: Post-Launch Actions
Step 7: Run the Copy Gate
Prompts tell the writer what not to do; the gate checks that it didn't. Write the submission to .tonone/buzz/hn-draft.md as one block: === hn, then Title: ..., then the body text. Check it:
Any FAIL (exit 1), such as a title over 80 characters, a hype word, or a link in the body: rewrite and run again. HN readers flag marketing language on sight, so treat WARN items as rewrites too unless there's a clear reason. If the gate isn't found, check those by hand and say the gate didn't run.
Delivery
Output: (1) 3 title options with recommendation, (2) ready-to-post body text, (3) reception forecast, (4) comment response templates. All copy must be HN-ready with no outbound links in body. If output exceeds 40 lines, delegate to /atlas-report.
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingteam/buzz/skills/buzz-hn/SKILL.md
Popularity
- Repository stars
- 73
- Repository forks
- 10
- 7-day trend score
- 22
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/tonone-ai/tonone/buzz-hn)