lark-shared

Manages lark-cli authentication, identity selection, permissions, and high-risk operation approvals.

Updated Jun 29, 2026
One-click install
npx skills add https://github.com/trungpr1990-coder/AMI-MAKEUP --skill lark-shared-trungpr1990-coder
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lark-shared
Source: https://github.com/trungpr1990-coder/AMI-MAKEUP/tree/main/.agents/skills/lark-shared
Command: npx skills add https://github.com/trungpr1990-coder/AMI-MAKEUP --skill lark-shared-trungpr1990-coder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Configuring and authenticating lark-cli against Feishu (Lark) involves device-code flows, user vs bot identity choices, business-domain scopes, and confirmation gates for risky operations, which are easy to get wrong without clear rules. ## Core Features & Use Cases - Authentication & Authorization: Run auth login/status/logout with split-flow device-code authorization, QR code generation, and incremental scope grants via --domain or --scope. - Identity & Permission Handling: Distinguish user vs bot identities with --as, diagnose missing scopes from permission_violations errors, and route bot fixes to the developer console. - Safety Gates: Handle exit code 10 confirmation_required envelopes for high-risk writes, use --dry-run previews, and enforce relative-path and secret-handling rules. - Use Case: A user asks to access their Feishu calendar but hits a missing-scope error; the skill initiates a scoped login, shows the verification URL and QR code, then completes the device-code exchange in a later turn. ## Quick Start Ask the assistant to check your current lark-cli login status and identity, then authorize the scopes needed for your Feishu task.

Frequently Asked Questions about lark-shared

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I log in to lark-cli with specific permissions?▼

Run lark-cli auth login with either --domain (e.g., docs, drive, or all) or --scope for a specific permission. Add --no-wait --json to get a verification_url and device_code immediately, then complete the flow later with lark-cli auth login --device-code.

How do I check my current lark-cli login status and identity?▼

Run lark-cli auth status --json --verify to see identity, token validity, user name, open ID, and granted scopes. For a quick check of the active identity, use lark-cli whoami.

What is the difference between user and bot identity in lark-cli?▼

User identity (--as user) accesses personal resources like calendars and cloud docs and requires auth login authorization. Bot identity (--as bot) acts as the app, cannot see user resources, and only needs scopes enabled in the developer console.

Why does lark-cli exit with code 10 on delete operations?▼

Exit code 10 with error.type confirmation_required means the command is a high-risk write requiring explicit approval. Show the user the risk action, and only retry with --yes appended after the user explicitly agrees.

How do I fix missing scope permission errors in lark-cli?▼

For user identity, run auth login with the missing --scope or --domain; scopes accumulate across logins. For bot identity, do not run auth login—open the console_url from the error and enable the scope in the developer console.

How do I resolve a Feishu wiki URL token to the underlying document?▼

Use lark-cli drive +inspect --url with the wiki URL to get the underlying object type and canonical token. Alternatively call the wiki get_node API and read obj_type and obj_token, then route to the matching doc, sheet, base, or drive commands.