check-bot
Skill0 starsChanged 5 months agoMITView on GitHub
Figure out why a bot is not working and tell the user, in plain language, what to fix. Use this when the user runs /check-bot, or says a bot is broken, not posting, not responding, erroring, offline, or "not working." Reads the bot's recent output and settings, checks the common causes, and explains the fix.
- Reads credentials
- Installs packages
In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- bot-styleSkill
- deploy-to-cloudSkill
- deploy-to-hostSkill
- discord-styleSkill
- edit-botSkill
- keep-runningSkill
- list-botsSkill
- make-botSkill
- package-botSkill
- remove-botSkill
- rotate-secretSkill
- security-checkSkill
- skillsSkill
- telegram-styleSkill
- test-botSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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 21
If no bot was named above, look in the bots/ folder (older bots may sit at the project root.
- Distinctive: line 31
Check the common causes, in roughly this order, and stop at the first that explains the symptom.
- Distinctive: line 61
If nothing obvious turns up, say so honestly and suggest the next thing to look at rather than guessing.
- Distinctive: line 64
Keep it plain and beginner-friendly.
≈ “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
check-bot
Work out why a bot is not behaving and explain the fix in plain words. The bot may be a Discord or a Telegram bot; read the matching style skill (discord-style for Discord, telegram-style for Telegram) once you know which, so you know what a correct setup looks like.
Talk to the user as if they are not a programmer. Translate any error into plain language; never just paste a raw stack trace at them.
The bot the user is asking about, and any symptom they described:
$ARGUMENTS
Work through these in order.
- If no bot was named above, look in the bots/ folder (older bots may sit at the project root; check there too), list the bots by name, and ask which one is misbehaving. Wait.
- Gather evidence. Look at the bot's recent output: if it runs under PM2, read its log
(pm2 logs
<name>); otherwise look at whatever error or output the user can show you. Read the bot's own code and settings enough to know what it expects, and note which platform and shape it is: Discord (discord.js with a bot token, or a Discord webhook URL) or Telegram (a BotFather token, using grammY for a full bot or the Telegram Bot API for a poster). Read the matching style skill. Check the common causes, in roughly this order, and stop at the first that explains the symptom.
Shared, both platforms:
- Is the bot even running? A scheduled post cannot happen if the process is not up.
- Dependencies: is node_modules there, that is, has npm install been run?
- The secret in .env: is it present, and not still the .env.example placeholder?
- Scheduling: is the schedule and timezone what the user expects (remember Cairo, weekdays are Sunday to Thursday)?
Discord:
- Is the secret the right kind? A very common mistake is pasting a webhook URL where a bot token belongs. A discord.js "invalid token" error almost always means this.
- Full bot: has it been invited to the server, does the target channel name exist, and are the intents it needs turned on (including any privileged one enabled in the Developer Portal)?
- Webhook poster: does the webhook still exist, or was it deleted on Discord's side?
Telegram:
- Is the token valid? A 401 or "Unauthorized" from the Telegram API means the token is wrong, mistyped, or was revoked in BotFather.
- Is the target chat ID right, and is the bot actually in that chat? A "chat not found" or "bot was kicked" error means the bot is not a member, or the ID is wrong. For a channel, the bot must be an admin.
- Full bot that should read all group messages: is privacy mode off in BotFather? With privacy mode on, the bot only sees messages aimed at it.
- Tell the user in plain language what you found and the single most likely fix, with the exact step. If it is something safe you can do for them (run npm install, point out a mistyped channel name or chat ID), offer to do it. If it needs them (regenerate a token, enable an intent, turn off privacy mode, get the bot invited or added), walk them through that step.
- If nothing obvious turns up, say so honestly and suggest the next thing to look at rather than guessing.
Keep it plain and beginner-friendly. Do not change a bot's behavior while diagnosing; fix only the specific thing that is broken, and explain it 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.

