lark-shared

Initialize Lark CLI configs, log in, and switch identities with --as.

641|104|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/eastreams/loong --skill lark-shared-eastreams
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lark-shared
Source: https://github.com/eastreams/loong/tree/main/skills/larksuite-cli/lark-shared
Command: npx skills add https://github.com/eastreams/loong --skill lark-shared-eastreams

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual and error-prone configuration and OAuth-like authentication flows for the Lark CLI across user and bot identities are common; this skill provides a guided, safe path to configure apps, login, and switch identities.

Core Features & Use Cases

  • Configuration initialization for new apps and domains.
  • Safe, auditable login flows for user and bot identities.
  • Identity switching with --as and scope management, plus guidance for permission denial handling.
  • Real-world use: a developer sets up a new Lark app, then logs in as a user to access personal resources, or switches to bot identity to operate on behalf of the app.

Quick Start

Run lark-cli config init to start the app configuration workflow and then run lark-cli auth login with the desired identity.

Frequently Asked Questions about lark-shared

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

FAQPage Schema
How do I set up and initialize authentication for the Lark CLI?

To set up Lark CLI authentication, you initialize your app configuration using the config workflow, then run the login command with your desired user or bot identity to establish a secure session.

How do I switch between user and bot identities when using the Lark CLI?

You switch between user and bot identities in the Lark CLI by using the --as flag during your operations, allowing you to toggle between personal resource access and app-level bot actions.

What is the safest way to manage permissions and scopes for a Lark app?

The safest way to manage Lark app permissions is through guided scope handling during login, which ensures explicit authorization and provides guidance for permission denial handling to prevent unauthorized access.

Can I configure the Lark CLI for multiple apps and domains?

Yes, you can configure the Lark CLI for multiple apps and domains by running the configuration initialization workflow, which safely establishes distinct app setups and domain contexts for your CLI operations.

Why do I need a guided workflow for Lark CLI login and identity management?

You need a guided workflow for Lark CLI login to reduce manual, error-prone OAuth-like setup, ensuring auditable authentication flows and safe identity switching across user and bot profiles.