agentleFS
posteverywhereposteverywhere/copilot-plugin/skills/write-x-thread-or-article/SKILL.md

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

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

    Ask the user when it isn't clear.

    line 14
  2. Very specific:

    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.

    line 21
  3. Distinctive:

    If a part is too long, the post is refused before anything goes out and the error names the part.

    line 24
  4. Very specific:

    After it publishes, call get_post_results and give the user the link.

    line 25
  5. Distinctive:

    Don't schedule the parts as separate posts.

    line 26
  6. Very specific:

    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": …

    line 34
  7. Very specific:

    Publish or schedule: After the user confirms, call schedule_post with the post_id and scheduled_for (with timezone) or publish_now: true.

    line 36
  8. Distinctive:

    Don't invent facts, numbers or quotes to fill a thread or an article.

    line 43

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

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

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_accounts to get the X account ids.

Write a thread

  1. 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.
  2. Write each part in 280 characters or fewer (X Premium accounts can go longer; get_platform_rules has the limit). One idea per part. Number the parts (1/6) only if the user likes that.
  3. Show the thread. Show every part with its character count. Ask the user to confirm.
  4. 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. 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, call schedule_post with the post_id and scheduled_for (with timezone) or publish_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_results and give the user the link. Don't schedule the parts as separate posts. They would not be linked as replies.

Write an X Article

  1. 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.
  2. 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.
  3. 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 ![caption](image:2), or they go at the end.
  4. Show the draft. Show the title, the body and which images go where. Ask the user to confirm.
  5. 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": {"content": "<body>", "settings": {"post_type": "article", "title": "<title>"}}}
  6. Publish or schedule. After the user confirms, call schedule_post with the post_id and scheduled_for (with timezone) or publish_now: true. Then call get_post_results and 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_posts can'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.

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.