Documents & Data · IN-DEPTH PROFILE

Lark Approval Skill

Lark Approval handles Feishu approval inboxes and instances, can search approval definitions and start a native instance, and keeps approval work separate from ordinary Lark Tasks.

View listed source ↗Installation guide ↓Choose a Lark Skill by task ↗
Best for

Feishu users managing approval queues

What you get

Review approval work + Find or start a defined approval

Main limitation

Available actions depend on the approval definition, current state, identity, and tenant permissions.

First risk

Consequential approval decision. Starting an approval or approving, rejecting, transferring, or withdrawing an instance can affect a business process. Require explicit user intent, verify the definition or instance, and preserve the human decision boundary.

EVIDENCE FRESHNESS

Three checks, kept separate

A recent source check is not a runtime test or security audit.

Upstream sourceChecked 2026-09-23

Pinned revision · a079fd7a

Open pinned commit ↗
SkillSignal profileSource-grounded

Updated 2026-09-23

Runtime & securityNot independently verified

Source review does not certify behavior or safety.

IN PLAIN ENGLISH

What it does—and when it fits

Lark Approval handles Feishu approval inboxes and instances, can search approval definitions and start a native instance, and keeps approval work separate from ordinary Lark Tasks. Its current instructions require the shared identity and permission rules, default to user identity for human approval actions, and use operation-specific references rather than guessed parameters.

This is aimed at Feishu users managing approval queues. Compare the examples below with your task, then review the limitations, permissions, and risks before installing.

What you get
  • Review approval workList pending, handled, or initiated instances and inspect the exact instance before deciding what to do.
  • Find or start a defined approvalSearch existing approval definitions and start a supported native instance when explicitly requested.
  • Take an approved actionApprove, reject, transfer, return, withdraw, or urge only with clear user intent and the correct current state.
What makes it different
  • This profile is manually organized around the current upstream SKILL.md workflow.
  • The capability boundary remains explicitly tied to open.feishu.cn.
  • Core uses, limitations, and risks are separated for pre-install review.
Community signalskills.sh All-time: #19 · 729.3K installs

No verified review text is in the current dataset. Use the linked source for the latest discussion.

Read the source note ↗

INSTALL BY AGENT

Choose your Agent

Paths come from official Agent docs or the universal installer behind skills.sh. Compatibility still follows this Skill's record.

Native

This Skill's current record explicitly names this Agent. Still inspect scripts, permissions, and external dependencies first.

Project install (recommended)
npx skills add larksuite/cli --skill lark-approval --agent claude-code
Personal install
npx skills add larksuite/cli --skill lark-approval --agent claude-code -g

Project install stays with this repository for team sharing. Personal install adds -g and works across repositories.

This command adds the Skill instructions only. Install lark-cli and sign in to Feishu separately before use. Official Lark CLI setup ↗

View install paths
Project path.claude/skills/lark-approval/
Personal path~/.claude/skills/lark-approval/
Official agent docs

Claude Code discovers custom Skill folders automatically at project or personal scope.

View path evidence ↗

TYPICAL WORKFLOW

A practical workflow

01

Review approval work

List pending, handled, or initiated instances and inspect the exact instance before deciding what to do.

02

Find or start a defined approval

Search existing approval definitions and start a supported native instance when explicitly requested.

03

Take an approved action

Approve, reject, transfer, return, withdraw, or urge only with clear user intent and the correct current state.

THE TRADEOFFS

Advantages and tradeoffs

Notable strengths

  1. This profile is manually organized around the current upstream SKILL.md workflow.
  2. The capability boundary remains explicitly tied to open.feishu.cn.
  3. Core uses, limitations, and risks are separated for pre-install review.

Limitations

  1. Available actions depend on the approval definition, current state, identity, and tenant permissions.
  2. Operation parameters must come from current references or schemas rather than guesses.

COMPARE THE TRADEOFF

Consider these close alternatives

These are deterministic nearby candidates, not paid placements or a universal ranking. Open the full profile before choosing.

01

Same job family · native to Codex + Claude Code

create-llms

Create an llms.txt index from repository documentation.
Tradeoff to check
Detailed package files are not fully catalogued.
First risk
Review before install · Medium
Source state
Pinned · 1f564408
Open create-llms profile ↗
02

Same job family · native to Codex + Claude Code

csharp-docs

Write useful XML documentation for C# APIs.
Tradeoff to check
Detailed package files are not fully catalogued.
First risk
Review before install · Medium
Source state
Pinned · 1f564408
Open csharp-docs profile ↗
03

Same job family · native to Codex + Claude Code

java-docs

Write consistent Javadoc for Java types and APIs.
Tradeoff to check
Detailed package files are not fully catalogued.
First risk
Review before install · Medium
Source state
Pinned · 1f564408
Open java-docs profile ↗
Compare more in the directory →

BEST FIT

Who it is for

→

Feishu users managing approval queues

→

Agents assisting controlled business workflows

BEFORE YOU USE IT

Risks to review before use

High

Consequential approval decision

Starting an approval or approving, rejecting, transferring, or withdrawing an instance can affect a business process. Require explicit user intent, verify the definition or instance, and preserve the human decision boundary.

High

External data and identity boundary

Requests access Feishu tenant resources. Use the correct identity, least-privilege scopes, and keep sensitive content out of logs.

SECURITY

What the permission profile means

  • Declared access remains governed by the current upstream SKILL.md and runtime requests.
  • Treat Feishu documents, messages, people, and business records as permission-controlled data.
  • SkillSignal has not independently executed or security-audited this package; external skills.sh labels are not SkillSignal certification.

Not a security certification. External ratings are attributed references. SkillSignal has not independently executed or security-reviewed this Skill.

COMMON QUESTIONS

Lark Approval Skill FAQ

What is the Lark Approval Skill?

Lark Approval handles Feishu approval inboxes and instances, can search approval definitions and start a native instance, and keeps approval work separate from ordinary Lark Tasks. Its current instructions require the shared identity and permission rules, default to user identity for human approval actions, and use operation-specific references rather than guessed parameters.

How do I install the Lark Approval Skill?

Open and review the listed source, choose the project or personal path for your Agent, then verify the first run in a controlled project. Open the listed source and read the current SKILL.md plus only the references required for this task.

Is the Lark Approval Skill safe to use?

SkillSignal checked the source on 2026-09-23, but that is not a runtime test or security certification. Review the “Consequential approval decision” risk first and begin with the least access required.

INSIDE THE PACKAGE

Indexed files

SKILL.mdUpstream Skill instructionsSource-linked

TAGS

feishuapprovalworkflow

Manually expanded from the current upstream SKILL.md and linked source at open.feishu.cn, checked 2026-09-23. This is an original summary, not an execution result or security certification.