dingtalk-workspace-cli

Manage DingTalk contacts, calendars, docs, todos, and AI tables via command line.

4|Updated May 16, 2026
One-click install
npx skills add https://github.com/reason-machines/devtools-skills --skill dingtalk-workspace-cli-reason-machines
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dingtalk-workspace-cli
Source: https://github.com/reason-machines/devtools-skills/tree/main/skills/dingtalk-workspace-cli
Command: npx skills add https://github.com/reason-machines/devtools-skills --skill dingtalk-workspace-cli-reason-machines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Accessing DingTalk enterprise data (contacts, calendars, documents, todos, AI tables, chat, drive, attendance) normally requires navigating multiple web interfaces or writing custom API integrations. This Skill lets you perform all of these operations from the command line or through AI agents using the official dws CLI with structured JSON output. ## Core Features & Use Cases - Unified Enterprise Data Access: Search contacts, manage calendar events, query AI table records, create todos, send chat messages, and manage drive files through one CLI. - AI Agent Friendly: Structured JSON responses, --jq filtering to reduce token usage, --dry-run previews, --yes for non-interactive execution, and dynamic schema discovery via dws schema. - Flexible Authentication: Browser login, OAuth device flow for headless environments, and custom app credentials for CI/CD pipelines. - Use Case: An AI agent needs to schedule a weekly team sync. It searches the engineering department for user IDs, creates a calendar event with attendees, and creates a reminder todo — all through chained dws commands. ## Quick Start Install the dws CLI, run dws auth login to authenticate, then ask the agent to list today's DingTalk calendar events in JSON format.

Frequently Asked Questions about dingtalk-workspace-cli

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

FAQPage Schema
How do I manage DingTalk calendar events from the command line?▼

Use the dws CLI with commands like dws calendar event list to view events and dws calendar event create with --summary, --start-time, --end-time, and --attendees flags to create them. Timestamps must use RFC3339 format with timezone, and add --yes for non-interactive execution.

How to query DingTalk AI table records with filters?▼

Run dws aitable record query with --base-id and --table-id, plus --filter-by-formula for conditions like '{Status}="Done"'. You can also sort, paginate with --page-size, and extract fields using --jq to reduce output size.

Does dws CLI work in headless or CI/CD environments?▼

Yes, dws supports OAuth device-flow login via dws auth login --device for headless environments, and custom app credentials via --client-id and --client-secret flags or DINGTALK_CLIENT_ID environment variables for CI/CD pipelines.

How do AI agents discover available dws commands dynamically?▼

Use dws schema to list all products and tool counts, then inspect specific tools like dws schema aitable.query_records --jq '.tool.parameters' to get parameter schemas. This lets agents discover capabilities without pre-built knowledge.

Why does dws event creation fail with timestamp errors?▼

DingTalk expects RFC3339 format with timezone, such as 2026-05-20T14:00:00+08:00. Unix timestamps and formats like '2026-05-20 14:00:00' are rejected. Attendance commands use plain date format like 2026-05-20 instead.

How do I reduce token usage when using dws with AI agents?▼

Use the --jq flag to extract only needed fields from JSON responses, for example --jq '.result[] | {name: .name, userId: .userId}'. This can reduce output from over 1000 tokens to around 50 tokens per command.