lark-shared

Manage Lark CLI configuration, authentication, and identity switching for user and bot scopes.

1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/eatbreads/.agents --skill lark-shared-eatbreads
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lark-shared
Source: https://github.com/eatbreads/.agents/tree/main/skills/lark-shared
Command: npx skills add https://github.com/eatbreads/.agents --skill lark-shared-eatbreads

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill documents how to initialize and manage Lark (Feishu) CLI application configuration, perform authentication flows, switch identities between user and bot, and resolve permission scope errors so agents and users can operate lark-cli safely and effectively.

Core Features & Use Cases

  • Configuration Initialization: Guidance for starting the app configuration flow and extracting authorization links from backgrounded CLI commands so users can complete setup.
  • Authentication & Identity Management: Rules for when to use user vs bot identities, how to perform auth login for user scopes, and how bot identity behaves without interactive login.
  • Permission Handling and Maintenance: How to interpret permission_violations, use developer console links to grant scopes, handle update notices embedded in CLI JSON output, and enforce security rules that prevent leaking secrets.
  • Use case: An AI agent initiates an auth login in the background, extracts the returned authorization URL, sends it to the user, and then guides scope adjustments in the developer console while avoiding exposing credentials.

Quick Start

Run lark-cli config init --new in the background, capture the authorization link from its output, and send the link to the user so they can complete the configuration.

Frequently Asked Questions about lark-shared

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

FAQPage Schema
How do I initialize Lark CLI configuration and complete the authentication login?

To initialize Lark CLI configuration, run 'lark-cli config init --new' in the background, extract the authorization URL from the CLI output, and open the link to complete the authentication login process safely.

When should I switch between user and bot identities for Feishu CLI operations?

Switch between user and bot identities based on resource access needs. Use user identity for interactive auth login scopes like calendars or cloud documents, while bot identity operates without interactive login for bot-level resources.

Why do I get permission_violation errors when accessing Feishu cloud documents or calendars?

Permission_violation errors occur when accessing Feishu cloud documents or calendars without proper scope configuration. Resolve them by using the developer console links provided in the CLI output to grant the required permission scopes.

What is the safest way to handle secrets and update notices in Lark CLI JSON output?

The safest way to handle secrets in Lark CLI JSON output is to enforce safety rules that prevent leaking credentials. Extract update notices carefully and ensure sensitive authorization links or tokens are never exposed in responses.

Can an AI agent automatically perform Lark CLI auth login and handle scope configuration?

Yes, an AI agent can initiate Lark CLI auth login in the background, extract the returned authorization URL, send it to the user, and then guide scope adjustments via the developer console without exposing credentials.