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:
In this repository82 other files it gives its agents.
- AGENTS.mdAGENTS.md
- log-discord-channel-replySkill
- log-discord-forum-postsSkill
- log-discord-group-chat-readSkill
- log-discord-meme-replySkill
- log-discord-server-replySkill
- log-discord-server-searchSkill
- log-facebook-groupsSkill
- log-facebook-marketplace-listingsSkill
- log-inbox-boss-maxxingSkill
- log-inbox-governor-resetSkill
- log-inbox-reactionsSkill
- log-inbox-rea-looksmaxxingSkill
- log-inbox-scope-ajobSkill
- log-inbox-show-meSkill
- log-inbox-sign-inSkill
- log-inbox-triageSkill
- log-inbox-voice-noteSkill
- log-instagram-dm-replySkill
- log-instagram-new-platformSkill
- log-linkedin-networkSkill
- log-linkedin-postsSkill
- log-reddit-contributor-maxxingSkill
- log-slack-dm-replySkill
- log-twitter-affiliate-marketingSkill
- log-twitter-collab-maxxingSkill
- log-twitter-dm-inboxSkill
- log-twitter-engager-dmsSkill
- log-twitter-followersSkill
- log-twitter-follow-upsSkill
- log-twitter-get-the-actionSkill
- log-twitter-manager-maxxingSkill
- log-twitter-network-maxingSkill
- log-twitter-niche-map-regionSkill
- log-twitter-notificationsSkill
- log-twitter-recruitingSkill
- log-twitter-reply-guy-funnelSkill
- log-twitter-topic-repliesSkill
- log-twitter-who-needs-youSkill
- log-web-competitor-trafficSkill
- accountToDryRunSkill
- adsPowerSkill
- agentHooksSkill
- callTimingSkill
- captureRuleSkill
- commitLogSkill
- consoleSkill
- conversationsSkill
- devlogMaxxingSkill
- discordServersSkill
- facebookFlowsSkill
- facebookInspectSkill
- facebookWarmupSkill
- flowSkill
- governorSkill
- hostSkill
- humanMouseSkill
- inspectSkill
- instagramSkill
- knowledgeBaseSkill
- The first 60 shown.
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
- Distinctive: line 15
When one of your posts gets comments, the people who commented are the warmest people on X for you.
≈ “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.
Files
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
| # | Step | Tool | Done when |
| 0 | Session check | twitterSessionCheck | loggedIn |
| 1 | Who commented on the post (not the account itself) | treg's X comments read | a list of commenters with their comment |
| 2 | Drop bots and hype accounts (few followers and no bio, or a one-word "🔥"), anyone already answered, and anyone not worth a reply | treg's X profile read, the account's past replies | the people worth answering |
| 3a | Answer the comment: one line that answers what they said, then the follow-up link | house style | passes twitterQueueCheck |
| 3b | Or their own post: read their recent posts and pick one from the last few days where you have a real take | treg's X posts read | one post per person and the line for it |
| 4 | Show the owner the table: who, what they said, the post being replied to, the line | wherever the owner reads | the owner says yes |
| 5 | Queue it with likes and send | README queue steps: twitterQueueBuild, twitterQueueRunLive | finished |
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 beforetwitterQueueBuild.
Next
- #36 expands spintax in the queue.
Likers and reposters aren't in a comments read: they have their own page, engagerDms.md.
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
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.

