[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M756WPMYMX7C27VJP3SGSCFF":3,"skill-same:01M756WPMYMX7C27VJP3SGSCFF":45},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M756WPMYMX7C27VJP3SGSCFF","mcp-builder",null,"MCP 服务器构建方法论 — 系统化构建生产级 MCP 工具，让 AI 助手连接外部能力","loudon84\u002Fnodeskclaw","loudon84","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F230070284?v=4","01M756SKTCF4G9W4JRJZA2V6X7","loudon","01M756SKVFJWH4J0G80K0FJPJK",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Floudon84\u002Fnodeskclaw\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fmcp-builder\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: mcp-builder\ndescription: MCP 服务器构建方法论 — 系统化构建生产级 MCP 工具，让 AI 助手连接外部能力\n---\n\n# MCP 服务器构建\n\n系统化设计、实现、测试和部署 Model Context Protocol 服务器的方法论。\n\n## 1. 协议核心概念\n\nMCP 定义三种原语：\n\n- **Tools（工具）**：AI 助手主动调用的函数，有副作用。如搜索、创建、删除操作。\n- **Resources（资源）**：AI 助手只读访问的数据源，用 URI 标识。如 `users:\u002F\u002F{id}\u002Fprofile`。\n- **Prompts（提示词模板）**：预定义交互模板，引导用户触发工作流。\n\n**选择原则：** 执行操作 → Tool | 读取数据 → Resource | 引导交互 → Prompt\n\n## 2. 项目结构规范\n\n### TypeScript\n```\nmy-mcp-server\u002F\n├── src\u002F\n│   ├── index.ts          # 入口，注册 tools\u002Fresources\n│   ├── tools\u002F             # 按功能拆分\n│   ├── resources\u002F\n│   └── lib\u002F               # 客户端封装、校验逻辑\n├── tests\u002F\n├── package.json\n└── tsconfig.json\n```\n\n关键依赖：`@modelcontextprotocol\u002Fsdk` + `zod`\n\n### Python\n```\nmy-mcp-server\u002F\n├── src\u002Fmy_mcp_server\u002F\n│   ├── server.py\n│   ├── tools\u002F\n│   └── lib\u002F\n├── tests\u002F\n└── pyproject.toml\n```\n\n关键依赖：`mcp` + `pydantic`\n\n## 3. Tool 设计原则\n\n### 命名\n- `snake_case` 格式，动词开头：`search_users`、`create_issue`、`delete_file`\n- 名称自解释，AI 助手靠名称选工具，模糊命名导致误调用\n\n### 参数\n- 每个参数有类型约束和 `.describe()` 描述\n- 可选参数给默认值，减少 AI 决策负担\n- 用枚举代替布尔开关\n\n```typescript\nserver.tool(\"search_issues\", {\n  query: z.string().describe(\"搜索关键词\"),\n  status: z.enum([\"open\", \"closed\", \"all\"]).default(\"open\").describe(\"状态筛选\"),\n  limit: z.number().min(1).max(100).default(20).describe(\"返回上限\"),\n}, async ({ query, status, limit }) => { \u002F* ... *\u002F });\n```\n\n### 描述\n说明**用途 + 返回内容 + 限制**，这是 AI 选择工具的关键依据：\n\n```typescript\nserver.tool(\"search_users\",\n  \"根据姓名或邮箱搜索用户。返回 ID、姓名、邮箱列表。模糊匹配，最多 50 条。\",\n  schema, handler);\n```\n\n### 输出\n- 结构化数据 → JSON，人类可读内容 → Markdown\n- 始终用 `content: [{ type: \"text\", text: \"...\" }]` 格式返回\n\n## 4. 输入验证和错误处理\n\n用 Zod\u002FPydantic 做 Schema 级校验，业务级校验放 handler 开头：\n\n```typescript\nserver.tool(\"get_user\", { id: z.string() }, async ({ id }) => {\n  try {\n    const user = await db.getUser(id);\n    if (!user) {\n      return {\n        content: [{ type: \"text\", text: `用户 ${id} 不存在，请检查 ID。` }],\n        isError: true,\n      };\n    }\n    return { content: [{ type: \"text\", text: JSON.stringify(user, null, 2) }] };\n  } catch (err) {\n    return {\n      content: [{ type: \"text\", text: `查询失败：${err.message}` }],\n      isError: true,\n    };\n  }\n});\n```\n\n**错误处理四原则：**\n1. 永远不让服务器崩溃 — try\u002Fcatch 包裹所有外部调用\n2. 返回可操作的错误信息 — 告诉 AI 问题是什么、能做什么\n3. 使用 `isError: true` — 让 AI 知道调用失败\n4. 区分错误类型 — 参数错误、权限不足、资源不存在、服务不可用\n\n## 5. 资源管理和生命周期\n\n```typescript\n\u002F\u002F 资源注册\nserver.resource(\"user-profile\", \"users:\u002F\u002F{userId}\u002Fprofile\", async (uri) => {\n  const profile = await db.getProfile(extractId(uri));\n  return { contents: [{ uri: uri.href, mimeType: \"application\u002Fjson\", text: JSON.stringify(profile) }] };\n});\n\n\u002F\u002F 生命周期：先初始化 → 再 connect → 监听关闭信号\nconst db = await Database.connect(config.dbUrl);\nawait server.connect(new StdioServerTransport());\nprocess.on(\"SIGINT\", async () => { await db.disconnect(); await server.close(); process.exit(0); });\n```\n\n关键点：使用连接池、所有外部调用设超时、优雅关闭清理资源。\n\n## 6. 测试策略\n\n### 单元测试 — 业务逻辑与 MCP 注册分离\n```typescript\n\u002F\u002F tools\u002Fsearch.ts 导出纯函数\nexport async function searchUsers(query: string, limit: number) { \u002F* ... *\u002F }\n\n\u002F\u002F search.test.ts 独立测试\ntest(\"返回匹配结果\", async () => {\n  const results = await searchUsers(\"alice\", 10);\n  expect(results[0].name).toContain(\"Alice\");\n});\n```\n\n### 集成测试 — 用 SDK Client 做端到端验证\n```typescript\nconst [clientTransport, serverTransport] = InMemoryTransport.createLinkedPair();\nawait server.connect(serverTransport);\nconst client = new Client({ name: \"test\", version: \"1.0.0\" });\nawait client.connect(clientTransport);\nconst result = await client.callTool(\"search_users\", { query: \"test\" });\nexpect(result.isError).toBeFalsy();\n```\n\n### MCP Inspector — 交互式调试\n```bash\nnpx @modelcontextprotocol\u002Finspector node dist\u002Findex.js\n```\n\n在浏览器中查看所有 tools\u002Fresources，手动调用并查看结果。\n\n**测试要点：** 每个 Tool 覆盖正常 + 异常路径、边界值、外部服务失败模拟。\n\n## 7. 安全考虑\n\n**权限控制：**\n- 最小权限原则，读写 Tool 分离\n- 危险操作要求确认参数（如 `confirm: true`）\n\n**输入安全：**\n- SQL 注入 → 参数化查询，绝不拼接\n- 路径遍历 → 校验路径，禁止 `..\u002F`\n- 命令注入 → 用 `execFile` 而非 `exec`\n\n**敏感数据：**\n- 密钥通过环境变量传入，不硬编码\n- 日志不打印完整敏感信息\n- 返回数据做脱敏处理\n\n**沙箱：** 文件操作限制目录、网络请求限制白名单、设置资源配额。\n\n## 8. 部署和分发\n\n### npm 发布\n```json\n{ \"bin\": { \"mcp-server-myservice\": \"dist\u002Findex.js\" }, \"files\": [\"dist\"] }\n```\n\n用户配置：\n```json\n{ \"mcpServers\": { \"myservice\": { \"command\": \"npx\", \"args\": [\"@yourorg\u002Fmcp-server-myservice\"], \"env\": { \"API_KEY\": \"xxx\" } } } }\n```\n\n### pip 发布\n```toml\n[project.scripts]\nmcp-server-myservice = \"my_mcp_server.server:main\"\n```\n\n### Docker — 适用于复杂依赖或隔离场景\n```dockerfile\nFROM node:20-slim\nWORKDIR \u002Fapp\nCOPY package*.json .\u002F && RUN npm ci --production\nCOPY dist .\u002Fdist\nENTRYPOINT [\"node\", \"dist\u002Findex.js\"]\n```\n\n## 9. 调试技巧\n\n**关键：MCP 用 stdio 通信，不能用 `console.log`，会破坏协议流。**\n\n```typescript\n\u002F\u002F 错误\nconsole.log(\"debug\");\n\u002F\u002F 正确\nconsole.error(\"[DEBUG]\", info);\n\u002F\u002F 更好\nserver.sendLoggingMessage({ level: \"info\", data: \"处理中\" });\n```\n\n**常见问题：**\n\n| 症状 | 原因 | 解决 |\n|------|------|------|\n| 启动无响应 | transport 未连接 | 检查 `server.connect()` |\n| Tool 不出现 | 注册在 connect 之后 | 先注册再 connect |\n| AI 不调用 Tool | 描述不清晰 | 改善名称和描述 |\n| 参数总错 | Schema 不明确 | 添加 `.describe()` |\n| 调用超时 | 外部服务慢 | 加超时和缓存 |\n\n**调试流程：** Inspector 验证基本功能 → 手动调用确认输入输出 → 连接真实 AI 客户端观察调用模式 → 根据实际行为调整设计。\n\n## 10. 构建检查清单\n\n### 设计\n- [ ] 明确 Tools vs Resources vs Prompts 分工\n- [ ] Tool 命名 `动词_名词`，描述说明用途和返回内容\n- [ ] 参数简洁，可选参数有合理默认值\n\n### 实现\n- [ ] 输入用 Zod\u002FPydantic 校验\n- [ ] 外部调用有 try\u002Fcatch 和超时\n- [ ] 错误返回 `isError: true` 并附可操作信息\n- [ ] 不用 `console.log`（用 stderr 或 SDK 日志）\n- [ ] 敏感数据走环境变量\n\n### 测试\n- [ ] 核心逻辑有单元测试\n- [ ] 有集成测试验证 MCP 协议交互\n- [ ] 用 MCP Inspector 手动验证过\n- [ ] 用真实 AI 客户端测试过\n\n### 部署\n- [ ] README 含安装和配置说明\n- [ ] 提供客户端配置 JSON 示例\n- [ ] 遵循 semver，无硬编码密钥\n","# MCP 服务器构建\n\n系统化设计、实现、测试和部署 Model Context Protocol 服务器的方法论。\n\n## 1. 协议核心概念\n\nMCP 定义三种原语：\n\n- **Tools（工具）**：AI 助手主动调用的函数，有副作用。如搜索、创建、删除操作。\n- **Resources（资源）**：AI 助手只读访问的数据源，用 URI 标识。如 `users:\u002F\u002F{id}\u002Fprofile`。\n- **Prompts（提示词模板）**：预定义交互模板，引导用户触发工作流。\n\n**选择原则：** 执行操作 → Tool | 读取数据 → Resource | 引导交互 → Prompt\n\n## 2. 项目结构规范\n\n### TypeScript\n```\nmy-mcp-server\u002F\n├── src\u002F\n│   ├── index.ts          # 入口，注册 tools\u002Fresources\n│   ├── tools\u002F             # 按功能拆分\n│   ├── resources\u002F\n│   └── lib\u002F               # 客户端封装、校验逻辑\n├── tests\u002F\n├── package.json\n└── tsconfig.json\n```\n\n关键依赖：`@modelcontextprotocol\u002Fsdk` + `zod`\n\n### Python\n```\nmy-mcp-server\u002F\n├── src\u002Fmy_mcp_server\u002F\n│   ├── server.py\n│   ├── tools\u002F\n│   └── lib\u002F\n├── tests\u002F\n└── pyproject.toml\n```\n\n关键依赖：`mcp` + `pydantic`\n\n## 3. Tool 设计原则\n\n### 命名\n- `snake_case` 格式，动词开头：`search_users`、`create_issue`、`delete_file`\n- 名称自解释，AI 助手靠名称选工具，模糊命名导致误调用\n\n### 参数\n- 每个参数有类型约束和 `.describe()` 描述\n- 可选参数给默认值，减少 AI 决策负担\n- 用枚举代替布尔开关\n\n```typescript\nserver.tool(\"search_issues\", {\n  query: z.string().describe(\"搜索关键词\"),\n  status: z.enum([\"open\", \"closed\", \"all\"]).default(\"open\").describe(\"状态筛选\"),\n  limit: z.number().min(1).max(100).default(20).describe(\"返回上限\"),\n}, async ({ query, status, limit }) => { \u002F* ... *\u002F });\n```\n\n### 描述\n说明**用途 + 返回内容 + 限制**，这是 AI 选择工具的关键依据：\n\n```typescript\nserver.tool(\"search_users\",\n  \"根据姓名或邮箱搜索用户。返回 ID、姓名、邮箱列表。模糊匹配，最多 50 条。\",\n  schema, handler);\n```\n\n### 输出\n- 结构化数据 → JSON，人类可读内容 → Markdown\n- 始终用 `content: [{ type: \"text\", text: \"...\" }]` 格式返回\n\n## 4. 输入验证和错误处理\n\n用 Zod\u002FPydantic 做 Schema 级校验，业务级校验放 handler 开头：\n\n```typescript\nserver.tool(\"get_user\", { id: z.string() }, async ({ id }) => {\n  try {\n    const user = await db.getUser(id);\n    if (!user) {\n      return {\n        content: [{ type: \"text\", text: `用户 ${id} 不存在，请检查 ID。` }],\n        isError: true,\n      };\n    }\n    return { content: [{ type: \"text\", text: JSON.stringify(user, null, 2) }] };\n  } catch (err) {\n    return {\n      content: [{ type: \"text\", text: `查询失败：${err.message}` }],\n      isError: true,\n    };\n  }\n});\n```\n\n**错误处理四原则：**\n1. 永远不让服务器崩溃 — try\u002Fcatch 包裹所有外部调用\n2. 返回可操作的错误信息 — 告诉 AI 问题是什么、能做什么\n3. 使用 `isError: true` — 让 AI 知道调用失败\n4. 区分错误类型 — 参数错误、权限不足、资源不存在、服务不可用\n\n## 5. 资源管理和生命周期\n\n```typescript\n\u002F\u002F 资源注册\nserver.resource(\"user-profile\", \"users:\u002F\u002F{userId}\u002Fprofile\", async (uri) => {\n  const profile = await db.getProfile(extractId(uri));\n  return { contents: [{ uri: uri.href, mimeType: \"application\u002Fjson\", text: JSON.stringify(profile) }] };\n});\n\n\u002F\u002F 生命周期：先初始化 → 再 connect → 监听关闭信号\nconst db = await Database.connect(config.dbUrl);\nawait server.connect(new StdioServerTransport());\nprocess.on(\"SIGINT\", async () => { await db.disconnect(); await server.close(); process.exit(0); });\n```\n\n关键点：使用连接池、所有外部调用设超时、优雅关闭清理资源。\n\n## 6. 测试策略\n\n### 单元测试 — 业务逻辑与 MCP 注册分离\n```typescript\n\u002F\u002F tools\u002Fsearch.ts 导出纯函数\nexport async function searchUsers(query: string, limit: number) { \u002F* ... *\u002F }\n\n\u002F\u002F search.test.ts 独立测试\ntest(\"返回匹配结果\", async () => {\n  const results = await searchUsers(\"alice\", 10);\n  expect(results[0].name).toContain(\"Alice\");\n});\n```\n\n### 集成测试 — 用 SDK Client 做端到端验证\n```typescript\nconst [clientTransport, serverTransport] = InMemoryTransport.createLinkedPair();\nawait server.connect(serverTransport);\nconst client = new Client({ name: \"test\", version: \"1.0.0\" });\nawait client.connect(clientTransport);\nconst result = await client.callTool(\"search_users\", { query: \"test\" });\nexpect(result.isError).toBeFalsy();\n```\n\n### MCP Inspector — 交互式调试\n```bash\nnpx @modelcontextprotocol\u002Finspector node dist\u002Findex.js\n```\n\n在浏览器中查看所有 tools\u002Fresources，手动调用并查看结果。\n\n**测试要点：** 每个 Tool 覆盖正常 + 异常路径、边界值、外部服务失败模拟。\n\n## 7. 安全考虑\n\n**权限控制：**\n- 最小权限原则，读写 Tool 分离\n- 危险操作要求确认参数（如 `confirm: true`）\n\n**输入安全：**\n- SQL 注入 → 参数化查询，绝不拼接\n- 路径遍历 → 校验路径，禁止 `..\u002F`\n- 命令注入 → 用 `execFile` 而非 `exec`\n\n**敏感数据：**\n- 密钥通过环境变量传入，不硬编码\n- 日志不打印完整敏感信息\n- 返回数据做脱敏处理\n\n**沙箱：** 文件操作限制目录、网络请求限制白名单、设置资源配额。\n\n## 8. 部署和分发\n\n### npm 发布\n```json\n{ \"bin\": { \"mcp-server-myservice\": \"dist\u002Findex.js\" }, \"files\": [\"dist\"] }\n```\n\n用户配置：\n```json\n{ \"mcpServers\": { \"myservice\": { \"command\": \"npx\", \"args\": [\"@yourorg\u002Fmcp-server-myservice\"], \"env\": { \"API_KEY\": \"xxx\" } } } }\n```\n\n### pip 发布\n```toml\n[project.scripts]\nmcp-server-myservice = \"my_mcp_server.server:main\"\n```\n\n### Docker — 适用于复杂依赖或隔离场景\n```dockerfile\nFROM node:20-slim\nWORKDIR \u002Fapp\nCOPY package*.json .\u002F && RUN npm ci --production\nCOPY dist .\u002Fdist\nENTRYPOINT [\"node\", \"dist\u002Findex.js\"]\n```\n\n## 9. 调试技巧\n\n**关键：MCP 用 stdio 通信，不能用 `console.log`，会破坏协议流。**\n\n```typescript\n\u002F\u002F 错误\nconsole.log(\"debug\");\n\u002F\u002F 正确\nconsole.error(\"[DEBUG]\", info);\n\u002F\u002F 更好\nserver.sendLoggingMessage({ level: \"info\", data: \"处理中\" });\n```\n\n**常见问题：**\n\n| 症状 | 原因 | 解决 |\n|------|------|------|\n| 启动无响应 | transport 未连接 | 检查 `server.connect()` |\n| Tool 不出现 | 注册在 connect 之后 | 先注册再 connect |\n| AI 不调用 Tool | 描述不清晰 | 改善名称和描述 |\n| 参数总错 | Schema 不明确 | 添加 `.describe()` |\n| 调用超时 | 外部服务慢 | 加超时和缓存 |\n\n**调试流程：** Inspector 验证基本功能 → 手动调用确认输入输出 → 连接真实 AI 客户端观察调用模式 → 根据实际行为调整设计。\n\n## 10. 构建检查清单\n\n### 设计\n- [ ] 明确 Tools vs Resources vs Prompts 分工\n- [ ] Tool 命名 `动词_名词`，描述说明用途和返回内容\n- [ ] 参数简洁，可选参数有合理默认值\n\n### 实现\n- [ ] 输入用 Zod\u002FPydantic 校验\n- [ ] 外部调用有 try\u002Fcatch 和超时\n- [ ] 错误返回 `isError: true` 并附可操作信息\n- [ ] 不用 `console.log`（用 stderr 或 SDK 日志）\n- [ ] 敏感数据走环境变量\n\n### 测试\n- [ ] 核心逻辑有单元测试\n- [ ] 有集成测试验证 MCP 协议交互\n- [ ] 用 MCP Inspector 手动验证过\n- [ ] 用真实 AI 客户端测试过\n\n### 部署\n- [ ] README 含安装和配置说明\n- [ ] 提供客户端配置 JSON 示例\n- [ ] 遵循 semver，无硬编码密钥\n",{"name":5,"description":7},"main","469ae3b28fb2a5ce3449f10148c9a4a6176b89b9",".cursor\u002Fskills\u002Fmcp-builder",1,"https:\u002F\u002Fgithub.com\u002Floudon84\u002Fnodeskclaw","https:\u002F\u002Fgithub.com\u002Floudon84","2026-10-23 16:15:34",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add loudon84\u002Fnodeskclaw --skill mcp-builder",{"tool":37,"command":38},"bunx","bunx skills add loudon84\u002Fnodeskclaw --skill mcp-builder",{"tool":40,"command":41},"pnpm","pnpm dlx skills add loudon84\u002Fnodeskclaw --skill mcp-builder","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Floudon84\u002Fnodeskclaw\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fmcp-builder\u002FSKILL.md",true,[],[46,53,60,67,73,80],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M756YPY12MWG00RKYW7E3BG1","live-attachment-ack","RM-18 live fixture. Acknowledge a prompt-first request. Do not read files or call tools.","https:\u002F\u002Fgithub.com\u002Floudon84\u002Fnodeskclaw\u002Fblob\u002Fmain\u002Ftools\u002Facceptance\u002Ffixtures\u002Frm18-live-attachment-ack\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M756YKW5Z87DF043K7JJ0HZ5","live-old-runtime-probe","RM-16 PC-09 fixture. Bind only to a Hermes API Server older than v2026.8.31.","https:\u002F\u002Fgithub.com\u002Floudon84\u002Fnodeskclaw\u002Fblob\u002Fmain\u002Ftools\u002Facceptance\u002Ffixtures\u002Frm16-pc09-live-old-runtime-probe\u002FSKILL.md",[],[],{"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":19},"01M756YHKPZ4YNN5BMA5P6JTC5","content-video-clone-workflow","Sanitized video clone workflow preserving login, upload, analysis, rewrite, generation, and manifest actions","https:\u002F\u002Fgithub.com\u002Floudon84\u002Fnodeskclaw\u002Fblob\u002Fmain\u002Fnodeskclaw-backend\u002Ftests\u002Ffixtures\u002Fagent_bundles\u002Fp5_video_clone_real_sanitized\u002Fskills\u002Fcontent-video-clone-workflow\u002FSKILL.md",[],[],{"skillNo":68,"name":62,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M756YDJQ3FC97J35B40P6288","Mock video clone workflow covering upload, analysis polling, and generation polling","https:\u002F\u002Fgithub.com\u002Floudon84\u002Fnodeskclaw\u002Fblob\u002Fmain\u002Fnodeskclaw-backend\u002Ftests\u002Ffixtures\u002Fagent_bundles\u002Fp5_video_clone_mock_agent\u002Fskills\u002Fcontent-video-clone-workflow\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M756YAJTC2PXNY6FGBPE1GCJ","oauth-probe","Checks mock OAuth broker access through tokenRef","https:\u002F\u002Fgithub.com\u002Floudon84\u002Fnodeskclaw\u002Fblob\u002Fmain\u002Fnodeskclaw-backend\u002Ftests\u002Ffixtures\u002Fagent_bundles\u002Fp4_oauth_probe_agent\u002Fskills\u002Foauth-probe\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M756Y888TCGNCRBWA7CDVCBA","resource-profile","Verifies resource recommendation metadata","https:\u002F\u002Fgithub.com\u002Floudon84\u002Fnodeskclaw\u002Fblob\u002Fmain\u002Fnodeskclaw-backend\u002Ftests\u002Ffixtures\u002Fagent_bundles\u002Fp3_resource_profile_agent\u002Fskills\u002Fresourceful\u002FSKILL.md",[],[]]