使用说明
DingTalk Office Automation Templates
Reusable DingTalk office automation templates built on top of the
dingtalk_workspaceMCP server.
中文文档 · Contributing · License · Release Notes
Overview
This repository packages reusable DingTalk-oriented command templates for assistant systems, internal automation platforms, prompt routers, and MCP-based office tooling.
It focuses on turning common DingTalk workflows into structured, reusable command templates with predictable safety boundaries.
Highlights
- reusable templates for core DingTalk office actions
- bilingual office routing entry point
- Chinese operational templates for day-to-day use
- inspect-first, draft-first, and preview-first workflow design
- structure ready for extension in open-source or internal tooling environments
What This Repository Covers
- contacts and department lookup
- chat message and DING drafting
- calendar checks and meeting coordination
- OA approval inspection and follow-up
- todo and task-style work management
- workspace-level routing for general office automation requests
Template Index
Core DingTalk Templates
commands/dingtalk/workspace.md
Office Routing Templates
commands/office/workspace.mdcommands/office/workspace-zh.mdcommands/office/message-zh.mdcommands/office/calendar-zh.mdcommands/office/approval-zh.mdcommands/office/task-zh.md
Repository Structure
.
|-- commands/
| |-- dingtalk/
| `-- office/
|-- CHANGELOG.md
|-- CONTRIBUTING.md
|-- LICENSE
|-- README.md
|-- README.zh-CN.md
`-- RELEASE-v0.1.0.md
Design Principles
- Inspect first, mutate second.
- Draft before send whenever possible.
- Keep approval, messaging, and scheduling operations explicit.
- Preserve cross-platform coordination through a unified office router.
- Support Chinese-speaking operational teams with direct command entry points.
Quick Start
1. Prepare DingTalk access
Make sure your DingTalk MCP environment is available. If authentication fails:
dws auth login
2. Pick a template
- Use
commands/dingtalk/workspace.mdfor DingTalk-only scenarios. - Use
commands/office/workspace.mdfor bilingual routing. - Use
commands/office/*-zh.mdfor Chinese operational command entry points.
3. Keep execution safe
- inspect current state first
- draft or summarize before mutation
- confirm or preview write actions whenever possible
Example Entry Points
DingTalk Workspace Routing
Use commands/dingtalk/workspace.md to summarize my pending OA approvals and draft a follow-up DING.
Chinese Office Routing
使用 commands/office/approval-zh.md 汇总待我审批的钉钉流程,并给出催办建议。
Typical Usage Scenarios
- building a DingTalk assistant command pack
- summarizing approvals, todos, and schedules
- drafting DINGs or operational chat messages
- standardizing MCP-based office automation flows
Who This Is For
- teams building DingTalk automation assistants
- MCP-based office tooling maintainers
- operators who need Chinese command entry points for approvals and messaging
- developers standardizing reusable office command templates
Who This Is Not For
- projects that only need raw API wrappers
- one-off scripts with no reuse strategy
- environments that do not use the
dingtalk_workspaceMCP server
MCP Baseline
Typical DingTalk operations in these templates rely on the dingtalk_workspace MCP server for:
- contacts and org lookup
- DING drafts and chat actions
- todos
- OA approvals
- calendar checks
Notes
- This repository does not include credentials, org-specific IDs, or private environment settings.
- You may adapt these templates to your own assistant or MCP orchestration layer.
Contributing
Contributions are welcome if they preserve:
- stable frontmatter
- explicit routing
- safe approval and message flows
- alignment between English and Chinese documentation
See CONTRIBUTING.md for details.
Security
If you discover a security issue or a template misuse risk, see SECURITY.md.
License
Released under the MIT License. See LICENSE.