--- name: log-twitter-engagement-replies description: "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:" when_to_use: "Use when the owner asks for this, in words like: \"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\"." metadata: summary: "Answering the people who engaged with your posts" --- # 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 the owner'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 "** and, if there is one, the follow-up link. The agent then reads this page and [README.md](https://github.com/matthewdonsemail-lab/log/blob/main/docs/useCases/twitter/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](https://treg.to/?ref=matthewdonse-aebsh)'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 `` ## 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](https://github.com/matthewdonsemail-lab/log/issues/36) expands spintax in the queue. Likers and reposters aren't in a comments read: they have their own page, [engagerDms.md](../log-twitter-engager-dms/SKILL.md). > Some links in this play carry ListeningKit's referral or affiliate credit (a `ref=` or `aff=` code). They cost the owner nothing extra; use the plain address without the code if you prefer.