What problem does it solve? Configuring and authenticating lark-cli against Feishu (Lark) involves device-code flows, user vs bot identity choices, business-domain scopes, and confirmation gates for risky operations, which are easy to get wrong without clear rules. ## Core Features & Use Cases - Authentication & Authorization: Run auth login/status/logout with split-flow device-code authorization, QR code generation, and incremental scope grants via --domain or --scope. - Identity & Permission Handling: Distinguish user vs bot identities with --as, diagnose missing scopes from permission_violations errors, and route bot fixes to the developer console. - Safety Gates: Handle exit code 10 confirmation_required envelopes for high-risk writes, use --dry-run previews, and enforce relative-path and secret-handling rules. - Use Case: A user asks to access their Feishu calendar but hits a missing-scope error; the skill initiates a scoped login, shows the verification URL and QR code, then completes the device-code exchange in a later turn. ## Quick Start Ask the assistant to check your current lark-cli login status and identity, then authorize the scopes needed for your Feishu task.