agentleFS
eunomia-bpfeunomia-bpf/eunomia.dev/.agents/skills/hackernews-publisher/SKILL.md

hackernews-publisher

Skill244 starsChanged 5 days agoMITView on GitHub

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.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 6 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

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

    line 17
  2. Distinctive:

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

    line 27
  3. Distinctive:

    Do not use unofficial submission automation, internal endpoints, or vote-related actions.

    line 38
  4. Distinctive:

    Prefer the original source: GitHub repo, paper, demo, or canonical article.

    line 45
  5. Distinctive:

    Use Show HN only for something readers can try.

    line 49
  6. Distinctive:

    Do not write generated comments for direct posting.

    line 50
  7. Very specific:

    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 …

    line 55
  8. Distinctive:

    After confirmed submission, capture the HN item URL.

    line 71
  9. Very specific:

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

    line 78

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Hacker News Publisher

Prepare Hacker News submissions. Publication authorization follows CLAUDE.md's Precedence Rule and Publishing section.

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

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

  1. 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 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.