agentleFS
Mohamed-Sherif-AliMohamed-Sherif-Ali/botter/.claude/skills/discord-style/SKILL.md

discord-style

Skill0 starsChanged 5 months agoMITView on GitHub

The house style for Discord bots. Pulled in automatically whenever Botter builds, edits, or checks a Discord bot. Not run directly. This is the Discord counterpart to telegram-style; read bot-style first for the shared rules, then apply these Discord specifics.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    Create a new webhook (you can name it and set its avatar here), and copy its URL.

    line 31
  2. Distinctive:

    When building a Discord bot, walk the user through:

    line 57
  3. Distinctive:

    Write the token into .env for them.

    line 63

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

discord-style

This is the Discord counterpart to telegram-style. Everything in bot-style still applies: the bot is standalone in its own folder, written in TypeScript and run with tsx, keeps its one secret in .env and out of git, saves any data it needs to a file so it can run on a host, uses croner for scheduling, and takes one of the two shapes. This skill covers what is specific to Discord. Where the two ever disagree, this skill wins for Discord bots.

The two shapes, in Discord terms

  • Webhook poster. The send-only shape. The one secret is a webhook URL; it posts by sending the message to that URL with Node's built-in fetch, so it needs no Discord library. Dependencies: croner and dotenv only. No bot account, no intents, no invite. It can only post to its one channel; it cannot read, respond, or react.
  • Full bot. The interactive shape. Uses discord.js with a bot token. Request the minimum intents the job needs. Dependencies: discord.js, croner, dotenv.

Creating the webhook (poster)

A webhook poster does not log in or look anything up. Its webhook URL is both its secret and its destination: the URL already points at one specific channel, so the bot just sends messages to it. Getting that URL is the one manual setup step:

  1. In Discord, open the channel the poster should post in.
  2. Open the channel's settings, choose Integrations, then Webhooks.
  3. Create a new webhook (you can name it and set its avatar here), and copy its URL.

That URL is sensitive: anyone who has it can post to that channel, so it goes in .env like any other secret and is never committed or shared. To change which channel the poster targets, create a webhook in the new channel and swap the URL; there is no channel-by-name lookup for a poster.

Finding the channel (full bot)

A full bot finds any target channel by its name once connected, and stops with a clear message if that name is not found. Never use a pasted channel ID. This is the full bot's counterpart to the poster's fixed webhook URL: the poster is wired to one channel by its URL, while a full bot resolves channels by name at runtime.

Intents

A full bot requests only the intents its job needs. If a privileged intent is required (presence, the member list), tell the user to enable it in the Developer Portal and say why, the same way telegram-style flags privacy mode.

Secrets

The one secret lives in .env, as bot-style says. For a webhook poster it is the webhook URL; for a full bot it is the bot token. Never hardcode it.

Setup, in short

When building a Discord bot, walk the user through:

  • Webhook poster: the only manual step is creating the webhook and copying its URL, as described above. When they paste it back, write it into .env for them.
  • Full bot: the user opens the Discord Developer Portal, creates an application, and copies two things back: the Application ID from the app's main page, and the bot token from the Bot section. 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 touch the OAuth2 settings; give them the link to click, choose their server, and approve. Say in one plain sentence which abilities the bot is asking for and why.

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.