dingtalk-link
v1.0.0钉钉机器人连接配置指南。用于安装、配置和排查 OpenClaw 钉钉连接器 (dingtalk-connector) 的问题。当用户需要连接钉钉机器人、配置 AppKey/AppSecret、或排查钉钉消息收发问题时使用。
⭐ 0· 99·0 current·0 all-time
by@chao980
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name and description match the content: the SKILL.md explains installing/configuring the dingtalk-connector, adding AppKey/AppSecret, restarting the gateway, and troubleshooting — all appropriate for a connector setup guide.
Instruction Scope
Instructions stay within the connector setup/troubleshooting scope (install plugin, edit ~/.openclaw/openclaw.json, restart gateway, check logs). Minor inconsistency: the prerequisites list an 'OpenRouter API Key' but the guide does not explain where/how to provide it (no env var or CLI step shown).
Install Mechanism
No install spec or code files are included in the skill bundle — it's instruction-only. The only install actions are user-directed CLI commands (openclaw plugins install, npm install -g) which are appropriate for a setup guide.
Credentials
The skill does not request environment variables or credentials within the bundle. It does instruct the user to provide AppKey/AppSecret (correct for this purpose). The mention of an 'OpenRouter API Key' in prerequisites is plausible but not further justified or mapped to a config/env variable in the instructions.
Persistence & Privilege
always is false and the skill is user-invocable only. There is no instruction to modify other skills' configs or system-wide settings beyond the connector's own OpenClaw config.
Assessment
This is a configuration guide, not executable code, and appears coherent for setting up a DingTalk connector. Before proceeding: (1) verify the plugin package name (@dingtalk-real-ai/dingtalk-connector) and GitHub repo to ensure you trust the publisher; (2) do not paste secrets into chat — enter AppKey/AppSecret only via the CLI or by editing your local ~/.openclaw/openclaw.json; (3) confirm where the 'OpenRouter API Key' should be stored in your environment or OpenClaw config if you use OpenRouter; (4) running npm install -g or plugin installs requires network and may require elevated privileges — perform those commands on a trusted machine; (5) back up your OpenClaw config before editing. If you want, I can check the referenced GitHub repo URL and the connector package name for authenticity before you install.Like a lobster shell, security has layers — review code before you run it.
latestvk979e515y19y0k7x75pd3fvx6583k47j
License
MIT-0
Free to use, modify, and redistribute. No attribution required.