Discord Claude Code Delegation
PassAudited by ClawScan on May 1, 2026.
Overview
This instruction-only skill is coherent, but it intentionally forwards Discord DM tasks and identifiers through a private bot-to-bot worker channel, so users should verify channel and bot permissions.
This skill appears safe for its stated purpose if you want a Discord-based controller-to-worker workflow. Before using it, confirm the worker lane is private, only the intended controller and worker bots are present, trusted bot IDs are allowlisted, and users understand that delegated DM content will be visible to the worker bot and retained wherever Discord messages are retained.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If the Discord lane or bot permissions are too broad, other accounts or bots could see delegated tasks or influence the relay workflow.
The skill depends on Discord bot identities and channel membership. This is expected for the stated controller-worker workflow, but users should ensure only the intended bots can read and write in the worker lane.
- one private worker lane in a Discord server - one controller bot present in that lane - one worker bot present in that lane
Use a dedicated private channel, verify the controller and worker bot IDs, and keep bot permissions limited to the minimum needed for this workflow.
The worker bot and anyone with access to the private lane may see the delegated task and associated Discord identifiers.
The task envelope copies the original DM task and Discord identifiers into the worker lane for another bot to process. This is central to the skill’s design and is disclosed, but it is still an inter-agent data handoff.
source-channel-id: <original-dm-channel-id> source-message-id: <original-dm-message-id> requester-discord-id: <requester-discord-id> task: @WORKER_BOT <worker-facing task body>
Avoid delegating highly sensitive content unless the worker lane and bot operators are trusted; keep the lane private and use the documented trusted-author and channel allowlists.