Loading...
Loading...
Direct Query for Feishu Meeting Minutes (Note): Query minute details, display type (normal minute / unified minute), associated document tokens, and the original verbatim transcript of unified minutes when the note_id is known. This skill is used when users already have a note_id and want to query minute metadata, minute type, and document tokens for minutes/verbatim transcripts; the verbatim transcript of unified minutes is not an independent document and must be retrieved by note +transcript using the note_id. This skill only accepts note_id as the entry point.
npx skill4agent add larksuite/cli lark-note../lark-shared/SKILL.mdnote_idlark-vclark-minuteslark-docSource of: If the entry is a document, first usenote_idto read document metadata; thedocs +fetch --api-version v2 --doc <doc_token>in the response indicates a VC original record block, where the value of the<vc-transcribe-tab vc-node-id="..."></vc-transcribe-tab>attribute is thevc-node-idused by the Note domain. This is an explicit attribute mapping; do not infernote_idfromnote_id, title, content or backlink.doc_tokenOnly minute title available: When the user says "Query the verbatim transcript / original record / who said what of xx minute" and there is no,note_id,meeting_id,calendar_event_id, meeting number or Miaoji URL, first search for the minute document and fetch its content. Only theminute_tokenin the content can enter this skill; otherwise, only read the explicit "verbatim record/transcript" Docx link in the content, do not force entry into the Note domain.<vc-transcribe-tab vc-node-id="...">
note_idnote_display_typeunknownnormalunifiednormalnote_doc_tokenverbatim_doc_tokenunifiednote +transcriptnote_idnote_doc_tokenverbatim_doc_tokenshared_doc_tokens| User Expression | Command / Route |
|---|---|
Known | |
| Only natural language minute title, user requests verbatim transcript / original record / who said what | Do not enter this skill; route to lark-drive / lark-doc first, then return after obtaining |
| Use the value of |
Known | |
Known | First use |
note_display_type| Condition | Agent Follow-up Action |
|---|---|
| User requests minute content / summary / to-dos / sections | |
| |
| |
| If the current result comes from |
| |
The discriminant key is, not whethernote_display_typeis empty. Theverbatim_doc_tokenof unified minutes may also have a value, but the verbatim transcript of unified minutes should uniformly useverbatim_doc_token(more structured output).note +transcript
meeting_idcalendar_event_idminute_tokenvc-node-id<vc-transcribe-tab>note_idnote_iddoc_tokenvc-node-id<vc-transcribe-tab>docs +fetch --api-version v2note_idlark-cli note +<verb> [flags]| Shortcut | Description |
|---|---|
| Get note detail (display type, document tokens) by note_id |
| Fetch the unified note transcript and save it to a file |
+detail+transcript| Method | Required scope |
|---|---|
| |
| |