New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Discord App Setup

by vellum-ai in vellum-ai/vellum-assistant

Connect a Discord bot to the assistant via the Discord Gateway with guided application creation and intent configuration

MITAuto-check passedProductivity & Automation

Install Discord App Setup

skills CLI
$ npx skills add vellum-ai/vellum-assistant --skill discord-app-setup -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install vellum-ai/vellum-assistant discord-app-setup --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/vellum-ai/vellum-assistant.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/discord-app-setup .claude/skills/discord-app-setup && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
discord-app-setup
GitHub stars
1.4k
Token cost
~4.2k tokens
SKILL.md length
2,511 words
Files
8 (incl. scripts, references, assets)
Skills in repo
108
Repo updated
First seen
Licence
MIT

At a glance

Connect a Discord bot to the assistant via the Discord Gateway with guided application creation and intent configuration

  • Works in 9 steps: Check Existing Configuration → 5: Prefer the In-Product Wizard → Create the Discord Application → …
  • Tasks that involve Messaging and chat bots
  • SKILL.md covers Value Classification, Step 0: Check Existing…, Step 0.5: Prefer the… and Step 1: Create the Discord…, plus 8 more sections
  • Runs TypeScript scripts from its folder; calls bun; reaches discord.com

What it does

Discord App Setup is an agent skill from vellum-ai/vellum-assistant. Connect a Discord bot to the assistant via the Discord Gateway with guided application creation and intent configuration

Its SKILL.md is about 4.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including scripts, reference files and assets (for example `references/troubleshooting.md`, `scripts/__tests__/print-invite-url.test.ts` and `scripts/check-config.ts`). Compatibility notes: Designed for Vellum personal assistants

It sits in Productivity & Automation, covering Messaging and chat bots. It works with Discord. The repository describes itself as: An AI Assistant that’s easy to setup, does your work 24/7, knows your preferences and gets better over time. The licence is MIT.

When your agent uses it

  • Tasks that involve Messaging and chat bots

Example prompts

  • “/discord-app-setup”

Requirements

  • Node.js
  • Compatibility (from SKILL.md): Designed for Vellum personal assistants

Workflow steps

9 steps, taken from the step headings in SKILL.md.

  1. Check Existing Configuration
  2. 5: Prefer the In-Product Wizard
  3. Create the Discord Application
  4. Configure the Bot User
  5. Generate & Collect the Bot Token
  6. Validate the Bot Token
  7. Generate OAuth Invite URL & Add Bot to a Server
  8. Verify the User's Discord Identity
  9. Report What Setup Delivered

What it can do on your machine

Read from SKILL.md and the folder at commit 33cc983. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 5 files in scripts/ (TypeScript), which the agent can run.

    Shell commands in SKILL.md call:

    • bun

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • discord.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Vellum personal assistants

    From compatibility in the SKILL.md frontmatter.

Context cost

Discord App Setup loads about 4.2k tokens when it runs, and up to ~5.5k if it reads all its reference files. Until then it costs about 35 tokens; SKILL.md has 2,511 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~35
When it runs · the whole SKILL.md, loaded when a task matches
~4.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from vellum-ai/vellum-assistant at commit 33cc983, republished under its MIT licence (© vellum-ai). 2,511 words, ~4,236 tokens.

Download SKILL.mdSave it as .claude/skills/discord-app-setup/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
discord-app-setup
description
Connect a Discord bot to the assistant via the Discord Gateway with guided application creation and intent configuration
compatibility
Designed for Vellum personal assistants
metadata.icon
assets/icon.svg
metadata.emoji
🎮

You are helping your user create a Discord application and connect a Discord bot to the assistant via the Discord Gateway. Walk through each step below.

CRITICAL: Follow these steps strictly in order. Do NOT combine steps, skip ahead, or ask for the bot token before the bot user has been configured. The token is shown only once after reset — collect it the moment the user generates it, never before.

Value Classification

ValueTypeSecret?
Bot TokenCredentialYes

