agentleFS
uplikauplika/uplika-plugin/skills/threads/SKILL.md

threads

Skill3 starsChanged 33 days agoMITView on GitHub

Write Threads posts and chains in your voice, add a topic tag, reply to comments, and learn from your real insights what works.

10 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

5 rules. 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 1

    Distinctive

    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:

    Read ~/.uplika/<workspace-slug>/voice.md if it exists.

    line 12
  2. Very specific:

    Read the limits from select_channels or list_platforms.

    line 14
  3. Very specific:

    Topic tag: only when the person wants one: options.threads.topicTag, one topic, no periods or ampersands.

    line 21
  4. Distinctive:

    Check for machine-sounding text: before showing a draft, and rewrite when you find: the same bullet shape repeated, a summary sentence …

    line 22
  5. Very specific:

    Read with list_replies on the post (or open_post from a link).

    line 30

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “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

Short posts and chains on Threads, written hook first, sent after approval, and improved from the account's own numbers.

Before writing

  1. Read ~/.uplika/<workspace-slug>/voice.md if it exists. If not, ask three questions (tone, how posts end, words to avoid) and offer to save them with the voice-profile skill.
  2. Find the Threads account with select_channels (scope threads). If it answers workspace_required, ask which workspace and pass workspaceId.
  3. Read the limits from select_channels or list_platforms. Count characters the way charCount says.

Writing

  • Hook first. The first line is all most people see. Lead with the most specific thing: a number, a claim, a question, or the moment in a story. The hooks skill has formulas and Korean patterns.
  • One idea per post. A second idea is a second post or the next piece of a chain.
  • Chains for anything longer than one post: put the pieces in threadItems on publish (the first item is the root, the rest are replies under it in order). Each piece should stand on its own when someone lands on it.
  • Topic tag only when the person wants one: options.threads.topicTag, one topic, no periods or ampersands. It goes on the first piece.
  • Check for machine-sounding text before showing a draft, and rewrite when you find: the same bullet shape repeated, a summary sentence closing every paragraph, symmetrical "not X, but Y" contrasts, a philosophical closing line, and stacked connectors ("Moreover", "Additionally", "In addition").

Sending

Show the full text (every chain piece), the account and the time. Publish only after the person approves: publish with accountIds, threadItems or content, wait: true; for later, scheduledAt. Then give them the permalink.

Replies

  • Read with list_replies on the post (or open_post from a link). Draft replies in the same voice, show them, send approved ones with reply.
  • Mentions of the account come from list_mentions when the account holds that permission; if its notice says reconsent_required, the account was connected without it and one reconnect adds it (the troubleshoot skill explains).
  • Threads has no direct messages (faq:threads-no-dm). Liking and mentions depend on permissions shown in the features table of list_platforms; read it rather than promising.

Weekly review

Call list_channel_posts for the account and get_insights per post. Compare each post to the account's own median, never to other channels. Name the patterns behind the top posts (hook type, length, chain or single, posting time) and suggest the next three posts from them. Nulls are not zeros.

Tools

  • select_channels: the Threads account and its limits
  • list_platforms: rules and the features table
  • publish: send or schedule a post or chain after approval
  • list_replies: replies under a post
  • open_post: a post from a link with replies and metrics
  • reply: send an approved reply
  • list_mentions: posts that mention the account
  • list_channel_posts: the account's posts for the weekly review
  • get_insights: per-post metrics

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.