lark-workflow-standup-report Skill for Claude: Daily Lark Agenda and To-Dos
Has Claude combine your Lark or Feishu calendar and open tasks for a day or week into one short digest.
- Installs
- 470.5K
- on skills.sh
- Stars
- 17.9K
- on GitHub
- Updated
- Oct 2026
- last repo commit
lark-workflow-standup-report is a read-only recipe. It pulls events with calendar +agenda and your unfinished tasks with task +get-my-tasks --complete=false, then Claude merges them into one summary. The digest has a time-ordered event table, a to-do list, a meeting and task count, clash warnings and free slots. It loads on prompts like "what is on today" or "standup report".
It works as your user only. Sign in with lark-cli auth login --domain calendar,task, which grants the two scopes it needs: calendar:calendar.event:read and task:task:read. It reads the lark-calendar and lark-task skills for command details, so use the full set from the install box. Dates must be given in ISO 8601 form, and Claude works out "tomorrow" itself.
Good for
- People who start the day by checking calendar and to-dos in Lark
- Team members preparing a standup update
- Anyone who wants clashing meetings flagged before they happen
Install lark-workflow-standup-report
Claude Code
- 1
Copy this prompt.
Install the lark-workflow-standup-report skill in Claude Code. Run this command: npx @larksuite/cli@latest install Then check that it loaded and tell me how to use it.
- 2
Paste it into Claude Code. It shows the change and asks before running it.
Requires Node.js.
This skill only gives Claude instructions for the lark-cli command line, so install the CLI first, then the skills, then sign in. The skills command adds the whole larksuite/cli set, which includes lark-shared, the skill this one reads first for sign-in and permissions. The digest recipe reads lark-calendar and lark-task, both part of the same set.
From the project README. Source.
What's in the skill
When it loads
日程待办摘要:编排 calendar +agenda 和 task +get-my-tasks,生成指定日期的日程与未完成任务摘要。适用于了解今天/明天/本周的安排。
Sections in SKILL.md
- 适用场景
- 前置条件
- 工作流
- Step 1: 获取日程
- Step 2: 获取未完成待办
- Step 3: AI 汇总
- {日期}摘要({YYYY-MM-DD 星期X})
- 日程安排
- 待办事项
- 小结
- 权限表
- 参考
Key facts
- Author
- Lark Suite (larksuite)
- Installs on skills.sh
- 470,474 as of 2026-11-02
- License
- MIT
- Last repo commit
- 2026-10-30
- What is inside
- SKILL.md only; no scripts or extra files
- skills.sh audits
- Gen Agent Trust Hub: pass, Socket: pass, Snyk: pass
What it includes
Runs calendar +agenda for the date or range
Returns event title, times, free/busy state and your reply status.
Network ·
Step 1: get eventsRuns task +get-my-tasks --complete=false
Can limit to tasks due before a date; --page-all gets more than 20.
Network ·
Step 2: get open tasksMerges both into one summary
Sorts by time, flags overlaps, labels declined events and leaves them out of the clash check, marks overdue tasks.
Try: “What is on my plate today?”
Read ·
Step 3: build the digest
From the official docs
Permissions
Low risk
The workflow only reads your calendar and tasks, so the main risk is that titles and attendee names reach your AI provider.
What it can do
- Read your data
- Create and change things
- Delete things
- Read-only mode
Watch out for
It acts as you in Lark after you sign in
The repo README warns that the agent works under your user identity within the authorized scope. Grant only the scopes you need and read commands before you approve them. github.com
Event and task titles go to your AI provider
Claude reads titles, attendees and due dates to build the digest. Keep sensitive events off a calendar you point it at. github.com
Security advisories
No published security advisories as of Nov 2, 2026.
Technical details
| Turning on read-only | The workflow only reads: it needs calendar:calendar.event:read and task:task:read, so sign in with just those two areas. |
|---|---|
| Talks to | Lark/Feishu Open Platform API calls made by lark-cli. Your AI provider receives whatever Claude reads from Lark |
| Sign-in and keys | lark-cli stores credentials in the OS keychain, per the repo README. |
| Scopes |
|
Questions
How do I install lark-workflow-standup-report?
Use the install box at the top of this page. The box lists three steps: install the Lark CLI, add the Lark skills, then set up an app and sign in. The skill is only instructions, so Claude cannot use it until lark-cli is installed and you are signed in.
Do I need a Lark account to use lark-workflow-standup-report?
Yes. You need a Lark or Feishu account, plus an app set up with lark-cli config init. The README then has you sign in with lark-cli auth login --recommend. There is no separate API key to paste.
Does it change my calendar or tasks?
No. It only reads events and unfinished tasks. Changing them is a job for lark-calendar and lark-task.
What does the digest contain?
An event table with time, title, organizer and your reply status, a list of open tasks with due dates, a count of meetings and tasks, overlap warnings and free slots. Declined events are labelled and left out of the clash check.
Is lark-workflow-standup-report safe?
Use it with care. It only reads your calendar and tasks, but those can name colleagues and projects. The repo README warns that after you authorize Lark permissions the agent acts under your user identity and that model mistakes or prompt injection can cause real changes.
Information
updated Nov 2, 2026
- Repository
- larksuite/cli
- Folder
skills/lark-workflow-standup-report
Sources
Docs, issue trackers and discussions this page is built from.
Show all 3Hide
- larksuite/cli README · github.com
- lark-workflow-standup-report SKILL.md · github.com
- lark-skill-maker SKILL.md · github.com