[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71529YDTSK320VR702CY2QM":3,"skill-same:01M71529YDTSK320VR702CY2QM":65},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":14,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":50,"install":51,"resources":64},"01M71529YDTSK320VR702CY2QM","acceptance-orchestrator",null,"Use when a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention.","sapsapshen\u002Fai-memory-router","sapsapshen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F20347959?v=4","01M6XDQEF1DP50DKF37H81J3J5","shenmian","01M6XDQEJPE41Y3DT2763X8ZJN",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcursor\u002Facceptance-orchestrator\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"acceptance orchestrator","orchestrator","acceptance","implementation","issue","safe","2026","human","verification","with","review","task","when","use","minimal","intake","end","re","deployment","community","2026-11-10 10:12:30",false,"---\nname: acceptance-orchestrator\ndescription: Use when a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention.\nrisk: safe\nsource: community\ndate_added: \"2026-03-12\"\n---\n\n# Acceptance Orchestrator\n\n## Overview\n\nOrchestrate coding work as a state machine that ends only when acceptance criteria are verified with evidence or the task is explicitly escalated.\n\nCore rule: **do not optimize for \"code changed\"; optimize for \"DoD proven\".**\n\n## Required Sub-Skills\n\n- `create-issue-gate`\n- `closed-loop-delivery`\n- `verification-before-completion`\n\nOptional supporting skills:\n- `deploy-dev`\n- `pr-watch`\n- `pr-review-autopilot`\n- `git-ship`\n\n## Inputs\n\nRequire these inputs:\n- issue id or issue body\n- issue status\n- acceptance criteria (DoD)\n- target environment (`dev` default)\n\nFixed defaults:\n- max iteration rounds = `2`\n- PR review polling = `3m -> 6m -> 10m`\n\n## State Machine\n\n- `intake`\n- `issue-gated`\n- `executing`\n- `review-loop`\n- `deploy-verify`\n- `accepted`\n- `escalated`\n\n## Workflow\n\n1. **Intake**\n   - Read issue and extract task goal + DoD.\n\n2. **Issue gate**\n   - Use `create-issue-gate` logic.\n   - If issue is not `ready` or execution gate is not `allowed`, stop immediately.\n   - Do not implement anything while issue remains `draft`.\n\n3. **Execute**\n   - Hand off to `closed-loop-delivery` for implementation and local verification.\n\n4. **Review loop**\n   - If PR feedback is relevant, batch polling windows as:\n     - wait `3m`\n     - then `6m`\n     - then `10m`\n   - After the `10m` round, stop waiting and process all visible comments together.\n\n5. **Deploy and runtime verification**\n   - If DoD depends on runtime behavior, deploy only to `dev` by default.\n   - Verify with real logs\u002FAPI\u002FLambda behavior, not assumptions.\n\n6. **Completion gate**\n   - Before any claim of completion, require `verification-before-completion`.\n   - No success claim without fresh evidence.\n\n## Stop Conditions\n\nMove to `accepted` only when every acceptance criterion has matching evidence.\n\nMove to `escalated` when any of these happen:\n- DoD still fails after `2` full rounds\n- missing secrets\u002Fpermissions\u002Fexternal dependency blocks progress\n- task needs production action or destructive operation approval\n- review instructions conflict and cannot both be satisfied\n\n## Human Gates\n\nAlways stop for human confirmation on:\n- prod\u002Fstage deploys beyond agreed scope\n- destructive git\u002Fdata operations\n- billing or security posture changes\n- missing user-provided acceptance criteria\n\n## Output Contract\n\nWhen reporting status, always include:\n- `Status`: intake \u002F executing \u002F accepted \u002F escalated\n- `Acceptance Criteria`: pass\u002Ffail checklist\n- `Evidence`: commands, logs, API results, or runtime proof\n- `Open Risks`: anything still uncertain\n- `Need Human Input`: smallest next decision, if blocked\n\nDo not report \"done\" unless status is `accepted`.\n","# Acceptance Orchestrator\n\n## Overview\n\nOrchestrate coding work as a state machine that ends only when acceptance criteria are verified with evidence or the task is explicitly escalated.\n\nCore rule: **do not optimize for \"code changed\"; optimize for \"DoD proven\".**\n\n## Required Sub-Skills\n\n- `create-issue-gate`\n- `closed-loop-delivery`\n- `verification-before-completion`\n\nOptional supporting skills:\n- `deploy-dev`\n- `pr-watch`\n- `pr-review-autopilot`\n- `git-ship`\n\n## Inputs\n\nRequire these inputs:\n- issue id or issue body\n- issue status\n- acceptance criteria (DoD)\n- target environment (`dev` default)\n\nFixed defaults:\n- max iteration rounds = `2`\n- PR review polling = `3m -> 6m -> 10m`\n\n## State Machine\n\n- `intake`\n- `issue-gated`\n- `executing`\n- `review-loop`\n- `deploy-verify`\n- `accepted`\n- `escalated`\n\n## Workflow\n\n1. **Intake**\n   - Read issue and extract task goal + DoD.\n\n2. **Issue gate**\n   - Use `create-issue-gate` logic.\n   - If issue is not `ready` or execution gate is not `allowed`, stop immediately.\n   - Do not implement anything while issue remains `draft`.\n\n3. **Execute**\n   - Hand off to `closed-loop-delivery` for implementation and local verification.\n\n4. **Review loop**\n   - If PR feedback is relevant, batch polling windows as:\n     - wait `3m`\n     - then `6m`\n     - then `10m`\n   - After the `10m` round, stop waiting and process all visible comments together.\n\n5. **Deploy and runtime verification**\n   - If DoD depends on runtime behavior, deploy only to `dev` by default.\n   - Verify with real logs\u002FAPI\u002FLambda behavior, not assumptions.\n\n6. **Completion gate**\n   - Before any claim of completion, require `verification-before-completion`.\n   - No success claim without fresh evidence.\n\n## Stop Conditions\n\nMove to `accepted` only when every acceptance criterion has matching evidence.\n\nMove to `escalated` when any of these happen:\n- DoD still fails after `2` full rounds\n- missing secrets\u002Fpermissions\u002Fexternal dependency blocks progress\n- task needs production action or destructive operation approval\n- review instructions conflict and cannot both be satisfied\n\n## Human Gates\n\nAlways stop for human confirmation on:\n- prod\u002Fstage deploys beyond agreed scope\n- destructive git\u002Fdata operations\n- billing or security posture changes\n- missing user-provided acceptance criteria\n\n## Output Contract\n\nWhen reporting status, always include:\n- `Status`: intake \u002F executing \u002F accepted \u002F escalated\n- `Acceptance Criteria`: pass\u002Ffail checklist\n- `Evidence`: commands, logs, API results, or runtime proof\n- `Open Risks`: anything still uncertain\n- `Need Human Input`: smallest next decision, if blocked\n\nDo not report \"done\" unless status is `accepted`.\n",{"name":5,"risk":24,"source":38,"date_added":44,"description":7},"2026-03-12","main","7a38d8e7073e61c16eda85681cb32fb68a8657a5","skills-store\u002Fcursor\u002Facceptance-orchestrator","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router","https:\u002F\u002Fgithub.com\u002Fsapsapshen","2026-04-14 21:12:12",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add sapsapshen\u002Fai-memory-router --skill acceptance-orchestrator",{"tool":57,"command":58},"bunx","bunx skills add sapsapshen\u002Fai-memory-router --skill acceptance-orchestrator",{"tool":60,"command":61},"pnpm","pnpm dlx skills add sapsapshen\u002Fai-memory-router --skill acceptance-orchestrator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcursor\u002Facceptance-orchestrator\u002FSKILL.md",true,[],[66,89,114,124,137,156],{"skillNo":67,"name":68,"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":77,"publishedAt":39},"01M71ATQRKG48SH06FQ697T5G9","wechat-search","Search WeChat Official Account articles using OpenClaw's web search and fetch capabilities with compliance-focused design.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fwechat-search-release\u002FSKILL.md",[72],{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[78,79,80,81,82,83,84,85,86,87,88,28],"wechat search","wechat","search","capabilities","openclaw","design","web search","compliance","web","official","fetch",{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":39},"01M71ATNAVGZB35PFYM2GC5N00","trend-tap","Real-time trending topics aggregator across 7 platforms (X\u002FTwitter, Reddit, Google Trends, Hacker News, Zhihu, Bilibili, Weibo). Trigger: when user says 'trend', 'trends', 'trend tap', '热点', '热搜', or asks what is trending\u002Fhot. Do NOT use web_search — this skill already fetches live data from all platforms with zero API keys.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftrend-tap\u002FSKILL.md",[],[96,97,98,99,100,101,80,102,103,104,105,31,106,107,108,109,110,111,112,113],"trend","trend tap","tap","api keys","Bash","time","trending","hacker","aggregator","do","brew","live","data","google","install","read","across","api",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":39},"01M71ATJ9AM5KM15AA8PS302EB","trend-radar","Real-time trending topics aggregator across 7 platforms (X\u002FTwitter, Reddit, Google Trends, Hacker News, Zhihu, Bilibili, Weibo). Trigger: when user says 'trend', 'trends', 'trend pulse', '热点', '热搜', or asks what is trending\u002Fhot. Do NOT use web_search — this skill already fetches live data from all platforms with zero API keys.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftrend-radar\u002FSKILL.md",[],[121,122,96,106,107,108,109,100,80,111,123,112,113,31,104,103,102,110,101,99],"trend radar","radar","pulse",{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":39},"01M71ATGF095N3EJM9G8SD0BB5","tech-news-daily","每日科技新闻汇——从全球多个 RSS 源抓取最新科技新闻，翻译（英→中）、去重、排版成每日简报。当用户询问科技新闻、科技新鲜事、每日科技、技术动态、Daily Tech News 或类似表达时触发此技能。","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftech-news-daily\u002FSKILL.md",[],[131,132,133,134,135,136],"news","tech","tech news daily","daily","rss","翻译",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":148,"publishedAt":39},"01M71ATFAEAMQ17M70NQNY7SR8","summarize","Summarize URLs or files with the summarize CLI (web, PDFs, images, audio, YouTube).","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fsummarize\u002FSKILL.md",[143],{"categoryNo":144,"categoryName":145,"taxonomyType":146,"taxonomyTypeDesc":147},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[139,86,149,150,151,28,106,152,153,154,98,155,110],"Audio","cli","youtube","images","https","files","pdfs",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":39},"01M71ATDNS3R0M4H936PACQAWZ","sonoscli","Control Sonos speakers (discover\u002Fstatus\u002Fplay\u002Fvolume\u002Fgroup).","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fsonoscli\u002FSKILL.md",[],[158,163,164,165,110,166,153,167,168,169,170,171],"status","play","go","latest","github","discover","control","cmd","volume"]