lark-shared

Configure Lark CLI apps, authenticate identities, and manage permission scopes.

Updated Feb 14, 2026
One-click install
npx skills add https://github.com/liutao96/skill --skill lark-shared-liutao96
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lark-shared
Source: https://github.com/liutao96/skill/tree/main/lark-shared
Command: npx skills add https://github.com/liutao96/skill --skill lark-shared-liutao96

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides developers and operators on how to use the Lark CLI to configure apps, authenticate access, switch identities, manage scopes, and enforce security rules when interacting with Feishu/Lark resources.

Core Features & Use Cases

  • Provides a structured workflow for initial app configuration via lark-cli config init
  • Supports authentication flows for both user and bot identities using lark-cli auth login
  • Enables identity switching with --as and scope management to access the right resources
  • Enforces safety practices to prevent credential leakage and unintended actions

Quick Start

Run lark-cli config init to initialize the app and then run lark-cli auth login to grant the necessary scopes.

Frequently Asked Questions about lark-shared

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

FAQPage Schema
How do I authenticate and log in to Lark CLI for app configuration?

To authenticate with Lark CLI, first run lark-cli config init to initialize your app settings, then execute lark-cli auth login to grant the necessary scopes for user or bot identities.

Can I switch between bot and user identities when using Lark CLI?

Yes, Lark CLI supports identity switching using the --as flag, allowing developers to toggle between bot and user identities to access specific resources and manage different permission scopes.

What is the best way to manage permission scopes for Feishu or Lark resources?

The best way to manage permission scopes is by using Lark CLI to configure app authentication and handle identity switching, ensuring your bot and user identities have the correct access levels.

How do I configure Lark CLI for multi-environment workflows?

You can configure Lark CLI for multi-environment workflows by running lark-cli config init to establish project setup parameters, then applying secure initialization and identity management rules across environments.

Why does Lark CLI enforce safety rules during authentication flows?

Lark CLI enforces safety rules during authentication and initialization to prevent credential leakage and avoid unintended actions when interacting with Feishu or Lark resources.

Do I need to initialize app configuration before managing Lark CLI identities?

Yes, you must run lark-cli config init for initial app configuration before using lark-cli auth login to manage identities, switch users, and handle permission scopes securely.