New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Buzz Hn

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

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…

MITAuto-check: notes

Install Buzz Hn

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill buzz-hn -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace buzz-hn --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/ai-agency/tonone/bundle/marketing-team/skills/buzz-hn .claude/skills/buzz-hn && rm -rf skills-src

Use ~/.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/

Facts

Skill name
buzz-hn
GitHub stars
2.8k
Token cost
~1.8k tokens
SKILL.md length
442 words
Files
1
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

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…

  • Works in 7 steps: Gather Submission Context → HN Submission Type → Craft the Title → …
  • Asked to write an HN post
  • SKILL.md covers Steps and Delivery
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Buzz Hn is an agent skill from jeremylongshore/tons-of-skills-marketplace. 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".

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Asked to write an HN post
  • Craft a Show HN
  • Prepare our Hacker News launch
  • Help me post on HN

Example prompts

  • “write an HN post”
  • “craft a Show HN”
  • “prepare our Hacker News launch”
  • “/buzz-hn”

Requirements

  • Pre-approved tools (allowed-tools): Read, Bash, Glob, Grep, AskUserQuestion

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Gather Submission Context
  2. HN Submission Type
  3. Craft the Title
  4. Write the Body Text
  5. Predicted Reception Analysis
  6. Comment Response Templates
  7. Post-Launch Actions

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Bash
    • Glob
    • Grep
    • AskUserQuestion

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Buzz Hn loads about 1.8k tokens when it runs. Until then it costs about 99 tokens; SKILL.md has 442 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~99
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k

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.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Bash, Glob, Grep, AskUserQuestion

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.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 442 words, ~1,761 tokens.

