lark-shared

Configure lark-cli authentication and safely manage Feishu resources.

9|Updated Jun 11, 2026
One-click install
npx skills add https://github.com/llm011/ethan-agent --skill lark-shared-llm011
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lark-shared
Source: https://github.com/llm011/ethan-agent/tree/main/ethan/defaults/skills/lark-shared
Command: npx skills add https://github.com/llm011/ethan-agent --skill lark-shared-llm011

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents configuration, authentication, identity, permission, and safety errors when using lark-cli to manage Feishu resources.

Core Features & Use Cases

  • Configuration and Authentication: Initialize lark-cli, start user authorization flows, generate required QR codes, and switch between user and bot identities.
  • Permission Recovery: Handle missing scopes and authorization failures with identity-specific remediation instead of treating them as terminal errors.
  • Safe Operations: Enforce relative-path rules, protect credentials, preview risky requests, and require explicit confirmation before high-risk writes.
  • Maintenance Guidance: Detect update notices and recommend updating both lark-cli and its associated Skills.
  • Use Case: When a Feishu document operation fails because of missing permissions, use this Skill to identify the identity involved, initiate the appropriate authorization or scope configuration flow, and safely resume the task after approval.

Quick Start

Use the lark-shared skill to configure lark-cli, authenticate the appropriate Feishu identity, and safely diagnose any permission error.

Frequently Asked Questions about lark-shared

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

FAQPage Schema
How do I fix Feishu permission errors when managing resources with lark-cli?

To fix Feishu permission errors, you need identity-specific permission recovery. This process identifies whether the user or bot identity lacks scopes, initiates the appropriate authorization flow, and safely resumes the resource management task after approval.

How do I configure lark-cli authentication and generate QR codes for Feishu user authorization?

Configuring lark-cli authentication involves initializing the CLI and starting the user authorization flow. This process generates the required QR codes and allows you to securely switch between user and bot identities for Feishu operations.

What is the safest way to execute high-risk write operations in Feishu using lark-cli?

The safest way to execute high-risk write operations is by enforcing relative-path validation and credential protection. You must preview risky requests via dry-run and require explicit confirmation before any destructive Feishu resource modifications are applied.

Why does my lark-cli bot identity fail to access specific Feishu documents despite being authenticated?

Your lark-cli bot identity fails because of missing identity-aware scopes. You must diagnose the identity involved, apply identity-specific scope handling to recover permissions, and complete the correct authorization flow to regain access.

Do I need to update lark-cli and associated Skills when maintenance notices appear?

Yes, you need to update lark-cli and associated Skills when maintenance notices appear. Detecting update notices ensures you maintain identity-aware scope handling and safe operations without encountering deprecated authentication or permission recovery workflows.