agentleFS
tang-vutang-vu/social-posting-skills/.agents/skills/post-threads/SKILL.md

post-threads

Skill9 starsChanged 2 months agoMITView on GitHub

Adapt and publish campaign items on Threads (Meta) — posts and composer-chain threads

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No engagement bait, no recycled comments, no bait questions.

    line 34

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

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

Threads Adapter

Facts live in platforms/threads.json (500 chars, 10 images, topic tags). Threads' feature set changes fast — re-check the data file quarterly.

What Threads rewards (culture)

  • Casual, warm, conversational. Instagram energy, not LinkedIn energy.
  • Short personal takes and reply-chain storytelling.
  • One topic tag per post (tags, not hashtag strings).

Drafting from the content graph

  • core-claim → conversational opener, not a headline.
  • proof → 2–4 follow-up posts in a chain.
  • cta → soft ask; hard sells read badly here.
  • Link → reply-preferred (heuristic label in the data).

Publishing

  • agent-browser → playbook uses "Add to thread" composer chaining; posts publish together as a chain.
  • api → official Threads API exists (Meta app required); not implemented.
  • manual → draft package.

Genuine engagement

  • Reply casually to commenters; Threads is a conversation space.
  • No engagement bait, no recycled comments, no bait questions.

Pitfalls

  • Feature churn: text attachments, reply approvals, fediverse — verify current behavior in the data file before promising capabilities.
  • Automation via browser is brittle here — drafts are the safe fallback.

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.