How to use the Lark Calendar Manager agent skill (lark-calendar)

What is an agent skill and what does lark-calendar let the agent do?

An agent skill is a folder containing a SKILL.md file and supporting reference documents. When it is installed, the agent reads these instructions when a request matches the skill's description, so it knows which commands to run and in what order.

Once lark-calendar is installed and lark-cli is set up, the agent can: view today's or upcoming schedule (+agenda), search events by keyword, time range or attendee (+search-event), get details for one event (+get), create events and invite attendees (+create), update fields or add and remove attendees and rooms (+update), delete events (+delete), check busy times (+freebusy), suggest meeting slots (+suggestion), find and book meeting rooms (+room-find), reply to invitations (+rsvp), and list attendees and rooms (+list-attendees).

Install the lark-calendar skill

Download the ZIP for this skill from this page and unzip it. For a personal install, place the folder in ~/.claude/skills/. For a single project, place it in that project's .claude/skills/ folder.

Alternatively, in the Claude apps, open Settings → Capabilities → Skills and upload the ZIP there.

The skill also requires the lark-cli command-line tool and a Lark/Feishu account authorization. The SKILL.md file points to ../lark-shared/SKILL.md for authentication and permission handling, so read that file before first use.

• Personal: ~/.claude/skills/
• Project: .claude/skills/ inside your project
• Claude apps: Settings → Capabilities → Skills

Check the requirements before you start

The skill declares that it needs the lark-cli binary, Lark/Feishu account authorization using either a user or bot identity, and network access to Lark/Feishu APIs. It runs scripts and uses the network. Calendar permissions are handled through the shared authentication guide referenced by the skill.

Choose the identity based on whose calendar you are working with. For your own schedule, the skill uses --as user, which is the default for most cases. For events that a bot created or owns, it uses --as bot.

Ask for calendar tasks in natural language

You do not need to type commands yourself. Describe what you want, and the agent maps it to the right operation. The skill is triggered by requests such as checking your schedule, creating or changing a meeting, or looking up or booking a meeting room.

The skill translates casual wording like 'book a calendar' or 'check today's calendar' into operations on events, not on the calendar container itself. For time-sensitive requests, give a concrete date and time zone where you can, because the skill needs explicit times to book rooms.

• Show me my agenda for tomorrow.
• Search my events this week for 'weekly sync'.
• Find a 30-minute slot next week when Ann and Ben are both free.
• Create a 'Product review' meeting on 12 March from 14:00 to 15:00 (+08:00) with ou_aaa and ou_bbb.
• Book a meeting room for Thursday 14:00 to 15:00.
• Who is attending event <event_id>, and which rooms are booked?

Understand the commands behind the requests

Creating an event needs a start and end time with a timezone offset, because times without an offset are read using the machine's timezone. Descriptions use Markdown. Search results include only basic fields, so use +get for full details.

For a single-slot room search, the skill requires a concrete time block. Vague ranges like 'this afternoon' should first go through +suggestion. The +freebusy command reports which intervals are free but does not judge whether a slot is suitable for a meeting; for that, the skill uses +suggestion.

• --start and --end: ISO 8601 with offset, for example 2026-03-12T14:00+08:00
• --attendee-ids: comma-separated IDs, where ou_ is a user, oc_ is a group chat and omm_ is a meeting room
• Multiple values in --attendee-ids are OR matches within the same type

Handle recurring events and video meeting records carefully

For recurring events, the skill asks you to confirm the scope before changing anything: this occurrence only, all occurrences, or this and following ones. It does not default to a single occurrence. Updating or deleting all occurrences also has to handle exceptions, which are separate events created when one instance was edited on its own.

Past video meeting records are not calendar events. Queries about last week's meetings or meetings happening now are routed through the meeting relationship rules, and past video-meeting records belong to the lark-meeting skill. Tasks belong to lark-task.

• Delete and transfer operations are irreversible or affect other people; +transfer requires --yes
• Use --apply-to for recurring events and their exceptions
• Share links: send the calendar share link from calendar events share_info, not a constructed applink

Safety notes: scripts and network access

This skill runs scripts and uses the network to call Lark/Feishu APIs. It acts on your real calendar, so every write operation (create, update, delete, RSVP, transfer, room booking) changes live data that other people can see.

After a write command succeeds, the skill reports the result from the command output and does not re-query the calendar unless you ask it to check or the output is insufficient.

• Review the summary, times, attendees and room before confirming a write.
• Confirm the scope of any recurring-event change.
• Treat deletes and owner transfers as final.