How to use the Daily Standup Report agent skill (Lark/Feishu)

What is an agent skill and what does this one do?

An agent skill is a folder containing a SKILL.md file with instructions that an AI agent reads when a task matches the skill's description. This skill is distributed as a single SKILL.md file.

When triggered, the skill reads your calendar events with the lark-cli command-line tool, reads your unfinished tasks, and then summarises both for the day you asked about. The summary converts event times to your local timezone (the source notes this is usually Asia/Shanghai), lists meetings with your RSVP status, flags meetings whose times overlap, and shows pending to-dos sorted by due date with overdue items marked.

• Meetings are sorted by start time and shown with time, title, organiser and RSVP status.
• RSVP values are shown as: accepted, declined, awaiting confirmation (needs_action) or tentative.
• Declined meetings are labelled but do not count toward busy time or conflict checks.
• To-dos are sorted by due date, overdue ones are labelled 'overdue', and tasks without a due date appear last.
• The skill reads only; it does not create or change events or tasks.

Before you install: requirements

The skill needs the lark-cli command-line tool installed, a Lark/Feishu user account, and an authorisation step that grants calendar and task access. The skill only supports user identity, so it works with your own login rather than a bot or app identity.

The permissions it needs are read-only: calendar:calendar.event:read for calendar events and task:task:read for tasks.

• lark-cli installed (the skill checks for it as a required binary).
• A Lark/Feishu user account.
• Authorisation via lark-cli with the calendar and task domains.
• Read scopes: calendar:calendar.event:read and task:task:read.

Install the skill from a ZIP or the Claude apps

Download the ZIP for this skill from this page and unzip it. For Claude Code, place the unzipped skill folder in ~/.claude/skills/ to make it available to all your projects, or in a project's .claude/skills/ folder to limit it to that project.

If you use the Claude apps instead, open Settings, go to Capabilities, then Skills, and upload the skill there.

• Personal install: ~/.claude/skills/ (available everywhere).
• Project install: .claude/skills/ inside the project folder.
• Claude apps: Settings → Capabilities → Skills → upload.

Authorise lark-cli to read your calendar and tasks

Before the first run, sign in through lark-cli and request the calendar and task domains. The skill's instructions say this authorisation step must be completed before it executes its commands.

The skill's permission table maps each command to the scope it needs, so you can check that a grant covers both reads.

How to trigger the skill with natural requests

You do not need special syntax. Ask for a summary in plain language, and the agent should match the request to this skill. The skill's description covers requests about today, tomorrow and the week ahead, and the source lists these as typical triggers.

Requests that match the skill include questions about today's schedule and to-dos, tomorrow's meetings, a morning briefing, a stand-up or daily report summary, and what is planned this week.

• What's on today, meetings and to-dos?
• What meetings do I have tomorrow?
• Give me my morning briefing summary.
• Prepare my standup report.
• What's on my plate this week?

Examples of what you will get back

The skill returns a Markdown summary with a heading for the date, a schedule table, a to-do checklist and a short wrap-up. The wrap-up gives the count of meetings and to-dos, any conflict warnings, and free time gaps inferred from the calendar.

Under the hood, the skill fetches calendar events with calendar +agenda and unfinished tasks with task +get-my-tasks --complete=false. For a specific date it needs ISO 8601 dates such as 2026-03-26T00:00:00+08:00, so the agent calculates the target date itself rather than accepting words like 'tomorrow' in the command.

• Schedule table columns: time, event, organiser, status.
• To-do list items show the task and its due date.
• Summary lines: meeting count, to-do count, conflicts, free slots.

Safety, privacy and network notes

This skill runs scripts and uses the network, because lark-cli sends requests to Lark/Feishu under your login. It reads your personal calendar and tasks, so the summary may contain private details. Think before sharing the output in a group chat or document.

The skill is read-only by design. Be aware that the summary is generated from your data and is only as current as the last fetch.

• Runs scripts: yes. Uses network: yes.
• Reads personal calendar and task data under your own login.
• Do not share summaries with others without checking for sensitive meeting titles or task notes.
• Write access is not part of this skill.

Tips for better briefings

Ask for a specific day or range, such as tomorrow or this week, so the agent sets the date window correctly. Without a date filter, the task query can return many items; the skill recommends filtering by due date and includes a note about paging for lists longer than 20 items.

Older tasks without due dates are not all listed. The skill's rules show only tasks created within the last 30 days and fold older ones into a count.

• Name the date in your request for the most accurate window.
• Expect at most 20 tasks per default query; the skill mentions a page-all option for longer lists.
• Tasks without due dates are shown last, and old ones may be collapsed into a count.