lark-shared

Configure lark-cli authentication, identities, and permission troubleshooting for Feishu operations.

641|104|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/loongclaw-ai/loongclaw --skill lark-shared-loongclaw-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lark-shared
Source: https://github.com/loongclaw-ai/loongclaw/tree/main/skills/larksuite-cli/lark-shared
Command: npx skills add https://github.com/loongclaw-ai/loongclaw --skill lark-shared-loongclaw-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill clarifies the Lark CLI onboarding steps so agents can complete configuration init, authentication, identity switching, and scope repairs without permission roadblocks or accidental bot versus user mismatches.

Core Features & Use Cases

  • Configuration Initialization: Start with lark-cli config init to create application settings, watch the output for the authorization link, and share it with the user for completion.
  • Authentication & Identity Management: Use lark-cli auth login with explicit domain or scope arguments, switch between user and bot contexts with --as flags, and respect the differing resource visibility when fulfilling requests.
  • Permission Troubleshooting and Updates: Interpret permission_violations alerts, direct users to console URLs for missing scopes, monitor _notice.update entries, and remind them to update the CLI and skills while guarding secrets and double-checking write or delete actions.

Quick Start

Ask the agent to run lark-cli config init --new, capture the authorization link it prints, and confirm when the shared initialization flow completes.

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 for Feishu resources?

Initialize lark-cli authentication by running lark-cli config init, capturing the printed authorization link, and completing the shared initialization flow to access Feishu resources without blocking errors.

How do I switch between user and bot identities in lark-cli?

Switch between user and bot identities in lark-cli by using the --as flags during auth login, allowing you to respect the differing resource visibility when fulfilling requests in either context.

Why do I get permission_violations errors during my Feishu CLI operations?

Permission_violations errors occur when your lark-cli app lacks required scopes. Interpret the alerts, direct users to the console URLs for missing scopes, and repair permissions to resolve the issue.

Do I need explicit scopes for lark-cli auth login?

Yes, lark-cli auth login requires explicit domain or scope arguments to authorize the app correctly, ensuring precise access control over Feishu resources without accidental permission mismatches.

How does lark-cli handle secrets during write or delete commands?

Lark-cli provides guarded guidance that denies leaking secrets and prompts for explicit confirmations before executing write or delete commands, ensuring safe CLI workflow operations.