Discord Hub Builder
ReviewAudited by ClawScan on May 10, 2026.
Overview
This skill matches its Discord server-building purpose, but it needs a privileged Discord bot token and will make persistent server changes, so users should dry-run and verify permissions.
Install only if you are comfortable giving a dedicated Discord bot Manage Channels, Manage Roles, Send Messages, and Manage Messages permissions. Run the dry run first, confirm the guild ID, and manually verify channel permissions afterward, especially for owner-only, readonly, or personal channels.
Findings (3)
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.
Running the live command will change the target Discord server by adding roles, categories, channels, and pinned messages.
The live run uses Discord API POST calls to create server resources. This is expected for a server-builder skill, but it is a persistent mutation of a third-party account/server.
channel = api("POST", f"/guilds/{guild_id}/channels", token, ch_data)Run the documented dry run first, confirm the target guild ID, and preferably test on a non-production server before making live changes.
Anyone with the bot token and these permissions could make significant changes to the Discord server.
The skill requires a privileged Discord bot token. This is purpose-aligned for creating roles and channels, but the token can modify the server and should be treated as sensitive.
Requires a Discord bot token with Manage Channels, Manage Roles, and Send Messages permissions
Use a dedicated bot with only the needed permissions, keep the token private, rotate it if exposed, and remove or reduce permissions after setup if no longer needed.
Channels described as owner-only or readonly may not actually be restricted until the user manually configures Discord permissions.
The skill initially claims there are no manual steps, but later says some channel permissions must be configured manually. This is disclosed, but users should not assume restricted or readonly channels are enforced by the script.
No manual steps. ... Set channel-specific permissions manually for `#task-queue` ... and readonly channels
After the build, verify all channel permissions in Discord before posting private or sensitive information.