OpenClaw Lark/Feishu Plugin connects an OpenClaw agent to Lark or Feishu workspaces, allowing it to work with messages, documents, databases, spreadsheets, calendars, and tasks. It is for OpenClaw users who want their agent to read and update Lark/Feishu workspace data. The catalogue skills provide the agent workflows for operating those connected workspace features.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add larksuite/openclaw-lark --skill feishu-calendargit clone --depth 1 https://github.com/larksuite/openclaw-larkWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/larksuite/openclaw-lark/feishu-calendar)<a href="https://agentmods.dev/skills/larksuite/openclaw-lark/feishu-calendar"><img src="https://agentmods.dev/badge/skills/larksuite/openclaw-lark/feishu-calendar/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/larksuite/openclaw-lark/feishu-calendar"><img src="https://agentmods.dev/badge/skills/larksuite/openclaw-lark/feishu-calendar.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00033 | $0.02575 |
| Opus 5 | $0.00016 | $0.01288 |
| Sonnet 5 | $0.00007 | $0.00515 |
| Haiku 4.5 | $0.00003 | $0.00258 |
Grade A, and why
feishu-calendar scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
88% identical to feishu-calendar — 13 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
飞书日历管理 (feishu-calendar)
🚨 执行前必读
- ✅ 时区固定：Asia/Shanghai（UTC+8）
- ✅ 时间格式：ISO 8601 / RFC 3339（带时区），例如
2026-02-25T14:00:00+08:00 - ✅ create 最小必填：summary, start_time, end_time
- ✅ user_open_id 强烈建议：从 SenderId 获取（ou_xxx），确保用户能看到日程
- ✅ ID 格式约定：用户
ou_...，群oc_...，会议室omm_...，邮箱email@...
📋 快速索引：意图 → 工具 → 必填参数
| 用户意图 | 工具 | action | 必填参数 | 强烈建议 | 常用可选 |
|---|---|---|---|---|---|
| 创建会议 | feishu_calendar_event | create | summary, start_time, end_time | user_open_id | attendees, description, location |
| 查某时间段日程 | feishu_calendar_event | list | start_time, end_time | - | - |
| 改日程时间 | feishu_calendar_event | patch | event_id, start_time/end_time | - | summary, description |
| 搜关键词找会 | feishu_calendar_event | search | query | - | - |
| 回复邀请 | feishu_calendar_event | reply | event_id, rsvp_status | - | - |
| 查重复日程实例 | feishu_calendar_event | instances | event_id, start_time, end_time | - | - |
| 查忙闲 | feishu_calendar_freebusy | list | time_min, time_max, user_ids[] | - | - |
| 邀请参会人 | feishu_calendar_event_attendee | create | calendar_id, event_id, attendees[] | - | - |
🎯 核心约束（Schema 未透露的知识）
1. user_open_id 为什么必填？
工具使用用户身份：日程创建在用户主日历上，用户本人能看到。
但为什么还要传 user_open_id：将发起人也添加为参会人，确保：
- ✅ 发起人会收到日程通知
- ✅ 发起人可以回复 RSVP 状态（接受/拒绝/待定）
- ✅ 发起人出现在参会人列表中
- ✅ 其他参会人能看到发起人
如果不传：
- ⚠️ 用户能看到日程，但不会作为参会人
- ⚠️ 如果只有其他参会人，发起人不在列表中（不符合常规逻辑）
2. 参会人权限（attendee_ability）
工具已默认设置 attendee_ability: "can_modify_event"，参会人可以编辑日程和管理参与者。
| 权限值 | 能力 |
|---|---|
none |
无权限 |
can_see_others |
可查看参与人列表 |
can_invite_others |
可邀请他人 |
can_modify_event |
可编辑日程（推荐） |
3. 统一使用 open_id（ou_...格式）
- ✅ 创建日程：
user_open_id = SenderId - ✅ 邀请参会人：
attendees[].id = "ou_xxx"
⚠️ ID 格式区分：
ou_xxx：用户的 open_id（你应该使用的）user_xxx：日程内部的 attendee_id（list 接口返回，仅用于内部记录）
4. 会议室预约是异步流程
添加会议室类型参会人后，会议室进入异步预约流程：
- API 返回成功 →
rsvp_status: "needs_action"（预约中） - 后台异步处理
- 最终状态：
accept（成功）或decline（失败）
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 243 lines · 33 tokens per session scan A 98d11afa39cb
feishu-calendar is a skill published in the GitHub repository larksuite/openclaw-lark (2,375 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 2,575 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to feishu-calendar, differing in 13 lines, and is treated as a copy.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.