
Feishu Fetch Doc
- 217 installs
- 2.3k repo stars
- Updated July 22, 2026
- larksuite/openclaw-lark
Pull Feishu/Lark cloud docs into Markdown inside your coding agent so specs and wikis become agent-readable context.
About
feishu-fetch-doc is an agent skill for solo builders and small teams who keep specs in Feishu/Lark and want Claude Code, Cursor, or Codex to read them as Markdown. It fetches cloud document body text in Lark-flavored Markdown and explains how embedded media is not inlined: images, attachments, and whiteboards appear as HTML tags with tokens that you download separately through feishu_doc_media. For knowledge-base links, the skill enforces a safe flow—resolve the wiki token first to learn obj_type and obj_token, then call the right fetch tool instead of assuming every wiki page is a docx. Use it during build when onboarding an agent to internal docs, syncing PRDs, or grounding codegen on living documentation. It pairs naturally with other openclaw-lark skills for media and wiki resolution. Complexity is intermediate because you must orchestrate multiple tools and paths on disk for binaries.
- Returns Lark-flavored Markdown from docx URLs, raw tokens, or wiki links
- Documents HTML token tags for images, files, and whiteboards that require feishu_doc_media download
- Wiki URLs must be resolved via feishu_wiki_space_node get before calling the correct obj_type tool
- Accepts full Feishu docx/wiki URLs or bare tokens as doc_id
Feishu Fetch Doc by the numbers
- 217 all-time installs (skills.sh)
- Ranked #2,698 of 16,659 AI & Agent Building skills by installs in the Skillselion catalog
- Security screen: HIGH risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
npx skills add https://github.com/larksuite/openclaw-lark --skill feishu-fetch-docAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 217 |
|---|---|
| repo stars | ★ 2.3k |
| Security audit | 2 / 3 scanners passed |
| Last updated | July 22, 2026 |
| Repository | larksuite/openclaw-lark ↗ |
What it does
Pull Feishu/Lark cloud docs into Markdown inside your coding agent so specs and wikis become agent-readable context.
Files
feishu_mcp_fetch_doc
获取飞书云文档的 Markdown 内容(Lark-flavored 格式)。
重要:图片、文件、画板的处理
文档中的图片、文件、画板需要通过 `feishu_doc_media`(action: download)工具单独获取!
识别格式
返回的 Markdown 中,媒体文件以 HTML 标签形式出现:
- 图片:
<image token="Z1FjxxxxxxxxxxxxxxxxxxxtnAc" width="1833" height="2491" align="center"/>- 文件:
<view type="1">
<file token="Z1FjxxxxxxxxxxxxxxxxxxxtnAc" name="skills.zip"/>
</view>- 画板:
<whiteboard token="Z1FjxxxxxxxxxxxxxxxxxxxtnAc"/>获取步骤
1. 从 HTML 标签中提取 token 属性值 2. 调用 feishu_doc_media 下载:
{
"action": "download",
"resource_token": "提取的token",
"resource_type": "media",
"output_path": "/path/to/save/file"
}参数
- `doc_id`(必填):支持直接传文档 URL 或 token
- 直接传 URL:
https://xxx.feishu.cn/docx/Z1FjxxxxxxxxxxxxxxxxxxxtnAc(系统自动提取 token) - 直接传 token:
Z1FjxxxxxxxxxxxxxxxxxxxtnAc - 知识库 URL/token 也支持:
https://xxx.feishu.cn/wiki/Z1FjxxxxxxxxxxxxxxxxxxxtnAc或Z1FjxxxxxxxxxxxxxxxxxxxtnAc
Wiki URL 处理策略
知识库链接(/wiki/TOKEN)背后可能是云文档、电子表格、多维表格等不同类型的文档。当不确定类型时, 不能直接假设是云文档,必须先查询实际类型。
处理流程
1. 先调用 `feishu_wiki_space_node`(action: get)解析 wiki token:
{ "action": "get", "token": "wiki_token_here" }2. 从返回的 `node` 中获取 `obj_type`(实际文档类型)和 `obj_token`(实际文档 token) 3. 根据 `obj_type` 调用对应工具:
| obj_type | 工具 | 传参 |
|---|---|---|
docx | feishu_mcp_fetch_doc | doc_id = obj_token |
sheet | feishu_sheet | spreadsheet_token = obj_token |
bitable | feishu_bitable_* 系列 | app_token = obj_token |
| 其他 | 告知用户暂不支持该类型 | — |
示例
用户:帮我看下这个文档 https://xxx.feishu.cn/wiki/ABC123
1. 调用 feishu_wiki_space_node(action: get, token: ABC123) 2. 返回 obj_type: "docx", obj_token: "doxcnXYZ789" 3. 调用 feishu_mcp_fetch_doc(doc_id: doxcnXYZ789)
工具组合
| 需求 | 工具 |
|---|---|
| 获取文档文本 | feishu_mcp_fetch_doc |
| 下载图片/文件/画板 | feishu_doc_media(action: download) |
| 解析 wiki token 类型 | feishu_wiki_space_node(action: get) |
| 读写电子表格 | feishu_sheet |
| 操作多维表格 | feishu_bitable_* 系列 |
Related skills
FAQ
Is Feishu Fetch Doc safe to install?
skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.