DingTalk Knowledge Base Skill

Minimal DWS Execution Contract

Only use
```
dws
```
; add
```
--format json
```
for structured reads and judge based on actual responses.
Known commands are called directly; check the leaf narrow Schema when parameters/constraints/safety are unclear. Read a known leaf Help only once if the Schema is unavailable; fix
```
unknown flag
```
once using the same leaf Help. For
```
unknown command
```
, do not check Help: prefer the explicit suggestion in the error, then an explicit compatible entry in the loaded Skill/reference; if neither exists, report drift and stop, with the full Catalog prohibited. Low-frequency references are not treated as Help by default; root/parent/product Help is prohibited. Once discovered, must execute or explain the blocker.
Do not guess commands/flags/fields/IDs/accounts/business facts; IDs come from actual responses. Disambiguate when the target has zero hits, multiple candidates, or unknown type; only use contract defaults for optional time/display scope; stop when required information is missing.
Resolve/read/write under the same profile; IDs do not cross organizations. With multiple accounts, only use the unique
```
isOrgCurrent=true
```
; otherwise the user must specify - never select the first item, most recently logged-in, or most recently used account.
Do not output or record token, refresh token, appSecret, or webhook token; do not ask for authentication when it is already injected.
Writes must match explicit intent; confirmation follows the final Runtime gate/Schema; only add
```
--yes
```
after confirmation.
Verify results after writes; do not claim success based on exit codes alone. Exits require a final reply distinguishing completed, partial, blocked, pending confirmation, and failed; preserve existing data and
```
complete/hasMore/stopReason/failures
```
.
Timestamps are displayed in the session timezone; preserve original values when necessary.
For authentication/permissions/profile/confirmation/unknown errors, only read the corresponding reference in
```
dingtalk-shared
```
; do not keep guessing substitute commands.

The "unique" in the auto-generated list below refers only to single-page matches;

+resolve-space/+wiki-new-doc

do not serve as authoritative unique resolution before writes - resolve via the Golden Route and use the real workspaceId.

Shortcuts (Prefer when no dedicated script/recipe exists)

The following shortcuts enter both the public catalog and the Runtime Schema. Route by this skill/recipe; when a shortcut matches, it takes precedence over atomic commands. For parameters, only query

dws schema --cli-path "wiki +<shortcut>" --compact --jq '{cli_path,parameters,constraints,confirmation}' -f json

; when only the published

result

is needed, query

--jq '{cli_path,outcomes:.result.outcomes,pagination}'

; for field-level details, query

data_schema

; do not infer missing info from Help/examples. Read a known leaf Help once only if the Schema is unavailable; fix

unknown flag

once with the same leaf Help. For

unknown command

, Help is prohibited: error suggestion → explicit entry in loaded Skill/reference; if neither exists, report drift. Full Catalog/root/parent/product Help is prohibited; omit

--compact

only for mapping, interface, or provenance audits. Only when existing routes and references cannot locate a low-frequency capability, use

dws shortcut list --service wiki --format json

to discover.

Shortcut	Risk	Use Cases
`dws wiki +resolve-space`	read	Search knowledge spaces by name and resolve the unique spaceId within a single response (read-only)
`dws wiki +wiki-new-doc`	write	Create a new document node under the knowledge base with the specified name (resolves workspaceId via a single name search)

Golden Route

