lark-shared

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

3|1|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/HuXiangyu123/CUA-Lark-Agent --skill lark-shared-huxiangyu123
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lark-shared
Source: https://github.com/HuXiangyu123/CUA-Lark-Agent/tree/main/lark-cli/skills/lark-shared
Command: npx skills add https://github.com/HuXiangyu123/CUA-Lark-Agent --skill lark-shared-huxiangyu123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides users through configuring and operating lark-cli for authentication, identity switching (--as user or --as bot), and permission management, reducing setup friction and misconfigurations.

Core Features & Use Cases

  • Configuration initialization with lark-cli config init
  • Identity management with --as user or --as bot for accessing different resources
  • Permission handling and scope management with guidance for resolving missing permissions
  • Safe error handling and guidance to maintain secure workflows

Quick Start

Run lark-cli config init to begin setup, then authenticate with your chosen identity and verify the required scopes.

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 authentication and manage user versus bot permissions?

Initialize lark-cli authentication by running lark-cli config init, then use --as user or --as bot to switch identities and verify scope permissions for secure resource access.

What is the best way to resolve insufficient permission errors when using lark-cli?

Resolve lark-cli insufficient permission errors by checking your current identity scope with --as user or --as bot, then re-authenticating to apply the required access scopes.

How do I switch between user and bot identity contexts for lark-cli operations?

Switch lark-cli identity contexts by appending --as user or --as bot to your commands, allowing you to access different resources based on the specific identity's configured scopes.

Does lark-cli config init require any specific dependencies to set up authentication?

No dependencies are required for lark-cli config init, as it provides a structured setup with built-in safety checks to guide authentication and scope initialization independently.

Why does lark-cli authentication fail when switching identity scopes without proper initialization?

lark-cli authentication fails during identity switching if lark-cli config init was not run first, preventing the system from safely loading the required scopes for the user or bot context.