[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MPH9HXFC7P4AVJ4ZV09P4P":3,"skill-same:01M6MPH9HXFC7P4AVJ4ZV09P4P":59},{"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":25,"linkOnly":26,"markdownContent":27,"markdownBody":28,"frontMatter":29,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":40,"ownerHtmlUrl":41,"ownerBlogUrl":42,"ownerDescription":43,"updatedAt":44,"install":45,"resources":58},"01M6MPH9HXFC7P4AVJ4ZV09P4P","lark-openapi-explorer",null,"飞书\u002FLark 原生 OpenAPI 探索：从官方文档库中挖掘未经 CLI 封装的原生 OpenAPI 接口。当用户的需求无法被现有 lark-* skill 或 lark-cli 已注册命令满足，需要查找并调用原生飞书 OpenAPI 时使用。","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1571,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fzlsbksdxl\u002Fcodex-lark\u002Fskills\u002Flark-openapi-explorer\u002FSKILL.md",[],[19,20,21,22,23,24],"openapi","explorer","lark openapi explorer","lark","cli","文档","2026-11-10 10:12:30",false,"---\nname: lark-openapi-explorer\nversion: 1.0.0\ndescription: \"飞书\u002FLark 原生 OpenAPI 探索：从官方文档库中挖掘未经 CLI 封装的原生 OpenAPI 接口。当用户的需求无法被现有 lark-* skill 或 lark-cli 已注册命令满足，需要查找并调用原生飞书 OpenAPI 时使用。\"\nmetadata:\n  requires:\n    bins: [\"lark-cli\"]\n---\n\n# OpenAPI Explorer\n\n> **前置条件：** 先阅读 [`..\u002Flark-shared\u002FSKILL.md`](..\u002Flark-shared\u002FSKILL.md) 了解认证、身份切换和安全规则。\n\n当用户的需求**无法被现有 skill 或 CLI 已注册 API 覆盖**时，使用本技能从飞书官方 markdown 文档库中逐层挖掘原生 OpenAPI 接口，然后通过 `lark-cli api` 裸调完成任务。\n\n## 文档库结构\n\n飞书 OpenAPI 文档以 markdown 层级组织：\n\n```\nllms.txt                          ← 顶层索引，列出所有模块文档链接\n  └─ llms-\u003Cmodule>.txt            ← 模块文档，包含功能概述 + 底层 API 文档链接\n       └─ \u003Capi-doc>.md            ← 单个 API 的完整说明（方法\u002F路径\u002F参数\u002F响应\u002F错误码）\n```\n\n文档入口：\n\n| 品牌 | 入口 URL |\n|------|----------|\n| 飞书 (Feishu) | `https:\u002F\u002Fopen.feishu.cn\u002Fllms.txt` |\n| Lark | `https:\u002F\u002Fopen.larksuite.com\u002Fllms.txt` |\n\n> 所有文档以**中文**编写。如果用户使用英文交流，需将文档内容翻译为英文后输出。\n\n## 挖掘流程\n\n严格按以下步骤逐层检索，**不要跳步或猜测 API**：\n\n### Step 1：确认现有能力不足\n\n```bash\n# 先检查是否已有对应的 skill 或已注册 API\nlark-cli \u003C可能的service> --help\n```\n\n如果已有对应命令或 shortcut，直接使用，**不需要继续挖掘**。\n\n### Step 2：从顶层索引定位模块\n\n用 WebFetch 获取顶层索引，找到与需求相关的模块文档链接：\n\n```\nWebFetch https:\u002F\u002Fopen.feishu.cn\u002Fllms.txt\n  → 提取问题：\"列出所有模块文档链接，找出与 \u003C用户需求关键词> 相关的链接\"\n```\n\n- 飞书品牌使用 `open.feishu.cn`\n- Lark 品牌使用 `open.larksuite.com`\n- 如不确定用户品牌，默认使用飞书\n\n### Step 3：从模块文档定位具体 API\n\n用 WebFetch 获取模块文档，找到具体 API 的文档链接：\n\n```\nWebFetch https:\u002F\u002Fopen.feishu.cn\u002Fllms-docs\u002Fzh-CN\u002Fllms-\u003Cmodule>.txt\n  → 提取问题：\"找出与 \u003C用户需求> 相关的 API 说明和文档链接\"\n```\n\n### Step 4：获取 API 完整规范\n\n用 WebFetch 获取具体 API 文档，提取完整的调用规范：\n\n```\nWebFetch https:\u002F\u002Fopen.feishu.cn\u002Fdocument\u002Fserver-docs\u002F...\u002F\u003Capi>.md\n  → 提取问题：\"返回完整 API 规范：HTTP 方法、URL 路径、路径参数、查询参数、请求体字段（名称\u002F类型\u002F必填\u002F说明）、响应字段、所需权限、错误码\"\n```\n\n### Step 5：通过 CLI 调用 API\n\n使用 `lark-cli api` 裸调：\n\n```bash\n# GET 请求\nlark-cli api GET \u002Fopen-apis\u002F\u003Cpath> --params '{\"key\":\"value\"}'\n\n# POST 请求\nlark-cli api POST \u002Fopen-apis\u002F\u003Cpath> --data '{\"key\":\"value\"}'\n\n# PUT 请求\nlark-cli api PUT \u002Fopen-apis\u002F\u003Cpath> --data '{\"key\":\"value\"}'\n\n# DELETE 请求\nlark-cli api DELETE \u002Fopen-apis\u002F\u003Cpath>\n```\n\n## 输出规范\n\n向用户呈现挖掘结果时，按以下格式组织：\n\n1. **API 名称与功能**：一句话描述\n2. **HTTP 方法与路径**：`METHOD \u002Fopen-apis\u002F...`\n3. **关键参数**：列出必填和常用可选参数\n4. **所需权限**：scope 列表\n5. **调用示例**：给出 `lark-cli api` 的完整命令\n6. **注意事项**：频率限制、特殊约束等\n\n如果用户使用英文交流，将以上所有内容翻译为英文。\n\n## 安全规则\n\n- **写入\u002F删除类 API**（POST\u002FPUT\u002FDELETE）调用前必须确认用户意图\n- 建议先用 `--dry-run` 预览请求（如支持）\n- 不要猜测 API 路径或参数——必须从文档中获取确认\n- 涉及敏感操作（删除群、移除成员等）时，向用户说明影响范围\n\n## 使用场景示例\n\n### 场景 1：用户需要拉人进群（未被 CLI 封装）\n\n```bash\n# Step 1: 确认 CLI 没有封装\nlark-cli im --help\n# → 发现没有 chat_members 相关的 create 命令\n\n# Step 2-4: 通过文档挖掘获得 API 规范\n# → POST \u002Fopen-apis\u002Fim\u002Fv1\u002Fchats\u002F:chat_id\u002Fmembers\n\n# Step 5: 调用\nlark-cli api POST \u002Fopen-apis\u002Fim\u002Fv1\u002Fchats\u002Foc_xxx\u002Fmembers \\\n  --data '{\"id_list\":[\"ou_xxx\",\"ou_yyy\"]}' \\\n  --params '{\"member_id_type\":\"open_id\"}'\n```\n\n### 场景 2：用户需要设置群公告\n\n```bash\n# Step 1: 确认 CLI 没有封装\nlark-cli im --help\n# → 没有 announcement 相关命令\n\n# Step 2-4: 挖掘文档\n# → PATCH \u002Fopen-apis\u002Fim\u002Fv1\u002Fchats\u002F:chat_id\u002Fannouncement\n\n# Step 5: 调用\nlark-cli api PATCH \u002Fopen-apis\u002Fim\u002Fv1\u002Fchats\u002Foc_xxx\u002Fannouncement \\\n  --data '{\"revision\":\"0\",\"requests\":[\"\u003Chtml>公告内容\u003C\u002Fhtml>\"]}'\n```\n\n## 参考\n\n- [lark-shared](..\u002Flark-shared\u002FSKILL.md) — 认证和全局参数\n- [lark-skill-maker](..\u002Flark-skill-maker\u002FSKILL.md) — 如需将挖掘到的 API 固化为新 Skill\n","# OpenAPI Explorer\n\n> **前置条件：** 先阅读 [`..\u002Flark-shared\u002FSKILL.md`](..\u002Flark-shared\u002FSKILL.md) 了解认证、身份切换和安全规则。\n\n当用户的需求**无法被现有 skill 或 CLI 已注册 API 覆盖**时，使用本技能从飞书官方 markdown 文档库中逐层挖掘原生 OpenAPI 接口，然后通过 `lark-cli api` 裸调完成任务。\n\n## 文档库结构\n\n飞书 OpenAPI 文档以 markdown 层级组织：\n\n```\nllms.txt                          ← 顶层索引，列出所有模块文档链接\n  └─ llms-\u003Cmodule>.txt            ← 模块文档，包含功能概述 + 底层 API 文档链接\n       └─ \u003Capi-doc>.md            ← 单个 API 的完整说明（方法\u002F路径\u002F参数\u002F响应\u002F错误码）\n```\n\n文档入口：\n\n| 品牌 | 入口 URL |\n|------|----------|\n| 飞书 (Feishu) | `https:\u002F\u002Fopen.feishu.cn\u002Fllms.txt` |\n| Lark | `https:\u002F\u002Fopen.larksuite.com\u002Fllms.txt` |\n\n> 所有文档以**中文**编写。如果用户使用英文交流，需将文档内容翻译为英文后输出。\n\n## 挖掘流程\n\n严格按以下步骤逐层检索，**不要跳步或猜测 API**：\n\n### Step 1：确认现有能力不足\n\n```bash\n# 先检查是否已有对应的 skill 或已注册 API\nlark-cli \u003C可能的service> --help\n```\n\n如果已有对应命令或 shortcut，直接使用，**不需要继续挖掘**。\n\n### Step 2：从顶层索引定位模块\n\n用 WebFetch 获取顶层索引，找到与需求相关的模块文档链接：\n\n```\nWebFetch https:\u002F\u002Fopen.feishu.cn\u002Fllms.txt\n  → 提取问题：\"列出所有模块文档链接，找出与 \u003C用户需求关键词> 相关的链接\"\n```\n\n- 飞书品牌使用 `open.feishu.cn`\n- Lark 品牌使用 `open.larksuite.com`\n- 如不确定用户品牌，默认使用飞书\n\n### Step 3：从模块文档定位具体 API\n\n用 WebFetch 获取模块文档，找到具体 API 的文档链接：\n\n```\nWebFetch https:\u002F\u002Fopen.feishu.cn\u002Fllms-docs\u002Fzh-CN\u002Fllms-\u003Cmodule>.txt\n  → 提取问题：\"找出与 \u003C用户需求> 相关的 API 说明和文档链接\"\n```\n\n### Step 4：获取 API 完整规范\n\n用 WebFetch 获取具体 API 文档，提取完整的调用规范：\n\n```\nWebFetch https:\u002F\u002Fopen.feishu.cn\u002Fdocument\u002Fserver-docs\u002F...\u002F\u003Capi>.md\n  → 提取问题：\"返回完整 API 规范：HTTP 方法、URL 路径、路径参数、查询参数、请求体字段（名称\u002F类型\u002F必填\u002F说明）、响应字段、所需权限、错误码\"\n```\n\n### Step 5：通过 CLI 调用 API\n\n使用 `lark-cli api` 裸调：\n\n```bash\n# GET 请求\nlark-cli api GET \u002Fopen-apis\u002F\u003Cpath> --params '{\"key\":\"value\"}'\n\n# POST 请求\nlark-cli api POST \u002Fopen-apis\u002F\u003Cpath> --data '{\"key\":\"value\"}'\n\n# PUT 请求\nlark-cli api PUT \u002Fopen-apis\u002F\u003Cpath> --data '{\"key\":\"value\"}'\n\n# DELETE 请求\nlark-cli api DELETE \u002Fopen-apis\u002F\u003Cpath>\n```\n\n## 输出规范\n\n向用户呈现挖掘结果时，按以下格式组织：\n\n1. **API 名称与功能**：一句话描述\n2. **HTTP 方法与路径**：`METHOD \u002Fopen-apis\u002F...`\n3. **关键参数**：列出必填和常用可选参数\n4. **所需权限**：scope 列表\n5. **调用示例**：给出 `lark-cli api` 的完整命令\n6. **注意事项**：频率限制、特殊约束等\n\n如果用户使用英文交流，将以上所有内容翻译为英文。\n\n## 安全规则\n\n- **写入\u002F删除类 API**（POST\u002FPUT\u002FDELETE）调用前必须确认用户意图\n- 建议先用 `--dry-run` 预览请求（如支持）\n- 不要猜测 API 路径或参数——必须从文档中获取确认\n- 涉及敏感操作（删除群、移除成员等）时，向用户说明影响范围\n\n## 使用场景示例\n\n### 场景 1：用户需要拉人进群（未被 CLI 封装）\n\n```bash\n# Step 1: 确认 CLI 没有封装\nlark-cli im --help\n# → 发现没有 chat_members 相关的 create 命令\n\n# Step 2-4: 通过文档挖掘获得 API 规范\n# → POST \u002Fopen-apis\u002Fim\u002Fv1\u002Fchats\u002F:chat_id\u002Fmembers\n\n# Step 5: 调用\nlark-cli api POST \u002Fopen-apis\u002Fim\u002Fv1\u002Fchats\u002Foc_xxx\u002Fmembers \\\n  --data '{\"id_list\":[\"ou_xxx\",\"ou_yyy\"]}' \\\n  --params '{\"member_id_type\":\"open_id\"}'\n```\n\n### 场景 2：用户需要设置群公告\n\n```bash\n# Step 1: 确认 CLI 没有封装\nlark-cli im --help\n# → 没有 announcement 相关命令\n\n# Step 2-4: 挖掘文档\n# → PATCH \u002Fopen-apis\u002Fim\u002Fv1\u002Fchats\u002F:chat_id\u002Fannouncement\n\n# Step 5: 调用\nlark-cli api PATCH \u002Fopen-apis\u002Fim\u002Fv1\u002Fchats\u002Foc_xxx\u002Fannouncement \\\n  --data '{\"revision\":\"0\",\"requests\":[\"\u003Chtml>公告内容\u003C\u002Fhtml>\"]}'\n```\n\n## 参考\n\n- [lark-shared](..\u002Flark-shared\u002FSKILL.md) — 认证和全局参数\n- [lark-skill-maker](..\u002Flark-skill-maker\u002FSKILL.md) — 如需将挖掘到的 API 固化为新 Skill\n",{"name":5,"version":30,"metadata":31,"description":7},"1.0.0",{"requires":32},{"bins":33},[34],"lark-cli","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fzlsbksdxl\u002Fcodex-lark\u002Fskills\u002Flark-openapi-explorer",490,"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 02:12:02",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill lark-openapi-explorer",{"tool":51,"command":52},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill lark-openapi-explorer",{"tool":54,"command":55},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill lark-openapi-explorer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fzlsbksdxl\u002Fcodex-lark\u002Fskills\u002Flark-openapi-explorer\u002FSKILL.md",true,[],[60,68,75,82,108,133],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":67},"01M746ZWACVKMZ1BJXJZHYJSSX","migrate-to-e2e","Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for \u002Fmigrate-to-e2e, \"migrate our tests to e2e\", \"port these Maestro flows\", \"move our TesterArmy tests\", or when a project has an e2e config and an older suite still running.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fmigrate-to-e2e\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":67},"01M746ZPTAX1Q0FBKAB1CYND7E","e2e","Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fe2e\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":67},"01M746ZJN784HVHMDP9MQGCSGG","create-verification-skill","Generate a project-local verify-\u003Capp> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for \u002Fcreate-verification-skill, \"make a verification skill for this repo\", or when a project has no scripted way to prove UI behavior.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":25},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,23,106,107],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","when","you","done","reviewer","io","change","merge","past",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":25},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[115,116,117,104,118,119,120,121,122,123,124,125,126,127,94,128,129,130,131,132],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":150,"publishedAt":25},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[139,144,147],{"categoryNo":140,"categoryName":141,"taxonomyType":142,"taxonomyTypeDesc":143},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":145,"categoryName":146,"taxonomyType":142,"taxonomyTypeDesc":143},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":148,"categoryName":149,"taxonomyType":142,"taxonomyTypeDesc":143},"01JBSEEDCAT000000000000010","后端与接口",[135,151,152,153,154,155,156,129,157,95,158,159,160,161,100,162,163,164,165,166],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]