lark-vc-agent

Routes legacy lark-vc-agent requests to the lark-meeting skill for Lark meeting operations.

8|2|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/luojiaaoo/xpeech --skill lark-vc-agent-luojiaaoo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lark-vc-agent
Source: https://github.com/luojiaaoo/xpeech/tree/main/xpeech/agent/skills/buildin/lark-skills/lark-vc-agent
Command: npx skills add https://github.com/luojiaaoo/xpeech --skill lark-vc-agent-luojiaaoo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Older configurations and user requests may still reference the legacy lark-vc-agent name for Lark video conferencing tasks. This Skill preserves backward compatibility by redirecting all such requests to the current lark-meeting skill, so existing setups keep working without reconfiguration. ## Core Features & Use Cases - Legacy Name Compatibility: Accepts requests explicitly targeting lark-vc-agent and forwards them to lark-meeting for actual handling. - Unified Routing: Ensures all Lark meeting and video conferencing operations follow the routing and action guidelines defined in lark-meeting. - Use Case: A user with an older configuration that specifies lark-vc-agent asks to schedule a Lark video meeting; the request is transparently handled by the lark-meeting skill without any changes to the user's setup. ## Quick Start Ask the agent to schedule or manage a Lark video meeting, and requests referencing lark-vc-agent will be handled through the lark-meeting skill automatically.

Frequently Asked Questions about lark-vc-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I schedule a Lark video meeting with lark-vc-agent?▼

Requests sent to lark-vc-agent are delegated to the lark-meeting skill, which handles all meeting scheduling and management. Simply ask to schedule a Lark meeting and the routing happens automatically.

What is the difference between lark-vc-agent and lark-meeting?▼

lark-vc-agent is a compatibility entry that does not process business logic itself. It exists only to support the legacy name and forwards all requests to lark-meeting, which contains the actual routing and action guidelines.

Does lark-vc-agent work without lark-meeting installed?▼

No. lark-vc-agent declares lark-meeting as a required skill and lark-cli as a required binary. Without lark-meeting present, there is no implementation to handle the delegated requests.

When should I use lark-vc-agent instead of lark-meeting?▼

Only use lark-vc-agent when a user or upstream configuration explicitly specifies that legacy name. For all new configurations, reference lark-meeting directly since it contains the actual meeting functionality.

Why are my lark-vc-agent requests handled by a different skill?▼

This is by design. lark-vc-agent is a compatibility shim that reads lark-meeting's SKILL.md and follows its routing rules, so all meeting operations are executed by lark-meeting.