Back to skill
Skillv1.0.0

ClawScan security

DingTalk Channel Setup · ClawHub's context-aware review of the artifact, metadata, and declared behavior.

Scanner verdict

BenignMar 9, 2026, 6:06 AM
Verdict
benign
Confidence
high
Model
gpt-5-mini
Summary
The skill's requested actions and configuration align with its stated purpose (setting up a DingTalk channel); it is an instruction-only guide that modifies only OpenClaw plugin/config files and asks for expected DingTalk credentials.
Guidance
This guide is coherent for setting up a DingTalk channel. Before proceeding: (1) verify you trust the npm package @soimy/dingtalk and its upstream repository (review code or repository reputation) because installing the plugin will execute third-party code; (2) back up ~/.openclaw/openclaw.json before automated scripts modify it; (3) treat Client ID/Client Secret as sensitive—do not share them or paste them into public locations; (4) prefer official registries or verify the mirror you use (npmmirror) and any proxy settings to avoid supply-chain/Man-in-the-Middle risks. If you cannot verify the plugin source, consider inspecting the plugin package contents after installation before enabling it.

Review Dimensions

Purpose & Capability
okName/description (DingTalk channel setup) match the instructions: installing a dingtalk OpenClaw plugin, adding it to ~/.openclaw/openclaw.json, and supplying DingTalk AppKey/AppSecret. No unrelated credentials, binaries, or unexpected capabilities are requested.
Instruction Scope
okSKILL.md instructs only installation of the plugin, editing OpenClaw config, restarting the gateway, and basic troubleshooting (checking gateway status, logs, plugin directory). Those file paths and commands (openclaw, ~/.openclaw/openclaw.json, extension directory) are directly relevant to the stated task and are not overly broad.
Install Mechanism
noteThe skill is instruction-only (no code), but it instructs using `openclaw plugins install @soimy/dingtalk` which will fetch and install an npm-scoped plugin. Installing a third-party plugin runs code obtained from the npm registry (or a mirror). This is expected for a plugin-based setup but is a downstream trust/risk consideration; the SKILL.md itself does not use obscure download URLs.
Credentials
okThe only sensitive inputs are the expected DingTalk credentials (Client ID/AppKey and Client Secret) used to configure the channel. No unrelated secrets or system credentials are requested. The guide suggests setting HTTP(S)_PROXY and NPM_CONFIG_REGISTRY for installation, which is normal for users behind proxies.
Persistence & Privilege
okThe skill does not request elevated or persistent platform privileges. always is false and the instructions only modify the skill's own OpenClaw config (~/.openclaw/openclaw.json) and extension directory, which is appropriate for adding a channel plugin.