lark-shared

Configure lark-cli authentication, identity selection, and permission handling for Feishu resources.

Updated Sep 13, 2026
One-click install
npx skills add https://github.com/U1traVeno/skills --skill lark-shared-u1traveno
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lark-shared
Source: https://github.com/U1traVeno/skills/tree/main/profiles/lark/lark-shared
Command: npx skills add https://github.com/U1traVeno/skills --skill lark-shared-u1traveno

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Managing lark-cli setup and authorization is error-prone: choosing between user and bot identities, granting the right scopes or business domains, handling device-code login flows, and interpreting JSON envelopes and high-risk confirmation gates all require precise rules. This Skill provides the shared operational rules so every lark-cli task is executed correctly and safely. ## Core Features & Use Cases - Authentication & Authorization: Run config init, auth login by domain or scope, check login status with auth status, log out, and handle split-flow device-code authorization with QR code generation. - Identity & Permission Handling: Distinguish user vs bot identities via --as, route missing-scope errors to the developer console for bots or incremental auth login for users. - Safety & Output Contracts: Interpret success/error JSON envelopes correctly (ok == true, not code == 0), suppress _notice noise, and follow the exit-10 approval protocol for high-risk write operations using --yes and --dry-run. - Use Case: A user asks to access their Feishu calendar but gets a permission error. The Skill guides the agent to run auth login --scope with --no-wait, present the verification URL and QR code, then complete the device-code flow in a later turn. ## Quick Start Ask the agent to check your current lark-cli login identity and token validity, or to initiate authorization for a specific Feishu business domain such as docs or drive.

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 auth login --device-code.

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

User identity (--as user) accesses personal resources like calendars and cloud drive and requires auth login authorization. Bot identity (--as bot) acts as the application, needs only appId and appSecret, and cannot access user-owned resources.

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

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

Why does lark-cli fail with a permission error and how do I fix it?▼

The error response lists missing scopes in permission_violations plus a console_url. For bot identity, open the console_url in the developer console to enable scopes; for user identity, run auth login with the missing --scope or --domain.

What does exit code 10 mean in lark-cli?▼

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

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

A /wiki/<token> is a node token, not the underlying object token. Run lark-cli drive +inspect --url with the wiki URL to get the canonical obj_type and obj_token, then route to the appropriate doc, sheet, base, or drive commands.