lark-shared

To set up Lark CLI authentication, run lark-cli config init and follow the prompts to configure the app, authorize permissions, and switch identities. This initialization provides step-by-step guidance for first-time app setup and scope validation.

Identity switching in Lark CLI allows you to perform actions under either user or bot contexts using the --as parameter. It is needed when managing permissions and executing tasks that require different authorization scopes between user and bot identities.

To handle permission denied errors during Lark CLI scope management, use the explicit guidance and safety checks provided to validate required scopes. The workflow includes dry-run previews to safely navigate permission errors and secure secrets during authorization.

Yes, you can preview Lark CLI permission changes using the built-in dry-run preview feature. This safety check allows you to verify scope management and identity switching actions before they are actually applied to your configuration.

No external dependencies are required for secure secrets handling in Lark CLI workflows. The skill implements built-in safety checks and explicit guidance to manage permissions and secure secrets directly during configuration and identity switching.