agentleFS
matthewdonsemail-labmatthewdonsemail-lab/log/.claude/skills/log-twitter-engagement-replies/SKILL.md

log-twitter-engagement-replies

Skill63 starsChanged 2 days agoMITView on GitHub

Answering the people who engaged with your posts. A log play (docs/useCases/twitter/engagementReplies.md): When one of your posts gets comments, the people who commented are the warmest people on X for you. There are two ways to follow up, both public replies:

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:

    When one of your posts gets comments, the people who commented are the warmest people on X for you.

    line 15

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

Answering the people who engaged with your posts

This is the log play twitter/engagementReplies. Before anything else, call the log MCP tool getGuide({ useCase: "twitter/engagementReplies" }): it returns this page and makes it the session's play, so every log tool's answer says which step you are on and a send with no play loaded is refused (rules 157, 158). Then follow the steps in order.

Draft every message from that person's own thread and matt's real replies (voice with no text, search), never from memory, and never send two that read alike (sameAsSent).

When one of your posts gets comments, the people who commented are the warmest people on X for you. There are two ways to follow up, both public replies:

  • Answer their comment under your post, pointing at the follow-up (a newer post, a video, an article).
  • Reply to a fresh post of theirs where you have a real take, so the conversation moves onto their timeline.

How the owner asks for it: "reply to everyone who commented on my last tweet", "answer the comments on my post", "reply to the people who replied to my tweet with the follow-up link".

Run it from a fresh context

Say: "go on docs/useCases/twitter/engagementReplies.md for <post url>" and, if there is one, the follow-up link. The agent then reads this page and README.md and runs the steps.

The steps

#StepToolDone when
0Session checktwitterSessionCheckloggedIn
1Who commented on the post (not the account itself)treg's X comments reada list of commenters with their comment
2Drop bots and hype accounts (few followers and no bio, or a one-word "🔥"), anyone already answered, and anyone not worth a replytreg's X profile read, the account's past repliesthe people worth answering
3aAnswer the comment: one line that answers what they said, then the follow-up linkhouse stylepasses twitterQueueCheck
3bOr their own post: read their recent posts and pick one from the last few days where you have a real taketreg's X posts readone post per person and the line for it
4Show the owner the table: who, what they said, the post being replied to, the linewherever the owner readsthe owner says yes
5Queue it with likes and sendREADME queue steps: twitterQueueBuild, twitterQueueRunLivefinished

Where the comment was a question (for example "what does the first message actually look like"), the answer is the reply. Unanswered questions are the best openers.

What a line looks like

someone asked: "what is that tool?"

the thing i replaced in this one i ran all my followers through it for cents <follow-up link>

What the runs taught

  • Write in house style from the start. Copy written with full stops and commas is refused by twitterQueueCheck.
  • Vary the lines. Spintax ({a|b}) is a quick way to draft variations, but expand it into plain lines before twitterQueueBuild.

Next

  • #36 expands spintax in the queue.

Likers and reposters aren't in a comments read: they have their own page, engagerDms.md.

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.