log-slack-dm-reply
Skill63 starsChanged yesterdayMITView on GitHub
Reading and answering a Slack DM. A log play (docs/useCases/slack/dmReply.md): Read what someone wrote to the account on Slack and answer it in the owner's voice, on the account's own session, with no browser.
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-twitter-affiliate-marketingSkill
- log-twitter-collab-maxxingSkill
- log-twitter-dm-inboxSkill
- log-twitter-engagement-repliesSkill
- 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
Read what someone wrote to the account on Slack and answer it in the owner's voice, on the account's own session, with no browser.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Reading and answering a Slack DM
This is the log play slack/dmReply. Before anything else, call the log MCP tool getGuide({ useCase: "slack/dmReply" }): 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).
Read what someone wrote to the account on Slack and answer it in the owner's voice, on the account's own session, with no browser.
How the owner asks for it: "read the messages with <someone> on slack", "reply to <someone> on slack", "what did <someone> say in <workspace>"
Run it from a fresh context
Say: "go on docs/useCases/slack/dmReply.md for <someone>". The agent reads this page and runs the steps.
The steps
| # | Step | Tool | Done when |
| 0 | The account is known: a local row with its d cookie | localAccountList {}; if missing, the owner runs log slack cookies save --account <name> in a terminal | the account is listed |
| 1 | Session check, and which workspaces it is in | slackSessionCheck, then slackWorkspaces | loggedIn, with the workspace's domain |
| 2 | Find the chat by who it is with | slackChats { account, workspace } | one DM or group with that person |
| 3 | Read the chat | slackRead { account, workspace, chat, limit } | their latest message and what came before it |
| 4 | Pull how the owner writes to them, then draft only from facts the owner gave | voice { to, with, context } (no text) | a draft that answers what they asked |
| 5 | Gate the draft | voice { to, with, context, text } | it passes |
| 6 | Send it, one message per line | slackSendLive { account, workspace, chat, text, approvedBy: "<owner>", confirmLive: true } | Slack answers each line with its ts |
| 7 | Tell the owner what they said and what went out | the reply to the owner | both quoted with their times |
New messages arrive by themselves: the inbox hook keeps log slack watch --inbox open for every signed-in account and puts each new DM, group message or mention in front of the agent (>>> NEW SLACK MESSAGE).
What the runs taught
- Read the chat before sending. The voice gate inside
slackSendLivereads the chat's context from the .db, not from Slack (rule 137).slackReadstores what it reads there as backfill, so step 3 is what gives the gate the chat's history. Once a thank-you was refused three times while the .db held only 2 of the other person's messages, and the gate read it as a cold first message with an ask in it. Backfilled history is never shown as new messages. - Send by who it is with. Give
chatas the person (their name or handle), not only the D… id, so the gate matches the owner's history with them by name. - Don't stack messages on a chat the owner already answered. When the owner's own messages are the newest in the chat (the owner has already said thanks), a third message is refused as not the owner's voice, and it reads like it. Answer it with a reaction instead (
slackReactLive, inbox/reactions), or leave it. A 🙏 on a contact's short thank-you went out this way.
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.

