What problem does it solve? When you already hold a Lark meeting note ID (note_id) but need the underlying document tokens, display type, or raw verbatim transcript, manually navigating Feishu Docs and meeting records is slow and error-prone. This Skill routes a known note_id directly to the right lark-cli commands. ## Core Features & Use Cases - Note Detail Lookup: Run note +detail --note-id to retrieve the AI summary doc token, verbatim doc token, shared doc tokens, and the note_display_type (normal / unified / unknown). - Unified Transcript Retrieval: Run note +transcript --note-id to pull the full raw verbatim record of unified-type notes, saved locally as Markdown or plain text. - Routing Discipline: Enforces strict domain boundaries—meeting_id lookups go to lark-vc, minute_token to lark-minutes, event_id to lark-calendar, and Docx body reading to lark-doc. - Use Case: A user has a note_id from vc +detail and wants the meeting transcript. The Skill checks note_display_type; if unified, it fetches the transcript directly; if normal, it routes to docs +fetch on the verbatim_doc_token. ## Quick Start Use the lark-note skill to look up the details and transcript for note_id abc123 with lark-cli.