lark-shared

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

Updated May 22, 2026
One-click install
npx skills add https://github.com/CalWade/aigc-creator --skill lark-shared-calwade
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lark-shared
Source: https://github.com/CalWade/aigc-creator/tree/main/.agents/skills/lark-shared
Command: npx skills add https://github.com/CalWade/aigc-creator --skill lark-shared-calwade

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up and operating lark-cli against Feishu (Lark) resources involves confusing identity models, OAuth device flows, scope errors, and risky write operations. This Skill gives the AI agent clear operational rules so setup, login, and error recovery happen correctly on the first attempt. ## Core Features & Use Cases - Guided Initialization & Auth: Runs lark-cli config init and split-flow auth login with QR code generation, so users complete device authorization without blocking the conversation. - Identity & Permission Handling: Distinguishes bot vs user identity (--as), interprets permission_violations errors, and issues the correct incremental scope login command. - High-Risk Operation Gate: Handles exit code 10 confirmation envelopes, previews dangerous requests with --dry-run, and only retries with --yes after explicit user consent. - Use Case: A user asks the agent to read their Feishu calendar but hits a scope error. The Skill directs the agent to run lark-cli auth login --scope "calendar:calendar:readonly" --no-wait --json, show the QR code, and complete the device-code flow in a later turn. ## Quick Start Ask the agent to initialize lark-cli and log in with the calendar read scope, then follow the QR code and authorization link it presents.

Frequently Asked Questions about lark-shared

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

FAQPage Schema
How do I authenticate lark-cli with Feishu scopes?▼

Run lark-cli auth login with either --domain for a business domain or --scope for a specific permission, which is the recommended least-privilege approach. Multiple logins accumulate scopes incrementally, and bot identity never requires auth login.

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

Bot identity (--as bot) only needs appId and appSecret but cannot access user resources like calendars or personal cloud docs. User identity (--as user) requires both console scope configuration and user authorization via auth login.

Why does lark-cli return permission_violations errors?▼

The error means required scopes are missing; the response lists the needed scopes plus a console_url. For bot identity, open the console URL to enable scopes; for user identity, run auth login with the missing scope.

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

Exit code 10 with error.type confirmation_required indicates a high-risk write operation blocked by a safety gate. Show the action to the user, get explicit consent, then retry the original command with --yes appended.

Can lark-cli accept absolute file paths for uploads?▼

No, path parameters like --file, --output, and @file only accept relative paths under the current working directory; absolute paths trigger an unsafe file path error. Prefer passing large data through stdin instead.