agentleFS
prantikmedhiprantikmedhi/crossbar/skills/x-write-like-me/SKILL.md

x-write-like-me

Skill2 starsChanged 11 days agoMITView on GitHub

Draft X posts, replies, quotes and threads in the user's own voice by studying their recent posts with Crossbar, then post only what the user approves. Use when the user asks to write, draft or reply on X "like me", in their voice, or to turn notes, a link or a changelog into a post.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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:

    Call x_whoami, then x_user_posts for the user (about 40 posts, include_replies: true).

    line 10

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

Write like the user

1. Learn the voice (once per session)

Call x_whoami, then x_user_posts for the user (about 40 posts, include_replies: true). Note, don't over-fit:

  • length (one-liners or paragraphs), line breaks, lists
  • case (all lowercase?), punctuation, emoji (which, how often), hashtags (usually none)
  • how they open and end, whether they use links in the post or in a reply
  • topics they post about and what they never touch

2. Draft

  • Give 2–3 options of different shapes (one-liner, short take, mini-thread) unless asked for one.
  • Under 280 characters each unless the user has longer posts.
  • Plain claims over hype. No "🚀 Excited to announce", no "game-changer", no hashtag walls, unless that is how the user writes.
  • Replies: read the post with x_get_post first; answer the post, not the topic.
  • Threads: first post must stand alone. Number only if the user does.

3. Approve, then post

Show the drafts. Post nothing until the user picks one, and then post exactly that text with x_post, x_reply or x_quote. For a thread, post the first, then reply to your own post with each next one, in order, using the id the previous call returned.

Report the link. If the write field is not applied, check the profile before trying again.

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.