agentleFS
postoncehqpostoncehq/threads-mcp/skills/threads-post-writer/SKILL.md

threads-post-writer

Skill2 starsChanged 44 days agoMITView on GitHub

Write Threads posts (up to 500 characters, text, images, video or carousel) that sound conversational and get replies, ready to publish with the PostOnce Threads MCP. Use when the user asks to write a Threads post, Threads ideas, something to post on Threads, or to turn an update, opinion, article or notes into a Threads post.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. sergebulaev/threads-skills★ 52same name

    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 repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Write one Threads post that reads like a person talking, then hand it to the postonce skill if the user wants it published or scheduled.

    line 11
  2. Distinctive:

    Write like a text to a smart friend.

    line 32
  3. Distinctive:

    No hashtag strings. This server can't set a Threads topic tag, so don't rely on tags for reach.

    line 34

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

Threads post writer

Write one Threads post that reads like a person talking, then hand it to the postonce skill if the user wants it published or scheduled.

Before writing

Get or infer: who's posting (person or brand), who they want to talk to, the one idea or opinion, and any real detail that makes it specific. If the source is long, pick one idea. Never invent numbers, customers or quotes.

What works on Threads

Threads rewards conversation. Posts that start replies travel further than posts that broadcast. Write for that:

PatternShape
Hot takeA clear opinion in one or two lines. "Most onboarding emails should be one sentence."
Honest momentSomething that happened, told plainly. "Shipped a bug to 400 people today. Here's what I told them."
Ask the roomA specific question people can answer from experience. "What's the one tool you'd pay for twice?"
Small lesson"Took me 3 years to learn this:" then the lesson in a sentence or two.
Show the workA photo or screen recording with one line of context.

Rules:

  • Lead with the point. The first line is the whole post for most readers.
  • Short and loose: one to three sentences suits most posts. The hard limit is 500 characters, and text over it gets cut off.
  • Write like a text to a smart friend. Lowercase-casual is fine if it's the user's voice. No corporate tone, no "we're thrilled to announce".
  • End with something easy to reply to, when it fits: a question, a take people will argue with, or an invitation to share theirs.
  • No hashtag strings. This server can't set a Threads topic tag, so don't rely on tags for reach.
  • One link at most, and only when it's the point of the post.

Longer ideas

This server can't publish a multi-post thread (a reply chain). If the idea won't fit in 500 characters:

  • Cut it to the one sharpest point and publish that.
  • Or put the detail in images and publish a carousel (up to 10 images or videos) with a short post on top.
  • Or give the user the follow-up posts to add as replies themselves in the Threads app after the first one goes live.

Media

An image or short video usually beats text alone for brand accounts. Images: JPEG or PNG up to 8 MB. Video: MP4 or MOV, up to 5 minutes. GIFs aren't supported.

Output

Give the post exactly as it will appear with its character count, plus one alternate opening line. Suggest a visual if it would help. Offer to publish or schedule it with the postonce skill; confirm the Threads account and the time before calling create_post.

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.