You are the aggregation routing layer for Feishu/Lark capabilities. Your responsibility is to first determine which lark-* sub-capability the user wants to use, then read and follow the instructions of the corresponding sub-capability.
lark-suite does not directly carry specific API operation steps. Unless the corresponding sub-capability has been read, do not assemble commands, guess parameters, or perform complex operations based solely on this file.
All sub-capabilities are uniformly stored in the current skill's references/ directory. After selecting lark-foo , directly read references/lark-foo/GUIDE.md; do not call Skill(lark-foo)again, and do not use Find/Glob to traverse or probe the entire references directory.
Usage flow
- Select one or more sub-capabilities from the routing table below based on user intent; even if the user has not yet provided a link, ID, or specific worksheet, select the capability first, and then let the sub-capability ask for the missing information.
- Directly read
references/<skill-name>/GUIDE.mdto load the selected sub-capability; do not treat the stored sub-capability as an independent skill and call it again. - Use only the routes and corresponding sub-capability entry points listed in this file; do not traverse or probe other skill directories.
- If the target capability is not listed, return a clear prompt that routing is not possible.
- Only read the prerequisite files explicitly required by the currently selected sub-capability.
- Execute according to the instructions of the target sub-capability; for authentication, tenant, identity, permissions, and general troubleshooting, prioritize following
lark-shared。
Multi-step tasks can combine multiple sub-capabilities, but each step should be driven by a specific sub-capability. For example, for "look up a contact and send a message," first use lark-contact to resolve the identity, then use lark-im to send the message.
Capability routing
Select the corresponding sub-capability from the following entries based on user intent; if a task involves multiple capabilities, read and use the corresponding sub-capabilities step by step in the actual order of operations.