lark-shared

Configure Lark CLI authentication and switch between user and bot identities.

20|1|Updated Mar 15, 2026

Search Tags:#authentication #cli #permissions #configuration #lark #larksuite

Ready to run

npx skills add https://github.com/ImChong/Humanoid_Robot_Learning_Paper_Notebooks --skill lark-shared-imchong

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: lark-shared
Source: https://github.com/ImChong/Humanoid_Robot_Learning_Paper_Notebooks/tree/main/.agents/skills/lark-shared
Command: npx skills add https://github.com/ImChong/Humanoid_Robot_Learning_Paper_Notebooks --skill lark-shared-imchong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines Lark CLI configuration and authentication workflows for accessing Feishu/Lark resources.

Core Features & Use Cases

Configuration onboarding: initialize and configure the Lark CLI project with proper authentication flow.
Identity management: switch between user and bot identities, and manage permissions/scopes.
Guidance on errors: interpret permission related responses (console_url, hint) to resolve access issues.

Quick Start

Run lark-cli config init to begin configuring your Lark app and follow the on-screen prompts.

Frequently Asked Questions about lark-shared

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

FAQPage Schema

How do I configure Lark CLI authentication for the first time?▼

To configure Lark CLI authentication, run the `lark-cli config init` command to initialize your project and follow the on-screen prompts to complete the authentication flow for accessing Feishu or Lark resources.

How do I switch between user and bot identities in Lark CLI?▼

Switching between user and bot identities in Lark CLI is supported through the identity management feature, allowing you to manage different contexts and handle permissions or scopes for your specific application requirements.

What is the best way to troubleshoot Lark CLI permission errors?▼

Troubleshooting Lark CLI permission errors involves interpreting the permission-related responses provided by the system, specifically utilizing the generated `console_url` and `hint` messages to identify and resolve access issues.

Do I need to manage scopes separately when using Lark CLI for user and bot contexts?▼

Yes, managing scopes is required when using Lark CLI for user and bot contexts, as the identity management feature explicitly handles scope configuration to ensure correct access levels across different identity types.

Why does my Lark CLI configuration require a safety prompt during login?▼

Lark CLI configuration requires a safety prompt during login to securely manage the authentication workflows, protecting sensitive credentials and ensuring safe access to your Feishu or Lark resources.

Can I initialize a Lark CLI project without prior authentication setup?▼

No, initializing a Lark CLI project requires setting up the authentication flow, as configuration onboarding explicitly integrates the login process to properly establish access to Lark resources from the start.