What problem does it solve?
Older configurations and user habits may still reference the legacy lark-note skill name, which no longer handles business logic directly. This Skill preserves backward compatibility by transparently forwarding all such requests to the lark-meeting skill, so existing setups keep working without reconfiguration.
Core Features & Use Cases
- Legacy Name Compatibility: Accepts invocations under the old lark-note name without breaking existing workflows.
- Unified Request Routing: Delegates all note and meeting-related requests to the lark-meeting skill's routing and action guidelines.
- Use Case: A user's AI agent configuration still specifies lark-note for meeting notes. When triggered, this Skill loads the lark-meeting instructions and processes the request through the maintained meeting workflow.
Quick Start
Ask the agent to handle your Lark meeting notes request, and it will route the task through the lark-meeting skill automatically.