What problem does it solve? Older configurations and user requests may still reference the legacy lark-minutes skill name, which no longer handles business logic directly. This compatibility entry ensures those requests are not lost and are instead forwarded to the lark-meeting skill that owns the actual meeting and minutes functionality. ## Core Features & Use Cases - Backward Compatibility: Accepts requests addressed to the legacy lark-minutes name without breaking existing workflows. - Unified Routing: Delegates all meeting and minutes related tasks to the lark-meeting skill, keeping behavior consistent. - Use Case: A user with an old configuration asks the agent to process Lark meeting minutes via lark-minutes; the agent reads this entry, loads the lark-meeting skill instructions, and completes the task through the maintained implementation. ## Quick Start Ask the agent to handle your Lark meeting minutes request and it will route the task through the lark-meeting skill automatically.