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-troubleshootgit 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-troubleshoot)<a href="https://agentmods.dev/skills/larksuite/openclaw-lark/feishu-troubleshoot"><img src="https://agentmods.dev/badge/skills/larksuite/openclaw-lark/feishu-troubleshoot/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-troubleshoot"><img src="https://agentmods.dev/badge/skills/larksuite/openclaw-lark/feishu-troubleshoot.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.00092 | $0.00613 |
| Opus 5 | $0.00046 | $0.00307 |
| Sonnet 5 | $0.00018 | $0.00123 |
| Haiku 4.5 | $0.00009 | $0.00061 |
Grade A, and why
feishu-troubleshoot 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-troubleshoot — 12 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.
What it actually says
飞书插件问题排查
❓ 常见问题（FAQ）
卡片按钮点击无反应
现象：点击卡片按钮后没有任何反应，然后提示报错.
原因：应用未开通「消息卡片回传交互」权限。
解决步骤：
- 登录飞书开放平台：https://open.feishu.cn/app
- 选择您的应用 → 事件与回调
- 在回调配置中,修改订阅方式为"长链接"并添加回调 "卡片回传交互"(card.action.trigger)
- 创建应用版本 → 提交审核 → 发布
🔍 诊断命令（深度工具）
注意：诊断命令仅用于排查复杂/疑难的权限相关问题。常规权限问题会自动触发授权流程，无需手动诊断。
何时使用诊断：
- 多次授权后仍然报错
- 自动授权流程无法解决的问题
- 需要查看完整的权限配置状态
使用方法：
在飞书聊天会话中直接输入（作为用户消息发送）：
/feishu doctor
诊断命令会检查：
-
📋 诊断摘要（首先展示）：
- 总体状态（✅ 正常 / ⚠️ 警告 / ❌ 失败）
- 发现的问题列表和简要描述
-
环境信息：
- 插件版本
-
账号信息：
- 凭证完整性（appId, appSecret 掩码）
- 账户启用状态
- API 连通性测试
- Bot 信息（名称和 openId）
-
应用身份权限：
- 应用已开通的必需权限数量
- 缺失的必需权限列表
- 一键申请链接（自动带上缺失权限参数）
-
用户身份权限：
- 用户授权状态统计（✓ 有效 / ⟳ 需刷新 / ✗ 已过期）
- Token 自动刷新状态（是否包含 offline_access）
- 权限对照表（应用已开通 vs 用户已授权，逐项对比）
- 应用权限缺失时的申请指引和链接
- 用户授权不足时的重新授权操作方法
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 · 71 lines · 92 tokens per session scan A 6f0e43bc7958
feishu-troubleshoot is a skill published in the GitHub repository larksuite/openclaw-lark (2,375 stars, last pushed 1mo ago), licensed MIT. It adds 92 tokens to every session and 613 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to feishu-troubleshoot, differing in 12 lines, and is treated as a copy.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.