User Intent	Sole Recommended Entry	Key Boundaries
Resolve the unique knowledge base by name	`+space-list --type <orgWikiSpace\|myWikiSpace> --limit 50 --page-all` then exact-match the name	Clarify the organization/personal scope first; the response requestedType must equal the requested scope; take workspaceId only when `autoPageComplete=true` and exactly one same-name item exists in the full result
Search or list knowledge bases	`+space-search --query <keyword>` / `+space-list [--type orgWikiSpace\|myWikiSpace]`	Add `--page-all` when the user wants all results; personal knowledge bases require explicit semantics
Discover DingTalk Drive storage space for Drive	`dws wiki space list --type <orgSpace\|mySpace> --format json`	Managed read-only prerequisite; switch back to Drive after receiving spaceId/rootFolderId, without entering Wiki node/member routes
View details for a known workspace	`dws wiki +space-get --workspace <ID or URL>`	Do not search again when the ID is known
Create or delete knowledge base	`+space-create --name <name>` / `+delete-space --workspace <ID>`	Creation reads back and verifies space type; assert type only when `spaceTypeVerified=true` . Deleting an entire space is high-risk
Browse or search nodes within the library	`+node-list --workspace <ID> [--folder <ID>]` / `+node-search --workspace <ID> --query <keyword>`	Directory listing and keyword search are separate; add `--page-all` for a complete list or complete search results
View node metadata	`dws wiki +node-get --node <ID or URL>`	Switch to Doc for content read/write afterwards
Create a node in a known workspace	`+node-create --workspace <ID> --name <name> [--type <type>]`	Supports adoc/axls/able/appt/adraw/amind/folder; verify ID, workspace, name, type, and explicit parent folder after creation
Create an empty document when only the knowledge base name is known	First resolve uniquely via full `+space-list` , then `+node-create --workspace <ID> --name <title> --type adoc`	Do not use single-page `+wiki-new-doc` to guess the space; content goes through Doc separately
Create a document from a local file in a new knowledge base then move it to "My Documents"	`+space-create` → `doc +import --file <relative path> --workspace <new workspaceId>` → `+move-to-drive --workspace <new workspaceId> --node <imported nodeId>`	Must actually import the document into the new knowledge base before moving out; do not query `mySpace` first, and do not use `doc +create` in the personal domain then fake this flow with `drive +move`
Copy, move into knowledge base, or move a Wiki online node out to "My Documents"	`+node-copy` / `+move` / `+move-to-drive`	"Wiki node → My Documents" always uses `+move-to-drive` ; pass `--workspace` as a pre-write ownership assertion when the source workspace is known; do not substitute with mySpace/rootFolderId + `drive +move`
Put standalone common attachments on the knowledge base home page	`dws drive upload --file <local file> --workspace <ID> --format json`	No `--convert` ; add `--folder <folder nodeId>` for subdirectories. Attachments within content switch to Doc media; converting to online documents switches to Doc import
Delete a node in the library	`+node-delete --workspace <ID> --node <ID>`	Verify ownership and confirm before deletion
List, add, modify, or remove knowledge base members	`member list` / `+member-add` / `+member-update` / `+member-remove`	Writes accept 1-30 users; adding/updating must specify a role, removing does not pass a role; use native member for multiple types, per-member roles, or notifications
View knowledge base activity feeds	`+feed-list --workspace <ID> [--exclude-file]`	Add `--page-all` for all activity; compare the two result sets only when the user explicitly asks to verify filter effects, and the unfiltered results must actually include that file event

Current Shortest Path

