lark-shared

Configure lark-cli authentication and manage high-risk write operations.

Updated May 11, 2026
One-click install
npx skills add https://github.com/heximao/agents --skill lark-shared-heximao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lark-shared
Source: https://github.com/heximao/agents/tree/main/skill-archive/lark/lark-shared
Command: npx skills add https://github.com/heximao/agents --skill lark-shared-heximao

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires lark-cli, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies the setup and operations of lark-cli, making it easy to handle configurations, authentication, and high-risk operations.

Core Features & Use Cases

  • Configuration Management: Streamline the initial setup and updates of lark-cli.
  • Authentication Handling: Assist with user and bot identity switching and managing permission errors.
  • High-Risk Operations: Safely navigate high-risk write operations with approval protocols and dry-run previews.
  • Use Case: Need to update lark-cli or handle a permission error? Use this Skill to guide you through the process.

Quick Start

Run lark-cli update to update lark-cli and all related Skills.

Frequently Asked Questions about lark-shared

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

FAQPage Schema
How do I handle lark-cli permission errors during authentication?

Lark-cli permission errors during authentication are resolved by managing user and bot identities. This skill coordinates with lark-cli to switch identities and clear permission blocks for secure access.

What is the best way to manage lark-cli configuration and updates?

Lark-cli configuration and updates are managed through streamlined setup and operational tasks. Running the update command refreshes lark-cli and all related skills to maintain current configurations.

Do I need lark-cli installed to manage high-risk write operations?

Lark-cli is required as a dependency to manage high-risk write operations. This skill coordinates with the CLI to enforce confirmation protocols and dry-run previews for secure execution.

Can I preview high-risk write operations before execution?

High-risk write operations can be previewed using dry-run functionality. This skill enforces approval protocols and coordinates with lark-cli to ensure secure navigation of dangerous writes.

Why does lark-cli authentication fail when switching between users and bots?

Lark-cli authentication fails during identity switching due to unmanaged permission errors. This skill handles user and bot identity coordination to resolve conflicts and ensure secure operations.