lark-shared

Automate Lark CLI configuration, authentication, and identity management workflows.

Updated Aug 17, 2024
One-click install
npx skills add https://github.com/LinoWhy/.dotfiles --skill lark-shared-linowhy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lark-shared
Source: https://github.com/LinoWhy/.dotfiles/tree/main/agents/.agents/skills/lark-shared
Command: npx skills add https://github.com/LinoWhy/.dotfiles --skill lark-shared-linowhy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Simplifies and standardizes the setup, authentication, and identity management tasks for the Lark CLI, reducing onboarding time and preventing misconfigurations.

Core Features & Use Cases

  • Guided configuration initialization to obtain and store app credentials.
  • Built-in authentication workflow including user and bot identity handling and domain/scope guidance.
  • Clear error handling and permission management for common authorization failures.

Quick Start

Run lark-cli config init --new to start the configuration flow.

Frequently Asked Questions about lark-shared

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

FAQPage Schema
How do I initialize Lark CLI configuration for a new app?

To initialize Lark CLI configuration, run lark-cli config init --new to start the guided flow for obtaining and storing your app credentials. This standardizes the setup process, reducing onboarding time and preventing misconfigurations.

How does identity switching work between user and bot in Lark CLI authentication?

Lark CLI authentication handles identity switching by allowing you to toggle between user and bot identities, providing domain and scope guidance to ensure the correct permission scopes are applied across your projects.

What is the best way to manage permission scopes across multiple Lark CLI projects?

Managing permission scopes across multiple Lark CLI projects is best handled through the built-in authentication workflow, which provides clear error handling and permission management for common authorization failures.

Why does my Lark CLI login flow fail with authorization errors?

Lark CLI login flows fail with authorization errors when permission scopes are misconfigured or app credentials are invalid. The CLI provides clear error handling and permission management to diagnose and resolve these common authorization failures.

Can I use Lark CLI config init to onboard new apps without manual credential setup?

Yes, you can use lark-cli config init --new to onboard new apps. The guided configuration initialization automates obtaining and storing app credentials, eliminating manual setup and preventing misconfigurations.