lark-note

Query Lark meeting note details and unified transcripts by note_id.

Updated Jun 29, 2026
One-click install
npx skills add https://github.com/trungpr1990-coder/AMI-MAKEUP --skill lark-note-trungpr1990-coder
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lark-note
Source: https://github.com/trungpr1990-coder/AMI-MAKEUP/tree/main/.agents/skills/lark-note
Command: npx skills add https://github.com/trungpr1990-coder/AMI-MAKEUP --skill lark-note-trungpr1990-coder

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), you need a direct way to look up the note's display type, its linked document tokens (AI summary, verbatim transcript, shared docs), and the raw unified transcript—without guessing IDs from document titles or URLs. ## 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_doc_tokens for a given note_id. - Unified Transcript Retrieval: Run note +transcript --note-id to fetch the 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's verbatim record; the skill checks note_display_type and routes to either docs +fetch on the verbatim_doc_token or note +transcript for unified notes. ## Quick Start Use the lark-note skill to look up the details and transcript entry points for note_id <your_note_id>.

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's document tokens from a note_id?▼

Run `lark-cli note +detail --note-id <note_id>` to retrieve the note_display_type, note_doc_token, verbatim_doc_token, and shared_doc_tokens. Then use `docs +fetch --doc <token>` to read the corresponding document content.

How to fetch the raw verbatim transcript of a Lark meeting note?▼

First confirm via `note +detail` that note_display_type is unified, then run `lark-cli note +transcript --note-id <note_id>`. For normal notes, read the verbatim_doc_token as a regular Docx document instead.

Can I find a note_id from a meeting_id or minute_token?▼

Not directly in this skill. Use `vc +detail --meeting-ids` for meeting_id, `minutes +detail --minute-tokens` for minute_token, or `calendar +meeting --event-ids` for event_id, then pass the resulting note_id to note +detail.

Why does note +transcript fail for my meeting note?▼

The transcript command only works when note_display_type is unified; the CLI validates this before pulling data. For normal notes, fetch the verbatim_doc_token via docs +fetch, and for unknown types with a token, treat it as an independent document.

Can I derive a note_id from a Docx URL or document title?▼

No. The skill explicitly forbids reverse-deriving note_id from doc_token, titles, body text, or backlinks. Only a vc-node-id from a vc-transcribe-tab element in a fetched document is a valid note_id source.