lark-approval

First run lark-cli approval tasks query with topic 1 to get the instance_code and task_id, then run lark-cli approval tasks approve with both values and an optional comment. The two IDs must be used together, and write operations require the --yes flag after user confirmation.

Search launchable definitions with approvals search, fetch the definition with approvals get to read form controls and node_list, then call instances create with a JSON-array form string. Third-party definitions (is_external=true) cannot be created this way and must use their create_link.

Approval todos are approval documents and instances, not Lark tasks. Any action on approval documents such as approve, reject, transfer, or query belongs to the approval skill; only non-approval todos should go to lark-task.

Error 1395001 means the task state changed or the write precondition failed, often because someone else already processed the task or your operation rights changed. Do not retry blindly; run one status query with tasks query or instances get, then report the conclusion.

Unsupported controls include text, mutableGroup, account, serialNumber, tripGroup, and several HR control groups such as onboarding and offboarding groups. If a definition contains these, it cannot be fully submitted through the API alone.

No, this skill does not upload files. For attachmentV2 and image controls the user must directly provide the file code; without it, the instance cannot be submitted through this skill.