Skills lark-note

📦

lark-note

Name: lark-note
Author: larksuite

v1.0.0 Content revision r2 Safe 📁 Filesystem access⚙️ External commands

Retrieve Lark Meeting Notes and Transcripts

Meeting records are difficult to retrieve when note types and document tokens vary. This skill uses an explicit note_id to find details and route transcript access correctly.

Supports: Claude Codex Code(CC)

🥉 77 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "lark-note" from https://skillstore.io/skills/larksuite-lark-note.md and its manifest at https://skillstore.io/api/skills/larksuite-lark-note/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/larksuite-lark-note.md Signed manifest GET /api/skills/larksuite-lark-note/manifest Signed lockfile GET /api/skills/larksuite-lark-note/lockfile

Test it

Using "lark-note". Find details for note_id nt_abc123.

Expected outcome:

Display type: unified. Main note document: docus_main. Retrieve the transcript through the unified transcript route.

Using "lark-note". Get the transcript for a normal note with verbatim document docus_verbatim.

Expected outcome:

The transcript is a separate document. Read docus_verbatim through the document workflow.

Security Audit

Safe

v5 • 7/23/2026 Open versioned report

All 62 static findings are false positives caused by Markdown links, inline code formatting, documented lark-cli commands, or Chinese-language entropy. The files contain no executable scripts, dynamic command construction, prompt injection, obfuscated payloads, or unauthorized data handling.

Files scanned

146

Lines analyzed

Review items

False positives ignored

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/larksuite-lark-note/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/larksuite-lark-note/security.svg)](https://skillstore.io/skills/larksuite-lark-note?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/larksuite-lark-note?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/larksuite-lark-note/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/larksuite-lark-note.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

larksuite. (2026). lark-note security audit report (audit version 5) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/larksuite-lark-note/audits/5

BibTeX citation

@techreport{larksuite-larksuite-lark-note-2026,
  author = {larksuite},
  title = {lark-note security audit report (audit version 5)},
  institution = {Skillstore},
  year = {2026},
  number = {5},
  url = {https://skillstore.io/skills/larksuite-lark-note/audits/5},
  note = {Author version 1.0.0}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "lark-note security audit report (audit version 5)"
version: "1.0.0"
type: report
authors:
  - name: "larksuite"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/larksuite-lark-note/audits/5"
identifiers:
  - type: other
    value: "skillstore:larksuite-lark-note:audit:5"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

100

Maintainability

Content

Community

Spec Compliance

What You Can Build

Inspect meeting note assets

Retrieve note type and document tokens before opening summaries, transcripts, or shared files.

Review exact discussion

Select the correct transcript route and retrieve speaker-level meeting records.

Build reliable note workflows

Resolve explicit identifiers and avoid incorrect routing between normal and unified notes.

Try These Prompts

Look up note details

Use note_id {note_id} to retrieve the display type and all available document tokens. Summarize the result.

Choose a transcript route

Inspect note_id {note_id}. Retrieve its transcript through the correct route for normal, unknown, or unified display types.

Follow a document reference

Use the explicit vc-node-id {vc_node_id} from fetched document markup. Retrieve the matching note details and explain the next route.

Audit transcript retrieval

For note_id {note_id}, explain the selected transcript route. Retrieve complete content and report the output location or failure without partial results.

Best Practices

Provide an exact note_id or an explicit vc-node-id from fetched document markup.
Retrieve note details before choosing a transcript route.
Use the authenticated user identity and verify access to sensitive meeting content.

Avoid

Do not infer note_id from a title, document token, text, or backlink.
Do not pass a minute token as a note identifier.
Do not identify unified notes from verbatim_doc_token presence alone.

Frequently Asked Questions

What identifier does this skill require?

It requires an explicit note_id or a verified vc-node-id from fetched document markup.

Can it find a note by title?

No. Use a Lark document search workflow first, then return with an explicit vc-node-id.

How does it choose the transcript route?

It checks note_display_type. Normal notes use a document token, while unified notes use the Note transcript workflow.

Where are unified transcripts saved?

They are saved under the local notes directory as Markdown, or as text when plain text format is selected.

Does it overwrite existing transcript files?

No. Existing files cause an error unless the user explicitly requests overwrite behavior.

What access does it need?

It needs lark-cli, an authenticated user identity, and permission to read the requested Lark meeting content.

Developer Details

Author

larksuite

License

MIT

Author version

v1.0.0

Skillstore revision

Repository

https://github.com/larksuite/cli/tree/main/skills/lark-note/

Ref

ebdfe608f5de2b66ff37ab4af12af8ac4f5e8006

Maintenance freshness

7/25/2026

Usage

12 downloads · 0 views

File structure

📁 references/

📄 lark-note-detail.md

📄 lark-note-transcript.md

📄 SKILL.md