The Bot Token is the only value that needs to be persisted. Always collect it via the assistant's secure credential prompt — never accept it pasted in plaintext chat.

The Application ID and Public Key are derivable from the bot token at any time via Discord's API and do not need to be stored separately.

Setup Steps

Step 0: Check Existing Configuration

Before starting, run the check script:

bash
bun skills/discord-app-setup/scripts/check-config.ts

The script outputs JSON: { "configured": boolean, "details": string, "error"?: string }.

  • If error is present, stop. The check could not run, so the credential state is unknown, and configured: false here does not mean "not set up". Do not start the setup walkthrough. It will not fix this, and re-running setup on an app that already has a token forces a needless token reset that breaks any other deployment using it.
    • cli_not_found means the assistant command is missing from this environment's PATH. That is an installation problem. Report it as one, quote details, and stop.
    • cli_failed or unparseable_output means the CLI ran but did not answer usefully. Report details verbatim and stop.
  • If configured is true — Discord is already set up. Offer to verify the connection or reconfigure.
  • If configured is false with no error, the check ran and found no token. Continue to Step 0.5.

Step 0.5: Prefer the In-Product Wizard

If an interactive client is connected, call ui_show with surface_type: "channel_setup" and data: { channel: "discord" }. This opens the Discord setup wizard in the side panel: create the app, connect the token through a masked field, add the bot to a server, and finish with a hand-back to identity verification, all without the token entering chat. The wizard is non-blocking and auto-notifies you when it is closed.

⚠️ Tool call first, announcement second, in the same turn. Do not claim the wizard is open until the ui_show call has returned success. After success, tell the user:

I've opened the Discord setup wizard in the side panel. It walks you through creating the app, connecting its bot token, and adding the bot to a server, and its last step hands verification back to me. It will notify me when you close it; ask me here if you hit a snag.

When a notification saying the user completed the wizard and asked to verify their identity arrives, the wizard's finish step was reached: the user confirmed the bot joined a server and pressed its Verify me action. Re-run the Step 0 check script to confirm a token was stored, then skip the invite question below and go straight to Step 6 (identity verification) without re-asking which channel.

When a plain wizard-closed notification arrives, re-run the Step 0 check script to confirm a token was stored. A stored token completes Steps 1 through 4; the invite (Step 5) happens on the wizard's Add to server step, and closing the panel does not prove it happened. Ask the user directly:

Did you add the bot to a server in the wizard? If not, I can give you the install link again.

If they did not, run the Step 5 invite script and have them complete it before continuing. Only then continue at Step 6 (identity verification). Do not mark setup complete while the bot is in no server.

If ui_show fails (no interactive client, or the surface is rejected), fall back to the chat-guided flow below: it collects the token through the secure credential prompt instead.

Step 1: Create the Discord Application

Tell the user:

Open https://discord.com/developers/applications and click New Application in the top-right. Give it a name (this is how the bot appears to users) and accept the Developer Terms of Service. After creation you'll land on the application's General Information page.

Wait for the user to confirm they've created the app before proceeding. Discord does not support manifest-based creation — the rest of the configuration happens step by step in the portal.

Offer the assistant's avatar as the app icon. General Information is where Discord takes one, so this is the moment to mention it; the wizard path in Step 0.5 shows the same thing on its own create step. The rendered PNG sits at $VELLUM_WORKSPACE_DIR/data/avatar/avatar-image.png and is 512x512 for a character avatar. Tell the user:

While you're on General Information, you can set the bot's icon to your assistant's avatar. I can point you at the file if you'd like it.

Skip this if the assistant has no avatar set. It is cosmetic, so do not block setup on it.

Step 2: Configure the Bot User

Discord automatically attaches a Bot user to every new application. This integration needs no privileged intents, so the only thing to do here is confirm all three are off.

Direct the user:

In the left sidebar click Bot. Scroll to Privileged Gateway Intents and leave all three OFF:

  • ⬜ Presence Intent
  • ⬜ Server Members Intent
  • ⬜ Message Content Intent

