lark-shared

Manage Feishu/Lark authorization, identity switching, and permissions via lark-cli.

28|2|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/echonoshy/ripple --skill lark-shared-echonoshy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lark-shared
Source: https://github.com/echonoshy/ripple/tree/main/skills/lark/lark-shared
Command: npx skills add https://github.com/echonoshy/ripple --skill lark-shared-echonoshy

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill simplifies the process of interacting with Feishu/Lark using the lark-cli, handling authorization, identity switching, permission management, and error handling, making it suitable for various scenarios like initial setup, login authorization, and permission issues.

Core Features & Use Cases

  • Authorization Management: Handles Ripple dialogue authorization, identity switching, and permission and scope management.
  • Error Handling: Provides guidance on handling errors like 'Permission denied' and prompts for updates.
  • Use Case: When you need to configure Feishu/Lark for the first time, log in, encounter permission issues, switch user/bot identities, see update notices, or require confirmation for high-risk operations.

Quick Start

Run the command 'lark-cli config show' to check your configuration and authentication status.

Frequently Asked Questions about lark-shared

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

FAQPage Schema
How do I manage Feishu authorization and switch user identities using lark-cli?

Feishu authorization and identity switching are managed through lark-cli by handling Ripple dialogue authorization and executing identity switches to operate under different user or bot profiles.

What should I do when lark-cli returns a permission denied error in Feishu?

A permission denied error in lark-cli indicates a Feishu scope issue; you must update your permission configurations and follow the provided error handling guidance to restore access.

Do I need a Feishu connector to use lark-cli for initial setup?

Yes, you need both the lark-cli and a Feishu connector installed to complete the initial setup and manage login authorization for your Feishu or Lark environment.

Can I check my current Feishu configuration and authentication status before running operations?

You can check your Feishu configuration and authentication status by running the 'lark-cli config show' command, which verifies your current setup before executing further operations.

How does lark-cli handle high-risk operations during Feishu permission management?

During Feishu permission management, lark-cli handles high-risk operations by pausing execution and requiring explicit confirmation before applying the sensitive configuration changes.

Why does my lark-cli session require updates during Feishu login authorization?

Your lark-cli session requires updates during Feishu login authorization when the system detects outdated configurations, prompting you to update to maintain secure access.