What problem does it solve? When using lark-cli to operate the Feishu Open Platform, user-identity tokens must be obtained and refreshed correctly. This Skill governs the entire lark-oauth authorization flow so lark-cli commands can execute with valid user credentials without manual token handling. ## Core Features & Use Cases - Device Authorization Flow handling: Detects authorization URLs in command output, relays them to the user, and polls with the saved device_code (up to 60 seconds, max 2 attempts) until the token is issued. - Token lifecycle management: Reuses cached access tokens, silently refreshes expired ones with single-rotation refresh tokens, and falls back to re-authorization on Feishu error codes 20026/20037/20064/20073. - Batch scope authorization: Collects all missing_scopes across a task and authorizes them in one lark-oauth --scope call, so the user only clicks the authorization link once. - Use Case: An agent needs to read a Bitable table and send a message via lark-cli. It runs the commands, collects missing scopes like base:record:read and im:message, executes one lark-oauth --scope command, sends the URL to the user, then reruns the blocked commands after authorization completes. ## Quick Start Authorize lark-cli with lark-oauth using the required scopes, then rerun my Feishu command once the token is ready.
