lark-approval
Manage Lark Approval Workflows via CLI
Streamline Lark approval workflow management through Claude Code integration. Query approval instances, approve or reject tasks, and transfer approvals using natural language commands.
Download the skill ZIP
Upload in Claude
Go to Settings → Capabilities → Skills → Upload skill
Toggle on and start using
Test it
Using "lark-approval". Show me my pending approval tasks
Expected outcome:
Found 3 pending approval tasks:
1. Leave Request - John Doe (2024-01-15 to 2024-01-17)
2. Expense Report $850 - Jane Smith
3. Purchase Order #12345 - Tech Team
Would you like to approve or reject any of these?
Using "lark-approval". Get details for approval instance ABC-123-XYZ
Expected outcome:
- Approval Instance: ABC-123-XYZ
- Status: In Progress
- Title: Software License Purchase
- Submitter: admin@company.com
- Submitted: 2024-01-14 10:30 UTC
- Current Node: Manager Approval
- Approvals: 1/2 completed
Using "lark-approval". Approve task TASK-789 for instance ABC-123-XYZ
Expected outcome:
Task approved successfully. The approval instance ABC-123-XYZ has advanced to the next stage in the workflow.
Security Audit
SafeAll static analysis findings are false positives. The detected 'external_commands' and 'filesystem' patterns are markdown code blocks containing CLI documentation examples, not executable code. This skill contains only documentation with bash command examples for the lark-cli tool. No actual code execution, filesystem access, or security risks present.
Quality Score
What You Can Build
Manager Approval Automation
Managers can quickly review, approve, or reject pending approval requests by describing what they want in natural language
Approval Workflow Monitoring
Operations teams can query approval status, check pending tasks, and track approval instances across the organization
Batch Approval Processing
Process multiple approval tasks efficiently by querying task lists and performing bulk approve/reject operations
Try These Prompts
Show me all my pending approval tasks that need attention
Approve the approval task with instance ID [instance_id] and task ID [task_id]
Get the full details of approval instance [instance_id] including current status and history
Transfer approval task [task_id] to user [user_id] with a note about the handoff
Best Practices
- Always run the schema command first to check required parameters before calling approval APIs
- Use the shared authentication setup from lark-shared skill to ensure proper API credentials
- Verify the required approval scopes (approval:instance:read, approval:task:write) are granted before execution
- Check approval status before performing actions to avoid errors on already-completed workflows
Avoid
- Do not guess parameter structures - always use lark-cli schema approval.resource.method to verify required fields
- Avoid approving or rejecting tasks without first reviewing the full instance details and context
- Do not transfer approval tasks without informing the recipient and documenting the reason
- Never hardcode approval instance IDs or user IDs in prompts - retrieve them dynamically