What problem does it solve? Feishu/Lark covers dozens of product domains (IM, calendar, docs, sheets, Base, mail, approval, OKR, meetings, wiki, drive), and an agent cannot know which CLI commands apply to a given request. This Skill acts as a central router that maps any Feishu/Lark user need to the correct sub-skill's SKILL.md so the right commands are executed. ## Core Features & Use Cases - Capability Routing: A directory of 20+ sub-skills (lark-im, lark-calendar, lark-doc, lark-sheets, lark-base, lark-drive, lark-mail, lark-meeting, lark-approval, lark-task, lark-wiki, lark-okr, and more) with a quick-lookup table mapping high-frequency requests to the right sub-skill. - Shared Conventions: Delegates authentication, identity switching, permission handling, and high-risk operation rules to lark-shared, and sends login/token/scope needs to the separate lark-oauth skill. - Workflow Orchestration: Includes composite workflows such as meeting-minutes weekly summaries and daily schedule-plus-todo standup reports. - Use Case: A user asks "check my schedule this afternoon and send the summary to the team group" — the router directs the agent to read lark-calendar/SKILL.md for the agenda and lark-im/SKILL.md for sending the message. ## Quick Start Ask the agent to handle any Feishu/Lark task, such as checking today's meetings or sending a message to a colleague, and it will route to the matching sub-skill.