If any are already enabled, turn them off and click Save Changes.

Why none are needed: the assistant's Discord client identifies with the non-privileged GUILDS, GUILD_MESSAGES, and DIRECT_MESSAGES intents only. It acts on messages that mention the bot and on DMs sent to it, and Discord exempts four cases from the Message Content restriction: messages that mention your app, DMs with your app, your app's own messages, and the target of a message context-menu command. Every message the assistant reads falls inside that exemption and already arrives with full text. Server Members would deliver GUILD_MEMBER_* events that nothing here consumes.

Turning them on would grant access the software never reads, and would opt the app into Discord's privileged-intent review (with annual reapplication) once it is visible to more than 10,000 users.

ℹ️ Two different Discord thresholds are easy to confuse. Bot verification is required past 100 servers. Privileged-intent review is required past 10,000 unique users who can see the app. With no privileged intents enabled, the second does not apply to this integration at all.

Wait for the user to confirm the intents are off before proceeding.

Step 3: Generate & Collect the Bot Token

Do NOT skip ahead. The bot token is the only path to the bot's identity — it must be collected immediately on generation, before the user navigates away from the page.

Direct the user:

On the same Bot page, click Reset Token and confirm. Discord displays the token once, right then: copy it now and paste it into the secure prompt that appears in your assistant.

There is no Copy or View Token button for a token that already exists. Once the token has been shown and you leave the page, Reset is the only way to get a usable value again.

⚠️ If this application is already connected somewhere else, Reset Token invalidates the old token immediately and breaks that deployment. Only reset if you are willing to reconnect anything else using this app.

Run the store script:

bash
bun skills/discord-app-setup/scripts/store-bot-token.ts

The script opens the assistant's secure credential prompt, validates the entry, and stores it under discord_channel:bot_token. Exit code 130 means the user cancelled the prompt — nothing was stored. That's a valid choice, not an error: ask whether they'd like to try again rather than treating it as a failure. Any other non-zero exit is a real failure — ask the user to reset the token and re-run.

Step 4: Validate the Bot Token

Run:

bash
bun skills/discord-app-setup/scripts/validate-token.ts

The script:

  • Calls GET https://discord.com/api/v10/users/@me to validate the token and capture botUserId, botUsername
  • Calls GET https://discord.com/api/v10/oauth2/applications/@me to capture the application's id, name, and verifyKey (public key)
  • Prints a summary of the bot + application identity to stdout
  • Exits 0 on success

If the script exits with a 401, the token is invalid — ask the user to reset and re-enter (repeat Step 3). The script does not persist any of the captured metadata; it's all derivable from the bot token on demand.

Show full SKILL.md (1,142 more words)Show less

Step 5: Generate OAuth Invite URL & Add Bot to a Server

The bot needs to be invited to a Discord server (guild) before it can receive or send messages.

Run:

bash
bun skills/discord-app-setup/scripts/print-invite-url.ts

