dingtalk-misc

Original：🇨🇳 Chinese

Translated

34 scripts

A long-tail product collection skill covering low-frequency DingTalk products: OA approval query and handling / legal smart contract / attendance / live / DING urgent messages / Open Platform apps and MCP development / Agoal goal management / log daily-weekly reports / spreadsheet / Open Platform doc search and OpenAPI escape hatch / standalone and doc-embedded whiteboard / DingTalk recruiting / DWS skill marketplace installation / Organization Brain Hrbrain / native Markdown / native HTML / PAT behavior authorization / multi-organization profile. Use when the user mentions any of the above products, especially Agoal/goal management/strategy decoding/business contracts and field configuration/scorecard/OKR/goal rules and periods/personal goals/goal templates/weekly-monthly report rule submission statistics/on-time/late/missing/follow-up, or querying/creating contract ledgers, batch importing contracts, drafting contracts from transcripts, archiving contracts, managing contract projects/counterparties/payments, or checking pending approvals/approve-reject-transfer-revoke approvals/clock-in/scheduling/daily-weekly report content filling/standalone whiteboard creation with content/whiteboard node read-write/cell read-write/recruiting positions/JD/creating positions/searching and installing skills/developer console apps/enterprise internal apps/checking app status or deletability/app member and role summary/app version history/enterprise internal app robot configuration, message mode, or online status/local robot connector/Stream connection/MCP services or tools/publishing or debugging MCP/fetching or invoking published MCP/turning OpenAPI, Swagger, Postman, curl, or HTTP interfaces into MCP or for Agent use/unwrapped OpenAPI/llms.txt/dws api/talent pool/employee profile/career history/performance/native .md files/Markdown version comparison/local draft diff/Markdown comments/native .html files/creating HTML pages/PAT authorization/switching organization/cross-organization/profile, and other related operations. Weekly/monthly report content filling belongs to report; rule-level on-time, late, missing statistics and personnel follow-up belong to Agoal; submitting daily/weekly/briefing reports with approvers, CC recipients, or approval flows belongs to OA approval. Real-time listening for future approval tasks or instance changes is not part of this skill; use dingtalk-event. After a match, the skill's Product Index Table locates the specific sub-product and command prefix, then executes according to that sub-product's instructions.

17installs

Sourcedingtalk-real-ai/dingtalk-workspace-cli

Added on2026-09-18

NPX Install

npx skill4agent add dingtalk-real-ai/dingtalk-workspace-cli dingtalk-misc

SKILL.md Content (Chinese)

View Translation Comparison →

Long-tail Product Collection Skill (dingtalk-misc)

Pre-Execution Routing

This file is only responsible for product routing. First use the table below to determine the unique product: for a single, clear Attendance, Report, Sheet, or Dev task, read the corresponding reference directly (it contains the minimal execution contract required for that task); for other products, read

dingtalk-shared

first, then read the unique product reference. Only read one precise shared reference when authentication, profile, confirmation, or error recovery is actually triggered; do not cold-start pre-read.

When the same request contains daily/weekly/briefing report names together with approval intent such as approvers, CC recipients, approval paths, or approval forms, the approval intent takes precedence: route uniformly to OA and read

oa.md

; this task must not execute

dws report

. Even if OA has no template with the same name, do not downgrade to submitting a Report; only deliver OA search results or ask for disambiguation. Only route to Report when the user explicitly asks to submit DingTalk logs and there is no approval-flow semantics.

For Attendance tasks, directly read the best-matching

attendance*.md

according to the product index; do not repeatedly pre-read

dingtalk-shared

. Read the corresponding shared content on demand only when cross-product orchestration, profile/auth issues, unknown global errors, or a Reference explicitly points to shared.

Product Index Table

