log-instagram-dm-reply
Skill63 starsChanged 2 days agoMITView on GitHub
Reading and answering an Instagram DM. A log play (docs/useCases/instagram/dmReply.md): Read what someone wrote to the account on Instagram and answer it in the owner's voice, with text or a meme, on the account's own session through vendor/instagrapi. No browser, ever.
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-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-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 Instagram and answer it in the owner's voice, with text or a meme, on the account's own session …
≈ “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 an Instagram DM
This is the log play instagram/dmReply. Before anything else, call the log MCP tool getGuide({ useCase: "instagram/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 Instagram and answer it in the owner's voice, with text or a meme, on the account's own session through vendor/instagrapi. No browser, ever.
How the owner asks for it: "read my instagram dms", "what did <someone> say on instagram", "reply to <someone> on instagram", "send <someone> a meme on instagram"
Run it from a fresh context
Say: "go on docs/useCases/instagram/dmReply.md for <someone>". The agent reads this page and runs the steps.
The steps
| # | Step | Tool | Done when |
| 1 | Session check | instagramSessionCheck { account } | loggedIn as the account's handle |
| 2 | The inbox, or the thread with them | instagramDms { account }, then instagramDms { account, with: "<handle>" } | their latest message and what came before it |
| 3 | Pull how the owner writes to them, then draft only from facts the owner gave | voice { to: "<handle>", with: "<who>", context } (no text) | a draft that answers what they said |
| 4 | For a meme, find one that fits the moment, ranked by the owner's taste, and save its picture | memelordSearch { query: ["<the moment>"], method: "fulltext", type: "meme" } | a template that fits, saved as a JPEG |
| 5 | Gate the draft or the meme | voice { to, with, context, text: "<draft or media url>" } | it passes |
| 6 | Send it: text one message per line, a meme as photo | instagramSendLive { account, with: "<handle>", text and/or photo: "<file>", approvedBy: "<owner>", confirmLive: true } | Instagram answers each message with its id |
| 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 instagram watch --inbox open for every signed-in Instagram account on Instagram's realtime connection and puts each new DM in front of the agent (>>> NEW INSTAGRAM MESSAGE).
What the runs taught
- Never the browser. On 2026-11-04 a meme went out through the account's AdsPower browser and the owner said that is not the way: read, send and watch are the engine's.
- A meme goes as the picture. Memelord answers with a media URL; save it as a JPEG and send it as
photo, never the link. - Pick from the top of the taste ranking, with judgement. A template built on a stereotype is skipped even when it ranks first.
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.

