write-x-thread-or-article
Skill0 starsChanged 28 days agoMITView on GitHub
Write an X (Twitter) thread or a long-form X Article and post it with PostEverywhere. Use when the user asks for a thread, a tweetstorm, a long post on X, an X Article, or wants to turn a blog post or idea into a thread or article on X.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- posteverywhere/copilot-pluginword for word, first seen Oct 17, 2026
- posteverywhere/claude-pluginword for word, first seen Sep 29, 2026
Other versions2 projects use a version of this.
Word for word · 2
- posteverywhere/claude-plugin★ 1100% same
- posteverywhere/copilot-plugin★ 0100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- agency-clientsSkill
- approval-workflowSkill
- brand-voiceSkill
- connect-social-accountsSkill
- cross-post-videoSkill
- fix-failed-postsSkill
- launch-announcementSkill
- plan-content-calendarSkill
- recycle-top-postsSkill
- repurpose-contentSkill
- review-post-performanceSkill
- schedule-social-postsSkill
- weekly-reportSkill
- write-blog-postSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 3 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Ask the user when it isn't clear.
- Very specific: line 21
Post it as a real thread: Call create_post with the X account_ids, content set to part 1, and thread_posts set to the other parts, in order.
- Distinctive: line 24
If a part is too long, the post is refused before anything goes out and the error names the part.
- Very specific: line 25
After it publishes, call get_post_results and give the user the link.
- Distinctive: line 26
Don't schedule the parts as separate posts.
- Very specific: line 34
Create it: Call create_post with only X account_ids, content set to the body, media_ids if any, draft: true, and platform_content: {"x": …
- Very specific: line 36
Publish or schedule: After the user confirms, call schedule_post with the post_id and scheduled_for (with timezone) or publish_now: true.
- Distinctive: line 43
Don't invent facts, numbers or quotes to fill a thread or an article.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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 threads and X Articles
A thread is a chain of short posts, each a reply to the one before. An X Article is one long-form piece with a title, headings and images, for X Premium accounts only.
Pick the format
- The idea fits in a few short points, or the account isn't on X Premium: a thread.
- The piece is long, needs headings or images in the body, and the account is on X Premium: an article.
- Ask the user when it isn't clear. Call
list_accountsto get the X account ids.
Write a thread
- Plan it. 3 to 10 parts. The first part is the hook: it must work on its own, because most people see only that one.
- Write each part in 280 characters or fewer (X Premium accounts can go longer;
get_platform_ruleshas the limit). One idea per part. Number the parts (1/6) only if the user likes that. - Show the thread. Show every part with its character count. Ask the user to confirm.
- Post it as a real thread. Call
create_postwith the Xaccount_ids,contentset to part 1, andthread_postsset to the other parts, in order. PostEverywhere posts each part as a reply to the one before, so it goes out as one linked thread.- To let the user check it first, add
draft: true. After they confirm, callschedule_postwith thepost_idandscheduled_for(withtimezone) orpublish_now: true. The whole thread goes out. - Threads and Bluesky accounts can take the same thread (Threads allows 500 characters a part, Bluesky 300). Other accounts in the same post get only part 1, so make a separate post for them.
- If a part is too long, the post is refused before anything goes out and the error names the part. Shorten that part or split it, then try again.
- After it publishes, call
get_post_resultsand give the user the link. Don't schedule the parts as separate posts. They would not be linked as replies.
- To let the user check it first, add
Write an X Article
- Check the limits. X Premium accounts only. Title up to 100 characters. Body up to 25,000 characters. Each X account can publish 2 articles in 24 hours.
- Write the body in simple formatting:
#headings,-lists,>quotes,**bold**,*italic*,[links](https://...),---dividers, code blocks and tables. A line that is only an X post link embeds that post. - Images (optional). Up to 5 images, no video. Upload each with
upload_media_from_url. The first image is the cover (2000 x 800 looks best). Place others in the body with a line like, or they go at the end. - Show the draft. Show the title, the body and which images go where. Ask the user to confirm.
- Create it. Call
create_postwith only Xaccount_ids,contentset to the body,media_idsif any,draft: true, andplatform_content:{"x": {"content": "<body>", "settings": {"post_type": "article", "title": "<title>"}}} - Publish or schedule. After the user confirms, call
schedule_postwith thepost_idandscheduled_for(withtimezone) orpublish_now: true. Then callget_post_resultsand give the user the link.
Be careful
- An article goes to X accounts only. If the user also wants other platforms, make a separate post for them.
- A post is a thread or an article, not both:
thread_postscan't be used with an X Article. - X Articles need X Premium. Ask the user if the account has it before you choose an article.
- Don't invent facts, numbers or quotes to fill a thread or an article.
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.

