skills.rest
zephyrwang6
zephyrwang6COMMUNITY
Explore all skills by this author →
GitHub

lark-shared

Initialize and manage Lark CLI authentication, identity switching, and permission recovery.

14|4|Updated Mar 31, 2026
Search Tags:#authentication#permissions#configuration#scope#bot#user#lark-cli
One-click install
npx skills add https://github.com/zephyrwang6/allSkills --skill lark-shared-zephyrwang6
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lark-shared
Source: https://github.com/zephyrwang6/allSkills/tree/main/lark-shared
Command: npx skills add https://github.com/zephyrwang6/allSkills --skill lark-shared-zephyrwang6

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you initialize and use lark-cli correctly when working with Lark resources, especially when authentication, identity selection, and permission errors block progress.

Core Features & Use Cases

  • First-time setup: Guides the initial lark-cli configuration flow so the tool is ready to use.
  • Authentication workflows: Supports user sign-in, scope-based authorization, and repeated login when new permissions are needed.
  • Identity handling: Helps choose between user and bot identities so actions target the correct resources.
  • Permission troubleshooting: Explains how to respond to missing scopes, console links, and access-denied errors without using the wrong identity.
  • Safety rules: Reinforces secure handling of secrets and confirms before destructive actions.

Quick Start

Ask me to set up lark-cli for your current task, choose the right identity, and resolve any missing permissions or login prompts.

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 first-time setup?▼

First-time lark-cli setup requires initializing the tool and completing the user sign-in flow. This guides scope-based authorization to ensure the CLI is ready to manage Lark resources securely.

Why does my Lark CLI bot identity lack permissions for resource automation?▼

Your Lark CLI bot identity lacks permissions when missing required developer-console scopes. You must choose between user and bot identities and grant incremental scope authorizations to resolve access-denied errors during resource automation.

How do I switch between user and bot identities in Lark CLI?▼

To switch user and bot identities in Lark CLI, select the correct identity context before executing commands. This ensures actions target the correct resources and prevents access errors caused by using the wrong identity.

What is the best way to troubleshoot missing scope errors in Lark CLI?▼

Troubleshoot Lark CLI missing scope errors by checking developer-console permissions and applying incremental scope authorization. You may need to repeat the login flow to request new permissions without switching identities incorrectly.

Are there safety rules for executing write or delete operations with Lark CLI?▼

Lark CLI safety rules enforce secure secret handling and require explicit confirmation before executing destructive write or delete operations. This prevents accidental data loss during Lark resource automation and ensures secure permission recovery.

Related Skills

Explore More Software Engineering Skills→
heximaoheximao

lark-cli

Integrate Feishu/Lark CLI commands with Hermes Agent for messaging and document creation.

Community
Intermediate
llm011llm011
9

lark-shared

Configure lark-cli authentication and safely manage Feishu resources.

Official
Advanced
chenguojun06-starchenguojun06-star
1

lark-openapi-explorer

Discover and invoke undocumented Lark OpenAPI endpoints via lark-cli.

Community
Advanced
chenguojun06-starchenguojun06-star
1

lark-shared

Configure Lark CLI authentication and resolve permission scope issues.

Community
Intermediate