Workflow (Before Each Execution)

1. First identify the current task type → e.g., list knowledge bases, read document, write document, create document, member management
2. Validate required configurations for this task → Read via bash scripts/dt_helper.sh --get KEY; only validate items essential for this task
3. Collect only missing configurations → If something is missing, ask the user for all missing values at once, and write them using bash scripts/dt_helper.sh --set KEY=VALUE
4. Get Token / operatorId → Directly call bash scripts/dt_helper.sh; details of token acquisition and caching are handled automatically
5. Execute the operation → For any command involving variable substitution, pipes, or multi-line logic, write it to /tmp/<task>.sh and then execute with bash /tmp/<task>.sh. Do not paste multi-line commands directly into the terminal (terminal tools may truncate them), and avoid using <<'EOF' syntax (heredoc can also be truncated in tools, leading to variable loss).

Validate Configuration by Task (Must be done first)

• Required for all tasks: DINGTALK_APP_KEY, DINGTALK_APP_SECRET, DINGTALK_MY_USER_ID
• Involving any document/knowledge base API calls: Must have DINGTALK_MY_OPERATOR_ID (if missing, first use bash scripts/dt_helper.sh --to-unionid to automatically convert and write back)
• Create/Read/Write/Delete/Member Management: Besides the above common items, there are no additional fixed configuration keys; workspaceId/nodeId/docKey are task parameters, obtained at runtime from user input or API responses.

Rule: Do not proceed to the API call step before passing the "current task configuration validation".

Credentials are prohibited from being printed in full in the output; when confirming, only show the first 4 characters + ****

Required Configuration

Identity Identifier Explanation

Execution Script Template

#!/bin/bash
set -e
HELPER="./scripts/dt_helper.sh"
NEW_TOKEN=$(bash "$HELPER" --token)
OPERATOR_ID=$(bash "$HELPER" --get DINGTALK_MY_OPERATOR_ID)

# Append specific API calls here, e.g., query knowledge base list:
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 "Knowledge Base List: $WORKSPACES"

Token Expiration Handling: dt_helper only caches based on time and cannot detect if a token is revoked early. If the API returns 401 (token invalid/expired), use --nocache to skip the cache and force re-acquisition:

NEW_TOKEN=$(bash "$HELPER" --token --nocache)

references/api.md Index

Once you've determined what to do, use the following commands to extract the complete API details (request format, parameter descriptions, return value examples) for the corresponding section from references/api.md:

grep -A 30 "^## 1. Query Knowledge Base List" references/api.md
grep -A 10 "^## 2. Query Knowledge Base Information" references/api.md
grep -A 35 "^## 3. Query Node List" references/api.md
grep -A 10 "^## 4. Query Single Node" references/api.md
grep -A 15 "^## 5. Query Node by URL" references/api.md
grep -A 28 "^## 6. Create Document" references/api.md
grep -A 10 "^## 7. Delete Document" references/api.md
grep -A 30 "^## 8. Read Document Content" references/api.md
grep -A 15 "^## 9. Overwrite Document Content" references/api.md
grep -A 12 "^## 10. Append Text to Paragraph" references/api.md
grep -A 18 "^## 11. Add Document Member" references/api.md
grep -A 12 "^## 12. Update Document Member Permissions" references/api.md
grep -A 10 "^## 13. Remove Document Member" references/api.md
grep -A 10 "^## Error Codes" references/api.md
grep -A 10 "^## Required Application Permissions" references/api.md

Weekly Installs

414

Repository

breath57/dingtalk-skills

GitHub Stars

29

First Seen

Mar 5, 2026

Security Audits

Gen Agent Trust HubWarnSocketPassSnykPass

Installed on

github-copilot411

gemini-cli410

codex410

kimi-cli410

cursor410

opencode410