Documents & Data · IN-DEPTH PROFILE

Lark VC Agent Skill

Lark VC Agent is now a compatibility entry that delegates to the unified Lark Meeting workflow, where an authorized application bot can visibly join or leave a live Feishu meeting, read active-meeting events, and send requested messages or reactions.

View listed source ↗Installation guide ↓
Best for

Developers building live Feishu meeting assistants

What you get

Join a live meeting + Observe active events

Main limitation

It requires internal or gray-release access plus the documented bot scopes and configuration.

First risk

Visible bot presence and live-meeting privacy. Joining, messaging, reacting, and listening occur in a live meeting and can affect every attendee. Obtain authorization, identify the bot clearly, minimize captured data, and confirm externally visible actions.

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 Agent is now a compatibility entry that delegates to the unified Lark Meeting workflow, where an authorized application bot can visibly join or leave a live Feishu meeting, read active-meeting events, and send requested messages or reactions.

This is aimed at Developers building live Feishu meeting assistants. Compare the examples below with your task, then review the limitations, permissions, and risks before installing.

What you get
  • Join a live meetingJoin by the 9-digit meeting number when the tenant and application have the preview capability.
  • Observe active eventsDiscover active meetings and page through participant, speech, and other live event streams.
  • Interact and leaveSend a requested message or reaction, then leave using the long meeting ID while preserving identity continuity.
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: #47 · 671.9K 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 --agent claude-code
Personal install
npx skills add larksuite/cli --skill lark-vc-agent --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-agent/
Personal path~/.claude/skills/lark-vc-agent/
Official agent docs

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

View path evidence ↗

TYPICAL WORKFLOW

A practical workflow

01

Join a live meeting

Join by the 9-digit meeting number when the tenant and application have the preview capability.

02

Observe active events

Discover active meetings and page through participant, speech, and other live event streams.

03

Interact and leave

Send a requested message or reaction, then leave using the long meeting ID while preserving identity continuity.

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. It requires internal or gray-release access plus the documented bot scopes and configuration.
  2. The legacy entry contains no operating steps; lark-meeting and the live-meeting scene must be available.

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

→

Developers building live Feishu meeting assistants

→

Teams testing visible application-bot participation

BEFORE YOU USE IT

Risks to review before use

High

Visible bot presence and live-meeting privacy

Joining, messaging, reacting, and listening occur in a live meeting and can affect every attendee. Obtain authorization, identify the bot clearly, minimize captured data, and confirm externally visible actions.

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

What is the Lark VC Agent Skill?

Lark VC Agent is now a compatibility entry that delegates to the unified Lark Meeting workflow, where an authorized application bot can visibly join or leave a live Feishu meeting, read active-meeting events, and send requested messages or reactions.

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

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

INSIDE THE PACKAGE

Indexed files

SKILL.mdUpstream Skill instructionsSource-linked

TAGS

feishumeeting-botlive-events

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.