• DingTalk business operations go only through the

  dws

  CLI; scripts explicitly published by this Skill can orchestrate

  dws

  and complete presigned file uploads. Structured reads use

  --format json

  ; judge results based on actual returns.
• Known leaves execute directly. Only when parameters or security semantics are uncertain, read at most once

  dws schema --cli-path "aitable <leaf>" --compact --format json

  ; only when that compact leaf Schema is inconsistent with actual Cobra behavior, read

  dws aitable <leaf> --help

  for the same leaf. It is forbidden to explore commands through parent Help, product Help, or the full Catalog.
• Do not guess commands, flags, fields, IDs, accounts, or times. Subsequent IDs must come from real returns; stop and disambiguate when there are zero hits, multiple candidates, or unclear types.
• Parsing targets, reading context, and final execution must use the same profile; do not reuse userId, openDingTalkId, or openConversationId across organizations. Multi-account organizations use only the explicit default account with

  isOrgCurrent=true

  ; when there is no default account, ask the user to specify; do not select the first item, most recently logged-in, or most recently used account.
• Do not output or log credentials such as token, refresh token, appSecret, or webhook token; do not ask for credentials when the host has already injected authentication.
• Write operations must conform to the user's explicit intent. Whether confirmation is needed is determined by the final Runtime gate and Schema; when the user has explicitly requested execution in this turn and the target and impact of a non-destructive write operation are unambiguous, that explicit instruction is the confirmation for this turn; the first call carries the

  --yes

  required by Runtime directly, without first creating

  confirmation_required

  . File import is a non-idempotent operation and still triggers the Runtime confirmation gate per the Golden Route; append

  --yes

  only after confirmation. Destructive or high-risk actions such as deletion or disabling automations must first explain the object, action, and impact and obtain independent confirmation.
• After writing, verify according to the task result contract; do not claim success based solely on the exit code. Partial results, unknown delivery statuses, and failed items must be faithfully retained.
• Runtime Schema is the authoritative source for current capabilities and security semantics; within the same leaf task, read it once and reuse. Read leaf Help only when the Schema is missing fields, unclear, or conflicts with actual execution; invalidate the cache immediately when versions, profiles change, or contract errors appear.
• Mutation returns, HTTP 200, and exit code 0 are only call receipts, not the final object state. After writing, clear affected read caches and initiate an independent read-back using the real ID/unique key returned; do not reuse pre-write results.
• Writes to the same Base are serial by default; controlled concurrent writes are allowed only when they target different Bases, have no data/ID/order dependencies, and failures can be read back independently. Independent read-only calls default to a maximum of 4-way concurrency.
• When a write call times out, the connection is interrupted, or the returned result is unknown, do not automatically replay it as-is; first check the real state. Read-only calls may retry transient errors with a cap.
• Structured results may use a unified

  ok/outcome

  , legacy

  status

  , or boolean

  success

  envelope; do not assume a fixed

  data

  layer.

  partial_failure

  may appear in stdout and return exit code 7; parse the envelope first before judging the execution result.
• The

  uploadUrl

  , token, authorization, signature, etc., returned by file upload are credentials; do not output or log them; recursively redact structured errors as well.
• When timestamps are shown to users, convert them to readable time with timezone; default to the current session timezone, and retain the original value when necessary.
• When encountering authentication, permission, profile, confirmation, or unknown errors, only load the corresponding reference in

  dingtalk-shared

  ; do not keep guessing alternative commands.

• form share update

  :

  dws aitable form share update --help

• +form-share-update

  :

  dws schema --cli-path "aitable +form-share-update" --compact --format json

+

--help

-h

<BASE_ID>

<TABLE_ID>

<VIEW_ID>

dws aitable form share update --base-id <BASE_ID> --table-id <TABLE_ID> --view-id <VIEW_ID> --enabled true
请将 <BASE_ID>、<TABLE_ID>、<VIEW_ID> 替换为真实值；未传入的分享配置保持原值。本次仅查询 help/schema，未执行写操作。

--format json

help/schema

--form-name

--enabled

dws aitable +form-share-update --base-id base-123 --table-id table-456 --view-id view-789 --enabled true --form-name "报名表" --format json
未传入的分享配置保持原值。本次仅查询 help/schema，未执行写操作。

form share get

dws schema --cli-path "aitable form share get" --compact --format json

form share update

dws schema --cli-path "aitable form share update" --compact --format json

+form-share-get

dws schema --cli-path "aitable +form-share-get" --compact --format json

+form-share-update

dws schema --cli-path "aitable +form-share-update" --compact --format json

cpSynced

data.executed=false

tool/arguments/executed

dry_run=true

cpSynced

ok=true

required

additionalProperties

arguments

enabled

cpSynced=true

data.succeeded[0].response

data.failed[0].error

execution_started=true

status

cpSynced=false

form share update

+form-share-update

shareFormUuid

status

formCover

cpSynced

cpSynced=true

cpSynced=false

formCover

Command reference: aitable.md; PostgreSQL read-only queries: aitable-psql.md; complex commands load

