Lark Calendar & Tasks

**Judgement:** A solid, focused automation skill for teams using Lark (Feishu), providing comprehensive calendar and task CRUD operations with attendee/assignee management. Best suited for organizations already invested in Lark who want to script or integrate scheduling and task workflows. **What it does well** - Covers full lifecycle for calendar events (create/update/delete/list) and tasks, including attendee and member management. - Supports both CLI-style scripts and programmatic Node.js usage, making it easy to embed in other automations. - Handles timezones via IANA identifiers and enforces a consistent time format (`YYYY-MM-DD HH:MM:SS`). - Includes an employee directory for automatic name → `user_id` mapping, with multiple aliases per person. **Key risks / limitations** - **Environment & permissions:** Requires correct Lark app configuration and scopes (e.g., `task:task:write`, `contact:contact:readonly`). Misconfiguration will cause failures, especially for task features and dynamic employee lookup. - **Static fallback directory:** Without `contact:contact:readonly`, the skill uses a static employee list. If this list is not maintained, events/tasks may be assigned to wrong or missing users. - **Business rule side-effect:** The rule "Boyang is always added as attendee to every calendar event" may be undesirable or a privacy/oversight concern in some organizations and needs to be clearly understood before use. - **Destructive operations:** Update/delete for events and tasks can cause data loss or confusion if IDs are wrong or used in bulk scripts; implementing your own safeguards (logging, dry-run) is advisable. **Recommended scenarios** - Teams heavily using Lark/Feishu who want scripted scheduling (e.g., auto-create standups, review meetings, or project milestones). - Development or DevOps workflows that auto-create tasks from CI/CD events, code reviews, or incident management systems. - Internal admin/ops tools that need to generate or synchronize calendars and task lists across a known set of employees. **Less ideal for** - Organizations not standardized on Lark/Feishu. - Non-technical users without support, since setup requires environment variable and app permission configuration. - Use cases needing fine-grained access control or multi-tenant separation beyond what Lark’s own app permissions provide.