What this skill does
Lark Approval treats approval requests as specific resources, separate from general tasks. It documents reading requests and actions such as approving, rejecting, transferring or withdrawing them, with the required identity and permissions. Confirm available actions in each operation's reference.
An AI employee can help an owner gather information before deciding: summarise the request, identify associated documents and flag missing data. The business decision retains its responsible person and criteria. Reading a request to summarise it does not imply permission to approve it or commit the organisation.
When it can help
- Summarise pending requests.
- Find the status of a specific request.
- Gather information for an approval decision.
A task to get started
Read the pending requests I can review and summarise their amount, reason and available documents. Flag those needing clarification and leave final approval to me.
What you need
- Lark CLI with access to the approvals system.
- An authorised identity and permission for the specific requests.
Limits and result review
- Feishu approvals are separate from Hub's action controls.
- This external source cannot be imported directly through Hub's GitHub catalogue.
How to explore this skill
This skill is distributed through Feishu. Hub currently imports public GitHub repositories; consult the original source for its requirements and procedure.
View on skills.sh ↗A skill provides a procedure. Each employee's permissions, approvals and connections still determine available actions. Adding it does not automatically install software or execute the author's scripts.
Sources and documentation
An iabot editorial explanation based on original documentation. Authorship remains with open.feishu.cn. This guide is not a Hub compatibility test and does not distribute a translation of the author’s code.
Read the iabot manual →