lark-shared

Automate Lark CLI configuration, authentication, and scope management workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides developers and agents through Lark CLI application configuration and authentication to avoid failed operations caused by missing scopes, incorrect identity context, or unsafe handling of secrets.

Core Features & Use Cases

  • Configuration Initialization: Walks through running configuration initialization when first using the CLI and extracting authorization links from the CLI output.
  • Authentication & Identity Management: Explains user versus bot identities, how to perform auth login for users, when bot credentials suffice, and how to switch context using the --as flag.
  • Permission Handling & Safety: Details how to interpret permission_violations and console_url responses, instructs how to request specific scopes, prohibits exposing secrets, and recommends dry-run and explicit confirmation for destructive operations.

Quick Start

Initiate configuration by running lark-cli config init --new in background and send the extracted authorization link to the user.

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 extract the authorization URL?

To initialize Lark CLI configuration, run `lark-cli config init --new` in the background and extract the authorization URL from the CLI output to send to the user for login.

Why am I getting permission denied errors when using the Lark CLI?

Permission denied errors occur when your Lark CLI identity lacks required scopes. Interpret the `permission_violations` and `console_url` responses, then request specific scopes in the developer console.

How do I switch between user and bot identities for Lark CLI authentication?

Switch Lark CLI authentication context between user and bot identities using the `--as` flag. Perform auth login for users, or use bot credentials when they suffice for the operation.

What is the best way to handle secrets during Lark app authentication?

The best way to handle secrets during Lark app authentication is to strictly prohibit exposing them. Enforce secret-handling rules and recommend dry-run and explicit confirmation for destructive operations.

Does the Lark CLI support dry-run mode for destructive operations?

Yes, Lark CLI supports dry-run mode. It recommends using dry-run and explicit confirmation for destructive operations to prevent accidental data loss during app configuration and authentication workflows.

When do I need to request specific scopes in the Lark developer console?

You need to request specific scopes in the Lark developer console when your CLI operations fail due to missing permissions, guided by `console_url` responses from permission violation errors.