[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KVT2R84Y6VH5E4C05FGJK7":3,"skill-same:01M6KVT2R84Y6VH5E4C05FGJK7":71},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M6KVT2R84Y6VH5E4C05FGJK7","digital_employee",null,"根据一句业务需求，自动规划并创建一组分工明确的数字员工（Agent），再把他们编排成一条工作流，无需逐个手工创建。","mateaix\u002Fmateclaw","mateaix","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F57164338?v=4","01M6KVQ3JXJP7M6D3BKS2BAMFF","01M6KVQ3Q8YG7DT57AY22TBXGG",1196,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmateaix\u002Fmateclaw\u002Fblob\u002Fdev\u002Fmateclaw-server\u002Fsrc\u002Fmain\u002Fresources\u002Fskills\u002Fdigital_employee\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33],"digital employee","workflow","create","generate","team","list","catalog","builder","draft","digital_employee,agent,workflow,team","capability","2026-11-10 10:12:30",false,"---\nname: digital_employee\nnameZh: 数字员工组建\nnameEn: Digital Employee Builder\nversion: \"1.0.0\"\nicon: \"?‍?\"\ndescription: \"根据一句业务需求，自动规划并创建一组分工明确的数字员工（Agent），再把他们编排成一条工作流，无需逐个手工创建。\"\ntags: digital_employee,agent,workflow,team\ndependencies:\n  tools:\n    - listAvailableAgents\n    - list_capability_catalog\n    - create_employee\n    - workflow_draft_generate\n---\n\n# 数字员工组建\n\n把一句业务需求，变成「一支分工明确的数字员工团队 + 一条把他们串起来的工作流」。用户不必逐个设计、逐个手工创建 Agent。\n\n## 何时使用\n\n- 用户描述了一个**需要多个角色协作**的目标（\"帮我搭一个做竞品分析的团队\"、\"我要一套从线索到成交的销售流程\"）。\n- 用户说\"建几个 Agent \u002F 数字员工帮我做 X\"、\"把 X 这件事自动化成一支团队\"。\n- 现有 Agent 不足以覆盖需求，需要新建专才角色。\n\n## 不应使用\n\n- 一个 Agent 就能完成 → 直接用 `chat_with_agent` 或现有 Agent。\n- 只是想编排**已存在**的 Agent 协作 → 用 `multi_agent_collaboration`。\n- 只是想把流程做成工作流，且员工都已存在 → 直接用 `workflow_draft_generate`。\n\n## 工作流程\n\n### 第一步：理解需求，盘点现状\n\n1. 读懂用户的业务目标、产出物、是否有触发条件（定时 \u002F 来消息时）、要不要审批、结果发到哪个渠道。\n2. 调用 `listAvailableAgents()` 看现有员工——**能复用就复用**，不要重复造同名角色。\n3. 调用 `list_capability_catalog()` 拿到可分配的**技能名**和**工具名**清单。后续 `create_employee` 只能用清单里的真实名字，不要臆造。\n\n如果需求关键信息缺失（产出物、角色边界），先向用户澄清一句再继续，不要凭空假设。\n\n### 第二步：设计团队（2–6 个角色）\n\n把目标拆成**互补的角色**，每个角色给出：\n\n- `name`：工作区内唯一，用英文 kebab-case（如 `market-research-analyst`）。\n- `description`：一句话职责，工作流编排器会据此分配任务。\n- `systemPrompt`：定义这个员工的专长、视角、工作方式——要具体，别写空话。\n- `skillNames` \u002F `toolNames`：从 `list_capability_catalog()` 里挑这个角色真正需要的；**留空则继承全局默认能力**（通才）。专才角色建议显式收窄。\n- `agentType`：默认 `react`；只有当角色需要\"先规划再分步执行\"时才用 `plan_execute`。\n\n设计原则：\n\n- 角色数量 2–6 个，宁少勿滥；每个角色职责单一、边界清晰。\n- 避免两个角色职责重叠。\n- 一般不指定 `modelName`，留空用工作区默认模型；用户明确要求某模型时才填。\n\n### 第三步：逐个创建员工\n\n对每个设计好的角色调用一次 `create_employee(...)`：\n\n```\ncreate_employee(\n  name=\"market-research-analyst\",\n  description=\"负责竞品功能、定价、市场动态的检索与结构化整理\",\n  systemPrompt=\"你是资深市场研究分析师……（写清专长与产出格式）\",\n  skillNames=[\"news\", \"web_search\"],   \u002F\u002F 来自 list_capability_catalog，可留空\n  toolNames=[\"web_search\"]              \u002F\u002F 来自 list_capability_catalog，可留空\n)\n```\n\n- 工具会返回 `agentId` 和实际绑定的技能\u002F工具；**记下每个员工的 name**，下一步要用。\n- 若返回 `[error]`（如重名），换个名字重试，不要中断整个流程。\n- 创建即启用——员工立刻可被工作流引用。\n\n### 第四步：编排工作流\n\n所有员工创建完成后，调用一次 `workflow_draft_generate(description=...)`。在 `description` 里：\n\n- **点名第三步创建的真实员工**（用它们的 name），说明执行顺序、依赖关系、并行还是串行。\n- 写清触发条件、是否需要审批、产出发往哪个渠道。\n\n由于员工已经落库，`workflow_draft_generate` 会读到它们作为可用数字员工，直接引用真实 agent，而不是填 `TODO_*_AGENT` 占位。\n\n> 工作流只会保存为**草稿**，不会自动发布、不会自动启用触发器。这是安全约定——让用户在工作流编辑器里 review 后再 publish。\n\n### 第五步：汇报\n\n给用户一份清晰小结：\n\n- 创建了哪些员工（name + 职责 + 绑定的关键能力）。\n- 生成的工作流草稿名称、id、各步骤如何串联。\n- 草稿编译预校验是否通过、有无缺失字段需要补。\n- 明确告知：工作流是草稿，请到工作流编辑器确认后再发布。\n\n## 关键规则\n\n- 员工 name 用英文 kebab-case 且工作区内唯一；工作流 step.name \u002F outputVar 的命名约束由 `workflow_draft_generate` 负责，本技能不必操心。\n- 技能名 \u002F 工具名必须来自 `list_capability_catalog()`，臆造的名字会被静默跳过。\n- 先创建员工，**再**生成工作流——顺序不能反，否则工作流只能拿到占位符。\n- 能复用现有 Agent 就复用，避免制造一堆同质化角色。\n- 不自动发布工作流，不自动启用触发器。\n","# 数字员工组建\n\n把一句业务需求，变成「一支分工明确的数字员工团队 + 一条把他们串起来的工作流」。用户不必逐个设计、逐个手工创建 Agent。\n\n## 何时使用\n\n- 用户描述了一个**需要多个角色协作**的目标（\"帮我搭一个做竞品分析的团队\"、\"我要一套从线索到成交的销售流程\"）。\n- 用户说\"建几个 Agent \u002F 数字员工帮我做 X\"、\"把 X 这件事自动化成一支团队\"。\n- 现有 Agent 不足以覆盖需求，需要新建专才角色。\n\n## 不应使用\n\n- 一个 Agent 就能完成 → 直接用 `chat_with_agent` 或现有 Agent。\n- 只是想编排**已存在**的 Agent 协作 → 用 `multi_agent_collaboration`。\n- 只是想把流程做成工作流，且员工都已存在 → 直接用 `workflow_draft_generate`。\n\n## 工作流程\n\n### 第一步：理解需求，盘点现状\n\n1. 读懂用户的业务目标、产出物、是否有触发条件（定时 \u002F 来消息时）、要不要审批、结果发到哪个渠道。\n2. 调用 `listAvailableAgents()` 看现有员工——**能复用就复用**，不要重复造同名角色。\n3. 调用 `list_capability_catalog()` 拿到可分配的**技能名**和**工具名**清单。后续 `create_employee` 只能用清单里的真实名字，不要臆造。\n\n如果需求关键信息缺失（产出物、角色边界），先向用户澄清一句再继续，不要凭空假设。\n\n### 第二步：设计团队（2–6 个角色）\n\n把目标拆成**互补的角色**，每个角色给出：\n\n- `name`：工作区内唯一，用英文 kebab-case（如 `market-research-analyst`）。\n- `description`：一句话职责，工作流编排器会据此分配任务。\n- `systemPrompt`：定义这个员工的专长、视角、工作方式——要具体，别写空话。\n- `skillNames` \u002F `toolNames`：从 `list_capability_catalog()` 里挑这个角色真正需要的；**留空则继承全局默认能力**（通才）。专才角色建议显式收窄。\n- `agentType`：默认 `react`；只有当角色需要\"先规划再分步执行\"时才用 `plan_execute`。\n\n设计原则：\n\n- 角色数量 2–6 个，宁少勿滥；每个角色职责单一、边界清晰。\n- 避免两个角色职责重叠。\n- 一般不指定 `modelName`，留空用工作区默认模型；用户明确要求某模型时才填。\n\n### 第三步：逐个创建员工\n\n对每个设计好的角色调用一次 `create_employee(...)`：\n\n```\ncreate_employee(\n  name=\"market-research-analyst\",\n  description=\"负责竞品功能、定价、市场动态的检索与结构化整理\",\n  systemPrompt=\"你是资深市场研究分析师……（写清专长与产出格式）\",\n  skillNames=[\"news\", \"web_search\"],   \u002F\u002F 来自 list_capability_catalog，可留空\n  toolNames=[\"web_search\"]              \u002F\u002F 来自 list_capability_catalog，可留空\n)\n```\n\n- 工具会返回 `agentId` 和实际绑定的技能\u002F工具；**记下每个员工的 name**，下一步要用。\n- 若返回 `[error]`（如重名），换个名字重试，不要中断整个流程。\n- 创建即启用——员工立刻可被工作流引用。\n\n### 第四步：编排工作流\n\n所有员工创建完成后，调用一次 `workflow_draft_generate(description=...)`。在 `description` 里：\n\n- **点名第三步创建的真实员工**（用它们的 name），说明执行顺序、依赖关系、并行还是串行。\n- 写清触发条件、是否需要审批、产出发往哪个渠道。\n\n由于员工已经落库，`workflow_draft_generate` 会读到它们作为可用数字员工，直接引用真实 agent，而不是填 `TODO_*_AGENT` 占位。\n\n> 工作流只会保存为**草稿**，不会自动发布、不会自动启用触发器。这是安全约定——让用户在工作流编辑器里 review 后再 publish。\n\n### 第五步：汇报\n\n给用户一份清晰小结：\n\n- 创建了哪些员工（name + 职责 + 绑定的关键能力）。\n- 生成的工作流草稿名称、id、各步骤如何串联。\n- 草稿编译预校验是否通过、有无缺失字段需要补。\n- 明确告知：工作流是草稿，请到工作流编辑器确认后再发布。\n\n## 关键规则\n\n- 员工 name 用英文 kebab-case 且工作区内唯一；工作流 step.name \u002F outputVar 的命名约束由 `workflow_draft_generate` 负责，本技能不必操心。\n- 技能名 \u002F 工具名必须来自 `list_capability_catalog()`，臆造的名字会被静默跳过。\n- 先创建员工，**再**生成工作流——顺序不能反，否则工作流只能拿到占位符。\n- 能复用现有 Agent 就复用，避免制造一堆同质化角色。\n- 不自动发布工作流，不自动启用触发器。\n",{"icon":39,"name":5,"tags":32,"nameEn":40,"nameZh":41,"version":42,"description":7,"dependencies":43},"?‍?","Digital Employee Builder","数字员工组建","1.0.0",{"tools":44},[45,46,47,48],"listAvailableAgents","list_capability_catalog","create_employee","workflow_draft_generate","dev","11106843d72d25b29c2cd08d7fdbbd222c21df6a","mateclaw-server\u002Fsrc\u002Fmain\u002Fresources\u002Fskills\u002Fdigital_employee",361,"https:\u002F\u002Fgithub.com\u002Fmateaix\u002Fmateclaw","https:\u002F\u002Fclaw.mate.vip","https:\u002F\u002Fgithub.com\u002Fmateaix","2026-11-13 15:43:14",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add mateaix\u002Fmateclaw --skill digital_employee",{"tool":63,"command":64},"bunx","bunx skills add mateaix\u002Fmateclaw --skill digital_employee",{"tool":66,"command":67},"pnpm","pnpm dlx skills add mateaix\u002Fmateclaw --skill digital_employee","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmateaix\u002Fmateclaw\u002Fblob\u002Fdev\u002Fmateclaw-server\u002Fsrc\u002Fmain\u002Fresources\u002Fskills\u002Fdigital_employee\u002FSKILL.md",true,[],[72,83,116,142,168,187],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":79,"publishedAt":34},"01M6KW155AABG05Q3FR8CN3D9H","sample","Test fixture for SkillBundleMaterializer.","https:\u002F\u002Fgithub.com\u002Fmateaix\u002Fmateclaw\u002Fblob\u002Fdev\u002Fmateclaw-server\u002Fsrc\u002Ftest\u002Fresources\u002Ftest-bundles\u002Fsample\u002FSKILL.md",[78],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[74,80,81,82],"test","for","fixture",{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":94,"publishedAt":34},"01M6KW0P1T4EGBRN0HYZKJSHGB","xhs_note","小红书图文创作 \u002F 笔记 \u002F 种草文案 (xiaohongshu \u002F red note) — 端到端：成文→配图(≥3 张竖版)→去AI化→在线预览打包交付。以图为主、文字辅助：标题四件套 + 碎句正文 + 话题标签，配 3:4 竖版卡片，最少 3 张图。honors user persona & style memory.","https:\u002F\u002Fgithub.com\u002Fmateaix\u002Fmateclaw\u002Fblob\u002Fdev\u002Fmateclaw-server\u002Fsrc\u002Fmain\u002Fresources\u002Fskills\u002Fxhs_note\u002FSKILL.md",[89],{"categoryNo":90,"categoryName":91,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115],"note","xhs note","xhs","创作","persona","memory","红书","user","red","图文","内容创作","style","小红书","笔记","xiaohongshu","去AI化","linux","文案","windows","macos","文字",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":123,"publishedAt":34},"01M6KW0J69PPWSCVSR6JVJ0P1F","x_intel","Read X (Twitter) posts, search, timelines and user profiles via the official xurl CLI.","https:\u002F\u002Fgithub.com\u002Fmateaix\u002Fmateclaw\u002Fblob\u002Fdev\u002Fmateclaw-server\u002Fsrc\u002Fmain\u002Fresources\u002Fskills\u002Fx_intel\u002FSKILL.md",[122],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[124,125,126,127,128,129,130,131,132,133,111,134,135,136,137,138,139,140,141,114],"x intel","shell","xurl","execute","twitter","social-media","via","profiles","research","true","read","command","cli","social","search","official","Media","posts",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":156,"publishedAt":34},"01M6KW0DEPAYEF2JQ70PGN0Y8D","writing-plans","Write implementation plans: bite-sized tasks, paths, code.","https:\u002F\u002Fgithub.com\u002Fmateaix\u002Fmateclaw\u002Fblob\u002Fdev\u002Fmateclaw-server\u002Fsrc\u002Fmain\u002Fresources\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[148,151,154,155],{"categoryNo":149,"categoryName":150,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":152,"categoryName":153,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":90,"categoryName":91,"taxonomyType":92,"taxonomyTypeDesc":93},[157,158,159,160,161,162,163,164,165,166,24,167],"plans","writing plans","writing","implementation","planning","paths","write","documentation","tasks","code","design",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":175,"publishedAt":34},"01M6KW08Q6EEN0ZSH5JRMAFH0B","webhook-subscriptions","Webhook subscriptions: event-driven agent runs.","https:\u002F\u002Fgithub.com\u002Fmateaix\u002Fmateclaw\u002Fblob\u002Fdev\u002Fmateclaw-server\u002Fsrc\u002Fmain\u002Fresources\u002Fskills\u002Fwebhook-subscriptions\u002FSKILL.md",[174],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[176,177,178,179,180,181,182,183,184,185,186],"subscriptions","webhook subscriptions","webhook","event-driven","automation","event","integrations","push","events","notifications","driven",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":191,"categories":192,"keywords":200,"publishedAt":34},"01M6KW04W8S4EMJHSNHY3HWAY3","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002Fmateaix\u002Fmateclaw\u002Fblob\u002Fdev\u002Fmateclaw-server\u002Fsrc\u002Fmain\u002Fresources\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[193,196,199],{"categoryNo":194,"categoryName":195,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":197,"categoryName":198,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[201,80,186,202,203,103,204,205,206,207,166,208,209,210],"development","test driven development","quality","tdd","tests","enforce","refactor","testing","red-green-refactor","green"]