lark-shared

Configure lark-cli authentication, identity switching, and scope management for Feishu resources.

1.3k|142|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/MiniMax-AI/minimax-code --skill lark-shared-minimax-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lark-shared
Source: https://github.com/MiniMax-AI/minimax-code/tree/main/packages/local-runtime/assets/skills/lark-tools/cli-skills/lark-shared
Command: npx skills add https://github.com/MiniMax-AI/minimax-code --skill lark-shared-minimax-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It guides agents through the shared groundwork of operating Feishu/Lark resources via lark-cli: initial app configuration, user versus bot authentication, permission scope handling, and safe resolution of permission-denied errors. ## Core Features & Use Cases - Authentication & Identity Management: Distinguishes user identity (--as user) from bot identity (--as bot), with rules for when each applies and how to switch. - Scope & Permission Handling: Uses lark-cli auth login --recommend for first-time broad authorization and incremental --scope grants for high-sensitivity scopes, with an agent-driven device-flow flow (--no-wait --json plus background --device-code). - Update & Safety Rules: Detects _notice.update in CLI output to prompt upgrades, and enforces security rules such as never printing secrets and confirming destructive operations. - Use Case: When a user asks the agent to read their Feishu calendar and the CLI returns a permission error, the agent starts the device authorization flow, shows the user the verification URL, and completes login in the background. ## Quick Start Ask the agent to log in to Feishu with lark-cli using the recommended scopes and show you the authorization link to approve.

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 Feishu with lark-cli?

Run lark-cli auth login --recommend for first-time authorization, which grants the recommended scope set Feishu auto-approves. For scopes outside the recommended set, use lark-cli auth login --scope with the specific missing scope name.

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

User identity (--as user) accesses personal resources like calendars and cloud docs and requires OAuth login, while bot identity (--as bot) only needs an appId and appSecret but cannot see user resources. Switch between them with the --as flag.

How do I fix lark-cli permission denied errors?

Check the error response for permission_violations listing missing scopes. For bot identity, open the provided console_url to enable scopes in the developer backend; for user identity, run auth login with --recommend or the specific missing --scope.

Can an AI agent run lark-cli auth login non-interactively?

Yes, use lark-cli auth login --no-wait --json to immediately get a verification_url and device_code, show the URL to the user, then run lark-cli auth login --device-code in the background to wait for approval. Tokens are stored in the global lark-cli store automatically.

Should I use lark-cli --domain or --scope for authorization?

Use --recommend instead of --domain, because domain-based requests trigger repeated authorization prompts for each new module. The recommended scope set covers common scopes across domains, and incremental --scope grants accumulate safely on top.