What problem does it solve? First-time lark-cli users often get stuck on app configuration, OAuth login, and confusing permission errors when accessing Feishu/Lark resources. This Skill provides the shared foundation for initializing the CLI, choosing the right identity (user vs bot), and resolving permission-denied errors correctly. ## Core Features & Use Cases - App Configuration: Runs lark-cli config init in background mode and extracts the authorization link to send to the user. - Identity Management: Switches between --as user and --as bot identities, explaining why a bot cannot see user calendars, docs, or mailboxes. - Permission Troubleshooting: Parses permission_violations, console_url, and hint fields from errors, then guides scope activation in the developer console or incremental auth login --scope authorization. - Update & Safety Rules: Detects _notice.update version prompts and enforces security rules like never printing appSecret or accessToken. - Use Case: A user asks the agent to check their calendar but hits a permission error; the agent identifies the missing scope, runs lark-cli auth login --scope "calendar:calendar:readonly" in background, and sends the authorization link to the user. ## Quick Start Help me initialize lark-cli configuration and log in with user identity so I can access my Feishu calendar.
