菜单
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".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | configure |
| description | 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". |
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. Each persona runs its own bot with its own token, stored at discord/<persona>-bot-token (e.g. discord/julia-bot-token).
If $ARGUMENTS contains a bot token (long alphanumeric string):
pass insert discord/<persona>-bot-token (prompt user to paste)DISCORD_BOT_TOKEN=$(pass show discord/<persona>-bot-token) npm startIf no arguments provided, show status:
pass show discord/<persona>-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:8091",
"port": 8094,
"dm_policy": "pairing",
"guilds": {}
}
Create this file if it doesn't exist when configuring.
daemon_url defaults to the host hub daemon (http://localhost:8091). Production persona bots point at their persona spoke's URL instead — Docker service name + spoke port (e.g. http://bridgey-julia:8092).
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 ~/projects/markets/bridgey/apps/discord-bot && DISCORD_BOT_TOKEN=$(pass show discord/<persona>-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 ~/projects/markets/bridgey/apps/discord-bot/npm install --omit=dev --prefix ~/projects/markets/bridgey/apps/discord-botdist/bot.js is missing, rebuild: cd ~/projects/markets/bridgey/apps/discord-bot && npm run buildThis skill should be used when the user asks to "set up bridgey", "check bridgey status", "add a bridgey agent", or "scan the tailnet for bridgey". Lifecycle surface for the bridgey A2A daemon — first-time setup, health dashboard, remote-agent registration, and Tailscale mesh discovery.
Deploy an agent to a remote server as a Docker container with Tailscale SSH access, optional Coolify integration, and bidirectional sync. Walks through server setup, hardening, Tailscale, Docker, deployment, and post-install tooling. Use when the user asks to deploy an agent remotely, set up a remote server, run an agent 24/7, or make an agent headless.
Check the health and status of the remote agent deployment. Use when the user says "remote status", "check remote", "is my agent running", "server status", or runs /remote-status.
Sync agent files between local and remote server. Use when the user says "sync", "push to remote", "pull from remote", "sync agent", or runs /sync.
Manage Discord sender access — allow/deny senders, set DM policy. Use when user says "discord access", "allow discord user", "deny discord user", "discord pairing".