lark-shared

Configure lark-cli authentication, identity switching, and scope management.

Updated Aug 23, 2026

Search Tags:#security #authentication #scope-management #lark-cli #config-init #identity-switch

Ready to run

npx skills add https://github.com/ShunsukeHayashi/lark-harness --skill lark-shared-shunsukehayashi

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides shared rules and guidance for configuring lark-cli, handling authentication, identity switching (--as user/bot), and managing scopes and permission denials to enable consistent and secure usage across teams.

Core Features & Use Cases

Shared configuration and authentication guidance for lark-cli, including initialization, login flows, and identity switching.
Clear handling of permission errors, scope requirements, and safe defaults to reduce misconfigurations.
Use Case: A developer configures a new workspace, authenticates as a bot, and validates scopes before automating actions.

Quick Start

Run lark-cli config init to complete the initial setup and authentication flow.

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 for initial setup and authentication?▼

To configure Lark CLI for initial setup, run the `lark-cli config init` command to complete the authentication flow and establish your workspace connection safely.

How does identity switching work when using Lark CLI?▼

Identity switching in Lark CLI allows you to execute commands as different users or bots by applying the `--as` flag, ensuring actions are performed with the correct permissions and governance.

What is the best way to handle permission-denied errors in Lark CLI?▼

Handling permission-denied errors in Lark CLI requires validating your current scopes and applying the shared safety rules to adjust permissions or switch identities before retrying the action.

Can I use Lark CLI to manage scopes for multiple users and bots?▼

Yes, you can manage scopes for multiple users and bots in Lark CLI by applying the provided shared rules to validate scope requirements and ensure compliant permission configurations across your team.

Why do I need shared rules for Lark CLI configuration across a team?▼

Shared rules for Lark CLI configuration enforce consistent authentication and safe defaults across teams, reducing misconfigurations and ensuring secure identity governance during workspace automation.

What are the limitations when switching identities in Lark CLI?▼

When switching identities in Lark CLI, you may encounter permission-denied errors if the target user or bot lacks the required scopes, requiring you to validate and adjust permissions before proceeding.