Trigger Keywords	One-sentence Scope	Command Prefix	Detailed Reference
OA / approval / pending approval / approve / reject / revoke / initiated approval / start approval / approval attachments	OA approval query and handling; load create and attachment special instructions on demand	`dws oa`	Read core oa.md first; then read oa-create.md when initiating approval; then read oa-attachments.md for attachment operations
legal / smart contract / contract ledger / contract archive / contract project / counterparty / contract payments	Smart contract ledger, import, draft, archive, project, counterparty, and payment management	`dws contract`	contract.md
attendance / clock-in / shift / attendance group / scheduling / attendance report / leave balance	Attendance records, rules and configuration, scheduling, reports, and leave	`dws attendance`	Daily query/rules/settings: attendance.md; schedule import or schedule export: attendance-schedule.md; attendance Excel/report export: attendance-report.md; leave/balance: attendance-vacation.md
live / my live / live list	Live list and live record query	`dws live`	live.md
DING / urgent notification / phone DING / SMS DING / must-reach message	DING urgent messages (in-app/SMS/phone), personal DING	`dws ding`	ding.md
Open Platform app / enterprise internal app / app status or deletion conditions / app member management / app permissions / app version or version history / agentId / clientId / app robot configuration / robot message mode or online status / local robot connector / Stream connection / version release / connect / MCP service development / MCP tool publishing / MCP credentials / OpenAPI or Swagger or Postman or curl to MCP / expose API to Agent / published MCP invocation	Open Platform enterprise internal apps, and MCP services, tools, auth, credentials, collaborators, and dynamic invocation after publishing	`dws dev` / `dws dev mcp` / `dws mcp published`	Read one `references/dev/*.md` according to the Dev Direct Routing Rules below; read dev-index.md only when intent is unclear
DEAP digital employee / digital employee / persona / group awareness / DSH access	Compatibility routing; full natural-language orchestration is maintained only by the standalone `dingtalk-tag` skill	`dws dingtalk-tag`	Switch to `dingtalk-tag`
goal management / strategy decoding / business contract fields / scorecard / OKR / goal rule period / personal goals / goal templates / weekly-monthly report rule statistics / on-time late missing / follow-up	Agoal goal management and business goal follow-up	`dws agoal`	agoal.md
daily report / weekly report / monthly report / write log / inbox logs / sent logs	Log (daily/weekly/monthly report) query and template-based submission	`dws report` (alias `dws log` )	report.md
spreadsheet / worksheet / cell read-write / formula / hyperlink / floating image	Spreadsheet create/read-write/formula/hyperlink/floating image/export	`dws sheet`	sheet.md
Open Platform docs / API docs / interface docs / interface error	Open Platform developer documentation search	`dws devdoc`	devdoc.md
unwrapped OpenAPI / llms.txt / dws api / Raw API / API escape hatch	Official llms.txt tiered discovery; only generates and confirms Raw calls against enterprise internal app App Token server-side APIs	`dws api`	openapi-explorer.md
whiteboard / standalone whiteboard / doc-embedded whiteboard / canvas / OpenNodes / whiteboard nodes / SVG pre-render	Create with content, local SVG pre-render, read, pre-write diff preview, and update standalone or doc-embedded whiteboards; defaults to standalone whiteboard when no `partId` is present	`dws whiteboard`	whiteboard.md
recruiting / position / JD / open positions / create position / position details	DingTalk recruiting position query, details, and creation	`dws recruit`	recruit.md
search skills / find skills / install skills / skill marketplace / install DWS mono or multi skill	DWS skill marketplace search, download, install, and built-in skill deployment	`dws skill`	skill.md
talent pool / reserve cadre pool / employee profile / career history / performance records / employee tags / Organization Brain / talent search	Organization Brain: talent pool, employee profile specialized modules, and structured talent search	`dws hrbrain`	hrbrain.md
native Markdown / `.md` source / Markdown version comparison / local draft diff / overwrite Markdown / partial replace Markdown / Markdown comments	Native `.md` file read, create, version or draft comparison, full overwrite, partial replace, and comment list	`dws markdown`	markdown.md
native HTML / `.html` files / create HTML page / upload HTML file / read HTML source / overwrite HTML / partial replace HTML	Native `.html` / `.htm` file read, create, full overwrite, and partial replace (DingTalk Drive or document space)	`dws html`	html.md
PAT authorization / behavior permissions / scope authorization / one-time authorization / session authorization / permanent authorization / authorization browser policy	PAT behavior authorization and local browser policy	`dws pat`	pat.md
switch organization / change organization / cross-organization / multi-organization / profile / view which organizations are logged in	Multi-organization / profile management and cross-organization data retrieval	`dws profile` / `dws auth` / `--profile`	profile.md
Yida / AI app scripts / finance helper scripts (not productized)	No stable command surface; only helper scripts in the repo	(non-default route)	unsupported-scripts.md

