Lark Note

About

The lark-note skill routes Feishu meeting note (Note) operations through lark-cli using explicit note_id values only. It accepts note_id from the user or from a docs fetch vc-node-id attribute, then branches on note_display_type to fetch detail metadata, note body documents, or unified raw transcripts. Normal notes with verbatim_doc_token route transcript reads through docs fetch, while unified notes require note +transcript instead of guessing from tokens alone. The skill operates strictly as user context per lark-shared guidance and does not infer note_id from doc tokens, titles, backlinks, or natural language meeting names. Command routing covers note +detail for type and document tokens, docs fetch for note_doc_token bodies, and note +transcript for unified verbatim records. Out-of-scope tasks such as meeting calendar lookup, drive title search, or Docx reading defer to lark-vc, lark-drive, lark-doc, or lark-minutes skills. Version 1.0.0 metadata requires the lark-cli binary and links reference docs for detail and transcript field semantics.

• Accepts only explicit note_id from user input or vc-node-id on docs fetch v2 responses.
• Routes note_display_type unknown, normal, and unified to distinct detail, docs, or transcript commands.
• Uses lark-cli note +detail and note +transcript with mandatory --as user identity.
• Delegates note body reading to lark-doc via note_doc_token after detail lookup.
• Defers meeting search, drive title lookup, and minutes media to sibling Lark domain skills.