log-discord-forum-posts
Skill63 starsChanged 2 days agoMITView on GitHub
Going through a Discord forum for posts worth answering. A log play (docs/useCases/discord/forumPosts.md): Find a forum in a server, list its posts, read the ones that look right, and tell the owner which are worth answering and why: someone asking for help with something the owner has built or knows, a question nobody answered yet, a problem log solves. This page reads and sends nothing; answering one is [serverReply](serverReply.md).
In this repository82 other files it gives its agents.
- AGENTS.mdAGENTS.md
- log-discord-channel-replySkill
- 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-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
Files
Going through a Discord forum for posts worth answering
This is the log play discord/forumPosts. Before anything else, call the log MCP tool getGuide({ useCase: "discord/forumPosts" }): 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).
Find a forum in a server, list its posts, read the ones that look right, and tell the owner which are worth answering and why: someone asking for help with something the owner has built or knows, a question nobody answered yet, a problem log solves. This page reads and sends nothing; answering one is serverReply.
How the owner asks for it: "look at the <server> forum and find the one about <problem>", "go through the forum in <server> and tell me which posts to respond to", "list the posts in <server> #<forum>", "find posts in <server> asking for help with <thing>"
Run it from a fresh context
Say: "go on docs/useCases/discord/forumPosts.md for <server>, looking for <what>". The agent reads this page and runs the steps.
The steps
| # | Step | Tool | Done when |
| 1 | Find the server's forums | discordChannels { account, server: "<server>" } | the forum and media channels, with their tags; when the owner named the forum, that one |
| 2 | List the forum's posts, newest activity first | discordPosts { account, channel: "<server> #<forum>", limit: 50 } | each post's title, author, tags, replies, open or closed, and opening message |
| 3 | When the owner is looking for one subject, search the server for it too | discordSearch { account, server: "<server>", query: "<words>", channel: "<server> #<forum>" } | the posts whose replies mention it, not only their titles |
| 4 | Read each post that looks right, text only | discordRead { account, channel: "<server> #<forum> > <post title>", limit: 50, noMedia: true } | what was asked, what was answered, and whether the owner already wrote there |
| 5 | Tell the owner which posts are worth answering | the reply to the owner | each one named as "<server> #<forum> > <title>", who asked, when, what they need, whether anyone answered, and why it fits |
What to know
- Judge from the list first. The opening message, tags and reply count come with every post in step 2, so open only the ones that could fit. A closed or locked post can't be answered.
- Worth answering means someone asked something the owner can really help with, nobody has solved it, and it's recent enough that they're still there. A post where the owner already wrote is the owner's; say so instead of suggesting it.
- Search reaches the replies. A post's title can hide what it's about; step 3 finds posts where the subject comes up anywhere in them.
- Name every post.
"<server> #<forum> > <post title>", never its id.discordPostskeeps each post's name, sodiscordReadfinds it straight after. - Nothing is sent from this page. To answer one, follow serverReply with the post as the channel.
- What each part of a server is: the
discordServersskill in the discord guide.
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.

