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

lobsters-publisher

Skill244 starsChanged 5 days agoMITView on GitHub

Prepare or publish Lobsters submissions and follow-up drafts for eunomia.dev content, GitHub projects, papers, demos, and computing-focused technical posts. Use when asked to submit, adapt, publish, QA, or record Lobsters posts. Covers tag selection, computing-topic fit, self-promotion safety, browser duplicate checks, publication authorization, comment/private-message follow-up, and media ledger updates.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 6 are distinctive, and 4 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.

  • 4

    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. Very specific:

    Search: <https://lobste.rs/search>

    line 25
  3. Distinctive:

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

    line 27
  4. Distinctive:

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

    line 38
  5. Distinctive:

    Check whether the item is narrowly about computing.

    line 44
  6. Distinctive:

    Prefer the original/canonical source and remove tracking parameters.

    line 45
  7. Distinctive:

    Keep the title factual and unpromotional.

    line 47
  8. Very specific:

    Before opening the Lobsters submit page or comment box, write or update the Lobsters draft under …

    line 52
  9. Distinctive:

    After confirmed submission, capture the story URL.

    line 68
  10. Very specific:

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

    line 74

≈ “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

Lobsters Publisher

Prepare Lobsters submissions that fit the computing-focused community. Publication authorization follows CLAUDE.md's Precedence Rule and Publishing section.

Inputs

  • Source URL, GitHub repo, paper, demo, blog post, or topic.
  • Optional tags, 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 Lobsters fit, tags, title, source URL, self-promotion safety, browser checks, promotion balance, or 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. Check whether the item is narrowly about computing.
  2. Prefer the original/canonical source and remove tracking parameters.
  3. Choose predefined tags that accurately match the story.
  4. Keep the title factual and unpromotional.
  5. Disclose affiliation in comments when relevant.

Draft Archive

Before opening the Lobsters submit page or comment box, write or update the Lobsters draft under draft/media/YYYY-MM-DD/<source-slug>/lobsters.md using the local date. Include title, URL, tags, duplicate-check state, affiliation note, and any full paste-ready comment options.

Browser QA

  • title, URL, and tags are correct
  • duplicate/recent same-topic searches are clean
  • the account is allowed to submit the domain and tags
  • tracking parameters are absent
  • the final action matches the task: submitted when authorized, untouched for a draft-only task

Follow-Up

After confirmed submission, capture the story URL. Monitor comments and private messages only when the user asks or follow-up was part of the task. Draft substantive replies and move durable implementation work to GitHub.

Ledger Update

After confirmed submission, update .github/publisher/media/published.md with source path or URL, Lobsters URL, date, tags, 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.