lark-note

Queries Feishu meeting note details and unified transcripts by note_id via lark-cli.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/TrayMachi/dotfiles --skill lark-note-traymachi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lark-note
Source: https://github.com/TrayMachi/dotfiles/tree/main/agents/skills/lark-note
Command: npx skills add https://github.com/TrayMachi/dotfiles --skill lark-note-traymachi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When you already hold a Feishu (Lark) meeting note ID, you still need to figure out the note's display type, locate its linked document tokens, and retrieve the correct verbatim transcript without guessing or reverse-engineering IDs from unrelated documents. ## Core Features & Use Cases - Note Detail Lookup: Run note +detail --note-id to get the note's display type (normal, unknown, unified), body document token, and verbatim document token. - Unified Transcript Retrieval: Run note +transcript --note-id to fetch the full raw transcript of unified notes, saved locally as Markdown or plain text with automatic pagination. - Display-Type Routing: Route follow-up reads correctly based on note_display_type, sending normal verbatim transcripts to the doc reader and unified ones to the transcript command. - Use Case: A user pastes a vc-node-id extracted from a Feishu doc and asks who said what in the meeting; the skill confirms the note is unified via +detail, then pulls the full transcript with +transcript. ## Quick Start Use the lark-note skill to look up the detail and transcript for Feishu meeting note with note_id abc123.

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 Feishu meeting note transcript by note_id?

First run lark-cli note +detail --note-id to check the note_display_type. If it is unified, run note +transcript --note-id to fetch the full raw transcript; if it is normal, read the verbatim_doc_token as a Docx document instead.

How to find the note_id for a Feishu meeting note?

The note_id must be explicit: either the user provides it directly, or it comes from the vc-node-id attribute of a vc-transcribe-tab element returned by docs +fetch --api-version v2. Never derive it from doc_token, titles, or backlinks.

What is the difference between normal and unified Feishu notes?

Normal notes store their verbatim transcript as a separate Docx document referenced by verbatim_doc_token. Unified notes keep the raw record inside the Note domain, so the transcript must be pulled with note +transcript rather than document reading.

Can I search Feishu meeting notes by title with this skill?

No. Title-based search is out of scope; use document search and docs +fetch first to obtain a vc-node-id, then return to the Note domain. This skill only accepts an explicit note_id as its entry point.

Why does note +transcript fail on my Feishu note?

The command only works when note_display_type is unified; the CLI validates this and refuses otherwise. It also fails if the output file already exists, unless you pass --overwrite after confirming replacement is intended.