[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MPJVVVDY0JDM0GH28FM0PC":3,"skill-same:01M6MPJVVVDY0JDM0GH28FM0PC":123},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M6MPJVVVDY0JDM0GH28FM0PC","lark-wiki",null,"飞书知识库：管理知识空间、空间成员和文档节点。创建和查询知识空间、查看和管理空间成员、管理节点层级结构、在知识库中组织文档和快捷方式。当用户需要在知识库中查找或创建文档、浏览知识空间结构、查看或管理空间成员、移动或复制节点时使用。当用户给出 doubao.com 的 \u002Fwiki\u002F URL\u002Ftoken 时，也应直接使用本 skill，不要因为域名不是飞书而回退到 WebFetch；路由依据是 URL 路径模式和 token，而不是域名。不负责：上传文件到知识库节点下（走 lark-drive）、编辑文档\u002F表格\u002FBase 内容（走 lark-doc \u002F lark-sheets \u002F lark-base）。","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fzlsbksdxl\u002Fcodex-lark\u002Fskills\u002Flark-wiki\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33],"wiki","lark wiki","lark","cli","help","doc","文档","表格","webfetch","drive","base","token","URL","文件","sheets","2026-11-10 10:12:30",false,"---\nname: lark-wiki\nversion: 1.0.3\ndescription: \"飞书知识库：管理知识空间、空间成员和文档节点。创建和查询知识空间、查看和管理空间成员、管理节点层级结构、在知识库中组织文档和快捷方式。当用户需要在知识库中查找或创建文档、浏览知识空间结构、查看或管理空间成员、移动或复制节点时使用。当用户给出 doubao.com 的 \u002Fwiki\u002F URL\u002Ftoken 时，也应直接使用本 skill，不要因为域名不是飞书而回退到 WebFetch；路由依据是 URL 路径模式和 token，而不是域名。不负责：上传文件到知识库节点下（走 lark-drive）、编辑文档\u002F表格\u002FBase 内容（走 lark-doc \u002F lark-sheets \u002F lark-base）。\"\nmetadata:\n  requires:\n    bins: [\"lark-cli\"]\n  cliHelp: \"lark-cli wiki --help\"\n---\n\n# wiki (v2)\n\n**CRITICAL — 开始前 MUST 先用 Read 工具读取 [`..\u002Flark-shared\u002FSKILL.md`](..\u002Flark-shared\u002FSKILL.md)，其中包含认证、权限处理**\n\n> **成员管理硬限制：**\n> - 如果目标是“部门”，先判断身份，再决定是否继续。\n> - `--as bot` 对应 `tenant_access_token`。官方限制：这种身份下不能使用部门 ID (`opendepartmentid`) 添加知识空间成员。\n> - 遇到“部门 + --as bot”时，禁止先调用 `lark-cli wiki +member-add` 试错；直接说明该路径不可行。\n> - 如果用户明确要求“以 bot 身份运行”，且目标是部门，必须停下说明 bot 路径无法完成，不要静默切到 `--as user`。\n\n## 身份选择：优先使用 user 身份\n\n知识空间和节点都是用户的个人资源，**策略上应优先显式使用 `--as user`**（CLI 的 `--as` 默认值为 `auto`，不带 `--as` 时常被解析成 `bot`，列出的是应用所属空间而非用户的）。仅当用户明确要求“应用 \u002F bot 视角”时才用 `--as bot`（仍受上面的成员管理硬限制约束）。\n\n## 快速决策\n\n- 用户要**整理 \u002F 盘点 \u002F 归类 \u002F 重构知识库、个人文档库、文档库目录或 Wiki 节点结构**，或要生成整理方案、目标目录树、移动计划时，不要只使用 Wiki 节点 API。必须先阅读 [`..\u002Flark-drive\u002Freferences\u002Flark-drive-workflow.md`](..\u002Flark-drive\u002Freferences\u002Flark-drive-workflow.md)，再按其中 `Workflow Registry` 进入 [`knowledge_organize`](..\u002Flark-drive\u002Freferences\u002Flark-drive-workflow-knowledge-organize.md) workflow；该 workflow 负责 Drive \u002F Wiki \u002F 个人文档库的统一入口解析、资源盘点、分类计划、写前确认和结果验证。\n- 用户要把**已有 Wiki 节点移出知识库，放到 Drive 文件夹或“我的空间”根目录**：使用 `wiki +move-to-drive`，不要使用 `wiki +move` 或 `drive +move`。这是会改变节点归属和权限继承的写操作，执行前确认源节点与目标位置。\n- 用户给的是知识库 URL（`...\u002Fwiki\u002F\u003Ctoken>`），且后续要查成员\u002F加成员\u002F删成员：先调用 `lark-cli wiki spaces get_node --params '{\"token\":\"\u003Cwiki_token>\"}'` 获取 `space_id`，后续成员接口统一使用 `space_id`。\n- 用户要**删除**知识空间（`wiki +delete-space`）但只给了名称或 URL：**不能**把名称 \u002F URL 原样传给 `--space-id`，必须先解析出真实 `space_id`。解析方式：\n  - URL（`...\u002Fwiki\u002F\u003Ctoken>`）：`lark-cli wiki spaces get_node --params '{\"token\":\"\u003Cwiki_token>\"}' --format json`，读 `data.node.space_id`。\n  - 只知名称：`lark-cli wiki spaces list --format json`，边翻页边收集 items 并按 `name` 精确匹配；**一旦任一页累计到至少 1 条精确匹配就停止翻页**。只有当翻完所有页（`has_more=false`）仍无精确匹配时，才对已收集的全量 items 做宽松匹配（`name` trim 空格、大小写不敏感、子串包含）。\n  - **关键安全约束**：无论精确还是模糊，**无论命中 1 条还是多条，发起删除前都必须把候选（`name` + `space_id` + `description` + `space_type`）列给用户，由用户明确选定一个 `space_id` 再执行**。不要因为\"只命中一条\"就自动执行删除。\n  - 命中 0 条：停下来问用户是名称拼错了还是调用方无权限；**不要**自行改名字重试。\n  - 用户明确选定后再执行 `lark-cli wiki +delete-space --space-id \u003CID> --yes`（高风险写操作，必须显式 `--yes`）。\n  - 反例：不要把 wiki URL \u002F 名称直接当 `--space-id`（如 `--space-id \"https:\u002F\u002F...\u002Fwiki\u002F\u003Cwiki_token>\"`）；务必先用 `wiki spaces get_node` 解析出 `data.node.space_id` 再传。\n- 用户要在知识库中创建新节点，优先使用 `lark-cli wiki +node-create`。\n- 用户要列出 Wiki 节点：先用 `wiki +space-list --as user` 拿数字 `space_id`，再用 `wiki +node-list --space-id \u003Cspace_id>`。不要把 wiki URL、node token、doc token、名称直接当 `--space-id`。钻子节点时 `--parent-node-token` 必须是 wiki node token；如果用户给的是 docx\u002Fsheet\u002Fbase URL，先用 `wiki +node-get --node-token \u003Curl>` 解析出 `node_token`。\n- `wiki +node-list` 命中 `invalid_parameters`、`not_found`、`permission_denied` 时，不要重复调用同一参数；按 hint 修 `space_id` \u002F `parent_node_token` \u002F 权限。只有 `rate_limit` 才做退避重试。\n- 用户说“给知识库添加成员\u002F管理员”：先把目标解析成“用户 \u002F 群 \u002F 部门 \u002F 应用”四类之一，再决定 `--member-type`，不要先调 `wiki +member-add` 再根据报错反推类型。\n- 用户说“部门 + bot”：这是已知不支持路径。不要继续尝试 `wiki +member-add --as bot`；直接提示必须改成 `--as user`，或明确告知当前要求无法完成。\n- 用户说“用户 \u002F 群 \u002F 应用 + 添加成员”：先解析对应 ID，再执行 `wiki +member-add`。\n- 用户说“查看 \u002F 列出空间成员”：用 `wiki +member-list`；该 shortcut 默认只取一页，多成员场景显式加 `--page-all`。\n- 用户说“移除 \u002F 删除空间成员”：用 `wiki +member-remove`，必须传齐原始授予时的 `--member-type` 和 `--member-role`（不知道就先 `wiki +member-list` 查一下）。\n\n## Shortcuts（推荐优先使用）\n\nShortcut 是对常用操作的高级封装（`lark-cli wiki +\u003Cverb> [flags]`）。有 Shortcut 的操作优先使用。\n\n| Shortcut | 说明 |\n|----------|------|\n| [`+move`](references\u002Flark-wiki-move.md) | Move a wiki node, or move a Drive document into Wiki |\n| [`+move-to-drive`](references\u002Flark-wiki-move-to-drive.md) | Move a wiki node to a Drive folder and poll the async task |\n| [`+node-create`](references\u002Flark-wiki-node-create.md) | Create a wiki node with automatic space resolution |\n| [`+delete-space`](references\u002Flark-wiki-delete-space.md) | Delete a wiki space, polling the async delete task when needed |\n| [`+space-list`](references\u002Flark-wiki-space-list.md) | List all wiki spaces accessible to the caller |\n| [`+space-create`](references\u002Flark-wiki-space-create.md) | Create a wiki space (user identity only) |\n| [`+node-list`](references\u002Flark-wiki-node-list.md) | List wiki nodes in a space or under a parent node (supports pagination) |\n| [`+node-copy`](references\u002Flark-wiki-node-copy.md) | Copy a wiki node to a target space or parent node |\n| [`+node-get`](references\u002Flark-wiki-node-get.md) | Get a wiki node's details by node_token \u002F obj_token \u002F Lark URL |\n| [`+node-delete`](references\u002Flark-wiki-node-delete.md) | Delete a wiki node, polling the async delete task when needed |\n| [`+member-add`](references\u002Flark-wiki-member-add.md) | Add a member to a wiki space |\n| [`+member-remove`](references\u002Flark-wiki-member-remove.md) | Remove a member from a wiki space |\n| [`+member-list`](references\u002Flark-wiki-member-list.md) | List members of a wiki space (supports pagination) |\n\n## 成员添加流程\n\n- 调用 `lark-cli wiki +member-add` 前，先把自然语言里的“人 \u002F 群 \u002F 部门 \u002F 应用”解析成正确的 `--member-id`，不要猜格式。\n- 用户场景默认优先 `--member-type=openid`：用 `lark-cli contact +search-user --query \"\u003C姓名\u002F邮箱\u002F手机号>\" --format json` 获取 `open_id`。\n- 群组场景使用 `--member-type=openchat`：用 `lark-cli im +chat-search --query \"\u003C群名关键词>\" --format json` 获取 `chat_id`。\n- 应用场景使用 `--member-type=appid`：`--member-id` 传应用 ID，格式通常为 `cli_xxx`。\n- `userid` \u002F `unionid` 只在下游明确要求时才使用；先拿到 `open_id`，再调用 `lark-cli api GET \u002Fopen-apis\u002Fcontact\u002Fv3\u002Fusers\u002F\u003Copen_id> --params '{\"user_id_type\":\"open_id\"}' --format json` 读取 `user_id` \u002F `union_id`。\n- 部门场景使用 `--member-type=opendepartmentid`：当前 CLI 没有 shortcut，需调用 `lark-cli api POST \u002Fopen-apis\u002Fcontact\u002Fv3\u002Fdepartments\u002Fsearch --as user --params '{\"department_id_type\":\"open_department_id\"}' --data '{\"query\":\"\u003C部门名>\"}'` 获取 `open_department_id`。\n- 只有在目标类型和身份都已确认可行后，才调用 `lark-cli wiki +member-add`。对于部门场景，这意味着必须是 `--as user`。\n\n## 目标语义约束\n\n- `我的文档库` \u002F `My Document Library` \u002F `我的知识库` \u002F `个人知识库` \u002F `my_library` 都应视为 **Wiki personal library**，不是 Drive 根目录\n- 处理这类目标时，先解析 `my_library` 对应的真实 `space_id`，再执行 `wiki +move`、`wiki +node-create` 或其他 Wiki 写操作\n- 不要因为缺少显式 `space_id` 就退化成 `drive +move`\n- 如果用户明确说的是 Drive 文件夹、云空间（云盘\u002F云存储）根目录、`我的空间`，再按源对象分流：源对象是 Wiki 节点时用 `wiki +move-to-drive`，源对象已在 Drive 时用 `drive +move`\n\n## API Resources\n\n```bash\nlark-cli schema wiki.\u003Cresource>.\u003Cmethod>   # 调用原生 API 前必须先查看 --data \u002F --params 参数结构，不要猜测字段格式\nlark-cli wiki \u003Cresource> \u003Cmethod> [flags]  # 调用 API\n```\n\n### spaces\n\n- `create` — 创建知识空间\n- `get` — 获取知识空间信息\n- `get_node` — 获取知识空间节点信息\n- `list` — 获取知识空间列表\n\n### members\n\n- `create` — 添加知识空间成员\n- `delete` — 删除知识空间成员\n- `list` — 获取知识空间成员列表\n\n### nodes\n\n- `copy` — 创建知识空间节点副本\n- `create` — 创建知识空间节点\n- `list` — 获取知识空间子节点列表\n\n## 不在本 skill 范围\n\n- 上传 \u002F 下载文件到知识库节点下 → [`lark-drive`](..\u002Flark-drive\u002FSKILL.md)（`drive +upload --wiki-token`）\n- 编辑文档正文内容 → [`lark-doc`](..\u002Flark-doc\u002FSKILL.md)\n- 表格 \u002F 多维表格数据操作 → [`lark-sheets`](..\u002Flark-sheets\u002FSKILL.md) \u002F [`lark-base`](..\u002Flark-base\u002FSKILL.md)\n- 按名称搜索文档 \u002F Wiki \u002F 表格文件、评论与权限管理 → [`lark-drive`](..\u002Flark-drive\u002FSKILL.md)\n","# wiki (v2)\n\n**CRITICAL — 开始前 MUST 先用 Read 工具读取 [`..\u002Flark-shared\u002FSKILL.md`](..\u002Flark-shared\u002FSKILL.md)，其中包含认证、权限处理**\n\n> **成员管理硬限制：**\n> - 如果目标是“部门”，先判断身份，再决定是否继续。\n> - `--as bot` 对应 `tenant_access_token`。官方限制：这种身份下不能使用部门 ID (`opendepartmentid`) 添加知识空间成员。\n> - 遇到“部门 + --as bot”时，禁止先调用 `lark-cli wiki +member-add` 试错；直接说明该路径不可行。\n> - 如果用户明确要求“以 bot 身份运行”，且目标是部门，必须停下说明 bot 路径无法完成，不要静默切到 `--as user`。\n\n## 身份选择：优先使用 user 身份\n\n知识空间和节点都是用户的个人资源，**策略上应优先显式使用 `--as user`**（CLI 的 `--as` 默认值为 `auto`，不带 `--as` 时常被解析成 `bot`，列出的是应用所属空间而非用户的）。仅当用户明确要求“应用 \u002F bot 视角”时才用 `--as bot`（仍受上面的成员管理硬限制约束）。\n\n## 快速决策\n\n- 用户要**整理 \u002F 盘点 \u002F 归类 \u002F 重构知识库、个人文档库、文档库目录或 Wiki 节点结构**，或要生成整理方案、目标目录树、移动计划时，不要只使用 Wiki 节点 API。必须先阅读 [`..\u002Flark-drive\u002Freferences\u002Flark-drive-workflow.md`](..\u002Flark-drive\u002Freferences\u002Flark-drive-workflow.md)，再按其中 `Workflow Registry` 进入 [`knowledge_organize`](..\u002Flark-drive\u002Freferences\u002Flark-drive-workflow-knowledge-organize.md) workflow；该 workflow 负责 Drive \u002F Wiki \u002F 个人文档库的统一入口解析、资源盘点、分类计划、写前确认和结果验证。\n- 用户要把**已有 Wiki 节点移出知识库，放到 Drive 文件夹或“我的空间”根目录**：使用 `wiki +move-to-drive`，不要使用 `wiki +move` 或 `drive +move`。这是会改变节点归属和权限继承的写操作，执行前确认源节点与目标位置。\n- 用户给的是知识库 URL（`...\u002Fwiki\u002F\u003Ctoken>`），且后续要查成员\u002F加成员\u002F删成员：先调用 `lark-cli wiki spaces get_node --params '{\"token\":\"\u003Cwiki_token>\"}'` 获取 `space_id`，后续成员接口统一使用 `space_id`。\n- 用户要**删除**知识空间（`wiki +delete-space`）但只给了名称或 URL：**不能**把名称 \u002F URL 原样传给 `--space-id`，必须先解析出真实 `space_id`。解析方式：\n  - URL（`...\u002Fwiki\u002F\u003Ctoken>`）：`lark-cli wiki spaces get_node --params '{\"token\":\"\u003Cwiki_token>\"}' --format json`，读 `data.node.space_id`。\n  - 只知名称：`lark-cli wiki spaces list --format json`，边翻页边收集 items 并按 `name` 精确匹配；**一旦任一页累计到至少 1 条精确匹配就停止翻页**。只有当翻完所有页（`has_more=false`）仍无精确匹配时，才对已收集的全量 items 做宽松匹配（`name` trim 空格、大小写不敏感、子串包含）。\n  - **关键安全约束**：无论精确还是模糊，**无论命中 1 条还是多条，发起删除前都必须把候选（`name` + `space_id` + `description` + `space_type`）列给用户，由用户明确选定一个 `space_id` 再执行**。不要因为\"只命中一条\"就自动执行删除。\n  - 命中 0 条：停下来问用户是名称拼错了还是调用方无权限；**不要**自行改名字重试。\n  - 用户明确选定后再执行 `lark-cli wiki +delete-space --space-id \u003CID> --yes`（高风险写操作，必须显式 `--yes`）。\n  - 反例：不要把 wiki URL \u002F 名称直接当 `--space-id`（如 `--space-id \"https:\u002F\u002F...\u002Fwiki\u002F\u003Cwiki_token>\"`）；务必先用 `wiki spaces get_node` 解析出 `data.node.space_id` 再传。\n- 用户要在知识库中创建新节点，优先使用 `lark-cli wiki +node-create`。\n- 用户要列出 Wiki 节点：先用 `wiki +space-list --as user` 拿数字 `space_id`，再用 `wiki +node-list --space-id \u003Cspace_id>`。不要把 wiki URL、node token、doc token、名称直接当 `--space-id`。钻子节点时 `--parent-node-token` 必须是 wiki node token；如果用户给的是 docx\u002Fsheet\u002Fbase URL，先用 `wiki +node-get --node-token \u003Curl>` 解析出 `node_token`。\n- `wiki +node-list` 命中 `invalid_parameters`、`not_found`、`permission_denied` 时，不要重复调用同一参数；按 hint 修 `space_id` \u002F `parent_node_token` \u002F 权限。只有 `rate_limit` 才做退避重试。\n- 用户说“给知识库添加成员\u002F管理员”：先把目标解析成“用户 \u002F 群 \u002F 部门 \u002F 应用”四类之一，再决定 `--member-type`，不要先调 `wiki +member-add` 再根据报错反推类型。\n- 用户说“部门 + bot”：这是已知不支持路径。不要继续尝试 `wiki +member-add --as bot`；直接提示必须改成 `--as user`，或明确告知当前要求无法完成。\n- 用户说“用户 \u002F 群 \u002F 应用 + 添加成员”：先解析对应 ID，再执行 `wiki +member-add`。\n- 用户说“查看 \u002F 列出空间成员”：用 `wiki +member-list`；该 shortcut 默认只取一页，多成员场景显式加 `--page-all`。\n- 用户说“移除 \u002F 删除空间成员”：用 `wiki +member-remove`，必须传齐原始授予时的 `--member-type` 和 `--member-role`（不知道就先 `wiki +member-list` 查一下）。\n\n## Shortcuts（推荐优先使用）\n\nShortcut 是对常用操作的高级封装（`lark-cli wiki +\u003Cverb> [flags]`）。有 Shortcut 的操作优先使用。\n\n| Shortcut | 说明 |\n|----------|------|\n| [`+move`](references\u002Flark-wiki-move.md) | Move a wiki node, or move a Drive document into Wiki |\n| [`+move-to-drive`](references\u002Flark-wiki-move-to-drive.md) | Move a wiki node to a Drive folder and poll the async task |\n| [`+node-create`](references\u002Flark-wiki-node-create.md) | Create a wiki node with automatic space resolution |\n| [`+delete-space`](references\u002Flark-wiki-delete-space.md) | Delete a wiki space, polling the async delete task when needed |\n| [`+space-list`](references\u002Flark-wiki-space-list.md) | List all wiki spaces accessible to the caller |\n| [`+space-create`](references\u002Flark-wiki-space-create.md) | Create a wiki space (user identity only) |\n| [`+node-list`](references\u002Flark-wiki-node-list.md) | List wiki nodes in a space or under a parent node (supports pagination) |\n| [`+node-copy`](references\u002Flark-wiki-node-copy.md) | Copy a wiki node to a target space or parent node |\n| [`+node-get`](references\u002Flark-wiki-node-get.md) | Get a wiki node's details by node_token \u002F obj_token \u002F Lark URL |\n| [`+node-delete`](references\u002Flark-wiki-node-delete.md) | Delete a wiki node, polling the async delete task when needed |\n| [`+member-add`](references\u002Flark-wiki-member-add.md) | Add a member to a wiki space |\n| [`+member-remove`](references\u002Flark-wiki-member-remove.md) | Remove a member from a wiki space |\n| [`+member-list`](references\u002Flark-wiki-member-list.md) | List members of a wiki space (supports pagination) |\n\n## 成员添加流程\n\n- 调用 `lark-cli wiki +member-add` 前，先把自然语言里的“人 \u002F 群 \u002F 部门 \u002F 应用”解析成正确的 `--member-id`，不要猜格式。\n- 用户场景默认优先 `--member-type=openid`：用 `lark-cli contact +search-user --query \"\u003C姓名\u002F邮箱\u002F手机号>\" --format json` 获取 `open_id`。\n- 群组场景使用 `--member-type=openchat`：用 `lark-cli im +chat-search --query \"\u003C群名关键词>\" --format json` 获取 `chat_id`。\n- 应用场景使用 `--member-type=appid`：`--member-id` 传应用 ID，格式通常为 `cli_xxx`。\n- `userid` \u002F `unionid` 只在下游明确要求时才使用；先拿到 `open_id`，再调用 `lark-cli api GET \u002Fopen-apis\u002Fcontact\u002Fv3\u002Fusers\u002F\u003Copen_id> --params '{\"user_id_type\":\"open_id\"}' --format json` 读取 `user_id` \u002F `union_id`。\n- 部门场景使用 `--member-type=opendepartmentid`：当前 CLI 没有 shortcut，需调用 `lark-cli api POST \u002Fopen-apis\u002Fcontact\u002Fv3\u002Fdepartments\u002Fsearch --as user --params '{\"department_id_type\":\"open_department_id\"}' --data '{\"query\":\"\u003C部门名>\"}'` 获取 `open_department_id`。\n- 只有在目标类型和身份都已确认可行后，才调用 `lark-cli wiki +member-add`。对于部门场景，这意味着必须是 `--as user`。\n\n## 目标语义约束\n\n- `我的文档库` \u002F `My Document Library` \u002F `我的知识库` \u002F `个人知识库` \u002F `my_library` 都应视为 **Wiki personal library**，不是 Drive 根目录\n- 处理这类目标时，先解析 `my_library` 对应的真实 `space_id`，再执行 `wiki +move`、`wiki +node-create` 或其他 Wiki 写操作\n- 不要因为缺少显式 `space_id` 就退化成 `drive +move`\n- 如果用户明确说的是 Drive 文件夹、云空间（云盘\u002F云存储）根目录、`我的空间`，再按源对象分流：源对象是 Wiki 节点时用 `wiki +move-to-drive`，源对象已在 Drive 时用 `drive +move`\n\n## API Resources\n\n```bash\nlark-cli schema wiki.\u003Cresource>.\u003Cmethod>   # 调用原生 API 前必须先查看 --data \u002F --params 参数结构，不要猜测字段格式\nlark-cli wiki \u003Cresource> \u003Cmethod> [flags]  # 调用 API\n```\n\n### spaces\n\n- `create` — 创建知识空间\n- `get` — 获取知识空间信息\n- `get_node` — 获取知识空间节点信息\n- `list` — 获取知识空间列表\n\n### members\n\n- `create` — 添加知识空间成员\n- `delete` — 删除知识空间成员\n- `list` — 获取知识空间成员列表\n\n### nodes\n\n- `copy` — 创建知识空间节点副本\n- `create` — 创建知识空间节点\n- `list` — 获取知识空间子节点列表\n\n## 不在本 skill 范围\n\n- 上传 \u002F 下载文件到知识库节点下 → [`lark-drive`](..\u002Flark-drive\u002FSKILL.md)（`drive +upload --wiki-token`）\n- 编辑文档正文内容 → [`lark-doc`](..\u002Flark-doc\u002FSKILL.md)\n- 表格 \u002F 多维表格数据操作 → [`lark-sheets`](..\u002Flark-sheets\u002FSKILL.md) \u002F [`lark-base`](..\u002Flark-base\u002FSKILL.md)\n- 按名称搜索文档 \u002F Wiki \u002F 表格文件、评论与权限管理 → [`lark-drive`](..\u002Flark-drive\u002FSKILL.md)\n",{"name":5,"version":39,"metadata":40,"description":7},"1.0.3",{"cliHelp":41,"requires":42},"lark-cli wiki --help",{"bins":43},[44],"lark-cli","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fzlsbksdxl\u002Fcodex-lark\u002Fskills\u002Flark-wiki",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill lark-wiki",{"tool":61,"command":62},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill lark-wiki",{"tool":64,"command":65},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill lark-wiki","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fzlsbksdxl\u002Fcodex-lark\u002Fskills\u002Flark-wiki\u002FSKILL.md",true,[69,75,79,83,87,91,95,99,103,107,111,115,119],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Flark-wiki-delete-space.md","REFERENCE","参考文档",8452,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fzlsbksdxl\u002Fcodex-lark\u002Fskills\u002Flark-wiki\u002Freferences\u002Flark-wiki-delete-space.md",{"path":76,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Flark-wiki-member-add.md",3536,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fzlsbksdxl\u002Fcodex-lark\u002Fskills\u002Flark-wiki\u002Freferences\u002Flark-wiki-member-add.md",{"path":80,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Flark-wiki-member-list.md",2876,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fzlsbksdxl\u002Fcodex-lark\u002Fskills\u002Flark-wiki\u002Freferences\u002Flark-wiki-member-list.md",{"path":84,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Flark-wiki-member-remove.md",2899,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fzlsbksdxl\u002Fcodex-lark\u002Fskills\u002Flark-wiki\u002Freferences\u002Flark-wiki-member-remove.md",{"path":88,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Flark-wiki-move-to-drive.md",4570,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fzlsbksdxl\u002Fcodex-lark\u002Fskills\u002Flark-wiki\u002Freferences\u002Flark-wiki-move-to-drive.md",{"path":92,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Flark-wiki-move.md",10105,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fzlsbksdxl\u002Fcodex-lark\u002Fskills\u002Flark-wiki\u002Freferences\u002Flark-wiki-move.md",{"path":96,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Flark-wiki-node-copy.md",2398,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fzlsbksdxl\u002Fcodex-lark\u002Fskills\u002Flark-wiki\u002Freferences\u002Flark-wiki-node-copy.md",{"path":100,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Flark-wiki-node-create.md",6742,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fzlsbksdxl\u002Fcodex-lark\u002Fskills\u002Flark-wiki\u002Freferences\u002Flark-wiki-node-create.md",{"path":104,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Flark-wiki-node-delete.md",3003,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fzlsbksdxl\u002Fcodex-lark\u002Fskills\u002Flark-wiki\u002Freferences\u002Flark-wiki-node-delete.md",{"path":108,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":109,"sourceHtmlUrl":110},"references\u002Flark-wiki-node-get.md",2623,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fzlsbksdxl\u002Fcodex-lark\u002Fskills\u002Flark-wiki\u002Freferences\u002Flark-wiki-node-get.md",{"path":112,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":113,"sourceHtmlUrl":114},"references\u002Flark-wiki-node-list.md",4098,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fzlsbksdxl\u002Fcodex-lark\u002Fskills\u002Flark-wiki\u002Freferences\u002Flark-wiki-node-list.md",{"path":116,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":117,"sourceHtmlUrl":118},"references\u002Flark-wiki-space-create.md",1573,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fzlsbksdxl\u002Fcodex-lark\u002Fskills\u002Flark-wiki\u002Freferences\u002Flark-wiki-space-create.md",{"path":120,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":121,"sourceHtmlUrl":122},"references\u002Flark-wiki-space-list.md",2236,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fzlsbksdxl\u002Fcodex-lark\u002Fskills\u002Flark-wiki\u002Freferences\u002Flark-wiki-space-list.md",[124,134,142,150,158,166],{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":128,"licenseFileUrl":129,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":133},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":128,"licenseFileUrl":138,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":133},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":128,"licenseFileUrl":146,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":133},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":128,"licenseFileUrl":154,"sourceHtmlUrl":155,"categories":156,"keywords":157,"publishedAt":133},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":128,"licenseFileUrl":162,"sourceHtmlUrl":163,"categories":164,"keywords":165,"publishedAt":133},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":128,"licenseFileUrl":170,"sourceHtmlUrl":171,"categories":172,"keywords":173,"publishedAt":133},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]