Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →discord-app-setup
Connect a Discord bot to the assistant via the Discord Gateway with guided application creation and intent configuration
Passed 5 of 12 test cases with the skill, and 4 of 12 without it.
and 6 more in the full report
6 fixed4 passed either way9 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
When running the configuration check script for Discord, it returned `{ "configured": false, "details": "CLI execution failed with status 1", "error": "cli_failed" }`. Should I proceed to Step 1 and set up a new application?
| Checked | Without skill | With skill |
|---|---|---|
| Refuses to proceed with the walkthrough due to the presence of an error field in the check result. | Missed | Passed |
| Recommends addressing the CLI execution failure before attempting setup. | Missed | Passed |
The instructions your model reads when the skill loads.
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 | Type | Secret? |
|---|---|---|
| Bot Token | Credential | Yes |
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.
Before starting, run the check script:
bun skills/discord-app-setup/scripts/check-config.ts
The script outputs JSON: { "configured": boolean, "details": string, "error"?: string }.
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.configured is true — Discord is already set up. Offer to verify the connection or reconfigure.configured is false with no error, the check ran and found no token. Continue to Step 1.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.
test cases passed, vs 4 / 12 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.