Download SKILL.mdSave it as .claude/skills/buzz-hn/SKILL.md (or your agent's skills folder).
name
buzz-hn
description
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".
allowed-tools
Read, Bash, Glob, Grep, AskUserQuestion
version
0.1.0
author
tonone-ai <hello@tonone.ai>
license
MIT

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:

bash
find . -name "README*" 2>/dev/null | head -5
find . -name "*.md" 2>/dev/null | xargs grep -l "architecture\|how.we.built\|technical\|stack\|decision\|tradeoff" 2>/dev/null | head -10
Step 1: HN Submission Type

Identify the correct post format:

TypeFormatWhen 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"
Title options (provide 3 variants):

Option A: [title — most descriptive]
Option B: [title — most specific to technical approach]
Option C: [title — most curiosity-driven]

Recommended: Option [X] because [reason]
Show full SKILL.md (186 more words)Show less
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.
## Body Text

[Paragraph 1 — what this is and why you built it.
 One sentence on the problem. One sentence on the solution. One sentence on who it's for.]

[Paragraph 2 — the technical story.
 What was the hard part? What did you learn? What did you try that didn't work?
 Be specific: "We tried X but found Y, so we switched to Z."]

[Paragraph 3 — current state and what's ahead.
 How far is this? Alpha, production, used by real users? What are you unsure about?]

[Closing — invite discussion.
 "Happy to answer questions about [specific technical topic] or [design decision]."]
Step 4: Predicted Reception Analysis

Forecast how the HN community will respond:

## Reception Forecast

Likely upvote signal: [HIGH / MEDIUM / LOW]
Reason: [why this is or isn't a natural HN fit]

Likely pushback vectors:

1. [Most predictable criticism — e.g., "Why not just use X?"]
   Honest response: [your actual answer]

2. [Second likely criticism — e.g., "This doesn't work at scale because..."]
   Honest response: [your actual answer]

3. [Third likely criticism — e.g., "Security concern with approach Y"]
   Honest response: [your actual answer]

Likely genuine interest from: [who in the HN community will care most]
Peak engagement window: weekday 9-11am Pacific Time (US) or 7-9am Pacific (EU audience)
Step 5: Comment Response Templates

Prepare responses for the most predictable comment types. Write them now so you're not reactive.

## Comment Response Templates

### "Why not use [existing tool / library / competitor]?"
"[Tool X] is a reasonable choice for [use case]. We went a different direction because
[specific technical reason]. Happy to compare notes if you've used it — there may be
things we're missing."

### "This won't scale because [reason]"
"Fair concern. At [current scale] we haven't hit that wall yet. The approach breaks down
when [specific threshold]. Our plan for that is [answer or honest 'we haven't solved it yet']."

### "Security concern with [specific part of approach]"
"Good catch. [Acknowledge if valid.] We [mitigate / handle / still need to address] this by
[specific answer]. If you see other exposure, please let me know — genuinely useful to hear."

### "Interesting — how does this compare to [X] you did N months ago?"
[Personalize based on any prior HN posts or public work. Acknowledge continuity.]

### Negative / dismissive comment
Do not engage with pure negativity. Engage with the technical point if there is one.
One response, not a thread. "Fair — [acknowledge grain of truth]. [One sentence response.]"
Step 6: Post-Launch Actions
First 2 hours after posting:
[ ] Monitor the thread actively — respond to every technical question promptly
[ ] Upvote genuine comments (no ring-voting: only upvote comments you would upvote anyway)
[ ] Do not ask friends/colleagues to upvote — HN detects this
[ ] If the thread goes well, share the HN link (not the product link) on Twitter/LinkedIn
[ ] If you get a "flagged" warning — do not repost. Address it in the thread.

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.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/ai-agency/tonone/bundle/marketing-team/skills/buzz-hn of jeremylongshore/tons-of-skills-marketplace.

Open the folder on GitHubat commit cfae287

Compare with similar skills

Buzz Hn 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.

Buzz Hn compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Buzz Hn this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.8kAutomated safety check: NotesMIT
Hacker News Scrapergooseworks-ai/goose-skills1.2k1 repos~538Automated safety check: PassMIT
Hacker Newsunifapi-agent/agents589—~1.4kAutomated safety check: PassMIT
Hacker News Front Page Scrapergarrytan/gstack136k—~355Automated safety check: PassMIT
Aeon Hacker News DigestBankrBot/skills1.2k—~561Automated safety check: PassNone
Competitor News MonitorNousResearch/hermes-agent252k—~1.2kAutomated safety check: PassMIT

Similar skills

  • Hacker News Scraper

    gooseworks-ai/goose-skills

    Search Hacker News stories and comments using the free Algolia API.

    1.2k GitHub starsUsed in 1 repo~538 tokens
    Data & AnalyticsAuto-check passed

  • Hacker News

    unifapi-agent/agents

    When a workflow needs public Hacker News data through UnifAPI — the top/new/best/ask/show/jobs story feeds, item metadata, comment trees, or user karma.

    589 GitHub stars~1.4k tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed

  • Hacker News Front Page Scraper

    garrytan/gstack

    Scrapes the Hacker News front page and returns the top 30 stories as JSON with rank, title, link, points and comment count.

    136k GitHub stars~355 tokensUpdated today
    Data & AnalyticsAuto-check passed

  • Aeon Hacker News Digest

    BankrBot/skills

    Top Hacker News stories filtered by interest tags, with comment-mined insights (top, dissenting, expert/builder) and themed clustering.

    1.2k GitHub stars~561 tokensUpdated yesterday
    Auto-check passed

  • Competitor News Monitor

    NousResearch/hermes-agent

    Watch named companies for material news; cited digests. An agent skill from NousResearch/hermes-agent.

    252k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

  • News

    alsk1992/CloddsBot

    Monitor news and correlate with prediction market movements. An agent skill from alsk1992/CloddsBot.

    3k GitHub stars~462 tokensUpdated 9 days ago
    Auto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo

  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes

  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed

  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Questions about Buzz Hn

What does Buzz Hn do?

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…. Buzz Hn is an agent skill from jeremylongshore/tons-of-skills-marketplace. 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.

When should I use Buzz Hn?

Buzz Hn fits situations like: asked to write an HN post; craft a Show HN; prepare our Hacker News launch; help me post on HN.

How do I install Buzz Hn in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill buzz-hn -a claude-code`. Or copy the skill folder (plugins/ai-agency/tonone/bundle/marketing-team/skills/buzz-hn in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/buzz-hn in your project. Claude Code loads it when a task matches its description.

How do I install Buzz Hn in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill buzz-hn -a codex`. Or copy the skill folder (plugins/ai-agency/tonone/bundle/marketing-team/skills/buzz-hn in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/buzz-hn in your project. Codex loads it when a task matches its description.

Can I use Buzz Hn in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill buzz-hn -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/buzz-hn, .gemini/skills/buzz-hn, .github/skills/buzz-hn and .opencode/skills/buzz-hn in your project.

What does Buzz Hn need to run?

SKILL.md names no scripts, command-line tools or credentials: Buzz Hn is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Bash, Glob, Grep, AskUserQuestion.

Does Buzz Hn access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Buzz Hn safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Buzz Hn use?

Buzz Hn is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Buzz Hn use?

About 1.8k tokens (SKILL.md is roughly 7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Buzz Hn?

Skills that share tags, products or a category with Buzz Hn: Hacker News Scraper (gooseworks-ai/goose-skills, 1.2k stars), Hacker News (unifapi-agent/agents, 589 stars), Hacker News Front Page Scraper (garrytan/gstack, 136k stars) and Aeon Hacker News Digest (BankrBot/skills, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Buzz Hn?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.