references/aitable/*.md

as needed; playbook: 06-data-analytics.md.

+resolve-base

+resolve-table

+base-search

entity search

references/aitable.md

+table-bootstrap

--verbose

raw

pretty

• Read the field catalog only when record filter/sort is missing fieldId.
• The protocols and References for record filter/sort and view filter/sort/group are mutually exclusive. Regular record query/create/update/upsert go direct; only history, sharing, delete recovery, empty rows, or special field values read

  record-ops

  .
• Normal field types use

  text/number/date/singleSelect/currency

  ; the config for

  singleSelect

  is

  {"options":[{"name":"<option>"}]}

  , and RMB

  currency

  is

  {"currencyType":"CNY","formatter":"FLOAT_2"}

  .
• Use TodoWrite only when the task contains 4 or more independent business steps or the user explicitly requests it; do not split steps by individual CLI, update only at phase transitions.
• When multiple resource names require the same timestamp, take it once and reuse.
• Reuse fields already returned in JSON; do not repeat requests with

  --verbose/raw/pretty

  .
• Before creating a data source, you must first use

  +datasource-list-sources

  to obtain passthrough fields such as processCode; do not construct sourceConfig from memory.

• When record pagination reports

  INVALID_CURSOR

  ,

  CURSOR_SNAPSHOT_CHANGED

  , or

  CURSOR_SNAPSHOT_UNAVAILABLE

  , discard all accumulated results and the old cursor; there is no new resumable cursor, and you cannot keep the first page and deduplicate/splice it. For the first two, after checking conditions, re-query read-only from the first page without

  --cursor

  ; UNAVAILABLE requires waiting for server repair first. Do not re-run an entire command that includes writes. Resume only for normal recoverable errors with an actual valid checkpoint; see record-query for details.
• Before querying, writing, filtering, or sorting, first use

  field get

  to obtain the target field's

  fieldId

  ,

  type

  , and

  config

  ; the key in

  cells

  must use

  fieldId

  , not the Chinese name of the field.
• For select/multipleSelect writes, pass option names; when filtering, first uniquely resolve the option ID. For multipleSelect or other array-type fields, the second operand must be an array of option IDs/stable IDs; do not pass a bare string.
• Resolve people, departments, groups, related records, and similar conditions into stable structured IDs first; stop on zero hits, multiple hits, or type mismatches; do not pass display names or raw values directly.
• Non-analytical full row-by-row details with explicit user permission can use

  record query --all --page-limit 0

  directly, without needing or triggering the psql downgrade gate; do not use it to replace psql complex analysis or do calculations in local tools such as Agent context, Python, jq, JavaScript, or spreadsheets. Model-written loops are prohibited for automatic paging; manual paging must pass the real

  data.nextCursor

  through, with query conditions unchanged. A successful empty continuation page with

  records=[]

  and empty

  nextCursor

  is a normal last page; do not report an error, retry, or judge it as a missed query.
• For create or update, read back only with the ID actually returned; when the write effect is unknown, read back and do not replay successful batches.
• For full queries check

  hasMore

  ; for batch writes check the final state; do not claim full completion when pagination has not ended or on

  partial_success

  .
• Record

  cells

  use the current fieldId; write values according to the real field type; read-only fields cannot be written.
• For create or update, read back only with the ID actually returned; when the write effect is unknown, read back and do not replay successful batches.
• For full queries check

  hasMore

  ; for batch writes check the final state; do not claim full completion when pagination has not ended or on

  partial_success

  .

• Deletion is irreversible; verify the real target according to Runtime confirmation;

  base list

  only shows recent access. Stop when fields have zero/multiple candidates or unclear types; for multi-batch writes, retain completed batches and the resume position.
• Comment create/reply are non-idempotent; when a comment write operation is in an unknown state, first reconcile with

  comment list

  ; do not replay automatically; delete only removes the user's own comments and is irreversible; handling of associated replies is not guaranteed.

• app get

  /

  app page list

  will initialize a default App when the App does not exist; this is an idempotent conditional write;

  app page/widget create

  is non-idempotent and does not automatically retry. Deleting a Page cascades to delete all Widgets; deleting a Widget synchronously cleans up layouts; both require independent confirmation.
• Data source

  +datasource-create

  /

  +datasource-update

  triggers real data synchronization; confirm the target Base and sourceConfig before execution.

  +datasource-sync

  handles at most 5 tables per run.

1. Zero/multiple candidates, field ambiguity, or incomplete pagination: stop and return evidence; only a valid pagination session can pass through the real

   nextCursor

   . For invalid cursors, first execute the "Record Stability Constraints" above; do not apply ordinary checkpoint resumption.
2. For type errors, only re-check the target field; do not delete fields or lose input; resume

   partial_success

   from the checkpoint; for unknown writes, read back first.
3. When the error provides

   actions

   /

   available_flags

   , correct once only according to the

   next_command

   in it; stop when

   retryable=false

   or the target ID type does not match.
4. Data source sync

   errorCode=4014

   indicates duplicate triggering while a sync is running; you can retry later; before triggering sync on a non-data-source table, first use

   +base-get

   to confirm

   sync=true

   .

• Excel-style cell, range, and formula operations → Sheet in

  dingtalk-misc

  .
• Moving a Base as a whole between ordinary folders or doing outer storage renaming → Drive; copying/deleting Base structures, and creating, copying, moving, renaming, deleting Table, Dashboard, Section within a Base → AITable.
• Record primary document content → switch to

  dingtalk-doc

  after obtaining the real nodeId.