负责钉钉知识库和文档的所有操作。本文件为策略指南,仅包含决策逻辑和工作流程。完整 API 请求格式见文末「references/api.md 查阅索引」。
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiondingtalk-documentExecute the skills CLI command in your project's root directory to begin installation:
Fetches dingtalk-document from breath57/dingtalk-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate dingtalk-document. Access via /dingtalk-document in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
2
total installs
2
this week
44
GitHub stars
0
upvotes
Run in your terminal
2
installs
2
this week
44
stars
负责钉钉知识库和文档的所有操作。本文件为策略指南,仅包含决策逻辑和工作流程。完整 API 请求格式见文末「references/api.md 查阅索引」。
dt_helper.sh位于本SKILL.md同级目录的scripts/dt_helper.sh。
workspaceId 和 rootNodeIdtype 为 FILE 或 FOLDER/v1.0/doc/suites/documents/{id}):可用 docKey 或 dentryUuid
docKey、dentryUuid、nodeIddocKey / dentryUuid 可用于读写正文;nodeId 用于删除和文档管理类接口wiki/nodes 返回的 nodeId 实际上是 dentryUuid,可直接用于正文读写bash scripts/dt_helper.sh --to-unionid 自动转换bash scripts/dt_helper.sh --get KEY 读取;仅校验本任务必须项bash scripts/dt_helper.sh --set KEY=VALUE 写入bash scripts/dt_helper.sh,token 获取与缓存细节无需关心/tmp/<task>.sh 再 bash /tmp/<task>.sh 执行。不要把多行命令直接粘到终端里(终端工具会截断),也不要用 <<'EOF' 语法(heredoc 在工具中同样会被截断导致变量丢失)DINGTALK_APP_KEY、DINGTALK_APP_SECRET、DINGTALK_MY_USER_IDDINGTALK_MY_OPERATOR_ID(若缺失,先用 bash scripts/dt_helper.sh --to-unionid 自动转换并写回)workspaceId/nodeId/docKey 属于任务参数,运行时从用户输入或 API 响应中获取规则:未通过“本次任务配置校验”前,不得进入 API 调用步骤。
凭证禁止在输出中完整打印,确认时仅显示前 4 位 +
****
| 配置键 | 必填 | 说明 | 如何获取 |
|---|---|---|---|
DINGTALK_APP_KEY |
✅ | 应用 AppKey | 钉钉开放平台 → 应用管理 → 凭证信息 |
DINGTALK_APP_SECRET |
✅ | 应用 AppSecret | 同上 |
DINGTALK_MY_USER_ID |
✅ | 当前用户的企业员工 ID(userId) | 管理后台 → 通讯录 → 成员管理 → 点击姓名查看 |
DINGTALK_MY_OPERATOR_ID |
✅ | 当前用户的 unionId(operatorId) | 首次由 bash scripts/dt_helper.sh --to-unionid 自动转换并写入 |
| 标识 | 说明 |
|---|---|
userId(= staffId) |
企业内部员工 ID,可通过管理后台 -> 通讯录 -> 成员管理 -> 点击姓名查看 |
unionId |
跨企业/跨应用唯一标识,可通过 bash scripts/dt_helper.sh --to-unionid <userid> 获取 |
#!/bin/bash
set -e
HELPER="./scripts/dt_helper.sh"
NEW_TOKEN=$(bash "$HELPER" --token)
OPERATOR_ID=$(bash "$HELPER" --get DINGTALK_MY_OPERATOR_ID)
# 在此追加具体 API 调用,例如查询知识库列表:
WORKSPACES=$(curl -s -X GET "https://api.dingtalk.com/v2.0/wiki/workspaces?operatorId=${OPERATOR_ID}&maxResults=20" \
-H "x-acs-dingtalk-access-token: $NEW_TOKEN")
echo "知识库列表: $WORKSPACES"
Token 失效处理:dt_helper 仅按时间缓存,无法感知 token 被提前吊销。若 API 返回 401(token 无效/过期),用
--nocache跳过缓存强制重新获取:NEW_TOKEN=$(bash "$HELPER" --token --nocache)
确定好要做什么之后,用以下命令从 references/api.md 中提取对应章节的完整 API 细节(请求格式、参数说明、返回值示例):
grep -A 30 "^## 1. 查询知识库列表" references/api.md
grep -A 10 "^## 2. 查询知识库信息" references/api.md
grep -A 35 "^## 3. 查询节点列表" references/api.md
grep -A 10 "^## 4. 查询单个节点" references/api.md
grep -A 15 "^## 5. 通过 URL 查询节点" references/api.md
grep -A 28 "^## 6. 创建文档" references/api.md
grep -A 10 "^## 7. 删除文档" references/api.md
grep -A 30 "^## 8. 读取文档内容" references/api.md
grep -A 15 "^## 9. 覆盖写入文档内容" references/api.md
grep -A 12 "^## 10. 追加文本到段落" references/api.md
grep -A 18 "^## 11. 添加文档成员" references/api.md
grep -A 12 "^## 12. 更新文档成员权限" references/api.md
grep -A 10 "^## 13. 移除文档成员" references/api.md
grep -A 10 "^## 错误码" references/api.md
grep -A 10 "^## 所需应用权限" references/api.md
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
kagurananaga/official-document-writing-skill
travisjneuman/.claude
ityes22/game-design-document
sammcj/agentic-coding
yejinlei/pdf-ocr-skill
yejinlei/pdf-ocr-skill
Registry listing for dingtalk-document matched our evaluation — installs cleanly and behaves as described in the markdown.
dingtalk-document has been reliable in day-to-day use. Documentation quality is above average for community skills.
We added dingtalk-document from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: dingtalk-document is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in dingtalk-document — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend dingtalk-document for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
dingtalk-document fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
dingtalk-document fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Keeps context tight: dingtalk-document is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in dingtalk-document — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 74