Discord Project Manager
ReviewAudited by ClawScan on May 10, 2026.
Overview
The skill mostly matches its Discord-management purpose, but it deserves review because it can change OpenClaw/Discord permissions and one batch-removal path may reload the gateway repeatedly contrary to the documentation.
Install only if you want OpenClaw agents to manage Discord project channels and permissions. Before use, verify the bot is scoped to the intended guild, keep backups of ~/.openclaw/openclaw.json, and be cautious with batch permission-removal commands because they may reload the gateway more than once.
Findings (5)
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.
The skill can create Discord channels/threads and change Discord project access using your configured bot.
The skill explicitly requires a Discord bot token and Manage Channels permission, allowing it to act as the bot in the configured guild.
credentials: - name: "Discord bot token" ... source: "channels.discord.accounts.*.token in OpenClaw config" ... permissions: - "Discord bot: Manage Channels"
Use a bot with the minimum required Discord permissions, limit it to the intended guild, and review commands before allowing the agent to run them.
A mistaken or overly broad command can change which agents can access Discord channels and temporarily restart the OpenClaw gateway.
The skill patches OpenClaw configuration and reloads or restarts the gateway; this is disclosed and purpose-aligned, but it is high-impact local control.
['openclaw', 'config.patch', '--raw', patch_json, '--note', note] ... os.kill(pid, signal.SIGUSR1) ... ['openclaw', 'gateway', 'restart']
Back up OpenClaw configuration, review permission changes, and test in a non-critical guild or workspace first.
Removing multiple participants could repeatedly reload the gateway and disrupt running Discord/OpenClaw coordination more than the user expects.
Each remove_channel_permission call writes config and triggers a gateway reload in lib/config.py, while SKILL.md says batch add/remove uses a single patch and only one reload; multi-agent removals may therefore cause repeated gateway reloads.
for agent_id in agent_ids: ... self.config.remove_channel_permission(account_id, guild_id, thread_id) ... removed.append(agent_id)
Review or fix batch removal to build one combined config patch, or require explicit confirmation before multi-agent removals.
Project membership, ownership, and next-action data can persist in the skill directory after use.
The skill stores persistent local agent and project state that can influence later permission and project-management actions.
data/ ... agents.json # Agent registry ... projects.json # Project registry (threads, owners, participants, nextAction)
Protect the skill data directory and periodically review or clear stale project/agent registry entries.
It may be harder to independently verify the author, upstream repository, or release history.
The artifacts do not show a remote installer or hidden dependency, but provenance information is limited.
Source: unknown; Homepage: none; No install spec — this is an instruction-only skill.
Inspect the included code and only install it in environments where you are comfortable with the shown Discord/OpenClaw access.