x-publisher
Skill244 starsChanged 5 days agoMITView on GitHub
Prepare or publish eunomia.dev public content for X/Twitter posts, threads, and X Articles. Use when asked to draft, adapt, paste, publish, QA, or record X posts for blog, tutorial, project, paper, release, or GitHub updates. Covers concise platform-native copy, media and link checks, publication authorization, reply/mention/DM follow-up, and media ledger updates.
In this repository20 other files it gives its agents.
- app/AGENTS.mdAGENTS.md
- app/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- blog-writerSkill
- blog-writing-styleSkill
- content-launch-plannerSkill
- devto-publisherSkill
- eunomia-community-radarSkill
- eunomia-content-patrolSkill
- eunomia-research-reportSkill
- eunomia-social-radarSkill
- hackernews-publisherSkill
- juejin-publisherSkill
- linkedin-publisherSkill
- lobsters-publisherSkill
- medium-publisherSkill
- reddit-publisherSkill
- seo-geoSkill
- xiaohongshu-publisherSkill
- zhihu-publisherSkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 8 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
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
- Very specific: line 17
If the source path is missing, inspect .github/publisher/posts_queue.txt, .github/publisher/media/not-published.md, recent …
- Distinctive: line 27
Search: <https://x.com/search>
- Distinctive: line 29
Use a browser surface with the logged-in session when UI work is required.
- Distinctive: line 30
Never bypass authentication with search results or alternate sources.
- Distinctive: line 41
Do not directly access X APIs, internal endpoints, or background HTTP interfaces.
- Distinctive: line 47
Read the source and extract the core claim, evidence, link, media, and follow-up target.
- Distinctive: line 58
Do not add a separate interpretation or summary to a long-form share.
- Very specific: line 60
Prefer one specific source link: GitHub, eunomia.dev, paper, docs, or demo.
- Very specific: line 65
Before opening the X composer, write or update the X draft under draft/media/YYYY-MM-DD/<source-slug>/x.md using the local date.
- Distinctive: line 77
no confidential or unreleased claims are present
- Distinctive: line 82
After a confirmed publish, capture the post URL, then check notifications or search results only when the user asks or when follow-up was …
- Very specific: line 90
After confirmed publish, update .github/publisher/media/published.md with source path, title or hook, X URL, date, link target, media used, …
≈ “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.
Files
X Publisher
Prepare platform-native X posts from eunomia.dev content. Publication authorization follows CLAUDE.md's Precedence Rule and Publishing section.
Inputs
- Source Markdown path, project, repo URL, paper, or topic.
- Intended format when specified: single post, thread, quote post, or X Article.
- Optional image/video, target link, posting account, or follow-up plan.
If the source path is missing, inspect .github/publisher/posts_queue.txt,
.github/publisher/media/not-published.md, recent docs/blog/posts/, and
relevant GitHub repos before asking the user.
Platform Entry Points
- Post composer: https://x.com/compose/post
- Article composer: https://x.com/compose/articles
- Home/feed: https://x.com/home
- Notifications: https://x.com/notifications
- Search: https://x.com/search
Use a browser surface with the logged-in session when UI work is required. Never bypass authentication with search results or alternate sources.
References
Load references/platform-preferences.md when choosing X-native framing,
thread shape, link/media treatment, promotion balance, or reply/mention
follow-up. Do not load broad strategy drafts for routine posting unless the user
asks for campaign or content-platform planning.
Browser-Only Platform Boundary
Do not directly access X APIs, internal endpoints, or background HTTP interfaces. All drafting, QA, screenshots, and ledger evidence must come from normal browser interactions.
Draft Preparation
- Read the source and extract the core claim, evidence, link, media, and follow-up target.
- Choose the format:
- single post for the default long-form share case: the published article link plus one or two sentences stating its core problem, tension, or result
- thread only when the user explicitly asks for a multi-step explanation
- X Article only when the user explicitly asks for long-form on X
- For an X Article that syndicates an existing long-form source, preserve the source title exactly and keep the body substantively unchanged. Only make mechanical rendering fixes and set platform metadata. A rewrite requires an explicit request for that article.
- Do not add a separate interpretation or summary to a long-form share. Let one or two useful hook sentences earn the click, then provide the link.
- Prefer one specific source link: GitHub, eunomia.dev, paper, docs, or demo.
- Prepare media alt text when the UI allows it.
Draft Archive
Before opening the X composer, write or update the X draft under
draft/media/YYYY-MM-DD/<source-slug>/x.md using the local date. Include the
full paste-ready post or thread, character counts, primary link, media/alt text,
account target when known, and QA state.
Browser QA
- text is not truncated unexpectedly and the thread order is correct
- link cards resolve to the intended URL
- uploaded media renders and has useful alt text where supported
- hashtags are absent or minimal and genuinely useful
- no confidential or unreleased claims are present
- the final action matches the task: published when authorized, untouched for a draft-only task
Follow-Up
After a confirmed publish, capture the post URL, then check notifications or search results only when the user asks or when follow-up was part of the task. Prioritize substantive replies to technical questions, corrections, and implementation interest. Do not send DMs, like, repost, follow, or quote-post without explicit user instruction.
Ledger Update
After confirmed publish, update .github/publisher/media/published.md with
source path, title or hook, X URL, date, link target, media used, and follow-up
notes. Remove or update the matching row in
.github/publisher/media/not-published.md.
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
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.

