lark-shared

Configure and authenticate Lark CLI for user or bot identities.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/2p1c/2p1c_blog --skill lark-shared-2p1c
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lark-shared
Source: https://github.com/2p1c/2p1c_blog/tree/main/.agents/skills/lark-shared
Command: npx skills add https://github.com/2p1c/2p1c_blog --skill lark-shared-2p1c

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured framework for configuring and authenticating with Lark CLI, including identity management and permission guidance, to streamline secure usage across teams.

Core Features & Use Cases

  • Centralized guidance for configuration init, login flows, identity switching, and permission troubleshooting.
  • Enforces safety rules and prompts for authorization steps to prevent credential leakage and misconfigurations.
  • Use Case: A developer runs the shared setup to initialize an app, securely log in as bot or user, and adjust scopes as needed.

Quick Start

Begin by initializing the Lark CLI configuration and then authenticate to the desired identity (user or bot) using the login flow.

Frequently Asked Questions about lark-shared

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

FAQPage Schema
How do I set up Lark CLI configuration and authenticate for the first time?

Initialize Lark CLI configuration by running the shared setup to initialize your app, then authenticate to your desired identity using the secure login flow. This facilitates secure setup for Lark CLI across team workflows by enforcing safety rules.

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

Identity switching in Lark CLI involves applying identity-aware permissions to toggle securely between user and bot contexts. This mechanism ensures proper authorization scopes are maintained during workflows, preventing credential leakage and misconfigurations.

What is the best way to troubleshoot Lark CLI permission issues?

Troubleshooting Lark CLI permission issues involves applying identity-aware safety checks to resolve authorization failures. Guidance is provided to adjust scopes as needed, preventing misconfigurations and ensuring secure usage across team workflows.

Do I need specific safety checks to prevent credential leakage when using Lark CLI?

Yes, you need enforced safety rules and authorization prompts to prevent credential leakage when using Lark CLI. The setup framework applies identity-aware safety checks during login flows to ensure secure configuration.

Can I use this Lark CLI setup framework to manage permissions across different team workflows?

Yes, you can use this setup framework to manage Lark CLI permissions across team workflows. It provides centralized guidance for permission troubleshooting and enforces identity-aware safety checks to streamline secure usage.