What this skill does
Lark Event works with technical events: notifications emitted when something happens, such as receiving a message or changing a resource. It explains discovering event types, inspecting their data and receiving them with time or quantity limits. These are not calendar events.
For technical teams, notifications can start processes that respond to changes. The AI employee can inspect an example and document its fields before an automation is built. A person defines the permitted response and its verification; receiving a notification alone does not authorise changing other systems.
When it can help
- Inspect an event's information.
- Prepare a bounded notification-reception test.
- Document the input to a Feishu automation.
A task to get started
Check what data our application's message-received event provides. Capture a limited sample, explain its fields and propose processing without sending automatic replies.
What you need
- Lark CLI and authorised subscriptions to the required events.
- A technical environment prepared to receive and handle notifications.
Limits and result review
- Event consumers need error handling and subscription cleanup.
- The skill does not create a permanent service or support direct GitHub import into Hub.
How to explore this skill
This skill is distributed through Feishu. Hub currently imports public GitHub repositories; consult the original source for its requirements and procedure.
View on skills.sh ↗A skill provides a procedure. Each employee's permissions, approvals and connections still determine available actions. Adding it does not automatically install software or execute the author's scripts.
Sources and documentation
An iabot editorial explanation based on original documentation. Authorship remains with open.feishu.cn. This guide is not a Hub compatibility test and does not distribute a translation of the author’s code.
Read the iabot manual →