Documents & Data · IN-DEPTH PROFILE

Lark VC Skill

Lark VC is now a compatibility entry that delegates to the unified Lark Meeting workflow.

View listed source ↗Installation guide ↓
Best for

Teams reviewing Feishu meetings and their artifacts

What you get

Find the right meeting + Resolve meeting artifacts

Main limitation

The legacy entry no longer contains the operating guidance; it requires lark-meeting and its scenario references.

First risk

Meeting privacy and visible messages. Transcripts, participants, and messages can contain sensitive information, while message sends are visible to attendees. Preserve identity, minimize reads, and confirm writes.

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 VC is now a compatibility entry that delegates to the unified Lark Meeting workflow. That workflow discovers active or ended meetings, reads live events, sends in-meeting messages, retrieves participant snapshots, and resolves Note, Minutes, transcript, recording, and document artifacts while preserving source identity.

This is aimed at Teams reviewing Feishu meetings and their artifacts. Compare the examples below with your task, then review the limitations, permissions, and risks before installing.

What you get
  • Find the right meetingRoute active, ended, scheduled, and title-only meeting requests to the correct search surface.
  • Resolve meeting artifactsFollow meeting IDs to Note or Minutes tokens and choose transcripts, summaries, todos, or links by intent.
  • Inspect live stateRead paginated events or send a requested text or reaction without implying that the bot joined.
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: #34 · 727.4K 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-vc --agent claude-code
Personal install
npx skills add larksuite/cli --skill lark-vc --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-vc/
Personal path~/.claude/skills/lark-vc/
Official agent docs

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

View path evidence ↗

TYPICAL WORKFLOW

A practical workflow

01

Find the right meeting

Route active, ended, scheduled, and title-only meeting requests to the correct search surface.

02

Resolve meeting artifacts

Follow meeting IDs to Note or Minutes tokens and choose transcripts, summaries, todos, or links by intent.

03

Inspect live state

Read paginated events or send a requested text or reaction without implying that the bot joined.

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 legacy entry no longer contains the operating guidance; it requires lark-meeting and its scenario references.
  2. Note, Minutes, and user-bound meeting notes remain independent artifact chains with different permissions and defaults.

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

→

Teams reviewing Feishu meetings and their artifacts

→

Agents routing live and historical meeting questions

BEFORE YOU USE IT

Risks to review before use

High

Meeting privacy and visible messages

Transcripts, participants, and messages can contain sensitive information, while message sends are visible to attendees. Preserve identity, minimize reads, and confirm writes.

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 VC Skill FAQ

What is the Lark VC Skill?

Lark VC is now a compatibility entry that delegates to the unified Lark Meeting workflow. That workflow discovers active or ended meetings, reads live events, sends in-meeting messages, retrieves participant snapshots, and resolves Note, Minutes, transcript, recording, and document artifacts while preserving source identity.

How do I install the Lark VC 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 VC Skill safe to use?

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

INSIDE THE PACKAGE

Indexed files

SKILL.mdUpstream Skill instructionsSource-linked

TAGS

feishuvideo-conferencingmeeting-artifacts

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.