[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BFR3HCTFSF15AGYK3Q0D70":3,"skill-same:01M7BFR3HCTFSF15AGYK3Q0D70":48},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7BFR3HCTFSF15AGYK3Q0D70","claude-devfleet",null,"Orchestrate multi-agent coding tasks via Claude DevFleet — plan projects, dispatch parallel agents in isolated worktrees, monitor progress, and read structured reports.","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-AI-应用工具\u002FYYC3-AI-应用工具-Everything-claude-code\u002Fskills\u002Fclaude-devfleet\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: claude-devfleet\ndescription: Orchestrate multi-agent coding tasks via Claude DevFleet — plan projects, dispatch parallel agents in isolated worktrees, monitor progress, and read structured reports.\norigin: community\n---\n\n# Claude DevFleet Multi-Agent Orchestration\n\n## When to Use\n\nUse this skill when you need to dispatch multiple Claude Code agents to work on coding tasks in parallel. Each agent runs in an isolated git worktree with full tooling.\n\nRequires a running Claude DevFleet instance connected via MCP:\n```bash\nclaude mcp add devfleet --transport http http:\u002F\u002Flocalhost:18801\u002Fmcp\n```\n\n## How It Works\n\n```\nUser → \"Build a REST API with auth and tests\"\n  ↓\nplan_project(prompt) → project_id + mission DAG\n  ↓\nShow plan to user → get approval\n  ↓\ndispatch_mission(M1) → Agent 1 spawns in worktree\n  ↓\nM1 completes → auto-merge → auto-dispatch M2 (depends_on M1)\n  ↓\nM2 completes → auto-merge\n  ↓\nget_report(M2) → files_changed, what_done, errors, next_steps\n  ↓\nReport back to user\n```\n\n### Tools\n\n| Tool | Purpose |\n|------|---------|\n| `plan_project(prompt)` | AI breaks a description into a project with chained missions |\n| `create_project(name, path?, description?)` | Create a project manually, returns `project_id` |\n| `create_mission(project_id, title, prompt, depends_on?, auto_dispatch?)` | Add a mission. `depends_on` is a list of mission ID strings (e.g., `[\"abc-123\"]`). Set `auto_dispatch=true` to auto-start when deps are met. |\n| `dispatch_mission(mission_id, model?, max_turns?)` | Start an agent on a mission |\n| `cancel_mission(mission_id)` | Stop a running agent |\n| `wait_for_mission(mission_id, timeout_seconds?)` | Block until a mission completes (see note below) |\n| `get_mission_status(mission_id)` | Check mission progress without blocking |\n| `get_report(mission_id)` | Read structured report (files changed, tested, errors, next steps) |\n| `get_dashboard()` | System overview: running agents, stats, recent activity |\n| `list_projects()` | Browse all projects |\n| `list_missions(project_id, status?)` | List missions in a project |\n\n> **Note on `wait_for_mission`:** This blocks the conversation for up to `timeout_seconds` (default 600). For long-running missions, prefer polling with `get_mission_status` every 30–60 seconds instead, so the user sees progress updates.\n\n### Workflow: Plan → Dispatch → Monitor → Report\n\n1. **Plan**: Call `plan_project(prompt=\"...\")` → returns `project_id` + list of missions with `depends_on` chains and `auto_dispatch=true`.\n2. **Show plan**: Present mission titles, types, and dependency chain to the user.\n3. **Dispatch**: Call `dispatch_mission(mission_id=\u003Cfirst_mission_id>)` on the root mission (empty `depends_on`). Remaining missions auto-dispatch as their dependencies complete (because `plan_project` sets `auto_dispatch=true` on them).\n4. **Monitor**: Call `get_mission_status(mission_id=...)` or `get_dashboard()` to check progress.\n5. **Report**: Call `get_report(mission_id=...)` when missions complete. Share highlights with the user.\n\n### Concurrency\n\nDevFleet runs up to 3 concurrent agents by default (configurable via `DEVFLEET_MAX_AGENTS`). When all slots are full, missions with `auto_dispatch=true` queue in the mission watcher and dispatch automatically as slots free up. Check `get_dashboard()` for current slot usage.\n\n## Examples\n\n### Full auto: plan and launch\n\n1. `plan_project(prompt=\"...\")` → shows plan with missions and dependencies.\n2. Dispatch the first mission (the one with empty `depends_on`).\n3. Remaining missions auto-dispatch as dependencies resolve (they have `auto_dispatch=true`).\n4. Report back with project ID and mission count so the user knows what was launched.\n5. Poll with `get_mission_status` or `get_dashboard()` periodically until all missions reach a terminal state (`completed`, `failed`, or `cancelled`).\n6. `get_report(mission_id=...)` for each terminal mission — summarize successes and call out failures with errors and next steps.\n\n### Manual: step-by-step control\n\n1. `create_project(name=\"My Project\")` → returns `project_id`.\n2. `create_mission(project_id=project_id, title=\"...\", prompt=\"...\", auto_dispatch=true)` for the first (root) mission → capture `root_mission_id`.\n   `create_mission(project_id=project_id, title=\"...\", prompt=\"...\", auto_dispatch=true, depends_on=[\"\u003Croot_mission_id>\"])` for each subsequent task.\n3. `dispatch_mission(mission_id=...)` on the first mission to start the chain.\n4. `get_report(mission_id=...)` when done.\n\n### Sequential with review\n\n1. `create_project(name=\"...\")` → get `project_id`.\n2. `create_mission(project_id=project_id, title=\"Implement feature\", prompt=\"...\")` → get `impl_mission_id`.\n3. `dispatch_mission(mission_id=impl_mission_id)`, then poll with `get_mission_status` until complete.\n4. `get_report(mission_id=impl_mission_id)` to review results.\n5. `create_mission(project_id=project_id, title=\"Review\", prompt=\"...\", depends_on=[impl_mission_id], auto_dispatch=true)` — auto-starts since the dependency is already met.\n\n## Guidelines\n\n- Always confirm the plan with the user before dispatching, unless they said to go ahead.\n- Include mission titles and IDs when reporting status.\n- If a mission fails, read its report before retrying.\n- Check `get_dashboard()` for agent slot availability before bulk dispatching.\n- Mission dependencies form a DAG — do not create circular dependencies.\n- Each agent runs in an isolated git worktree and auto-merges on completion. If a merge conflict occurs, the changes remain on the agent's worktree branch for manual resolution.\n- When manually creating missions, always set `auto_dispatch=true` if you want them to trigger automatically when dependencies complete. Without this flag, missions stay in `draft` status.\n","# Claude DevFleet Multi-Agent Orchestration\n\n## When to Use\n\nUse this skill when you need to dispatch multiple Claude Code agents to work on coding tasks in parallel. Each agent runs in an isolated git worktree with full tooling.\n\nRequires a running Claude DevFleet instance connected via MCP:\n```bash\nclaude mcp add devfleet --transport http http:\u002F\u002Flocalhost:18801\u002Fmcp\n```\n\n## How It Works\n\n```\nUser → \"Build a REST API with auth and tests\"\n  ↓\nplan_project(prompt) → project_id + mission DAG\n  ↓\nShow plan to user → get approval\n  ↓\ndispatch_mission(M1) → Agent 1 spawns in worktree\n  ↓\nM1 completes → auto-merge → auto-dispatch M2 (depends_on M1)\n  ↓\nM2 completes → auto-merge\n  ↓\nget_report(M2) → files_changed, what_done, errors, next_steps\n  ↓\nReport back to user\n```\n\n### Tools\n\n| Tool | Purpose |\n|------|---------|\n| `plan_project(prompt)` | AI breaks a description into a project with chained missions |\n| `create_project(name, path?, description?)` | Create a project manually, returns `project_id` |\n| `create_mission(project_id, title, prompt, depends_on?, auto_dispatch?)` | Add a mission. `depends_on` is a list of mission ID strings (e.g., `[\"abc-123\"]`). Set `auto_dispatch=true` to auto-start when deps are met. |\n| `dispatch_mission(mission_id, model?, max_turns?)` | Start an agent on a mission |\n| `cancel_mission(mission_id)` | Stop a running agent |\n| `wait_for_mission(mission_id, timeout_seconds?)` | Block until a mission completes (see note below) |\n| `get_mission_status(mission_id)` | Check mission progress without blocking |\n| `get_report(mission_id)` | Read structured report (files changed, tested, errors, next steps) |\n| `get_dashboard()` | System overview: running agents, stats, recent activity |\n| `list_projects()` | Browse all projects |\n| `list_missions(project_id, status?)` | List missions in a project |\n\n> **Note on `wait_for_mission`:** This blocks the conversation for up to `timeout_seconds` (default 600). For long-running missions, prefer polling with `get_mission_status` every 30–60 seconds instead, so the user sees progress updates.\n\n### Workflow: Plan → Dispatch → Monitor → Report\n\n1. **Plan**: Call `plan_project(prompt=\"...\")` → returns `project_id` + list of missions with `depends_on` chains and `auto_dispatch=true`.\n2. **Show plan**: Present mission titles, types, and dependency chain to the user.\n3. **Dispatch**: Call `dispatch_mission(mission_id=\u003Cfirst_mission_id>)` on the root mission (empty `depends_on`). Remaining missions auto-dispatch as their dependencies complete (because `plan_project` sets `auto_dispatch=true` on them).\n4. **Monitor**: Call `get_mission_status(mission_id=...)` or `get_dashboard()` to check progress.\n5. **Report**: Call `get_report(mission_id=...)` when missions complete. Share highlights with the user.\n\n### Concurrency\n\nDevFleet runs up to 3 concurrent agents by default (configurable via `DEVFLEET_MAX_AGENTS`). When all slots are full, missions with `auto_dispatch=true` queue in the mission watcher and dispatch automatically as slots free up. Check `get_dashboard()` for current slot usage.\n\n## Examples\n\n### Full auto: plan and launch\n\n1. `plan_project(prompt=\"...\")` → shows plan with missions and dependencies.\n2. Dispatch the first mission (the one with empty `depends_on`).\n3. Remaining missions auto-dispatch as dependencies resolve (they have `auto_dispatch=true`).\n4. Report back with project ID and mission count so the user knows what was launched.\n5. Poll with `get_mission_status` or `get_dashboard()` periodically until all missions reach a terminal state (`completed`, `failed`, or `cancelled`).\n6. `get_report(mission_id=...)` for each terminal mission — summarize successes and call out failures with errors and next steps.\n\n### Manual: step-by-step control\n\n1. `create_project(name=\"My Project\")` → returns `project_id`.\n2. `create_mission(project_id=project_id, title=\"...\", prompt=\"...\", auto_dispatch=true)` for the first (root) mission → capture `root_mission_id`.\n   `create_mission(project_id=project_id, title=\"...\", prompt=\"...\", auto_dispatch=true, depends_on=[\"\u003Croot_mission_id>\"])` for each subsequent task.\n3. `dispatch_mission(mission_id=...)` on the first mission to start the chain.\n4. `get_report(mission_id=...)` when done.\n\n### Sequential with review\n\n1. `create_project(name=\"...\")` → get `project_id`.\n2. `create_mission(project_id=project_id, title=\"Implement feature\", prompt=\"...\")` → get `impl_mission_id`.\n3. `dispatch_mission(mission_id=impl_mission_id)`, then poll with `get_mission_status` until complete.\n4. `get_report(mission_id=impl_mission_id)` to review results.\n5. `create_mission(project_id=project_id, title=\"Review\", prompt=\"...\", depends_on=[impl_mission_id], auto_dispatch=true)` — auto-starts since the dependency is already met.\n\n## Guidelines\n\n- Always confirm the plan with the user before dispatching, unless they said to go ahead.\n- Include mission titles and IDs when reporting status.\n- If a mission fails, read its report before retrying.\n- Check `get_dashboard()` for agent slot availability before bulk dispatching.\n- Mission dependencies form a DAG — do not create circular dependencies.\n- Each agent runs in an isolated git worktree and auto-merges on completion. If a merge conflict occurs, the changes remain on the agent's worktree branch for manual resolution.\n- When manually creating missions, always set `auto_dispatch=true` if you want them to trigger automatically when dependencies complete. Without this flag, missions stay in `draft` status.\n",{"name":5,"origin":24,"description":7},"community","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-AI-应用工具\u002FYYC3-AI-应用工具-Everything-claude-code\u002Fskills\u002Fclaude-devfleet",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":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill claude-devfleet",{"tool":40,"command":41},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill claude-devfleet",{"tool":43,"command":44},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill claude-devfleet","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-AI-应用工具\u002FYYC3-AI-应用工具-Everything-claude-code\u002Fskills\u002Fclaude-devfleet\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"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":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"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":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"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":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"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":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"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":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"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",[],[]]