dws

Orchestrate DingTalk Workspace operations via a unified CLI with JSON outputs.

2.7k|181|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/DingTalk-Real-AI/dingtalk-workspace-cli --skill dws-dingtalk-real-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dws
Source: https://github.com/DingTalk-Real-AI/dingtalk-workspace-cli/tree/main/skills/mono
Command: npx skills add https://github.com/DingTalk-Real-AI/dingtalk-workspace-cli --skill dws-dingtalk-real-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openpyxl, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a unified command-line interface to manage DingTalk Workspace (DingTalk Workspace), aggregating operations across AI tables, AI search, calendar, contacts, chat, documents, drive, minutes, and more. It reduces fragmentation when performing cross-product tasks and enables automation in enterprise environments.

Core Features & Use Cases

  • Unified entry point to operate multiple DingTalk products from a single CLI
  • Chain multi-step workflows with JSON outputs and robust error handling
  • Optional resource directories (scripts/ references/ assets/) to support deterministic tasks and rich references

Quick Start

Use the dws CLI to manage DingTalk products and automate workflows.

Frequently Asked Questions about dws

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate DingTalk Workspace tasks across multiple products from the command line?

You can automate DingTalk Workspace tasks by using a unified CLI to orchestrate operations across products like AI tables, calendars, contacts, and docs, chaining multi-step workflows with JSON outputs and error recovery.

What is the best way to batch create documents and export attendance in DingTalk enterprise environments?

The best way to batch create documents and export attendance is by executing cross-product workflows through a unified DingTalk Workspace CLI, which aggregates fragmented operations into automated enterprise task sequences.

Does the DingTalk Workspace CLI require specific directory structures for automation scripts?

Yes, the DingTalk Workspace CLI enforces a discovery workflow requiring YAML frontmatter and a SKILL.md entry, while supporting optional scripts, references, and assets directories for deterministic task execution.

How does the DingTalk Workspace CLI handle errors during multi-product workflow automation?

The DingTalk Workspace CLI handles errors by returning JSON outputs and applying a built-in recovery workflow, ensuring robust error management during automated multi-product enterprise operations.

Can I use Python dependencies like openpyxl with DingTalk enterprise automation workflows?

Yes, you can use openpyxl with DingTalk enterprise automation workflows, as it is a required dependency for executing scripts that manage and process data across DingTalk Workspace products.

Why should I use a unified CLI for DingTalk Workspace instead of individual product APIs?

Using a unified CLI for DingTalk Workspace reduces fragmentation when performing cross-product tasks, providing a single entry point to manage multiple products and enabling streamlined enterprise automation workflows.