What problem does it solve? When you already hold a Feishu meeting note ID, you still need to resolve its display type, locate the underlying document tokens (AI summary, verbatim transcript, shared docs), and fetch unified raw transcripts—tasks that require knowing the correct lark-cli note commands and routing rules. ## Core Features & Use Cases - Note Detail Lookup: Run note +detail --note-id to retrieve note_display_type, note_doc_token, verbatim_doc_token, and shared document tokens. - Unified Transcript Retrieval: Run note +transcript --note-id to pull the full raw verbatim record for unified-type notes, saved locally as Markdown or plain text. - Routing Discipline: Enforces strict domain boundaries—deriving note_id only from explicit user input, vc-node-id in fetched docs, or upstream vc/minutes/calendar lookups, never reverse-engineering it from doc tokens or titles. - Use Case: A user has a note_id from a meeting detail query and wants the verbatim transcript; the Skill checks note_display_type, then either fetches the verbatim doc via docs or pulls the unified transcript. ## Quick Start Ask the assistant to look up the meeting note details and transcript for a given note_id using the lark-note skill.
