lark-note

Query Lark meeting note details and unified transcripts by note_id via lark-cli.

Updated Sep 13, 2026
One-click install
npx skills add https://github.com/U1traVeno/skills --skill lark-note-u1traveno
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lark-note
Source: https://github.com/U1traVeno/skills/tree/main/profiles/lark/lark-note
Command: npx skills add https://github.com/U1traVeno/skills --skill lark-note-u1traveno

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about lark-note

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get a Lark meeting note transcript by note_id?▼

First run lark-cli note +detail --note-id to check note_display_type. If it is unified, run note +transcript --note-id to save the full transcript locally; if normal, read the verbatim_doc_token with docs +fetch instead.

How to find the note_id for a Lark meeting?▼

The note skill only accepts an explicit note_id. Get it from vc +detail --meeting-ids for a meeting_id, from minutes +detail for a minute_token, from calendar +meeting for an event_id, or from a vc-node-id inside a Docx document.

Can I use a doc_token or minute_token as a note_id?▼

No. The note domain never derives note_id from doc_token, titles, body text, or backlinks, and minute_token is not a note_id. Resolve those through lark-doc, lark-minutes, or lark-vc first to obtain a real note_id.

What is the difference between normal and unified Lark meeting notes?▼

Normal notes store the verbatim transcript as a standalone Docx readable via docs +fetch on verbatim_doc_token. Unified notes require note +transcript to pull the raw record, even if a verbatim_doc_token is returned.

Why does note +transcript fail or refuse to run?▼

The CLI validates that the note is unified before fetching and aborts otherwise. It also fails if the target output file already exists unless you pass --overwrite, and any pagination failure discards partial results.