How to use the Lark VC Agent (Compatibility Alias) agent skill

What is an agent skill, and what does this one do?

An agent skill is a folder containing a SKILL.md file with instructions that an AI agent reads when a request matches the skill's description. The lark-vc-agent skill is a shim: its only job is to tell the agent to read the lark-meeting skill file and follow the routing and instructions there.

The skill's description says it should be used only when the user or upstream configuration explicitly names lark-vc-agent. Related requests are then handled by the lark-meeting skill.

• It does not handle meeting business logic directly.
• It forwards the agent to ../lark-meeting/SKILL.md, which must be read in full.
• It exists for backward compatibility with configurations that still use the old name.

What you need before installing

The skill declares two requirements in its metadata: the lark-cli command-line tool and the lark-meeting skill. The lark-meeting skill is the file this alias forwards to, so without it the alias cannot deliver any result.

• lark-cli command-line tool (listed as a required binary).
• lark-meeting skill, present alongside this one.
• The package ships a single file, SKILL.md. It runs no scripts and uses no network access according to the listing.

Install the lark-vc-agent skill

Download the ZIP for this skill from the directory page and unzip it. Then place the resulting folder in one of the following locations, depending on how you run your agent.

For a personal setup, put it in ~/.claude/skills/. For a single project, put it in that project's .claude/skills/ folder. Alternatively, in the Claude apps, open Settings, go to Capabilities, and upload the skill as a Skills entry.

• Personal: ~/.claude/skills/lark-vc-agent/
• Project: .claude/skills/lark-vc-agent/ inside your project folder
• Claude apps: Settings → Capabilities → Skills, then upload the ZIP
• Install lark-meeting the same way, because this alias depends on it.

How to trigger the skill with natural requests

The skill is meant to be triggered only when the request or your configuration explicitly names lark-vc-agent. Ordinary meeting requests should go to lark-meeting directly. If you are maintaining an older config, reference the name lark-vc-agent so the agent loads this shim and then follows lark-meeting.

Because the alias contains no meeting logic, the wording of your request matters less than whether the lark-meeting skill is installed and readable by the agent.

• Name the skill in your configuration or request, for example: use the lark-vc-agent skill to handle this meeting task.
• If a request does not name lark-vc-agent, the alias will not be selected, so use lark-meeting instead.
• Check that lark-meeting appears in your skills list before testing.

Examples of what happens

When an older workflow triggers lark-vc-agent, the agent reads SKILL.md, sees the instruction to read the lark-meeting file in full, and then follows that file's routing. The result therefore depends entirely on lark-meeting and on lark-cli being available.

The source does not list specific meeting commands for this alias, so refer to the lark-meeting skill for what tasks it supports.

• Old config references lark-vc-agent → alias loads → lark-meeting instructions are followed.
• Missing lark-meeting or lark-cli → the alias fails to deliver a result.

Safety notes: scripts and network

According to the listing, this skill runs no scripts and uses no network access. Its only file is SKILL.md, which contains instructions and a relative link to the lark-meeting skill. Any actual actions, including any network use, would come from the lark-cli tool and the lark-meeting skill, so review those separately before granting access.

• Runs scripts: no.
• Uses network: no (for this alias itself).
• Review lark-meeting and lark-cli before relying on them for meeting data.

Tips for a clean migration

If you are moving away from lark-vc-agent, the safest path is to update your configurations to reference lark-meeting directly and keep this alias only as a temporary bridge. Since the alias adds no capability, it is simply an extra hop.

• Install lark-meeting first and confirm it loads.
• Update configs to name lark-meeting, then remove lark-vc-agent when no longer needed.
• Keep this alias only while older configurations still depend on it.