dingtalk-shared

Routes ambiguous DingTalk CLI requests to product skills and enforces shared execution contracts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

When users refer vaguely to DingTalk or DWS operations without naming a product, paste ambiguous alidocs URLs, or request cross-product workflows, an agent can easily pick the wrong command, guess IDs, or mishandle write confirmations. This Skill provides the shared entry point that disambiguates intent, probes URL types, and enforces a minimal execution contract before any dws CLI command runs.

Core Features & Use Cases

  • Product Routing: Maps vague requests to the correct dingtalk-* product skill via routing tables, an intent guide, and URL pattern detection (adoc vs axls vs able vs xlsx).
  • Cross-Product Orchestration: Coordinates multi-step workflows (e.g., search a person, then create a calendar event with them as participant) with strict ID-passing conventions.
  • Safety Contract Enforcement: Defines confirmation gates for write operations, error recovery rules, retry semantics, and credential-handling prohibitions across all product skills.
  • Use Case: A user pastes an alidocs link saying "check this table." The Skill probes the node with dws drive info, detects extension=xlsx, and routes to dws drive download instead of incorrectly invoking sheet commands.

Quick Start

Ask the agent to handle a DingTalk request that mentions DWS generally or includes an ambiguous alidocs URL, and it will route to the right product skill automatically.

Frequently Asked Questions about dingtalk-shared

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

FAQPage Schema
How do I route an ambiguous DingTalk CLI request to the right product?

Read the routing reference to map the user's goal to a product skill such as dingtalk-chat, dingtalk-doc, or dingtalk-calendar. If the product is still unclear, consult the intent guide's comparison tables before loading any product skill.

How to handle an alidocs URL when the document type is unknown?

Run dws drive info --node with the URL and inspect the extension field. Route adoc to doc, axls to sheet, able to aitable, and xlsx or csv files to drive download; never guess the type from the URL alone.

What is the difference between doc, sheet, and aitable in DingTalk CLI?

doc handles rich-text document content, sheet handles cell-range operations on online spreadsheets (axls), and aitable handles structured records and fields in multidimensional tables. The intent guide provides decision rules for borderline cases.

Does the dws CLI require confirmation for write operations?

Yes. When the runtime gate or leaf schema marks confirmation as user_required, show the operation summary, get explicit user consent, then retry the original command with --yes appended. Never silently add --yes or pipe answers.

Why does a dws command fail with confirmation_required in non-interactive environments?

In agent or CI environments without a TTY, write commands without --yes fail with reason=confirmation_required instead of prompting. Present the risk summary to the user, and only after explicit approval retry the same command with --yes.

When should I not use this shared routing skill?

Skip it when the user clearly names a single product; load that product's dingtalk-* skill directly. The shared skill only provides global contracts and routing, not the full product command set.