Write HN posts that earn upvotes
buzz-hnskillsetup L1★39
tonone-ai/tonone ↗What it does
Write technical HN submissions that earn upvotes through honesty
Best for
Founders shipping something real who want HN upvotes by telling the actual technical story, not because they optimized for the algorithm.
Inputs
- · Submission type (Show HN, Ask HN, plain link, launch)
- · Core technical insight or story
- · What you built and how (tech stack, decisions, problems solved)
- · What you learned or got wrong
- · Metrics (users, performance, scale, time to build)
- · Founder background
Outputs
- · HN-optimized title (≤80 chars, specific, no marketing language)
- · 3 title variants with reasoning
- · Body text (200-400 words, first person, technical story)
- · Reception forecast with likely pushback vectors
Preconditions
- · Product, article, or project is real and shareable
- · Core technical insight identified
- · Can articulate what was hard or learned
Failure modes
- · Title too long or marketing-y ('revolutionary', 'game-changing')
- · Body includes outbound links (reputation killer for sub-100-karma accounts)
- · Story is not technical enough or too promotional
- · Does not mention failures or uncertainties (HN distrusts perfect narratives)
- · Reception forecast is too optimistic
Trust signals
- · Title rules are explicit and non-negotiable (≤80 chars, no marketing language, no links in body)
- · Example title variants provided
- · Body formula separates: what it is + problem + solution + who it's for (one paragraph)
- · Reception forecast includes specific pushback vectors
- · Emphasis on first-person storytelling and honesty about failures