Feishu Doc
openclaw/openclaw
Feishu document read/write workflows. An agent skill from openclaw/openclaw.
飞书多维表格（Base）操作：建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、workflow、角色权限；遇到 Base/多维表格/bitable 或 /base/ 链接时使用。文件导入转 lark-drive，认证/授权转 lark-shared。
Install Lark Base
$ npx skills add rongxinzy/RongxinAI --skill lark-base -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install rongxinzy/RongxinAI lark-base --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/rongxinzy/RongxinAI.git skills-src && mkdir -p .claude/skills && cp -r skills-src/MCPs/feishu/skills/lark-base .claude/skills/lark-base && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "lark-base" agent skill from https://github.com/rongxinzy/RongxinAI/tree/main/MCPs/feishu/skills/lark-base into .claude/skills/lark-base/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lark-base", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/rongxinzy/RongxinAI/tree/main/MCPs/feishu/skills/lark-baseType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add rongxinzy/RongxinAI --skill lark-base -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install rongxinzy/RongxinAI lark-base --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rongxinzy/RongxinAI.git skills-src && mkdir -p .agents/skills && cp -r skills-src/MCPs/feishu/skills/lark-base .agents/skills/lark-base && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "lark-base" agent skill from https://github.com/rongxinzy/RongxinAI/tree/main/MCPs/feishu/skills/lark-base into .agents/skills/lark-base/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lark-base", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add rongxinzy/RongxinAI --skill lark-base -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install rongxinzy/RongxinAI lark-base --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rongxinzy/RongxinAI.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/MCPs/feishu/skills/lark-base .cursor/skills/lark-base && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "lark-base" agent skill from https://github.com/rongxinzy/RongxinAI/tree/main/MCPs/feishu/skills/lark-base into .cursor/skills/lark-base/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lark-base", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/rongxinzy/RongxinAI.git --path MCPs/feishu/skills/lark-base--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add rongxinzy/RongxinAI --skill lark-base -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install rongxinzy/RongxinAI lark-base --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rongxinzy/RongxinAI.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/MCPs/feishu/skills/lark-base .gemini/skills/lark-base && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "lark-base" agent skill from https://github.com/rongxinzy/RongxinAI/tree/main/MCPs/feishu/skills/lark-base into .gemini/skills/lark-base/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lark-base", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install rongxinzy/RongxinAI lark-baseInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add rongxinzy/RongxinAI --skill lark-base -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/rongxinzy/RongxinAI.git skills-src && mkdir -p .github/skills && cp -r skills-src/MCPs/feishu/skills/lark-base .github/skills/lark-base && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "lark-base" agent skill from https://github.com/rongxinzy/RongxinAI/tree/main/MCPs/feishu/skills/lark-base into .github/skills/lark-base/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lark-base", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add rongxinzy/RongxinAI --skill lark-base -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install rongxinzy/RongxinAI lark-base --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rongxinzy/RongxinAI.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/MCPs/feishu/skills/lark-base .opencode/skills/lark-base && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "lark-base" agent skill from https://github.com/rongxinzy/RongxinAI/tree/main/MCPs/feishu/skills/lark-base into .opencode/skills/lark-base/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lark-base", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
lark-base- GitHub stars
- 154
- Used in
- 2 other repos
- Token cost
- ~3.4k tokens
- SKILL.md length
- 796 words
- Files
- 26 (incl. references)
- Skills in repo
- 94
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
飞书多维表格（Base）操作：建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、workflow、角色权限；遇到 Base/多维表格/bitable 或 /base/ 链接时使用。文件导入转 lark-drive，认证/授权转 lark-shared。
- Works in 7 steps: +record-list 的默认页、固定 --limit 和本地 jq… → 能由 Base 表达的筛选、排序、投影、聚合、分组和限制，应在 Base… → has_more=true… → …
- Tasks that involve Messaging and chat bots
- SKILL.md covers 何时使用, 使用边界, 先获取 Base Token 和所需 ID and 快速路由, plus 8 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Lark Base is an agent skill from rongxinzy/RongxinAI. 飞书多维表格（Base）操作：建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、workflow、角色权限；遇到 Base/多维表格/bitable 或 /base/ 链接时使用。文件导入转 lark-drive，认证/授权转 lark-shared。
Its SKILL.md is about 3.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 26 other files, including reference files (for example `references/dashboard-block-data-config.md`, `references/formula-field-guide.md` and `references/lark-base-cell-value.md`).
It sits in Productivity & Automation, covering Messaging and chat bots. The repository describes itself as: An all-in-one local AI Agent workspace with a fully self-developed stack. The licence is AGPL-3.0.
When your agent uses it
- Tasks that involve Messaging and chat bots
Example prompts
- “/lark-base”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- +record-list 的默认页、固定 --limit 和本地 jq 只能证明已读取范围内的事实，不能直接支撑全局最值、全量计数、Top/Bottom N、异常识别或分组结论。
- 能由 Base 表达的筛选、排序、投影、聚合、分组和限制，应在 Base 云端查询能力中执行；不要先拉原始记录到本地上下文再手工筛选排序。
- has_more=true 或等价分页信号表示当前结果不是全量；除非用户只要样例/前 N 条，不能基于该页回答全局问题。
- 多表查询必须先确认关系字段和连接键；link 单元格里的 record_id 是关系键，不是用户可读答案。
- 最终答案必须能追溯到真实表、真实字段、查询范围、筛选/排序/聚合条件和必要的连接键。
- 一次性原始记录查询优先用 +record-list / +record-search 的 filter/sort；聚合分析优先用 +data-query；要把结果长期显示在表里，才考虑新增 formula / lookup 字段。
- +data-query 可返回聚合结果或维度字段行，但维度行按字段组合去重且不返回 record_id；需要逐条记录、记录定位或完整行级字段时，再用 +record-list / +record-search / +record-get 回查。
What it can do on your machine
Read from SKILL.md and the folder at commit 9c64865. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Lark Base loads about 3.4k tokens when it runs, and up to ~82k if it reads all its reference files. Until then it costs about 36 tokens; SKILL.md has 796 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from rongxinzy/RongxinAI at commit 9c64865, republished under its AGPL-3.0 licence (© rongxinzy). 796 words, ~3,371 tokens.
Download SKILL.mdSave it as
.claude/skills/lark-base/SKILL.md (or your agent's skills folder). This skill also uses 25 other files; get the full folder from GitHub.- name
- lark-base
- description
- 飞书多维表格（Base）操作：建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、workflow、角色权限；遇到 Base/多维表格/bitable 或 /base/ 链接时使用。文件导入转 lark-drive，认证/授权转 lark-shared。
- version
- 1.2.3
- metadata.cliHelp
- lark-cli base --help
base
何时使用
使用本 skill：
- 用户明确提到 Base / 多维表格 / bitable，或给出
/base/链接。 - 用户要在 Base 内建表、改表、管理字段、写记录、查记录、配视图。
- 用户要在 Base 内做公式字段、lookup 字段、跨表计算、派生指标、筛选聚合、TopN、统计分析。
- 用户要管理 Base 表单、仪表盘、workflow、高级权限或角色。
- 用户要把旧 Base 聚合式命令或旧写法迁移到当前
lark-cli base +...shortcut。
不要使用本 skill：
- 只是认证、初始化配置、切换身份、处理 scope 或权限授权恢复，转
lark-shared。 - 把本地 Excel / CSV /
.base导入成 Base，转lark-drive +import --type bitable。 - 泛化数据分析、字段设计、公式讨论，但没有 Base/多维表格上下文。
使用边界
- Base 业务操作只使用
lark-cli base +...shortcut，不使用旧聚合式+table / +field / +record / +view / +history / +workspace。 - 本轮 Base 不依赖
lark-cli schema。SKILL 只保留路由、风险和复杂 JSON/DSL；简单命令由命令自身的参数、tips 和错误恢复承接。 - 用户要把 Excel / CSV /
.base导入成 Base 时，先转lark-cli drive +import --type bitable，导入完成后再回到 Base 命令。 - 认证、初始化、scope、身份切换、权限不足恢复属于
lark-shared；Base 文档只保留会影响 Base 路径选择的权限规则。
先获取 Base Token 和所需 ID
进入任何需要目标 Base 的 shortcut 前，必须先拿到可用的 base_token，以及当前任务需要的 table_id / view_id / record_id / form_id / dashboard_id / workflow_id 等真实 ID；不要把完整 URL、wiki token、workspace token 或孤立 raw token 直接当作 --base-token。
- 用户输入 URL 或分享链接：先运行
lark-cli base +url-resolve --url "<url>" --as user，用返回的base_token和相关 ID 继续后续命令。 - 用户输入 Base 标题、关键词或不确定名称：先运行
lark-cli base +title-resolve --title "<keyword>" --as user；--title传入标题中的短关键词，不超过 30 个字符；过长标题先取最有区分度的短关键词；多候选时先让用户消歧，不要猜。 - 文档嵌入 Base 标签：直接读取
<bitable>/<base_refer>的token作为--base-token，table-id作为--table-id，view-id作为--view-id；孤立 raw token 不走+url-resolve。 - 仍无法定位且用户不是要新建 Base 时，先反问用户要操作哪一个 Base；用户要新建时才用
+base-create。
快速路由
| 用户目标 | 优先命令 | 何时读 reference |
|---|---|---|
| 查 Base 本体 | +base-get | 用返回确认 Base 名称、owner、权限和可继续操作的 token |
| 创建/复制 Base | +base-create / +base-copy | 新建时强烈推荐用 --table-name + --fields 同时配置新 Base 里唯一一个初始数据表的 name 和 schema；写入后报告新 Base 标识和 permission_grant |
| 查看 Base 内资源目录 | +base-block-list | 想先了解一个 Base 里有哪些 table/docx/dashboard/workflow/folder 时优先用它；返回 ID 关系和 fewshot 看 --help |
| 管理 Base 内资源目录 | +base-block-create/move/rename/delete | 创建或整理 Base 直接管理的 folder/table/docx/dashboard/workflow；资源内容继续用对应命令 |
| 管理数据表 | +table-list/get/create/update/delete | 处理 table 的列出、详情、创建、重命名和删除 |
| 列/查/删字段 | +field-list/get/delete/search-options | 写入前用 list/get 确认字段类型、选项、ID；删除前确认目标字段 |
| 创建/更新字段 | +field-create / +field-update | 必读 lark-base-field-json.md；公式读 formula-field-guide.md；lookup 读 lookup-field-guide.md；命令细节读 lark-base-field-create.md / lark-base-field-update.md |
| 读记录明细 | +record-get / +record-list / +record-search | 涉及筛选、排序、Top/Bottom N、聚合、多表关联、全局结论时读 lark-base-data-analysis-sop.md |
| 写记录 | +record-upsert / +record-batch-create / +record-batch-update | 必读 lark-base-record-upsert.md / lark-base-record-batch-create.md / lark-base-record-batch-update.md 和 lark-base-cell-value.md |
| 附件字段 | +record-upload-attachment / +record-download-attachment / +record-remove-attachment | 附件不要伪造成普通 CellValue；上传走本地文件，下载/删除按 file token 或字段定位 |
| 删除记录 / 分享记录链接 / 历史 | +record-delete / +record-share-link-create / +record-history-list | 删除前确认 record；分享链接最多 100 条；历史读 lark-base-record-history-list.md，只查单条记录，不做整表审计 |
| 管理视图 | +view-* | +view-set-filter 读 lark-base-view-set-filter.md；其余配置先 get 现状，再按返回结构更新 |
| 一次性聚合统计 | +data-query | 必读 lark-base-data-analysis-sop.md 和入口 lark-base-data-query-guide.md；完整 DSL 再读 lark-base-data-query.md |
| 公式字段 | +field-create/update --json '{"type":"formula",...}' | 必读 formula-field-guide.md，读后再加隐藏确认 flag --i-have-read-guide |
| Lookup 字段 | +field-create/update --json '{"type":"lookup",...}' | 必读 lookup-field-guide.md，读后再加隐藏确认 flag --i-have-read-guide |
| 表单提交 | +form-submit | 先读 lark-base-form-detail.md 获取题目、filter 和附件所需 base_token；提交 JSON 读 lark-base-form-submit.md |
| 表单题目创建/更新 | +form-questions-create / +form-questions-update | 读 lark-base-form-questions-create.md / lark-base-form-questions-update.md |
| 其他表单管理 | +form-list/get/detail/create/update/delete / +form-questions-list/delete | +form-detail 读 lark-base-form-detail.md；删除前确认目标表单 |
| 仪表盘与组件 | +dashboard-* / +dashboard-block-* | 提到图表/看板/block 时先读 lark-base-dashboard.md；组件 data_config 读 dashboard-block-data-config.md；读取图表计算结果用 +dashboard-block-get-data |
| Workflow | +workflow-* | 创建/更新或理解 steps 时读入口 lark-base-workflow-guide.md 和 steps JSON SSOT lark-base-workflow-schema.md；list/get/enable/disable 只处理 workflow ID 与启停状态 |
| 高级权限与角色 | +advperm-* / +role-* | 角色操作先读入口 lark-base-role-guide.md；角色 create/update 或解读完整配置再读权限 JSON SSOT role-config.md；系统角色不可删除；关闭高级权限会影响自定义角色 |
Base 心智模型
- Base 曾用名 Bitable；返回字段、错误或旧文档里的
bitable多为历史兼容，不代表应改走裸 API 或另一套命令。 +base-block-list是查看一个 Base 内资源目录的新入口：它列出这个 Base 直接管理的folder/table/docx/dashboard/workflow，适合先判断 Base 里有什么，再决定走 table、dashboard、workflow 或 docx 命令。base-block只负责资源目录管理，包括创建资源、移动到 folder、重命名和删除；具体资源内容仍走 table/dashboard/workflow 命令。- 新建 Base 时，强烈推荐一次性执行
lark-cli base +base-create --name "<base>" --table-name "<table>" --fields '<field-json-array>'，同时配置新 Base 里唯一一个初始数据表的 name 和 schema；使用--fields前先读 lark-base-field-json.md 或复用+field-create的字段 JSON 形状，不要猜字段属性。 +base-create不传--table-name和--fields时，会创建一个默认 schema 的初始数据表。- 表、字段、视图、workflow、dashboard block 的名称和 ID 必须来自真实返回，不要凭用户口述猜。
- 存储字段可写；系统字段、
formula、lookup只读；附件字段走专用 attachment 命令。 - 一次性原始记录查询优先用
+record-list/+record-search的 filter/sort；聚合分析优先用+data-query；需要长期显示在表中时，才新增formula/lookup字段。 formula适合常规计算、条件判断、文本/日期处理和长期派生指标；lookup适合明确的跨表查找、筛选后取值或聚合引用。- 写入、分析、公式、lookup、workflow、dashboard 前，先读取真实结构：表、字段、视图、关联表和 dashboard block 名称都以命令返回为准。
- 跨表场景必须读取目标表结构；link 单元格中的关联
record_id只是连接键，最终回答要回查并展示用户可读字段。
身份与权限降级
- 默认显式使用
--as user操作用户资源；只有用户明确要求应用身份时，才直接用--as bot。 - user 身份报 scope/授权不足，或错误中包含
missing_scopes/hint，先转lark-shared做用户授权恢复，不要直接降级 bot。 - user 身份报资源级无访问且无授权恢复提示时，才可用
--as bot重试一次；bot 仍失败就停止重试并按权限错误处理。 91403或明确不可访问错误不要循环换身份重试。+base-create/+base-copy若用 bot 身份执行，关注返回中的permission_grant，并把用户是否可打开新 Base 告知用户。
Show full SKILL.md (318 more words)Show less
查询与统计规则
涉及查询、统计或判断结论时，先阅读 lark-base-data-analysis-sop.md，并遵守：
+record-list的默认页、固定--limit和本地jq只能证明已读取范围内的事实，不能直接支撑全局最值、全量计数、Top/Bottom N、异常识别或分组结论。- 能由 Base 表达的筛选、排序、投影、聚合、分组和限制，应在 Base 云端查询能力中执行；不要先拉原始记录到本地上下文再手工筛选排序。
has_more=true或等价分页信号表示当前结果不是全量；除非用户只要样例/前 N 条，不能基于该页回答全局问题。- 多表查询必须先确认关系字段和连接键；link 单元格里的
record_id是关系键，不是用户可读答案。 - 最终答案必须能追溯到真实表、真实字段、查询范围、筛选/排序/聚合条件和必要的连接键。
- 一次性原始记录查询优先用
+record-list/+record-search的 filter/sort；聚合分析优先用+data-query；要把结果长期显示在表里，才考虑新增formula/lookup字段。 +data-query可返回聚合结果或维度字段行，但维度行按字段组合去重且不返回record_id；需要逐条记录、记录定位或完整行级字段时，再用+record-list/+record-search/+record-get回查。
写入前置规则
- 更新前先看命令说明：需要完整提交时，先读取并补齐当前配置，只改用户指定的内容，再按命令要求提交；支持局部修改时，按命令说明和 reference 提交最小合法 payload。
- 优先用写入返回确认结果；返回信息不足或任务明确要求核验时，再读回。
- 写记录前先读字段结构；只写存储字段。系统字段、附件字段、
formula、lookup不作为普通记录写入目标。 - 附件上传、下载、删除走专用
+record-*-attachment命令。 - 写字段前先读 lark-base-field-json.md；涉及
formula/lookup时必须读 formula-field-guide.md / lookup-field-guide.md。 - 表名、字段名、视图名、workflow 配置中的名称必须来自真实返回；跨表场景还要读取目标表结构。
- 删除、角色更新、字段更新等高风险操作遵循 CLI 的 confirmation gate；目标不明确时先用 get/list 消歧。
- 批量写入单批最多 200 条；连续写同一表时串行执行，遇到
1254291按短暂等待后重试处理。 select字段只支持写入字段中已有的选项；构造 CellValue 前先用+field-list或+field-search-options确认目标选项存在。
表单与视图细节
+form-submit前必须先跑+form-detail，读取questions[].type、required、filter和附件场景需要的base_token；不要填写被 filter 隐藏的问题。- 表单附件不要写进
fields，放在--json.attachments；提交附件时必须同时传表单所属 Base 的--base-token。 +view-set-filter是唯一保留的 view reference；sort/group/card/timebar/visible-fields 这类配置先用对应 get 命令读现状，保留未修改字段，只替换用户要求变更的配置。- 视图适合持久化、共享和 UI 复用；一次性筛选/排序可先用
+record-list/+record-search的 filter/sort 验证结果，再按需要沉淀为持久视图。
Dashboard / Workflow / Role
- Dashboard 的复杂点是 block 的
data_config，不是 list/get/create/delete 命令参数。创建或更新 block 前先读 dashboard-block-data-config.md，组件必须串行创建；+dashboard-arrange是服务端智能布局，仅在用户明确要求重排/美化、或对本次会话从零新建的仪表盘做收尾整理时执行。+dashboard-block-get-data读取图表最终计算结果，不返回 block 名称、类型、布局或data_config；需要元数据先用+dashboard-block-get。 - Workflow 的复杂点是
steps结构。创建、更新或解释完整 workflow 时读入口 lark-base-workflow-guide.md 和 steps JSON SSOT lark-base-workflow-schema.md；enable/disable/list 只需确认 workflow ID、当前启停状态和用户意图。 - Role 的复杂点是权限 JSON。角色操作先读入口 lark-base-role-guide.md；
+role-create只支持自定义角色；+role-update是 delta merge；角色 create/update 或解读完整配置时读权限 JSON SSOT role-config.md。+role-delete只适用于自定义角色，系统角色不可删除；删除角色和关闭高级权限前必须确认目标和影响。
常见恢复
| 错误 / 现象 | 恢复动作 |
|---|---|
param baseToken is invalid / base_token invalid | 检查是否把 wiki token、workspace token 或完整 URL 当成了 --base-token；按入口规则重新获取真实 base_token |
not found 且输入来自 Wiki 链接 | 优先检查是否把 wiki token 当成 base token，不要立刻改走裸 API |
1254045 字段名不存在 | 重新 +field-list，使用真实字段名或字段 ID；注意空格、大小写和跨表字段 |
1254015 字段值类型不匹配 | 先 +field-list，再按 lark-base-cell-value.md 构造 CellValue |
Invalid discriminator value（字段写入缺 type） | 按完整提交规则读取当前字段，只改目标内容后提交；不要只补 type 重试 |
filter 报 value of type array / Only string values | 用 record/view 的 tuple --filter-json（非 +data-query 对象型），value 按字段 type 选标量或数组；见 lark-base-view-set-filter.md |
| 日期 / 人员 / 超链接字段报格式错误 | 日期用 YYYY-MM-DD HH:mm:ss；人员用 [{ "id": "ou_xxx" }]；超链接用 URL 或 markdown link 字符串 |
| formula / lookup 创建失败 | 先读 formula-field-guide.md / lookup-field-guide.md，再按 guide 重建请求 |
ignored_fields / READONLY | 移除只读字段，只写存储字段 |
1254104 | 批量超过 200，分批调用 |
1254291 | 并发写冲突，串行写入并在批次间短暂等待 |
91403 | 无权限访问该 Base，按 lark-shared 权限流程处理，不要盲目重试 |
保留 Reference
- lark-base-data-analysis-sop.md：查询/统计/全局结论的选路 SOP
- lark-base-data-query-guide.md / lark-base-data-query.md：聚合查询入口 fewshot 与 DSL SSOT
- lark-base-cell-value.md：记录 CellValue 构造
- lark-base-field-json.md：字段 JSON 构造
- formula-field-guide.md / lookup-field-guide.md：公式与 lookup 字段
- lark-base-field-create.md / lark-base-field-update.md：字段创建/更新命令级补充
- lark-base-record-upsert.md / lark-base-record-batch-create.md / lark-base-record-batch-update.md / lark-base-record-history-list.md：记录写入 JSON 与历史返回解释
- lark-base-view-set-filter.md：视图筛选 JSON
- lark-base-form-detail.md / lark-base-form-submit.md / lark-base-form-questions-create.md / lark-base-form-questions-update.md：表单详情、提交和复杂 JSON
- lark-base-dashboard.md / dashboard-block-data-config.md / lark-base-dashboard-block-get-data.md：仪表盘、组件配置与图表结果协议
- lark-base-workflow-guide.md / lark-base-workflow-schema.md：workflow 入口与 steps JSON SSOT
- lark-base-role-guide.md / role-config.md：角色入口与权限 JSON SSOT
© rongxinzy, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 25 other files (references) in MCPs/feishu/skills/lark-base of rongxinzy/RongxinAI.
- SKILL.md
- references/dashboard-block-data-config.md
- references/formula-field-guide.md
- references/lark-base-cell-value.md
- references/lark-base-dashboard-block-get-data.md
- references/lark-base-dashboard.md
- references/lark-base-data-analysis-sop.md
- references/lark-base-data-query-guide.md
- references/lark-base-data-query.md
- references/lark-base-field-create.md
- references/lark-base-field-json.md
- references/lark-base-field-update.md
- references/lark-base-form-detail.md
- references/lark-base-form-questions-create.md
- references/lark-base-form-questions-update.md
- references/lark-base-form-submit.md
- references/lark-base-record-batch-create.md
- references/lark-base-record-batch-update.md
- references/lark-base-record-history-list.md
- references/lark-base-record-upsert.md
- … and 6 more
Open the folder on GitHubat commit 9c64865
Used in 2 other repositories
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in rongxinzy/RongxinAI, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Lark Base next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Lark Base this skillrongxinzy/RongxinAI | 154 | 2 repos | ~3.4k | Automated safety check: Pass | AGPL-3.0 | |
| Feishu Docopenclaw/openclaw | 392k | — | ~516 | Automated safety check: Pass | MIT | |
| She Love Me863401402/she-love-me | 931 | 1 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Feishu Docraucvr/Group-Goki | 112 | 3 repos | ~592 | Automated safety check: Pass | MIT | |
| Wechat Article Extractorfreestylefly/wechat-article-extractor-skill | 136 | 1 repos | ~1k | Automated safety check: Pass | None | |
| Wechat Miniprogram Builderchenjin-cmd/wechat-miniprogram-builder | 356 | — | ~634 | Automated safety check: Pass | MIT |
Similar skills
She Love Me
863401402/she-love-me
Acquire, import, and analyze WeChat or QQ chat histories, including installing supported exporters, guiding required login or contact selection, converting exports, assessing relationship dynamics…
Feishu Doc
raucvr/Group-Goki
Feishu document read/write operations. An agent skill from raucvr/Group-Goki.
Wechat Article Extractor
freestylefly/wechat-article-extractor-skill
Extract metadata and content from WeChat Official Account articles.
Wechat Miniprogram Builder
chenjin-cmd/wechat-miniprogram-builder
This skill should be used when the user wants to build, launch, monetize, or promote a WeChat mini-program with AI (vibe coding) — including topic selection, account registration & ICP filing…
Slack
huangruiteng/CS-Notes
A skill your agent uses when you need to control Slack from Clawdbot via the slack tool, including reacting to messages or pinning/unpinning items in Slack channels or DMs.
More from rongxinzy/RongxinAI
All 94 skills in this repoSaaS Metrics Coach
rongxinzy/RongxinAI
SaaS financial health advisor. An agent skill from rongxinzy/RongxinAI.
Churn Prevention
rongxinzy/RongxinAI
Reduce voluntary and involuntary churn through cancel flow design, save offers, exit surveys, and dunning sequences.
Presentation Studio
rongxinzy/RongxinAI
The only skill for creating a new PowerPoint deck. An agent skill from rongxinzy/RongxinAI.
Zhiyuan Expert Manager
rongxinzy/RongxinAI
ZhiYuan Agent expert package lifecycle manager for the pi engine.
Ziwei Doushu
rongxinzy/RongxinAI
Professional Ziwei Doushu consultation skill with an offline calculation engine.
Lark Mail
rongxinzy/RongxinAI
飞书邮箱：Use when user mentions 起草邮件、写邮件、草稿、发送/回复/转发邮件、查阅邮件、看邮件、搜索邮件、邮件文件夹、邮件标签、邮件联系人、监听新邮件、邮件收信规则等；use for mail/email intent only.
Related
Categories
Questions about Lark Base
What does Lark Base do?
飞书多维表格（Base）操作：建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、workflow、角色权限；遇到 Base/多维表格/bitable 或 /base/ 链接时使用。文件导入转 lark-drive，认证/授权转 lark-shared。. Lark Base is an agent skill from rongxinzy/RongxinAI.
When should I use Lark Base?
Lark Base fits situations like: tasks that involve Messaging and chat bots.
How do I install Lark Base in Claude Code?
Run `npx skills add rongxinzy/RongxinAI --skill lark-base -a claude-code`. Or copy the skill folder (MCPs/feishu/skills/lark-base in rongxinzy/RongxinAI) into .claude/skills/lark-base in your project. Claude Code loads it when a task matches its description.
How do I install Lark Base in Codex?
Run `npx skills add rongxinzy/RongxinAI --skill lark-base -a codex`. Or copy the skill folder (MCPs/feishu/skills/lark-base in rongxinzy/RongxinAI) into .agents/skills/lark-base in your project. Codex loads it when a task matches its description.
Can I use Lark Base in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add rongxinzy/RongxinAI --skill lark-base -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lark-base, .gemini/skills/lark-base, .github/skills/lark-base and .opencode/skills/lark-base in your project.
What does Lark Base need to run?
SKILL.md names no scripts, command-line tools or credentials: Lark Base is instructions for the agent only.
Does Lark Base access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Lark Base safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Lark Base use?
Lark Base is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Lark Base use?
About 3.4k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 79k tokens, read only when the agent opens those files.
What are the alternatives to Lark Base?
Skills that share tags, products or a category with Lark Base: Feishu Doc (openclaw/openclaw, 392k stars), She Love Me (863401402/she-love-me, 931 stars), Feishu Doc (raucvr/Group-Goki, 112 stars) and Wechat Article Extractor (freestylefly/wechat-article-extractor-skill, 136 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Lark Base?
rongxinzy (a GitHub organization) maintains it in rongxinzy/RongxinAI, which has 154 GitHub stars. The repository holds 94 skills in this directory. The repository was last updated on October 10, 2026.
Source: rongxinzy/RongxinAI on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.