list-bots
Skill0 starsChanged 5 months agoMITView on GitHub
Show an overview of every bot the user has made. Use this when the user runs /list-bots, or asks what bots they have, which ones exist, or which are running. Lists each bot's name, its platform and shape, what it does, and whether it is currently running.
In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- bot-styleSkill
- check-botSkill
- deploy-to-cloudSkill
- deploy-to-hostSkill
- discord-styleSkill
- edit-botSkill
- keep-runningSkill
- 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
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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 9
Read the discord-style and telegram-style skills if you need help recognizing the shapes.
- Distinctive: line 33
If there are no bots yet, say so plainly and mention they can make one with make-bot.
≈ “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
list-bots
Give the user a quick, plain overview of the bots they have made, across both Discord and Telegram. Read the discord-style and telegram-style skills if you need help recognizing the shapes.
Talk to the user as if they are not a programmer. Use plain language.
$ARGUMENTS
Work through these in order.
- Find the bots: look in the bots/ folder, and also at the project root for any older bots made before the bots/ folder existed.
- For each bot, work out, without changing anything:
- its name (the folder name),
- its platform and shape: a Discord webhook poster (uses a webhook URL), a Discord full bot (uses discord.js and a token), a Telegram poster (uses a BotFather token to send via the Telegram Bot API), or a Telegram full bot (uses grammY),
- in one short line, what it does, taken from its README or code,
- whether it is currently running. If PM2 is in use, check pm2 list; if a bot is not under PM2, just say it is not running in the background.
- Show the user a simple list, one bot per line, with its name, platform and shape, what it does, and its running state. Keep it short and scannable; do not dump code or settings. If the user asked to narrow the list (for example, only the running ones), show just those.
- If there are no bots yet, say so plainly and mention they can make one with make-bot.
This skill only reads; it never changes anything.
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.