Notes

When a digital employee match occurs, immediately switch to the standalone
```
dingtalk-tag
```
; this skill does not keep duplicate reference docs.
After matching a product, you must read its
```
references/<product>.md
```
; do not guess commands from the index alone. For Report, read only report.md; for common Sheet loops, read only sheet.md. For complex tasks, load child references in the order of the phase you enter; at most one reference per phase and at most three per normal task. Batch pre-reading or repeated reads are forbidden.
Agoal / Report boundary: Filling in, submitting, or querying the body of ordinary daily/weekly/monthly reports goes to Report; rule-level submission statistics, counts of on-time/late/missing, personnel lists, and follow-up go to Agoal. The mere presence of 'monthly report' cannot alone route to Report; judge together with business terms such as 'rule/statistics/late/missing/follow-up'.
Attendance exception: Directly read the best-matching
```
attendance*.md
```
per the index table; do not read
```
attendance.md
```
first and then the scheduling, report, or vacation-specific Reference. Load a second one only when a single task truly spans two independent attendance domains.
Attendance performance optimization may only reduce repeated shared/Reference/Help/Schema loads and repeated remote queries; it is forbidden to omit user-required records, business fields, pagination, failed items, warnings, or post-write verification to save tokens. When an 'all/complete' conclusion is required, you must retain and check completeness evidence such as endpoint exhaustion/total counts.
For attendance command paths, flags, constraints, and return declarations, the live Cobra/Contract/precise leaf Schema is authoritative; the attendance Reference only maintains business routing, capability boundaries, and workflows. Known commands are executed directly; when uncertainty truly exists, read one precise compact leaf at most once, avoiding duplication of the entire command set which causes information drift.
A product's own local intent-disambiguation doc is named
```
references/<product>-intent-guide.md
```
, not the shared
```
references/intent-guide.md
```
.
If cross-product collaboration among products points to another product within this package, it is already written in the corresponding
```
references/<product>.md
```
as 'see references/X.md in this package'; no skill switch is needed. If it points to a top-10 standalone product (such as
```
chat
```
/
```
aisearch
```
/
```
doc
```
), still switch skills via
```
dingtalk-<product>
```
.
For yida / finance /
```
aiapp_create_and_poll.py
```
under
```
scripts/
```
, see unsupported-scripts.md; do not call them as official capabilities by default.
Dev direct routing rules: app status, CRUD, deletability→app.md; credentials→credentials.md; Open Platform app member/role summary→member.md, not Chat group members; permissions→permission.md; security config→security.md; web app→webapp.md; robot online config→robot.md; version history/pending versions/release→version.md; event subscription→event.md; local robot connector/Stream connection→connect.md; MCP→read mcp.md first, then incrementally read its API conversion, mapping, auth, expression, or troubleshooting child references only when entering the corresponding stage; never pre-read the whole set at once. For a task that clearly spans more than two Dev domains→read only recipes.md first. Single-domain tasks read only one reference; cross-domain tasks also must not pre-read topic references, and only add one more when a real response contains a special status or field not covered in this document. No need to read
```
dingtalk-shared
```
,
```
devapp.md
```
, or the index first; repeated Reference reads are forbidden.
Dev command discipline: Use auditable
```
dws dev ...
```
atomic paths by default; do not call
```
dws dev help
```
, subgroup help, or
```
dws devapp +...
```
to discover shortcuts. Locating an app by name is only
```
dws dev app list --name
```
; there is no
```
dws dev app search
```
. For an existing app's robot name, mode, and status, use
```
dws dev app robot get
```
, not
```
dws chat bot
```
. Connectors are
```
dws dev connect ...
```
, not under
```
dws dev app
```
. Known leaves are executed directly; only when the current parameters are truly uncertain, read that leaf's compact Schema once, and only when Schema is unavailable call the precise leaf
```
--help
```
once. Do not use group help to explore.
Dev JSON and pagination: All commands use
```
--format json
```
;
```
connect list/status
```
must also carry their own
```
--json
```
, otherwise the actual output is a table.
```
app list
```
,
```
permission list
```
,
```
event list
```
,
```
version list
```
only accept cursor pagination: read the returned
```
meta.pagination.endpoint_exhausted/next_token
```
, and pass
```
--cursor <next_token>
```
for continuation pages; do not guess
```
--page
```
or
```
--page-num
```
, and do not look for the legacy
```
hasMore/nextCursor
```
in
```
data
```
.
Dev completion discipline: Before executing, write down every deliverable requested by the user; execute in dependency order, and put cleanup actions such as deletion/deactivation last. A user's initial request for write operations authorizes dry-run only, not a formal confirmation after seeing preflight. You must first show the exact objects, actions, business parameters, and impact of the dry-run, then obtain the user's explicit confirmation of that preview; afterward only replace the same command's
```
--dry-run
```
with
```
--yes
```
. If the target or business parameters change in any way, re-run dry-run, present, and confirm again. Do not issue non-dry-run write calls before confirmation;
```
--dry-run
```
is not completion. After writing, do only one necessary read-back. Do not retry the same business error when parameters and state are unchanged; retry once only after new evidence actually changes the command, parameters, or state. Finally answer item by item; for empty lists explicitly write 'none yet', and do not let large chunks of raw JSON crowd out other results.
Devapp cross-domain fast path: For creating/cleaning apps plus capabilities such as robot, web, and members, first read
```
dev/recipes.md
```
; do not pre-read app or topic references. Read the exact paragraph only when parameters are missing; a failed creation cannot borrow another app. In subsequent rounds after confirmation, directly execute the already-confirmed unchanged commands; after completing the necessary read-back, continue in the same round with the next dry-run and ask for that item's confirmation, without separately asking 'continue?'. Reuse IDs, receipts, and already-read references; if targets/parameters change, run preflight confirmation again. If STREAM is explicit, pass
```
--mode STREAM
```
; if no connection is created, do not read connect; if publishing is explicit not required, do not enter the release chain.
DevDoc search budget: For clear developer-documentation tasks, read devdoc.md directly; no need to cold-start pre-read shared or Devapp. For each topic, search the original phrase first; if there are no results or all are irrelevant, an ordinary lookup may make at most one grounded rephrase, then report the miss. Do not arbitrarily replace or reduce specified query terms and page counts; a response does not mean relevant information was found, and continuous synonym or cross-product searches to try your luck are forbidden.
For OA tasks, first read the core oa.md. Only when entering the actual submission stage, incrementally read oa-create.md; only when handling approval attachments, incrementally read oa-attachments.md; do not pre-read the full create, control, node, and attachment sets for ordinary queries. If real-time notification is required for future approval tasks or instance changes, switch to the standalone
```
dingtalk-event
```
. Open Platform app event configuration still belongs to DevApp; execute per dev/event.md, and do not confuse it with personal real-time events.
For the boundary between native
```
.md
```
and online rich-text
```
adoc
```
and general file storage, see markdown.md; for native
```
.html
```
/
```
.htm
```
file read/write, see html.md; for cross-organization / profile rules, see profile.md.
PAT behavior authorization is not Open Platform app permission; for the latter, see dev/permission.md.

When the Agent uses OpenNodes to create a whiteboard with content, it must first run

whiteboard render

, show the SVG and render notes, then stop and wait for the user to explicitly confirm the current version before creating; after modifications, re-render and confirm again. Do not skip the preview and create directly; the initial creation request and post-creation read-back cannot replace the preview confirmation. See the creation flow at the whiteboard entry; blank creation, directly applying a template, and updating an existing whiteboard are not covered by this rule.

When the Agent updates existing whiteboard content (append, modify, delete, clear), it must first run

whiteboard +diff

, show the diff and risks, then stop and wait for the user to explicitly confirm the current diff before using the same sourceDigest to run

+update

; when diff fails or has blockers, do not write. Do not bypass it with an atomic update; render, dry-run, and post-write read-back cannot replace the diff. See the update flow at the whiteboard entry.