Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
breath57 avatar

Dingtalk Document

  • 1.7k installs
  • 97 repo stars
  • Updated June 26, 2026
  • breath57/dingtalk-skills

dingtalk-document manages DingTalk wikis and documents through dt_helper.sh with per-task config validation.

About

The dingtalk-document skill handles DingTalk wiki workspaces and document nodes with a strategy-first workflow before any API call. Core concepts include workspaces with workspaceId and rootNodeId, FILE or FOLDER nodes, docKey or dentryUuid identifiers for content APIs, and operatorId unionId requirements via scripts/dt_helper.sh. Each task validates only required config keys such as DINGTALK_APP_KEY, APP_SECRET, MY_USER_ID, and MY_OPERATOR_ID, collecting missing values once before execution. Multi-line commands must run from /tmp scripts because terminal tools truncate heredocs. references/api.md sections are grepped per operation for create, read, write, delete, and member management. Token cache uses --nocache on 401 responses. Credentials are never printed in full. Use when users mention DingTalk docs, knowledge bases, or dingtalk doc operations.

  • Validates per-task DingTalk config before any wiki or document API call.
  • Uses dt_helper.sh for token, unionId conversion, and cached credential access.
  • Maps workspace, node, docKey, and operatorId concepts for read and write flows.
  • Pulls API details from references/api.md via targeted grep sections.
  • Runs multi-step shell via /tmp scripts to avoid terminal truncation issues.

Dingtalk Document by the numbers

  • 1,654 all-time installs (skills.sh)
  • +17 installs in the week ending Aug 4, 2026 (Skillselion tracking)
  • Ranked #124 of 688 Office & Documents skills by installs in the Skillselion catalog
  • Security screen: MEDIUM risk (skills.sh audit)
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
At a glance

dingtalk-document capabilities & compatibility

Capabilities
workspace listing · document crud · member permissions · credential helper
Use cases
documentation · orchestration
From the docs

What dingtalk-document says it does

规则:未通过“本次任务配置校验”前,不得进入 API 调用步骤。
SKILL.md
npx skills add https://github.com/breath57/dingtalk-skills --skill dingtalk-document

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1.7k
repo stars97
Security audit2 / 3 scanners passed
Last updatedJune 26, 2026
Repositorybreath57/dingtalk-skills

How do I create, read, or update DingTalk knowledge base documents from an agent safely?

Operate DingTalk knowledge bases and documents: list workspaces, create files, read or write content, and manage members via dt_helper.sh and API references.

Who is it for?

Teams automating DingTalk document and knowledge base tasks via CLI helpers.

Skip if: Non-DingTalk chat or calendar workflows outside document APIs.

When should I use this skill?

User mentions DingTalk docs, knowledge base, dingtalk doc, or document member management.

What you get

Validated credentials plus executed wiki or document API operations with redacted secrets.

  • api integration scripts
  • wiki workspace list responses
  • authenticated api call patterns

By the numbers

  • Uses api.dingtalk.com v2.0 wiki workspace endpoints with default maxResults of 20 per page
  • All documented interfaces marked as verified usable in skill readme

Files

SKILL.mdMarkdownGitHub ↗

钉钉文档技能

负责钉钉知识库和文档的所有操作。本文件为策略指南,仅包含决策逻辑和工作流程。完整 API 请求格式见文末「references/api.md 查阅索引」。

dt_helper.sh 位于本 SKILL.md 同级目录的 scripts/dt_helper.sh

核心概念

  • 知识库(Workspace):文档容器,有 workspaceIdrootNodeId
  • 节点(Node):文件或文件夹,typeFILEFOLDER
  • 文档标识(用于 `/v1.0/doc/suites/documents/{id}`):可用 docKeydentryUuid
  • 创建文档响应会返回:docKeydentryUuidnodeId
  • 其中 docKey / dentryUuid 可用于读写正文;nodeId 用于删除和文档管理类接口
  • wiki/nodes 返回的 nodeId 实际上是 dentryUuid,可直接用于正文读写
  • operatorId:所有接口必须的 unionId 参数,通过 bash scripts/dt_helper.sh --to-unionid 自动转换

工作流程(每次执行前)

1. 先识别本次任务类型 → 例如:列知识库、读文档、写文档、创建文档、成员管理 2. 按本次任务校验所需配置 → 通过 bash scripts/dt_helper.sh --get KEY 读取;仅校验本任务必须项 3. 仅收集缺失配置 → 若缺少某项,一次性询问用户所有缺失值,用 bash scripts/dt_helper.sh --set KEY=VALUE 写入 4. 获取 Token / operatorId → 直接调用 bash scripts/dt_helper.sh,token 获取与缓存细节无需关心 5. 执行操作 → 凡是包含变量替换、管道或多行逻辑的命令,写入 /tmp/<task>.shbash /tmp/<task>.sh 执行。不要把多行命令直接粘到终端里(终端工具会截断),也不要用 <<'EOF' 语法(heredoc 在工具中同样会被截断导致变量丢失)

按任务校验配置(必须先做)

  • 所有任务通用必需DINGTALK_APP_KEYDINGTALK_APP_SECRETDINGTALK_MY_USER_ID
  • 涉及任何文档/知识库 API 调用:必须有 DINGTALK_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 跳过缓存强制重新获取:
```bash
NEW_TOKEN=$(bash "$HELPER" --token --nocache)
```

references/api.md 查阅索引

确定好要做什么之后,用以下命令从 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

Related skills

How it compares

Use for DingTalk wiki and document APIs; use other enterprise doc skills for Notion, Confluence, or Google Workspace integrations.

FAQ

What is operatorId?

The unionId required on document APIs, obtained via dt_helper.sh --to-unionid.

Can API run before config validation?

No. Complete per-task config checks before any document API call.

How are API details loaded?

Grep the matching section from references/api.md for the requested operation.

Is Dingtalk Document safe to install?

skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.