Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Disclaw
v1.1.2Manage Discord workspace structure and OpenClaw routing as code. Use when creating/renaming/deleting Discord channels, categories, threads, or managing agent...
⭐ 0· 478·1 current·1 all-time
by@ofan
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
Name/description, required binary ('disclaw'), and the described operations (create/rename/delete channels, manage bindings) are consistent. Requiring the Discord bot token in OpenClaw config (channels.discord.token) is appropriate for the stated purpose.
Instruction Scope
SKILL.md explicitly instructs enabling gateway access (openclaw.json: gateway.tools.allow: ["gateway"]) so disclaw can read/write OpenClaw config via the gateway API. That capability goes beyond only touching Discord — it can access OpenClaw configuration and (depending on gateway permissions) other config data. The docs also expose gateway URL and token overrides (OPENCLAW_GATEWAY_URL/TOKEN), which could be pointed to external endpoints if misused.
Install Mechanism
The packaged skill is instruction-only (no install spec), but SKILL.md tells users to run `npm install -g @ofan/disclaw`. Installing an external npm package (global) is a moderate risk: the package author is not identified here and npm postinstall scripts can execute arbitrary code. The skill itself does not supply the binary, so installing/trusting the npm package is required to actually use it.
Credentials
Only the Discord bot token (channels.discord.token) is declared as required, which is proportionate. However the gateway options can accept OPENCLAW_GATEWAY_TOKEN and a gateway URL; granting gateway access or providing a gateway token increases the scope of secrets the tool can use. Ensure the token provided is least-privilege for channel management only.
Persistence & Privilege
always:false and the skill is user-invocable (normal). The notable persistence concern is the instruction to modify openclaw.json to allow the gateway tool — that is a change to platform configuration that broadens what tools can do. The skill does not request permanent inclusion or claim to alter other skills' configs, but adding gateway permission is a significant platform-level capability and should be considered carefully.
What to consider before installing
Before installing or running this skill: 1) Verify the npm package publisher (@ofan/disclaw) and inspect the package contents (and any install scripts) before running `npm install -g`. 2) Use a Discord bot token with the minimum permissions required (prefer a token scoped to manage channels only). 3) Prefer CLI mode (no gateway) unless you trust the gateway — enabling gateway.tools.allow:["gateway"] gives the tool read/write access to OpenClaw config. 4) Never set OPENCLAW_GATEWAY_URL to an untrusted external endpoint and avoid supplying a gateway token unless necessary. 5) Test in a staging/guild with no important data and take manual backups before running `apply --yes` or `--prune`. 6) If you decide to enable gateway access, audit what other config the gateway exposes and consider revoking the permission when not in use.Like a lobster shell, security has layers — review code before you run it.
latestvk979beqh2bn1874njkdt76z5dx81wp4e
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
Binsdisclaw
Configchannels.discord.token