make-bot
Skill0 starsChanged 5 months agoMITView on GitHub
Generate a Discord or Telegram automation from a plain-English description, choosing the platform and the simplest shape that fits. Use this when the user runs /make-bot, or asks to create, build, scaffold, or set up a Discord or Telegram bot, a scheduled message, an announcement poster, or a "hook." Reads the task, settles the platform and approach with brief pros and cons, then builds it and walks the user through setup, automating every step it can.
- Reads credentials
- Installs packages
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
- 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
7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 26
If no description was given above, ask the user in one plain sentence what they want the automation to do, and wait.
- Distinctive: line 35
Make sure you understand the job.
- Very specific: line 54
Create the project at bots/<name> inside the Botter project, where <name> is the confirmed name, so every generated bot is grouped in one …
- Distinctive: line 58
Never hardcode the secret.
- Distinctive: line 60
Run npm install inside the folder so it is ready.
- Distinctive: line 69
When they paste the URL back, write it into .env for them.
- Distinctive: line 95
Keep everything minimal 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
make-bot
Generate a Discord or Telegram automation from the user's plain-English description. Botter builds for both platforms, and each has its own house style: read discord-style for Discord and telegram-style for Telegram. Read the matching style skill once the platform is settled, and follow it throughout. Both build on the same shared base in bot-style (standalone folder, TypeScript run with tsx, the secret-only .env, save-to-file, Cairo scheduling), and offer the same two shapes: a send-only poster and a full bot.
Talk to the user as if they are not a programmer. Use plain language, explain why when it helps, and never ask for anything technical they do not need (no IDs, no permission numbers, no hand-built links). Do every step you can for them; only ask them to do the few things that must be done by a human.
The user's description of the job:
$ARGUMENTS
Work through these in order.
- If no description was given above, ask the user in one plain sentence what they want the automation to do, and wait.
- Settle the platform: Discord or Telegram. If the user said which, use it. If the request makes it obvious (it names a Discord server or channel, or a Telegram chat), use that and say which you picked. Otherwise ask one short question - Discord or Telegram - and wait. Once it is settled, read that platform's style skill (discord-style or telegram-style) and follow it from here.
- Make sure you understand the job. If something essential is genuinely unclear - which channel or chat, what to say, which days, what time, or the timezone - ask one short, plain question and wait. State any assumption you make. Remember the Cairo locale: weekdays are Sunday through Thursday.
- Decide the simplest shape that does the job, using the style skill's "when to use each". Then propose it before building: name the shape you recommend in plain words, give two or three short pros and one or two cons, and say in a line what the alternative would mean. Ask the user to confirm or switch, and wait. Keep this to a few lines; do not lecture. Rule of thumb: if the job is only sending messages, recommend the poster; if it must respond, read, or react, recommend the full bot.
Propose a short, clear, lowercase project name based on its purpose (for example, standup-reminder). Ask the user to confirm it or type their own, and wait.
To save round-trips, you may present the platform, shape, and name together in one short message when no clarifying question is needed. Either way, do not create any files until the platform, the shape, and the name are all confirmed.
- Create the project at bots/
<name>inside the Botter project, where<name>is the confirmed name, so every generated bot is grouped in one place and kept out of Botter's git history. Build the project inside that folder, following the chosen platform's style skill for the chosen shape (files, dependencies, the secret-only .env, scheduling with croner in the Africa/Cairo timezone). Never hardcode the secret. - Run npm install inside the folder so it is ready.
Walk the user through setup in plain language, doing everything you can for them. Follow the path for the chosen platform and shape.
Discord, webhook poster:
- The only manual step is creating the webhook and copying its URL. Tell the user exactly where to click: in Discord, open the target channel, open its settings, choose Integrations, then Webhooks, create a new webhook, and copy its URL.
- When they paste the URL back, write it into .env for them.
Discord, full bot:
- Tell the user to open the Discord Developer Portal and create an application, then copy two things and paste them back: the Application ID from the app's main page, and the bot token from the Bot section (where they click to reveal it). Write the token into .env for them.
- Build the ready-to-click invite link yourself from the Application ID, with the minimum permissions the job needs, so they never open the OAuth2 settings. Give them the link and tell them to click it, choose their server, and approve.
- In one plain sentence, tell them which abilities the bot is asking for and why.
Telegram, either shape:
- The user creates the bot in BotFather: open BotFather in Telegram, send /newbot, follow the prompts, and copy the token it returns. Write that token into .env for them as TELEGRAM_TOKEN.
- Help them get the target chat ID and write it into .env (for example TELEGRAM_CHAT_ID). The
simplest way: add the bot to the target group or channel, or press Start in a direct chat, send
a message there, then read the chat id from https://api.telegram.org/bot
<token>/getUpdates. Group IDs are negative numbers; that is normal. - For a channel, the bot must be added as an admin before it can post. There is no invite link or developer portal; BotFather and adding the bot are all that is needed.
- Full bot only: if it must read all messages in a group, not just ones aimed at it, tell the user to turn off privacy mode in BotFather with /setprivacy, and say why.
- Finish in plain language with no emoji: give the single command to start it (npm start, run from inside the folder), and remind them the secret stays in .env and is never shared or committed.
Keep everything minimal and beginner-friendly. Do not add features the user did not ask for.
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.

