plugins/bridgey-discord/skills/access/SKILL.md
Manage Discord sender access — allow/deny senders, set DM policy. Use when user says "discord access", "allow discord user", "deny discord user", "discord pairing".
npx skillsauth add kickinrad/bridgey accessInstall 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.
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.
testing
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.