Guide · Agent skill
How to use the Lark VC compatibility skill (lark-vc)
Updated · written with AI from the project's own documentation and checked against our catalogue data
The lark-vc skill is a compatibility entry for an older skill name. It does not run meetings itself. When it is explicitly triggered, it tells the agent to read the lark-meeting skill's instructions and follow them. This guide is for people who have never installed an agent skill and for teams whose configurations still reference lark-vc. By the end you will know what the skill does, how to install it, how to trigger it, and what it depends on.
Lark VC Compatibility Redirectlarksuite/cli · MIT Download the skill Quick start
- 1Install lark-cli. Make sure the lark-cli command-line tool is installed and available as a binary, because the skill requires it.
- 2Get the lark-meeting skill. Obtain the lark-meeting skill, since lark-vc hands all work to it and does not include its own instructions.
- 3Download the lark-vc ZIP. Download the lark-vc package from this page.
- 4Install the skill. Unzip it into ~/.claude/skills/ or a project's .claude/skills/ folder, or upload the ZIP under Settings → Capabilities → Skills in the Claude apps.
- 5Trigger it with an explicit name. Ask the agent to use the lark-vc skill by name so it reads lark-meeting's instructions and follows them.
What the lark-vc skill does
An agent skill is a folder with a SKILL.md file that gives an AI agent extra instructions for a specific job. The lark-vc skill has one purpose: keep older setups working after the skill name changed. Its own file says it is used only for compatibility with the old name and does not handle business tasks directly.
The skill's file contains a single required action. The agent must fully read the lark-meeting skill's SKILL.md and follow the routing and action guidance in it. The real capability therefore lives in lark-meeting, not in lark-vc.
Install the lark-vc skill
Download the lark-vc ZIP from this page. You can install it in either of two ways.
For Claude Code, unzip the package into your user skills folder at ~/.claude/skills/, or into a project's .claude/skills/ folder if you want it limited to one project.
For the Claude apps, open Settings, go to Capabilities, then Skills, and upload the ZIP there.
- Option A: unzip into ~/.claude/skills/ for all your projects
- Option B: unzip into a project's .claude/skills/ folder for that project only
- Option C: upload the ZIP under Settings → Capabilities → Skills in the Claude apps
Check the prerequisites: lark-cli and lark-meeting
The skill declares two dependencies. The first is the lark-cli command-line tool, which the skill lists as a required binary. The skill assumes lark-cli is installed so the agent can talk to Lark (Feishu). Without it, the skill will not work.
The second is the lark-meeting skill. The lark-vc skill refers to it directly, so it must be available alongside lark-vc. The reviewed files for lark-vc do not include lark-meeting, so you need to obtain it separately.
- lark-cli command-line tool installed and available as a binary
- lark-meeting skill available, since lark-vc hands all work to it
Trigger the skill with a request
The lark-vc skill is meant to run only when the lark-vc name is explicitly specified, either by the user or by an upstream configuration. A general meeting request without that name is not what this skill is for, so write your request so it names lark-vc directly.
When triggered, the agent reads lark-meeting's instructions and handles the request under those rules. You do not need to phrase the request differently for lark-meeting.
- Name the skill explicitly, for example: Use the lark-vc skill to schedule a Lark meeting for Thursday at 10:00.
- Keep older automations or configuration files that reference lark-vc, since they will be routed to lark-meeting.
Examples of how it is used
Because lark-vc only forwards work, any example is really a lark-meeting task. The following shows the kind of request that uses the lark-vc name. The exact results depend on what lark-meeting and lark-cli support.
Use lark-vc to look up my upcoming Lark meetings and summarize the agenda for each one.
- An older scheduled workflow that still calls lark-vc keeps running without changes.
- A team migrating from lark-vc to lark-meeting tests a request with the old name to confirm routing works.
Safety notes: scripts and network
The lark-vc skill declares that it runs no scripts and uses no network on its own. Its only instruction is to read another file and follow it.
The work itself is done through lark-cli and lark-meeting, which are outside this file. Review those tools before you rely on them with real meeting data, because lark-vc's safety depends on what they do.
- lark-vc runs no scripts according to its declared metadata
- lark-vc does not use the network according to its declared metadata
- lark-cli and lark-meeting are not covered by this review
Tips for migrating from lark-vc to lark-meeting
Keep lark-vc installed while you update configurations. It acts as a safety net so existing references do not break.
When you are ready, point new configurations directly at lark-meeting. That removes the extra hop through the compatibility entry.
- Search your configuration files and automations for the name lark-vc before changing them.
- Confirm lark-cli and lark-meeting both work before you remove lark-vc.
- Test one workflow end to end before migrating the rest.
What people use it for
- Keeping an older automation that references lark-vc running after the rename
- Migrating a team from lark-vc to lark-meeting without breaking existing setups
- Testing that a request using the old lark-vc name still reaches lark-meeting
Frequently asked questions
What is the lark-vc skill used for?
It is a compatibility entry for an older skill name. It does not do meeting work itself. When explicitly triggered, it tells the agent to read the lark-meeting skill and follow its instructions.
Do I need lark-cli to use lark-vc?
Yes. The skill declares lark-cli as a required binary and assumes it is installed so the agent can talk to Lark (Feishu). Without lark-cli, the skill will not work.
How do I install the lark-vc skill?
Download the ZIP from this page and unzip it into ~/.claude/skills/ or a project's .claude/skills/ folder. You can also upload the ZIP in the Claude apps under Settings → Capabilities → Skills.
Is lark-vc free and what is its licence?
The item is listed under the MIT licence. This page does not state pricing for the skill, so check the source repository for any cost information.
Is lark-vc a standalone meeting tool?
No. The file contains no instructions of its own for meetings. The actual work depends on the lark-meeting skill, which is not included in the reviewed files.
Should I use lark-vc or lark-meeting for new work?
Use lark-meeting for new work. Keep lark-vc only for older configurations that still reference its name, since it exists to keep those working.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Use lark-vc if you have older configurations or automations that still reference the lark-vc name and you want them to keep working. Pick lark-meeting directly for new setups, or anything that needs a standalone meeting tool, because lark-vc contains no meeting instructions of its own.
Download the skill