lark-note

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

2|Updated Aug 9, 2026
One-click install
npx skills add https://github.com/DeepJH/doubao-skill-and-info --skill lark-note-deepjh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lark-note
Source: https://github.com/DeepJH/doubao-skill-and-info/tree/main/skills/lark-note
Command: npx skills add https://github.com/DeepJH/doubao-skill-and-info --skill lark-note-deepjh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When you already hold a Lark (Feishu) meeting note_id, you still need to resolve what the note contains—its display type, AI summary document token, verbatim transcript token, and shared documents—before you can read any content. This Skill routes note_id-based lookups through lark-cli so you get the right document tokens and unified raw transcripts without guessing. ## 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. - 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 guidance: Built-in routing tables map inputs like meeting_id, minute_token, event_id, or vc-node-id to the correct upstream skill (lark-vc, lark-minutes, lark-calendar) before entering the Note domain. - 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 Docx via docs or pulls the unified transcript directly. ## Quick Start Ask the assistant to look up the meeting note details and transcript for your known note_id using the lark-note skill.

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_doc_token, verbatim_doc_token, and shared_doc_tokens. You can then read the note body with docs +fetch using the returned tokens.

How to retrieve the verbatim transcript of a Lark meeting note?

First check note_display_type via note +detail. For unified notes, run note +transcript --note-id; for normal notes, fetch the verbatim_doc_token as a Docx document via docs +fetch.

Can I look up a Lark note using only a meeting_id or minute_token?

Not directly in this Skill. Use vc +detail --meeting-ids to get the note_id from a meeting_id, or minutes +detail --minute-tokens to get it from a minute_token, then call note +detail.

Does lark-cli note +transcript work for all note types?

No, note +transcript only works when note_display_type is unified. The CLI validates the type first and refuses to pull transcripts for normal notes, which store transcripts as separate Docx documents.

Why does note +transcript fail when the output file already exists?

The command refuses to overwrite an existing transcript file at ./notes/{note_id}/unified_transcript.md by default. Add the --overwrite flag only when you explicitly want to replace the existing file.