remove-bot
Skill0 starsChanged 5 months agoMITView on GitHub
Remove a Discord or Telegram automation the user made, cleanly and safely. Use this when the user runs /remove-bot, or asks to remove, delete, or get rid of a bot or webhook poster they made. Confirms which one, deletes its folder after the user agrees, and reminds the user to delete the leftover Discord app or webhook, or the Telegram bot in BotFather, so no live credential is left behind.
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
- list-botsSkill
- make-botSkill
- package-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 8
Remove a bot the user made, and make sure nothing risky is left behind.
- Distinctive: line 20
If no bot was named above, look in the bots/ folder (older bots may still sit at the project root.
- Distinctive: line 31
After they confirm, delete that bot's folder.
- Distinctive: line 48
Only ever remove the single bot folder the user confirmed.
≈ “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
remove-bot
Remove a bot the user made, and make sure nothing risky is left behind. 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, because you need its platform and shape to clean it up properly.
Talk to the user as if they are not a programmer. Use plain language.
The bot the user wants to remove:
$ARGUMENTS
Work through these in order.
- If no bot was named above, look in the bots/ folder (older bots may still sit at the project root; check there too), list the bots by name, and ask which one to remove. Wait.
- Once the bot is identified, read it just enough to tell its platform and shape: a Discord full bot (discord.js and a bot token), a Discord webhook poster (a webhook URL), or a Telegram bot (a BotFather token, either shape).
- Confirm before deleting anything. Tell the user the exact folder you are about to delete and that this cannot be undone, and ask them to confirm. Wait for a clear yes. Never delete anything outside that one bot folder.
- After they confirm, delete that bot's folder.
- Then handle the leftover credential, because deleting the folder does not turn anything off on
the platform's side. In plain language:
- Discord full bot: the bot's login token stays active until the application is deleted. Walk the user to the Discord Developer Portal, open that bot's application, and delete it there.
- Discord webhook poster: the webhook can still post until it is deleted. Walk the user to the channel's settings, then Integrations, then Webhooks, and delete the one this bot used.
- Telegram bot: the bot and its token stay alive in Telegram until the bot is deleted. Walk the user to BotFather, have them send /deletebot, pick this bot from the list, and confirm by typing the line BotFather asks for. This permanently removes the bot and kills its token. There is no API for this; it has to be done by hand in BotFather.
- Finish in plain language with no emoji: confirm the folder is gone, restate the one platform-side step they still need to do, and if this bot was tracked in git, mention they can commit its removal.
Only ever remove the single bot folder the user confirmed. Never touch skills, tools, CLAUDE.md, or anything else in the project.
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.

