agentleFS
jocarrdjocarrd/crux-agents/skills/x-posts/SKILL.md

x-posts

Skill4 starsChanged 18 days agoMITView on GitHub

Write and plan posts for X (Twitter) that reach people and build a personal brand. Covers how the algorithm distributes reach, the first-line hook, which format to use for each goal, when and how much to post and what to do in the first hour. Use when you need to write a tweet, prepare a thread, announce a launch or an article, or decide what to publish on X.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 8 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Quote: only if you add a fact, a nuance or your experience.

    line 61
  2. Very specific:

    Run the draft through /prose-check.

    line 70
  3. Distinctive:

    No asking for empty engagement ("RT si…", "comenta SÍ").

    line 71
  4. Distinctive:

    Do not edit in the first half hour except for a data error.

    line 88
  5. Distinctive:

    Do not publish another post of yours until this one has had its run.

    line 89
  6. Distinctive:

    Look at the account: the latest published and what performed.

    line 95
  7. Distinctive:

    Write two or three hooks and keep the most concrete one.

    line 99
  8. Distinctive:

    Write the body and decide where the link goes.

    line 100
  9. Very specific:

    Run /prose-check and the checklist below.

    line 101
  10. Distinctive:

    After publishing, the first hour.

    line 104

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

The deliverable is drafts. Nothing is ever published without the author's explicit OK on the exact text. How X distributes reach, with the measured weights and the sources, is in <this-skill-directory>/references/why.md; before an important campaign, check whether they have changed.

Do not use for the voice or data of a specific project (those go in its adapter), for long texts that are not for X, or for publishing on someone's behalf without their approval.

What decides reach

  • A reply is worth much more than a like; sharing or following the author too.
  • Negative signals (reporting, muting, "not interested") subtract enormously.
  • Several posts in a row from the same author perform worse; posts older than 48 hours are no longer distributed.
  • A link in the body reduces reach: it goes in the first reply, and the post has to be worth it without clicking.

One post, one goal

GoalWhat achieves itClosing
ConversationA well-grounded opinion, a question your audience knows how to answerA concrete question that can be answered in one line
Save and shareResource, list, framework, useful figuresNothing, or "link in the first reply"
FollowersA recognisable series, process with continuityWhat comes next
ClickA result that only makes full sense outside XLink in the first reply, with the reason why

Personal brand

Weekly split: process (the bulk: what you build, what went wrong, what you decided, with a number or screenshot), contribution (what helps someone who does not know you) and promotion (the minimum). Each post is a chapter of something that continues, the person comes ahead of the product, and you reply to everyone who replies.

The first line

It stands on its own, in under 10 words if possible, and says what it is about with concrete words. Forms that work: a result with a number, a chapter of a story ("Día N de…"), a decision ("Hoy he quitado X. El motivo:"), a mistake with its cost, a verifiable useful fact, a free resource, a well-grounded opinion, a real question. No "Esto lo cambia todo", "Nadie habla de" or "Hilo 🧵👇" on their own.

Formats

  • Short post: one idea, 1 to 4 lines, blank line between blocks.
  • With image or video: the image is understood without reading the post.
  • Thread: 5 to 12 posts; the first promises what the thread delivers, each one stands on its own, link and call to action at the end.
  • Reply: for a small account, the fastest route: contribute on accounts in your topic 2 to 10 times your size, early.
  • Quote: only if you add a fact, a nuance or your experience.
  • Self-reply: the link, an update or the next chapter.

Writing

  • Concrete before adjective ("tardaba 40 minutos, ahora 3").
  • Short sentences.
  • One or two emojis as a signal at the start of a block; at most one hashtag; mentions only with a reason.
  • Run the draft through /prose-check.
  • No asking for empty engagement ("RT si…", "comenta SÍ").

When and how much

FollowersPosts per dayThreads per weekReplies per day
Under 1,0001-3110-20
1,000-10,0002-51-25-15
Over 10,0003-62-35-10

At least 3 or 4 hours between your own posts. Post when your audience is awake and you can stay for the first hour.

The first hour

  1. The link, in the first reply, in minute one.
  2. Reply to every reply with something that continues the conversation.
  3. Do not edit in the first half hour except for a data error.
  4. Do not publish another post of yours until this one has had its run.
  5. At 48 hours look at impressions, replies, profile visits and new followers, and note which hook and format performed.

Procedure

  1. Look at the account: the latest published and what performed. Do not repeat an angle or a fact from the last 7 days.
  2. Choose the goal and where it fits in the week's split.
  3. Gather the proof: a number, a screenshot or a real example.
  4. Write two or three hooks and keep the most concrete one.
  5. Write the body and decide where the link goes.
  6. Run /prose-check and the checklist below.
  7. Show the author the exact text, the image, the reply with the link and the time. Wait for the OK.
  8. After publishing, the first hour.

Checklist

  • The first line says what it is about with concrete words.
  • There is a number, a screenshot or a real example.
  • A single idea and a single goal.
  • The link is not in the body, or there is a reason.
  • The post is worth it even if nobody clicks.
  • If it seeks conversation, it closes with something that can be answered.
  • At most one hashtag, mentions only with a reason.
  • Separated by at least 3 hours from the author's previous post.
  • Approved by the author, exact text.

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.