How do I install the Hackernews Publisher skill?

Run npx skillmds@latest add eunomia-bpf/hackernews-publisher in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Hackernews Publisher safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Hackernews Publisher?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Hackernews Publisher free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Hackernews Publisher?

eunomia-bpf (@eunomia-bpf) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Hackernews Publisher by eunomia-bpf

Name: Hackernews Publisher
Author: eunomia-bpf

Hackernews Publisher

Prepare or publish Hacker News submissions and follow-up drafts for eunomia.dev content, GitHub projects, papers, demos, and Show HN style launches. Use when asked to submit, adapt, publish, QA, or record HN posts. Covers original-source selection, title normalization, curiosity-first positioning, browser duplicate checks, publication authorization, comment follow-up, and media ledger updates.

eunomia-bpf Updated Sep 17, 2026

File contents

Hacker News Publisher

Prepare Hacker News submissions. A request to submit or a queue item marked 排队 authorizes the final submission; do not ask again at the last button. Stop only when the task is limited to a draft or preview.

Inputs

Source URL, GitHub repo, paper, demo, blog post, or topic.
Submission type when specified: regular link, Show HN, Ask HN, or comment.
Optional title, text, or follow-up plan.

If the source URL is missing, inspect recent docs/blog/posts/, relevant GitHub repos, and canonical eunomia.dev URLs before asking the user.

Platform Entry Points

Submit: https://news.ycombinator.com/submit
Show HN: https://news.ycombinator.com/show
New: https://news.ycombinator.com/newest
Search: https://hn.algolia.com/

Use a browser surface with the logged-in session when UI work is required.

References

Load references/platform-preferences.md when choosing HN fit, title, source URL, Show HN eligibility, browser checks, promotion balance, or comment follow-up. Do not load broad strategy drafts for routine submissions unless the user asks for campaign or content-platform planning.

Browser-Only Platform Boundary

Do not use unofficial submission automation, internal endpoints, or vote-related actions. All checks and submission prep must come from normal browser interactions.

Draft Preparation

Decide whether HN is appropriate for the item.
Prefer the original source: GitHub repo, paper, demo, or canonical article.
For an existing long-form source, preserve the original title exactly except for a platform-required marker such as [pdf]. A different title requires explicit user instruction.
Use Show HN only for something readers can try.
Do not write generated comments for direct posting; draft comment options for user review and ownership.

Draft Archive

Before opening the HN submit page or comment box, write or update the HN draft under draft/media/YYYY-MM-DD/<source-slug>/hackernews.md using the local date. Include submission type, title, URL, duplicate-check state, Show HN eligibility, and any full paste-ready comment options for user review.

Browser QA

the same URL/topic is not already active
title is neutral, not all-caps, and does not include the site name
URL is the original/canonical source
Show HN title is only used when the artifact is tryable
the final action matches the task: submitted when authorized, untouched for a draft-only task

Follow-Up

After confirmed submission, capture the HN item URL. Monitor comments only when the user asks or follow-up was part of the task. Draft concise, human-reviewed technical replies. Do not solicit upvotes or comments, and do not ask others to submit or promote the link.

Ledger Update

After confirmed submission, update .github/publisher/media/published.md with source path or URL, HN URL, date, submission type, title, and follow-up notes.

---name: hackernews-publisherdescription: Prepare or publish Hacker News submissions and follow-up drafts for eunomia.dev content, GitHub projects, papers, demos, and Show HN style launches. Use when asked to submit, adapt, publish, QA, or record HN posts. Covers original-source selection, title normalization, curiosity-first positioning, browser duplicate checks, publication authorization, comment follow-up, and media ledger updates.---# Hacker News PublisherPrepare Hacker News submissions. A request to submit or a queue item marked`排队` authorizes the final submission; do not ask again at the last button.Stop only when the task is limited to a draft or preview.## Inputs- Source URL, GitHub repo, paper, demo, blog post, or topic.- Submission type when specified: regular link, Show HN, Ask HN, or comment.- Optional title, text, or follow-up plan.If the source URL is missing, inspect recent `docs/blog/posts/`, relevantGitHub repos, and canonical eunomia.dev URLs before asking the user.## Platform Entry Points- Submit: <https://news.ycombinator.com/submit>- Show HN: <https://news.ycombinator.com/show>- New: <https://news.ycombinator.com/newest>- Search: <https://hn.algolia.com/>Use a browser surface with the logged-in session when UI work is required.## ReferencesLoad `references/platform-preferences.md` when choosing HN fit, title, sourceURL, Show HN eligibility, browser checks, promotion balance, or commentfollow-up. Do not load broad strategy drafts for routine submissions unless theuser asks for campaign or content-platform planning.## Browser-Only Platform BoundaryDo not use unofficial submission automation, internal endpoints, or vote-relatedactions. All checks and submission prep must come from normal browserinteractions.## Draft Preparation1. Decide whether HN is appropriate for the item.2. Prefer the original source: GitHub repo, paper, demo, or canonical article.3. For an existing long-form source, preserve the original title exactly except for a platform-required marker such as `[pdf]`. A different title requires explicit user instruction.4. Use Show HN only for something readers can try.5. Do not write generated comments for direct posting; draft comment options for user review and ownership.## Draft ArchiveBefore opening the HN submit page or comment box, write or update the HN draftunder `draft/media/YYYY-MM-DD/<source-slug>/hackernews.md` using the local date.Include submission type, title, URL, duplicate-check state, Show HN eligibility,and any full paste-ready comment options for user review.## Browser QA- the same URL/topic is not already active- title is neutral, not all-caps, and does not include the site name- URL is the original/canonical source- Show HN title is only used when the artifact is tryable- the final action matches the task: submitted when authorized, untouched for a draft-only task## Follow-UpAfter confirmed submission, capture the HN item URL. Monitor comments only whenthe user asks or follow-up was part of the task. Draft concise, human-reviewedtechnical replies. Do not solicit upvotes or comments, and do not ask others tosubmit or promote the link.## Ledger UpdateAfter confirmed submission, update `.github/publisher/media/published.md` withsource path or URL, HN URL, date, submission type, title, and follow-up notes.

Frequently asked questions