القائمة
Manage Discord sender access — allow/deny senders, set DM policy. Use when user says "discord access", "allow discord user", "deny discord user", "discord pairing".
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | access |
| description | Manage Discord sender access — allow/deny senders, set DM policy. Use when user says "discord access", "allow discord user", "deny discord user", "discord pairing". |
Manage who can send messages through the Discord transport.
When a new Discord user sends a DM with dm_policy: "pairing", the bot sends a pairing request through the bridgey daemon. The bridgey MCP server triggers an elicitation dialog — you'll see an inline approve/decline prompt in your Claude session. No codes or manual commands needed.
If elicitation isn't available (e.g. orchestrator mode), use allow <user_id> below.
Parse $ARGUMENTS to determine the action:
allow <user_id>Directly add a Discord user ID to the allowlist:
~/.bridgey/discord/access.json (create if missing: {"allowed_senders":[]})allowed_senders if not already presentdeny <user_id> or remove <user_id>Remove a user from the allowlist:
~/.bridgey/discord/access.jsonallowed_senderspolicy <pairing|allowlist|disabled>Update the DM policy in ~/.bridgey/discord.config.json:
dm_policy to the specified valuelistShow current access config:
~/.bridgey/discord/access.json (allowed senders)~/.bridgey/discord.config.jsonShow current access status summary and list available commands.
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".
This 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.