钉钉快速集成配置
v1.0.0钉钉快速集成配置 - 5分钟连接 OpenClaw 与钉钉，解锁机器人消息、审批流程、智能办公。适合：企业用户、钉钉生态、国内企业。
⭐ 0· 150·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The skill's name/description match the content: it explains how to configure DingTalk webhooks in OpenClaw. The only declared required binary is curl, which is reasonable for troubleshooting examples; there are no unexpected environment variables or unrelated services requested.
Instruction Scope
Instructions tell the user to edit ~/.openclaw/config.yml (to add webhook/secret) and to run openclaw gateway restart. This is appropriate for a configuration guide, but it implicitly assumes the user/agent can edit that config file and restart the OpenClaw service. The doc also describes OpenClaw behaviors (reading todos, monitoring, calling DingTalk APIs) — expected for integration but note these imply the agent will access whatever data sources OpenClaw uses.
Install Mechanism
No install spec or code is included (instruction-only). Nothing is downloaded or written by the skill itself, minimizing install-time risk.
Credentials
The skill does not request environment variables or external credentials, but it instructs the user to place webhook URLs and optional secrets into the local OpenClaw config file. Storing these tokens in plaintext in a user config is expected but the user should consider secure storage and access controls.
Persistence & Privilege
always is false and model invocation is permitted (default). The skill does not request persistent elevated privileges or modify other skills' configs; it only instructs how to configure OpenClaw itself.
Assessment
This guide appears legitimate and coherent for connecting OpenClaw to DingTalk, but before applying it: 1) verify the skill's source/author and trustworthiness; 2) back up your existing ~/.openclaw/config.yml before editing; 3) only paste webhook URLs and Secrets into your local config — treat them like passwords and restrict file permissions; 4) confirm the webhook domain is the official DingTalk endpoint (oapi.dingtalk.com) and do not use shortened or unknown URLs; 5) ensure you understand what OpenClaw will have access to (todo lists, monitoring data, approvals) and restrict its permissions if necessary; 6) if your environment requires tighter security, prefer DingTalk's IP whitelist or other hardened deployment patterns rather than storing long-lived secrets in plaintext.Like a lobster shell, security has layers — review code before you run it.
chinesevk97b72zfv16e97dtepv3x6xfvx8392nkdingtalkvk97b72zfv16e97dtepv3x6xfvx8392nkenterprisevk97b72zfv16e97dtepv3x6xfvx8392nklatestvk97b72zfv16e97dtepv3x6xfvx8392nk
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
钉 Clawdis
Binscurl