This calls GET /oauth2/applications/@me with the stored bot token to discover the application and prints the invite URL. Which URL depends on the app:

  • The app has Default Install Settings (configured on the portal's Installation page): the URL carries only the client ID, so the grant is whatever those settings say. This is Discord's current model, and it means a person who edits those settings sees their edit take effect instead of being silently overridden by parameters in the URL. Because those settings now own the grant, the script re-checks them: it refuses to print a URL when they omit the bot scope (installing would add no bot user at all), and it warns on stderr when they request scopes this integration never uses, grant Administrator, or omit permissions the integration exercises. gdm.join in particular would let the bot join group DMs, which inbound handling treats as private DMs. Have the user make the named edit on the Installation page rather than proceeding past a warning.
  • No Default Install Settings: the URL spells out the grant itself:
https://discord.com/oauth2/authorize?client_id=<APP_ID>&permissions=277025770560&scope=bot

The applications.commands scope is not requested separately: Discord includes it with the bot scope, and nothing here registers a command.

The default permission integer (277025770560) covers: View Channels, Send Messages, Send Messages in Threads, Embed Links, Attach Files, Read Message History, Add Reactions, Use External Emojis, and Use Slash Commands. It deliberately does not include Administrator, Manage Channels, Manage Roles, Manage Threads, Create Public Threads, Kick/Ban Members, or Mention Everyone — request more only if a downstream feature requires it, and document the reason.

When Default Install Settings exist, the same least-privilege bar applies to what the user configures there.

Direct the user:

Open the URL in your browser, choose the server you want the bot in, click Authorize, and complete the captcha if prompted.

Wait for the user to confirm the bot has joined the server before continuing.

Step 6: Verify the User's Discord Identity

This binds the user's Discord account to their identity, so the bot knows who it is talking to and can address them by name rather than treating them as a stranger. Without it the channel is connected but recognises nobody, so do not skip it silently.

It has to happen after Step 5: the code is delivered as a Discord DM, and Discord only permits a bot to DM someone it shares a server with.

Load the guardian-verify-setup skill:

  • Call skill_load with skill: "guardian-verify-setup".

The channel is already discord. Do not re-ask which channel to verify.

If the user wants to skip, continue to Step 7 and tell them they can verify later by saying "verify me on Discord".

Step 7: Report What Setup Delivered

Report exactly what is now true, and what is still required before the bot answers anything. Do not claim the bot is live: it appears online in the member list the moment it connects, which reads as "working" even while it ignores every message.

Summarize:

Discord connected.
✅ Application created
✅ Privileged intents left off (none are needed)
✅ Token stored and validated
✅ Bot in server: {guild_name}

Connected: {bot_username} (application: {application_name})
Intents: Guilds, Guild Messages, Direct Messages (no privileged intents)

Ready. Mention the bot in any channel it can see and it will reply
(for senders its admission policy accepts; see below when verification
was skipped).

Then tell the user how it is scoped:

In a server the bot replies when it is @mentioned in a channel it can see. Which channels those are is Discord's own setting, not ours: a bot reads a channel only where its role has View Channel, exactly as it would for a person.

If identity verification was skipped in Step 6, also say so plainly: the default Who-can-message policy admits trusted contacts, so until the user verifies (or the guardian widens the Discord policy in Channels), the bot will see mentions but decline to answer them. Do not present a skipped verification as a fully working setup.

To keep it out of a channel, deny View Channel to the bot's role there, or move the bot's role so it does not have access to a category. To let it in, grant the same permission. Discord's channel settings are the one place that lives, so there is nothing to configure on our side.

DMs are separate: the bot can be messaged directly, because a DM is already addressed to it alone. Who it answers there is governed by the channel's admission policy, which admits trusted contacts rather than anyone who shares a server with it.

Two things gate a reply and are worth naming if the bot stays silent: the mention itself (it does not respond to unmentioned messages), and the channel's admission policy, which by default admits trusted contacts rather than anyone in the server.

Implementation Rules

  • All token collection goes through a masked secure path: the in-product wizard (ui_show with surface_type: "channel_setup"), or the secure credential prompt via scripts/store-bot-token.ts in the chat-guided fallback. Do NOT ask the user to paste the token in chat.
  • Do NOT combine multiple steps into a single message. Each step must be its own turn. Wait for the user to confirm completion before moving on.
  • Do NOT collect the bot token before Step 3. The token is shown once and cannot be retrieved later, so it must be collected in the same turn the user generates it, with the secure prompt already open.
  • Do NOT request the Administrator permission on the OAuth invite URL. The default permission integer was chosen with the principle of least privilege — only request more if a downstream feature explicitly requires it, and document why.
  • Do NOT enable any privileged intent. The client identifies with GUILDS, GUILD_MESSAGES, and DIRECT_MESSAGES only, all three non-privileged, and nothing reads presence, member, or non-mention guild-message events. Enabling one grants access the software never uses and opts the app into Discord's privileged-intent review past 10,000 users.
  • Do NOT claim the bot replies everywhere once setup finishes. It answers only where it is @mentioned, in channels Discord lets it see. Say which server it joined rather than implying the whole account is wired up (Step 7).
  • Do NOT instruct the user to set an Interactions Endpoint URL. Gateway-connected bots receive interactions over the WebSocket — the HTTP endpoint is only needed for HTTP-only interaction handlers.
  • Do NOT end setup without offering identity verification. A connected bot that recognises nobody treats its own owner as a stranger. Step 6 is a skip the user declines explicitly, never one taken on their behalf.
  • Do NOT persist the application ID, public key, or bot user metadata anywhere outside the credential vault. They are derivable from the bot token on demand and persisting them risks staleness after a token reset.

Disconnecting

To disconnect Discord, delete the discord_channel:bot_token credential. Resetting the token in the developer portal also immediately invalidates the old credential. To remove the bot from a specific server, the server owner kicks it from the member list.

For 401/403, intent errors, OAuth invite errors, and token reset guidance, see references/troubleshooting.md.

© vellum-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 7 other files (scripts, references, assets) in skills/discord-app-setup of vellum-ai/vellum-assistant.

  • SKILL.md
  • assets/icon.svg
  • references/troubleshooting.md
  • scripts/__tests__/print-invite-url.test.ts
  • scripts/check-config.ts
  • scripts/print-invite-url.ts
  • scripts/store-bot-token.ts
  • scripts/validate-token.ts

Open the folder on GitHubat commit 33cc983

Compare with similar skills

Discord App Setup next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Discord App Setup compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Discord App Setup this skillvellum-ai/vellum-assistant1.4k—~4.2kAutomated safety check: PassMIT
Easy Openclawdaheiai/easy-openclaw112—~1.7kAutomated safety check: NotesNone
Discrawlopenclaw/openclaw392k—~698Automated safety check: PassMIT
Message Push0xranx/golembot322—~984Automated safety check: PassMIT
Task Manager0xranx/golembot322—~694Automated safety check: PassMIT
Discord Channel for NanoClawnanocoai/nanoclaw31k—~2.2kAutomated safety check: NotesMIT

Similar skills

  • Easy Openclaw

    daheiai/easy-openclaw

    OpenClaw 配置优化向导。采用“第 0 层测试观测（可选）+ 前 3 轮优化 + 第 4 轮接入扩展”流程：基础推荐层（含联网搜索与权限模式）、渠道增强层（Discord/Feishu/Telegram 分支优化）、Skills 推荐层（可执行可跳过）、新增渠道接入引导（可跳过）。用于帮助用户快速完成 OpenClaw 初始化或优化配置。用户说到“优化…

    112 GitHub stars~1.7k tokensUpdated 6 mo ago
    Productivity & AutomationAuto-check: notes

  • Discrawl

    openclaw/openclaw

    Discord archive: search, sync freshness, DMs, summaries, TUI, repo/release work.

    392k GitHub stars~698 tokensUpdated today
    Productivity & AutomationAuto-check passed

  • Message Push

    0xranx/golembot

    Send proactive messages to IM groups or individual users via the gateway Send API.

    322 GitHub stars~984 tokensUpdated 12 days ago
    Productivity & AutomationAuto-check passed

  • Task Manager

    0xranx/golembot

    Creates and manages scheduled tasks, cron jobs, recurring reminders, and timers via the Task HTTP API.

    322 GitHub stars~694 tokensUpdated 12 days ago
    Productivity & AutomationAuto-check passed

  • Discord Channel for NanoClaw

    nanocoai/nanoclaw

    Adds a Discord bot channel to NanoClaw through the Chat SDK bridge, with the adapter copied in from the channels branch and a registration test.

    31k GitHub stars~2.2k tokensUpdated yesterday
    Productivity & AutomationAuto-check: notes

  • Channel Config

    OPPO-Mente-Lab/X-OmniClaw

    Configure messaging channels in X-OmniClaw, including Feishu and Discord.

    265 GitHub stars~419 tokensUpdated 4 mo ago
    Productivity & AutomationAuto-check passed

More from vellum-ai/vellum-assistant

All 108 skills in this repo

  • Vellum GitHub App Setup

    vellum-ai/vellum-assistant

    Create and configure a GitHub App so the assistant can push commits, open PRs, and comment under its own bot identity.

    1.4k GitHub stars~3.1k tokensUpdated yesterday
    Auto-check passed

  • Sentry App Setup

    vellum-ai/vellum-assistant

    Create and configure a Sentry internal integration so the assistant can manage issues, alerts, and releases under its own identity

    1.4k GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed

  • Memory Corpus Ingest

    vellum-ai/vellum-assistant

    Ingest a large dataset into memory as a skimmed map. An agent skill from vellum-ai/vellum-assistant.

    1.4k GitHub stars~3k tokensUpdated yesterday
    Auto-check: notes

  • Plugin Builder

    vellum-ai/vellum-assistant

    A skill your agent uses when the user wants to build, scaffold, ship, or edit a Vellum plugin that bundles multiple surfaces (hooks, tools, skills, and more) into one installable package.

    1.4k GitHub stars~3.1k tokensUpdated yesterday
    Auto-check passed

  • Slack App Setup

    vellum-ai/vellum-assistant

    Connect a Slack app to the Vellum Assistant via Socket Mode.

    1.4k GitHub stars~2.5k tokensUpdated yesterday
    Auto-check: warnings

  • Amazon

    vellum-ai/vellum-assistant

    Shop on Amazon and Amazon Fresh through your browser. An agent skill from vellum-ai/vellum-assistant.

    1.4k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Discord App Setup

What does Discord App Setup do?

Connect a Discord bot to the assistant via the Discord Gateway with guided application creation and intent configuration. Discord App Setup is an agent skill from vellum-ai/vellum-assistant.

When should I use Discord App Setup?

Discord App Setup fits situations like: tasks that involve Messaging and chat bots.

How do I install Discord App Setup in Claude Code?

Run `npx skills add vellum-ai/vellum-assistant --skill discord-app-setup -a claude-code`. Or copy the skill folder (skills/discord-app-setup in vellum-ai/vellum-assistant) into .claude/skills/discord-app-setup in your project. Claude Code loads it when a task matches its description.

How do I install Discord App Setup in Codex?

Run `npx skills add vellum-ai/vellum-assistant --skill discord-app-setup -a codex`. Or copy the skill folder (skills/discord-app-setup in vellum-ai/vellum-assistant) into .agents/skills/discord-app-setup in your project. Codex loads it when a task matches its description.

Can I use Discord App Setup in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vellum-ai/vellum-assistant --skill discord-app-setup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/discord-app-setup, .gemini/skills/discord-app-setup, .github/skills/discord-app-setup and .opencode/skills/discord-app-setup in your project.

What does Discord App Setup need to run?

Going by SKILL.md and its folder, Discord App Setup needs TypeScript for the scripts in its folder and the command-line tools its instructions call (bun). Our summary lists: Node.js. Compatibility (from SKILL.md): Designed for Vellum personal assistants.

Does Discord App Setup access the network?

SKILL.md names 1 domain. In commands or code: discord.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Discord App Setup safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Discord App Setup use?

Discord App Setup is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Discord App Setup use?

About 4.2k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.3k tokens, read only when the agent opens those files.

What are the alternatives to Discord App Setup?

Skills that share tags, products or a category with Discord App Setup: Easy Openclaw (daheiai/easy-openclaw, 112 stars), Discrawl (openclaw/openclaw, 392k stars), Message Push (0xranx/golembot, 322 stars) and Task Manager (0xranx/golembot, 322 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Discord App Setup?

vellum-ai (a GitHub organization) maintains it in vellum-ai/vellum-assistant, which has 1,408 GitHub stars. The repository holds 108 skills in this directory. The repository was last updated on October 9, 2026.

Source: vellum-ai/vellum-assistant on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.