plugins/bridgey-discord/skills/configure/SKILL.md
Set up the Discord bot — configure token, daemon URL, guild channels. Use when user says "configure discord", "set discord token", "discord setup", "discord bot setup".
npx skillsauth add kickinrad/bridgey configureInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Configure the bridgey-discord transport adapter.
The bot reads DISCORD_BOT_TOKEN from the environment (not auto-loaded from a file). Recommended: store in pass and pass inline.
If $ARGUMENTS contains a bot token (long alphanumeric string):
pass insert discord/bot-token (prompt user to paste)DISCORD_BOT_TOKEN=$(pass show discord/bot-token) npm startIf no arguments provided, show status:
pass show discord/bot-token succeedsDISCORD_BOT_TOKEN env var is currently set~/.bridgey/discord.config.jsonConfig file: ~/.bridgey/discord.config.json
Default config structure:
{
"token_env": "DISCORD_BOT_TOKEN",
"daemon_url": "http://localhost:8092",
"port": 8094,
"dm_policy": "pairing",
"guilds": {}
}
Create this file if it doesn't exist when configuring.
Guide the user through adding guild channels:
guilds:{
"guilds": {
"<guild_id>": {
"channels": ["<channel_id_1>", "<channel_id_2>"],
"require_mention": true,
"allow_from": []
}
}
}
After configuration, tell the user:
cd ${CLAUDE_PLUGIN_ROOT} && DISCORD_BOT_TOKEN=$(pass show discord/bot-token) npm startdist/bot.js (esbuild bundle) with discord.js/zod as external depsDependencies (discord.js, zod) are auto-installed on first Claude Code session via the SessionStart hook. If the bot fails with a missing module error:
node_modules/discord.js exists in the plugin directorynpm install --omit=dev --prefix ${CLAUDE_PLUGIN_ROOT}dist/bot.js is missing, rebuild: cd ${CLAUDE_PLUGIN_ROOT} && npm run buildtesting
This skill should be used when the user asks to "set up bridgey", "configure bridgey", "initialize bridgey", "bridgey setup", "check bridgey status", "show bridgey agents", "is bridgey running", "bridgey health", "show connected agents", "add a bridgey agent", "connect to another agent", "register a remote agent", "add remote agent", "configure tailscale for bridgey", "scan tailnet for bridgey", or runs `/bridgey:setup`, `/bridgey:status`, `/bridgey:add-agent`, `/bridgey:tailscale-setup`, `/bridgey:tailscale-scan`. Lifecycle surface for the bridgey A2A daemon — first-time setup, health dashboard, remote-agent registration, and Tailscale mesh discovery.
data-ai
First-time Tailscale mesh network configuration for bridgey. Updates daemon binding for tailnet access and runs initial peer scan.
data-ai
Manually scan the Tailscale network for bridgey agents. Shows discovered, new, and removed agents.
testing
This skill should be used when the user asks to "check bridgey status", "show bridgey agents", "is bridgey running", "bridgey health", "show connected agents", runs "/bridgey:status", or wants to see the state of the bridgey daemon and connected agents.