agentleFS
Mohamed-Sherif-AliMohamed-Sherif-Ali/botter/.claude/skills/edit-bot/SKILL.md

edit-bot

Skill0 starsChanged 5 months agoMITView on GitHub

Change an existing Discord or Telegram automation from a plain-English description. Use this when the user runs /edit-bot, or asks to change, edit, update, tweak, fix, or add a feature to a bot or poster they already made. Finds the bot under bots/, applies the change following the matching style skill, and guides any extra setup.

  • Reads credentials
  • Installs packages

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    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
  1. Distinctive:

    If no change was described above, ask the user in one plain sentence what they want to change, and wait.

    line 21
  2. Distinctive:

    If the user named a bot, use it.

    line 26
  3. Distinctive:

    If there is only one bot, use it and say which one you are changing.

    line 27
  4. Distinctive:

    If there are several and the user did not say which, list them by name and ask which one.

    line 28
  5. Distinctive:

    Wait until the bot is clear.

    line 29
  6. Distinctive:

    Read that bot's current code and settings so you understand what it does now, which platform it is (Discord or Telegram), and which shape …

    line 31
  7. Distinctive:

    Check the change fits the current shape, using the style skill's "when to use each".

    line 35
  8. Distinctive:

    If the change adds a new dependency, run npm install in the bot's folder.

    line 43
  9. Distinctive:

    Keep changes minimal and beginner-friendly.

    line 53

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

edit-bot

Change a bot the user already made, from a plain-English description. The bot may be a Discord or a Telegram bot; once you know which, read the matching style skill (discord-style for Discord, telegram-style for Telegram) and keep every convention it sets. Read it before changing anything.

Talk to the user as if they are not a programmer. Use plain language and never ask for anything technical they do not need.

The user's requested change:

$ARGUMENTS

Work through these in order.

  1. If no change was described above, ask the user in one plain sentence what they want to change, and wait.
  2. Find which bot to change. Look in the bots/ folder (older bots may still sit at the project root; check there too if needed).
    • If the user named a bot, use it.
    • If there is only one bot, use it and say which one you are changing.
    • If there are several and the user did not say which, list them by name and ask which one. Wait until the bot is clear.
  3. Read that bot's current code and settings so you understand what it does now, which platform it is (Discord or Telegram), and which shape it is (a poster or a full bot). Read the matching style skill.
  4. Check the change fits the current shape, using the style skill's "when to use each". If the change needs abilities the current shape cannot do (for example, asking a poster to reply to messages), do not force it: explain this in plain words, propose switching to the other shape with a short pro and con, and wait for the user to confirm before rebuilding.
  5. Make the smallest change that satisfies the request. Keep everything else exactly as it was; do not rewrite or reformat parts you were not asked to touch. Keep following the style skill.
  6. If the change adds a new dependency, run npm install in the bot's folder. If it needs a new secret, a new channel or chat, or a new permission, walk the user through it the same way make-bot does for the bot's platform: write secrets into .env for them; for a Discord full bot, build any invite link yourself and say which intent to enable and why; for a Telegram bot, help get the chat ID and, if it must read all group messages, turn off privacy mode in BotFather.
  7. Finish in plain language with no emoji: say what you changed in a sentence or two, and how to see it, which is to stop the bot if it is running (Ctrl+C) and start it again with npm start from inside the bot's folder.

Keep changes minimal and beginner-friendly. Do not add anything the user did not ask for.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.