lark-shared

Manage Lark CLI configurations, authentications, and permissions via the Lark Suite API.

Updated May 8, 2026

Search Tags:#authentication #error handling #permissions #configuration #lark-cli

Ready to run

npx skills add https://github.com/gztcode/my-skills --skill lark-shared-gztcode

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies the process of configuring and managing the Lark CLI, providing tools for application setup, authentication, and error handling, saving time and reducing complexity.

Core Features & Use Cases

Configuration Initialization: Automates the initial setup of the Lark CLI.
Authentication: Handles user login and bot authentication.
Identity Switching: Allows users to switch between user and bot identities.
Permission and Scope Management: Provides tools for managing permissions and scopes.
Error Handling: Offers guidance on handling Permission denied errors.
Use Case: When users need to configure their Lark CLI, authenticate for the first time, or encounter permission issues, this Skill provides the necessary tools and instructions.

Quick Start

Initialize your Lark CLI configuration by running lark-cli config init.

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 configurations for application setup?▼

Handle user login and bot authentication by using the Lark Suite API access management features. This Skill provides tools to authenticate identities and switch between user and bot contexts as needed.

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

Switch between user and bot identities using the identity switching tools provided for Lark CLI operations. This allows seamless transitions between different authentication contexts during administrative tasks.

Why does my Lark CLI return a Permission denied error during authentication?▼

A Permission denied error occurs when Lark CLI authentication lacks sufficient scopes or correct permissions. This Skill offers specific error handling guidance and tools to manage and resolve user permission issues.

Do I need Lark Suite API access to manage CLI permissions and scopes?▼

Yes, Lark Suite API access and user authentication are required to manage CLI permissions and scopes. This access forms the foundation for setting up user applications and handling administrative tasks.

What's the best way to automate Lark CLI setup and avoid permission issues?▼

Automate Lark CLI setup and avoid permission issues by using the configuration initialization and scope management tools provided. This approach handles application setup, authentication, and error handling efficiently.