Menú
飞书审批：查询和处理审批待办/已办/实例，搜索可发起审批定义、查看定义详情并发起原生审批实例。当用户要处理审批任务、查看审批实例、搜索或发起审批时使用。审批待办不是飞书任务；非审批类待办走 lark-task。不负责创建审批定义；三方审批定义不走原生提单。
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Designing red team attack scenarios, building threat models, applying MITRE ATT&CK/OWASP frameworks, running Purple Team exercises, and performing AI/LLM red teaming. Use when adversarial security validation is needed.
飞书云文档（Docx / Wiki 文档）：读取和编辑飞书文档内容。当用户给出文档 URL 或 token，或需要查看、创建、编辑文档、插入或下载文档图片附件时使用。文档中嵌入的电子表格、多维表格、画板，先用本 skill 提取 token 再切到对应 skill。当用户给出 doubao.com 的 /docx/ 或 /wiki/ URL/token 时，也应直接使用本 skill；路由依据是 URL 路径模式和 token，而不是域名。不负责文档评论管理，也不负责表格或 Base 的数据操作。当用户明确要操作飞书思维笔记时，也使用本 skill。
Comprehending and investigating codebases. Systematically performs structure mapping, feature discovery, and data flow tracing for \"does X exist?\", \"how does Y work?\", or \"what is this module's responsibility?\". Includes a conversational Q&A mode (\"ask\") for navigator-style, multi-turn questions about a project. Does not write code.
Orchestrating specialist AI agent teams as a meta-coordinator. Decomposes requests into minimum viable chains, spawns each as an independent session in AUTORUN modes, and drives to final output. Use when a task spans multiple specialist domains, requires parallel agent execution, or needs hub-and-spoke routing across the skill ecosystem.
Converting repository changes into detailed learning documents. Use when turning diffs into teaching materials, recording design decisions, or creating onboarding materials for new members.
Specialist orchestrating codex exec / Antigravity CLI through dual paradigms — COMPETE (multi-variant comparison, select best) and COLLABORATE (decompose tasks across engines, integrate). Supports Solo/Team/Quick execution modes.
| name | lark-approval |
| description | 飞书审批：查询和处理审批待办/已办/实例，搜索可发起审批定义、查看定义详情并发起原生审批实例。当用户要处理审批任务、查看审批实例、搜索或发起审批时使用。审批待办不是飞书任务；非审批类待办走 lark-task。不负责创建审批定义；三方审批定义不走原生提单。 |
| zh_description | 用于查询、处理和发起飞书原生审批，区分审批待办与普通飞书任务。 |
| version | 1.0.6 |
| author | larksuite |
| source | github:larksuite/cli |
| source_url | https://github.com/larksuite/cli/tree/main/skills/lark-approval |
| license | MIT |
| tags | [feishu, lark, lark-cli, approval, workflow] |
| created_at | 2026-05-19 |
| updated_at | 2026-07-03 |
| quality | 3 |
| complexity | intermediate |
| metadata | {"requires":{"bins":["lark-cli"]},"cliHelp":"lark-cli approval --help"} |
CRITICAL — 开始前 MUST 先用 Read 工具读取 ../lark-shared/SKILL.md，其中包含认证、权限处理
所有命令默认 --as user（审批是人的动作）。调用前先按需读取 references 下对应的文件，查参数结构，不要猜字段；references 是第一信息源，只有在 reference 未覆盖的原生 / 高级场景下，才额外用 lark-cli ... --help、lark-cli schema 等方式补充确认字段。
审批待办不是飞书任务。只要用户的核心对象是审批单据 / 审批待办 / 审批实例，就优先使用 lark-approval，不要让渡给 lark-task。
lark-approval 的高优先级语义出现以下任一语义时，优先走 lark-approval：
判定规则： 只要最终动作是对审批单据做同意、拒绝、转交、退回、撤回、催办、加签、抄送、查详情、查已发起/已办/待办，就归 lark-approval。只有当用户处理的是非审批类任务/待办时，才走 lark-task。
| 想做什么 | 命令 | 按需读取 reference |
|---|---|---|
| 搜可发起定义 | approvals search | lark-approval-approvals-search.md |
| 看审批定义详情/提单前确认表单与流程 | approvals get | lark-approval-approvals-get.md |
| 发起原生审批实例/提交请假审批/提交报销审批/创建审批实例 | instances create | lark-approval-initiate.md |
| 查待办/已办 | tasks query（topic：1待办 2已办 17未读 18已读） | lark-approval-tasks-query.md |
| 看表单/进度/当前节点 | instances get | lark-approval-instances-get.md |
| 同意审批 | tasks approve | lark-approval-tasks-approve.md |
| 拒绝审批 | tasks reject | lark-approval-tasks-reject.md |
| 转交审批 | tasks transfer | lark-approval-tasks-transfer.md |
| 加签审批 | tasks add_sign | lark-approval-tasks-add-sign.md |
| 退回审批 | tasks rollback | lark-approval-tasks-rollback.md |
| 催办审批 | tasks remind | lark-approval-tasks-remind.md |
| 撤回已发起审批 | instances cancel | lark-approval-instances-cancel.md |
| 给审批实例追加抄送 | instances cc | lark-approval-instances-cc.md |
| 按定义查已发起审批 | instances initiated | lark-approval-instances-initiated.md |
处理链：
approvals search -> approvals get -> instances createtasks query 拿 instance_code + task_id（操作必须成对带上）→ 只有用户明确需要查看详情、当前节点、表单内容、或流程进度时，再 instances get → 执行操作tasks query 获取 instance_code + task_idinstances getinstance_code / task_id 时，不要先查列表再过滤instance_code + task_id 后，优先直接执行 tasks approve/reject/transfer/add_sign/rollback/remindtasks querylist -> filter -> detail -> write 全链路；对象已明确时应压缩步骤当拒绝 / 转交 / 退回 / 撤回 / 同意等写操作返回 1395001（任务状态异常 / 写前置校验失败）时，按下面规则处理：
tasks query 或 instances get），不要陷入 query/write 循环特别注意： 对拒绝 / 转交 / 撤回场景更要严格执行上述规则；这些场景最容易因状态切换而失败。
lark-cli approval approvals search --data '{"keyword":"请假"}' --as user
lark-cli approval approvals get --params '{"approval_code":"<code>"}' --as user
lark-cli approval instances create --data '{"approval_code":"<code>","form":"[...]"}' --yes --as user
lark-cli approval tasks query --params '{"topic":"1"}' --as user
lark-cli approval tasks approve --data '{"instance_code":"<ic>","task_id":"<tid>","comment":"同意"}' --as user
创建审批定义（走飞书客户端或审批管理后台）；三方定义发起（返回 create_link，引导用户通过链接发起）；非审批类待办 → lark-task
This supplement is maintained by the repository sync pipeline. It keeps the imported upstream skill usable inside this curated collection when the upstream source is intentionally concise.
1. Confirm that the user's task matches the skill trigger.
2. Read the relevant project files or user-provided context before acting.
3. Choose the smallest reversible action that advances the task.
4. Run the verification command or manual check that proves the result.
5. Report the outcome, evidence, and any remaining risk.