Documents & Data · IN-DEPTH PROFILE

Lark Note Skill

Lark Note is now a compatibility entry rather than a standalone meeting-note workflow.

View listed source ↗Installation guide ↓
Best for

Users with a legacy lark-note workflow or installed Skill

What you get

Preserve an older Skill name + Hand off to meeting guidance

Main limitation

The entry contains no direct operating steps and requires the lark-cli binary plus the lark-meeting companion Skill.

First risk

Sensitive meeting content and account access. The delegated workflow may access private meeting artifacts. Confirm the user identity and permissions, limit retrieval to the requested meeting, and review transcript or summary content before sharing.

EVIDENCE FRESHNESS

Three checks, kept separate

A recent source check is not a runtime test or security audit.

Upstream sourceChecked 2026-09-23

Pinned revision · a079fd7a

Open pinned commit ↗
SkillSignal profileSource-grounded

Updated 2026-08-24

Runtime & securityNot independently verified

Source review does not certify behavior or safety.

IN PLAIN ENGLISH

What it does—and when it fits

Lark Note is now a compatibility entry rather than a standalone meeting-note workflow. When explicitly selected, it delegates to the unified lark-meeting Skill, which owns the current routing and action guidance.

This is aimed at Users with a legacy lark-note workflow or installed Skill. Compare the examples below with your task, then review the limitations, permissions, and risks before installing.

What you get
  • Preserve an older Skill nameRecognize requests that explicitly refer to the legacy lark-note entry.
  • Hand off to meeting guidanceLoad lark-meeting instead of assuming the legacy entry has its own procedure.
  • Keep routing explicitUse the correct meeting or document workflow for the requested artifact.
What makes it different
  • This profile is manually organized around the current upstream SKILL.md workflow.
  • The capability boundary remains explicitly tied to open.feishu.cn.
  • Core uses, limitations, and risks are separated for pre-install review.
Community signalskills.sh All-time: #86 · 511.8K installs

No verified review text is in the current dataset. Use the linked source for the latest discussion.

Read the source note ↗

INSTALL BY AGENT

Choose your Agent

Paths come from official Agent docs or the universal installer behind skills.sh. Compatibility still follows this Skill's record.

Native

This Skill's current record explicitly names this Agent. Still inspect scripts, permissions, and external dependencies first.

Project install (recommended)
npx skills add larksuite/cli --skill lark-note --agent claude-code
Personal install
npx skills add larksuite/cli --skill lark-note --agent claude-code -g

Project install stays with this repository for team sharing. Personal install adds -g and works across repositories.

This command adds the Skill instructions only. Install lark-cli and sign in to Feishu separately before use. Official Lark CLI setup ↗

View install paths
Project path.claude/skills/lark-note/
Personal path~/.claude/skills/lark-note/
Official agent docs

Claude Code discovers custom Skill folders automatically at project or personal scope.

View path evidence ↗

TYPICAL WORKFLOW

A practical workflow

01

Preserve an older Skill name

Recognize requests that explicitly refer to the legacy lark-note entry.

02

Hand off to meeting guidance

Load lark-meeting instead of assuming the legacy entry has its own procedure.

03

Keep routing explicit

Use the correct meeting or document workflow for the requested artifact.

THE TRADEOFFS

Advantages and tradeoffs

Notable strengths

  1. This profile is manually organized around the current upstream SKILL.md workflow.
  2. The capability boundary remains explicitly tied to open.feishu.cn.
  3. Core uses, limitations, and risks are separated for pre-install review.

Limitations

  1. The entry contains no direct operating steps and requires the lark-cli binary plus the lark-meeting companion Skill.
  2. Meeting notes and transcripts remain subject to tenant identity, permission, artifact type, and the delegated Skill's rules.

COMPARE THE TRADEOFF

Consider these close alternatives

These are deterministic nearby candidates, not paid placements or a universal ranking. Open the full profile before choosing.

01

Same job family · native to Codex + Claude Code

create-llms

Create an llms.txt index from repository documentation.
Tradeoff to check
Detailed package files are not fully catalogued.
First risk
Review before install · Medium
Source state
Pinned · 1f564408
Open create-llms profile ↗
02

Same job family · native to Codex + Claude Code

csharp-docs

Write useful XML documentation for C# APIs.
Tradeoff to check
Detailed package files are not fully catalogued.
First risk
Review before install · Medium
Source state
Pinned · 1f564408
Open csharp-docs profile ↗
03

Same job family · native to Codex + Claude Code

java-docs

Write consistent Javadoc for Java types and APIs.
Tradeoff to check
Detailed package files are not fully catalogued.
First risk
Review before install · Medium
Source state
Pinned · 1f564408
Open java-docs profile ↗
Compare more in the directory →

BEST FIT

Who it is for

→

Users with a legacy lark-note workflow or installed Skill

→

Teams migrating to the unified Lark meeting workflow

BEFORE YOU USE IT

Risks to review before use

High

Sensitive meeting content and account access

The delegated workflow may access private meeting artifacts. Confirm the user identity and permissions, limit retrieval to the requested meeting, and review transcript or summary content before sharing.

High

External data and identity boundary

Requests access Feishu tenant resources. Use the correct identity, least-privilege scopes, and keep sensitive content out of logs.

SECURITY

What the permission profile means

  • Declared access remains governed by the current upstream SKILL.md and runtime requests.
  • Treat Feishu documents, messages, people, and business records as permission-controlled data.
  • SkillSignal has not independently executed or security-audited this package; external skills.sh labels are not SkillSignal certification.

Not a security certification. External ratings are attributed references. SkillSignal has not independently executed or security-reviewed this Skill.

COMMON QUESTIONS

Lark Note Skill FAQ

What is the Lark Note Skill?

Lark Note is now a compatibility entry rather than a standalone meeting-note workflow. When explicitly selected, it delegates to the unified lark-meeting Skill, which owns the current routing and action guidance.

How do I install the Lark Note Skill?

Open and review the listed source, choose the project or personal path for your Agent, then verify the first run in a controlled project. Open the listed source and read the current SKILL.md plus only the references required for this task.

Is the Lark Note Skill safe to use?

SkillSignal checked the source on 2026-09-23, but that is not a runtime test or security certification. Review the “Sensitive meeting content and account access” risk first and begin with the least access required.

INSIDE THE PACKAGE

Indexed files

SKILL.mdUpstream Skill instructionsSource-linked

TAGS

larkmeeting-notescompatibility

Manually expanded from the current upstream SKILL.md and linked source at open.feishu.cn, checked 2026-08-24. This is an original summary, not an execution result or security certification.