lark-shared

Lark CLI authentication is configured by running `lark-cli config init` and following the on-screen prompts to set up your app. This initialization process guides you through authenticating both user and bot identities safely without exposing credentials.

Switching between user and bot modes in Lark CLI is handled explicitly using the `--as user/bot` command flag. This identity management feature ensures you operate under the correct scope and permissions for your specific Lark resource integration task.

Permission errors during Lark CLI setup usually occur when app scopes are misconfigured or identity permissions are insufficient. The Skill provides troubleshooting guidance to resolve these errors by verifying your authentication flow and correcting scope management settings.

Yes, you can manage multiple Lark app scopes and identities safely for team integration. The Skill enforces safe operational practices and security safeguards to prevent misconfigurations and data leakage when switching identities or handling resources.

Lark CLI identity management ensures data security during resource operations by enforcing safe operational practices and explicit identity handling. It prevents data leakage by guiding the authentication flow and scope management for both user and bot modes.

The lark-shared Skill focuses on initial config, authentication flows, and permission troubleshooting for the Lark CLI. It does not cover advanced resource manipulation beyond ensuring safe identity handling and scope management during the setup phase.