Known workspaceId (including this round's creation receipt): execute the space/node/member/feed target command directly, without resolving again and without passing a name to
```
--workspace
```
. If the user additionally asks to "search by name", still complete that lookup step; having an ID does not mean explicit requests can be skipped.
Only the knowledge base name: first clarify the organization/personal scope, then verify the full name per the corresponding Golden Route branch; disambiguate when the scope is unknown, and do not scan both scopes and guess.
```
+space-search
```
is only for quickly browsing candidates;
```
+resolve-space/+wiki-new-doc
```
do not expose pagination completion evidence for name searches, so they are not authoritative unique resolution or part of the write Golden Route.
Known nodeId/URL: use
```
+node-get
```
directly for metadata; switch to Doc directly for content, without listing/searching first.
Pass the nodeId returned after node creation directly to Doc; do not re-locate via a same-name search. The
```
nodeId
```
of a created folder is what serves as the subsequent
```
--folder
```
; the receipt's
```
folderId
```
is its parent directory.
```
+node-copy/+move
```
target the "current library home page" using the current workspace and omit
```
--folder
```
; use
```
+move-to-drive
```
separately for moving out.
"Local file → new knowledge base → My Documents" is an ordered cross-product flow: after creating a space and receiving workspaceId, you must use
```
doc +import --workspace
```
to obtain the in-library nodeId, then
```
wiki +move-to-drive --workspace
```
; no step may be pre-created in the personal domain or substituted with a Drive root directory move.
When move/copy/delete already include pre-checks or read-back, the Agent does not re-assemble atomic commands.
General file operations in "document space/my documents" follow Drive per storage intent; however, when the source object is confirmed to be an online node in a Wiki workspace and the goal is to move it out to "My Documents", it is an explicit exception - use
```
wiki +move-to-drive
```
directly, without querying
```
mySpace
```
or calling
```
drive +move
```
. Use managed
```
wiki space list --type orgSpace|mySpace
```
only when a plain Drive node lacks spaceId/rootFolderId.

Key Result Semantics

+space-list/+node-list/+node-search/+feed-list

default to a single page; explicitly add

--page-all

for full requests, and check

autoPageComplete/autoPageStopReason/pagesFetched

and pagination metadata.

The top-level
```
requestedType
```
of
```
+space-list
```
is the server-side query's type scope; item-level
```
spaceType
```
appears only when actually returned by the server and cannot be faked with the request value. Before using list absence to prove a space does not exist, both correct scope and
```
autoPageComplete=true
```
must be satisfied.
```
+space-create
```
allows using
```
spaceType
```
only when it returns
```
spaceTypeVerified=true
```
; a type verification failure preserves the created workspaceId - do not retry creation or guess the type by name.
A missing business array in
```
+space-search/+node-search
```
is not zero hits; report empty results only for explicit empty arrays.
Organization name resolution requires a fully fetched list with exactly one exact same-name match; personal name resolution requires exactly one exact same-name entry in the native success receipt, without requiring auto-pagination fields. Stop on empty/malformed responses, zero entries, multiple entries, name mismatch, or incomplete organization pagination.
Single-page results of
```
+space-search
```
and
```
+resolve-space
```
cannot prove global uniqueness; never use the first-page unique candidate directly for writes.
```
+node-list/+node-search/+node-get
```
preserve server-side
```
extension/type/hasChildren
```
and normalize
```
parentFolderId
```
; absent fields mean the server did not provide them - do not infer type or hierarchy from names.
Creating a node must verify the new ID, workspace, name, type, and explicit parent folder; copying must first read the source node, then prove the new ID differs from the source ID and the copy landed in the target workspace/folder.
```
+move/+move-to-drive
```
return
```
source/target
```
, before/after workspace, and target domain; moving to My Documents also validates the target workspace via the
```
myWikiSpace
```
scope list. Deletion must have
```
success=true
```
.
The member list has no continuation cursor on the server side and caps at 50; do not claim results within the cap as complete; member writes only have terminal response evidence, so do not fabricate precise read-backs.
```
partial_failure
```
, incomplete pagination, or unknown write effects are not success.

Parameter and Safety Boundaries

workspaceId, nodeId, folderId, userId are not interchangeable; names cannot be used as IDs.
Write operations are confirmed only per the exact leaf Runtime; when a specific space/node/member, action, and impact have been explicitly authorized, carry
```
--yes
```
on the first formal execution; otherwise, confirm first. Re-confirm when parameters change; do not probe with
```
--yes
```
-less failures.
```
wiki member list --limit
```
defaults to 30, range 1-50; do not use member
```
--page-all
```
or raise the cap. Member writes accept 1-30
```
--users
```
; roles are only
```
MANAGER|EDITOR|DOWNLOADER|READER
```
.
```
+node-create --type
```
determines the content product; after creation, adoc→Doc, axls→Sheet, able→AITable.
Profile/organization remains consistent during space resolution, node operations, and verification.

On-demand Loading

When Golden Route parameters are sufficient, do not read references; otherwise, read at most one:

Trigger	Reference
Ambiguous boundaries among document space, knowledge base, Drive/Doc	intent-guide
Node type, copy, move, move-out, or deletion details	node-ops
Member roles, limits, and verification semantics	members
Pagination, spaces, activity feeds, and low-frequency errors	wiki reference
Cross-product creation/content-write short flows	lite-recipes

Error Shortest Path

Empty response, missing collection, zero/multiple candidates, or incomplete pagination: stop subsequent writes and return evidence;
```
+resolve-space resolved=true
```
cannot replace pagination completion evidence from a full space list.
workspace/node ownership inconsistency: stop; do not try swapping an ID or profile.
Write response missing a new ID or
```
success=true
```
: effect unknown; do targeted read-back by name/ID, do not blindly replay.
For
```
unknown flag
```
, only check the current leaf Help; for
```
unknown command
```
, only check the Wiki Shortcut list once.
When content, general storage, or Base records are mis-routed, switch back to the corresponding product; do not try approximate commands within Wiki.

Cross-Product Boundaries

Explicit knowledge base container, members, in-library hierarchy, and activity feeds → Wiki.
Content read/write/export once an in-library adoc node is locked → Doc; axls content → Sheet; able records/fields → AITable.
Storage search, transfer, and organization of common files, folders, and "My Documents/document space" → Drive; when the known source is a Wiki online node and the action is "move out to My Documents", use Wiki
```
+move-to-drive
```
.
Drive storage space discovery can reuse managed
```
wiki space list --type orgSpace|mySpace
```
; the results are spaceId/rootFolderId and cannot be handed to Wiki node/member. Knowledge base
```
orgWikiSpace/myWikiSpace
```
still returns workspaceId.
Wiki node move-in/move-out uses
```
+move/+move-to-drive
```
; do not treat workspaceId as a plain Drive folderId.

dingtalk-wiki

NPX Install

Tags

SKILL.md Content (Chinese)