[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BY7PENDZFWR7SX8TDXS67W":3,"skill-same:01M7BY7PENDZFWR7SX8TDXS67W":50},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7BY7PENDZFWR7SX8TDXS67W","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.","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills-claude\u002Fskills\u002Facceptance-orchestrator\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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## When to Use\n- The task already has an issue or clear acceptance criteria and should run end-to-end with minimal human re-intervention.\n- You need structured handoff across implementation, review, deployment, and final verification.\n- You want explicit stop conditions and escalation instead of silent partial completion.\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\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\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## When to Use\n- The task already has an issue or clear acceptance criteria and should run end-to-end with minimal human re-intervention.\n- You need structured handoff across implementation, review, deployment, and final verification.\n- You want explicit stop conditions and escalation instead of silent partial completion.\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\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n",{"name":5,"risk":24,"source":25,"date_added":26,"description":7},"safe","community","2026-03-12","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills-claude\u002Fskills\u002Facceptance-orchestrator",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill acceptance-orchestrator",{"tool":42,"command":43},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill acceptance-orchestrator",{"tool":45,"command":46},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill acceptance-orchestrator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills-claude\u002Fskills\u002Facceptance-orchestrator\u002FSKILL.md",true,[],[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]