[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B336DPJ9VN0JRKBKMAXPAW":3,"skill-same:01M7B336DPJ9VN0JRKBKMAXPAW":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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7B336DPJ9VN0JRKBKMAXPAW","team-agent-orchestration",null,"Run team-based orchestration for agent squads: work items with owners and scope, agent Kanban state, branch isolation, control pane visibility, and merge gates. Use when coordinating multiple agents in parallel across branches or worktrees — multi-agent fan-out, agent Kanban, squad coordination, or merging agent output into one product.","lytong760-cell\u002Fcompiler_ko","lytong760-cell","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F289977458?v=4","01M7B1YD239K88PFQRD4PVC9DW","Nguyên Games","01M7B1YD2RM70TZ71QNQ0XTN4R",2,"MIT","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fteam-agent-orchestration\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: team-agent-orchestration\ndescription: \"Run team-based orchestration for agent squads: work items with owners and scope, agent Kanban state, branch isolation, control pane visibility, and merge gates. Use when coordinating multiple agents in parallel across branches or worktrees — multi-agent fan-out, agent Kanban, squad coordination, or merging agent output into one product.\"\nmetadata:\n  origin: ECC\n---\n\n# Team Agent Orchestration\n\nUse this skill when agents are being managed like a team rather than a single assistant. The purpose is to make team-based orchestration reliable: clear work items, explicit ownership, agent Kanban state, branch isolation, control pane visibility, and merge gates.\n\n## When To Activate\n\n- The task spans multiple agents, tools, harnesses, branches, or worktrees.\n- The user mentions team orchestration, agent Kanban, squad, conductor, control pane, manager, desktop app, Zellij, tmux, Hermes, Devin, Codex, Claude Code, or multi-agent work.\n- A project needs shared workflow state across people and agents.\n- Existing agent fan-out is producing output but not mergeable product.\n\n## Operating Model\n\nTreat every agent as a teammate with a narrow contract:\n\n- **Owner**: the person or agent accountable for the work item.\n- **Scope**: files, branch, tool surface, and forbidden areas.\n- **State**: backlog, ready, running, review, blocked, merged, or archived.\n- **Evidence**: tests, screenshots, logs, review notes, or eval reports.\n- **Merge gate**: the exact condition that allows integration.\n\n## Agent Kanban\n\nUse agent Kanban when work must be visible across sessions.\n\n| Column | Meaning | Exit Criteria |\n| --- | --- | --- |\n| Backlog | Candidate work item, not yet shaped | Acceptance criteria written |\n| Ready | Shaped and assignable | Owner and branch\u002Fworktree assigned |\n| Running | Agent is actively working | Handoff artifact and changed files exist |\n| Review | Work is complete but not merged | Tests, diff review, and risk check pass |\n| Blocked | Needs external input or failed gate | Blocker has owner and next action |\n| Merged | Integrated into mainline | PR merged or local main updated |\n| Archived | No longer relevant | Reason recorded |\n\nEach card should fit this schema:\n\n```json\n{\n  \"id\": \"agent-card-001\",\n  \"title\": \"Build dynamic workflow skill\",\n  \"owner\": \"codex\",\n  \"state\": \"running\",\n  \"branch\": \"product\u002Fdynamic-workflow-team-orchestration\",\n  \"worktree\": \".\",\n  \"acceptance\": [\n    \"Skill exists\",\n    \"Tests cover required concepts\",\n    \"Content artifact contains video and article angles\"\n  ],\n  \"merge_gate\": \"lint, focused tests, and catalog check pass\",\n  \"handoff\": \"path\u002Fto\u002Fhandoff.md\"\n}\n```\n\n## Team-Based Orchestration Flow\n\n1. **Shape the board**: convert fuzzy ambition into work items with owners and merge gates.\n2. **Pick execution mode**: single-agent, dynamic workflow mode, dmux\u002Ftmux, worktree fan-out, or external desktop orchestrator.\n3. **Assign boundaries**: one owner per card, clear file scope, and no overlapping writes without an integrator.\n4. **Run agents**: each agent writes evidence and handoff notes, not just code.\n5. **Review in sequence**: tests first, then diff review, then security\u002Frisk checks, then content\u002Fproduct polish.\n6. **Merge deliberately**: one integrator resolves conflicts and updates the control pane or status artifact.\n7. **Extract reusable skill**: if the card pattern repeats, promote it into `skills\u002F`.\n\n## Control Pane Requirements\n\nA useful control pane for team orchestration should show:\n\n- Active work items and their agent Kanban state.\n- Owner, harness, branch, worktree, and last heartbeat.\n- Links to handoff artifacts, tests, screenshots, and PRs.\n- Blockers grouped by owner and unblock action.\n- Merge readiness by gate, not vibes.\n- Reusable workflow candidates that should become shared skills.\n\nDo not add more automation until the operator can answer: who owns this, what changed, what gate failed, and what can safely merge?\n\n## Dynamic Workflow Compatibility\n\nWhen a card needs dynamic workflow mode:\n\n- Put the task-local harness under the card owner.\n- Store inputs and outputs on the card.\n- Require an eval before moving from Running to Review.\n- Promote the harness to a shared skill only after repeat use.\n\n## Failure Modes To Watch\n\n- **Agent soup**: many agents running, no owner or merge gate.\n- **Invisible work**: useful output exists only in a chat transcript.\n- **Board theater**: a Kanban board exists but cards have no acceptance criteria.\n- **Overlapping writes**: parallel agents edit the same files without worktrees.\n- **No product artifact**: the process produces docs but no runnable or publishable surface.\n\n## Output Standard\n\nFinish each orchestration pass with:\n\n- Board\u002Fcard changes.\n- Merged or pending branches.\n- Tests and eval evidence.\n- Blockers with owner and next action.\n- New shared skill candidates.\n","# Team Agent Orchestration\n\nUse this skill when agents are being managed like a team rather than a single assistant. The purpose is to make team-based orchestration reliable: clear work items, explicit ownership, agent Kanban state, branch isolation, control pane visibility, and merge gates.\n\n## When To Activate\n\n- The task spans multiple agents, tools, harnesses, branches, or worktrees.\n- The user mentions team orchestration, agent Kanban, squad, conductor, control pane, manager, desktop app, Zellij, tmux, Hermes, Devin, Codex, Claude Code, or multi-agent work.\n- A project needs shared workflow state across people and agents.\n- Existing agent fan-out is producing output but not mergeable product.\n\n## Operating Model\n\nTreat every agent as a teammate with a narrow contract:\n\n- **Owner**: the person or agent accountable for the work item.\n- **Scope**: files, branch, tool surface, and forbidden areas.\n- **State**: backlog, ready, running, review, blocked, merged, or archived.\n- **Evidence**: tests, screenshots, logs, review notes, or eval reports.\n- **Merge gate**: the exact condition that allows integration.\n\n## Agent Kanban\n\nUse agent Kanban when work must be visible across sessions.\n\n| Column | Meaning | Exit Criteria |\n| --- | --- | --- |\n| Backlog | Candidate work item, not yet shaped | Acceptance criteria written |\n| Ready | Shaped and assignable | Owner and branch\u002Fworktree assigned |\n| Running | Agent is actively working | Handoff artifact and changed files exist |\n| Review | Work is complete but not merged | Tests, diff review, and risk check pass |\n| Blocked | Needs external input or failed gate | Blocker has owner and next action |\n| Merged | Integrated into mainline | PR merged or local main updated |\n| Archived | No longer relevant | Reason recorded |\n\nEach card should fit this schema:\n\n```json\n{\n  \"id\": \"agent-card-001\",\n  \"title\": \"Build dynamic workflow skill\",\n  \"owner\": \"codex\",\n  \"state\": \"running\",\n  \"branch\": \"product\u002Fdynamic-workflow-team-orchestration\",\n  \"worktree\": \".\",\n  \"acceptance\": [\n    \"Skill exists\",\n    \"Tests cover required concepts\",\n    \"Content artifact contains video and article angles\"\n  ],\n  \"merge_gate\": \"lint, focused tests, and catalog check pass\",\n  \"handoff\": \"path\u002Fto\u002Fhandoff.md\"\n}\n```\n\n## Team-Based Orchestration Flow\n\n1. **Shape the board**: convert fuzzy ambition into work items with owners and merge gates.\n2. **Pick execution mode**: single-agent, dynamic workflow mode, dmux\u002Ftmux, worktree fan-out, or external desktop orchestrator.\n3. **Assign boundaries**: one owner per card, clear file scope, and no overlapping writes without an integrator.\n4. **Run agents**: each agent writes evidence and handoff notes, not just code.\n5. **Review in sequence**: tests first, then diff review, then security\u002Frisk checks, then content\u002Fproduct polish.\n6. **Merge deliberately**: one integrator resolves conflicts and updates the control pane or status artifact.\n7. **Extract reusable skill**: if the card pattern repeats, promote it into `skills\u002F`.\n\n## Control Pane Requirements\n\nA useful control pane for team orchestration should show:\n\n- Active work items and their agent Kanban state.\n- Owner, harness, branch, worktree, and last heartbeat.\n- Links to handoff artifacts, tests, screenshots, and PRs.\n- Blockers grouped by owner and unblock action.\n- Merge readiness by gate, not vibes.\n- Reusable workflow candidates that should become shared skills.\n\nDo not add more automation until the operator can answer: who owns this, what changed, what gate failed, and what can safely merge?\n\n## Dynamic Workflow Compatibility\n\nWhen a card needs dynamic workflow mode:\n\n- Put the task-local harness under the card owner.\n- Store inputs and outputs on the card.\n- Require an eval before moving from Running to Review.\n- Promote the harness to a shared skill only after repeat use.\n\n## Failure Modes To Watch\n\n- **Agent soup**: many agents running, no owner or merge gate.\n- **Invisible work**: useful output exists only in a chat transcript.\n- **Board theater**: a Kanban board exists but cards have no acceptance criteria.\n- **Overlapping writes**: parallel agents edit the same files without worktrees.\n- **No product artifact**: the process produces docs but no runnable or publishable surface.\n\n## Output Standard\n\nFinish each orchestration pass with:\n\n- Board\u002Fcard changes.\n- Merged or pending branches.\n- Tests and eval evidence.\n- Blockers with owner and next action.\n- New shared skill candidates.\n",{"name":5,"metadata":24,"description":7},{"origin":25},"ECC","main","c32dc0b68600587f78aff3310f3bbd4212173ab3",".kilo\u002Fskills\u002Fteam-agent-orchestration",1,"https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko","https:\u002F\u002Fko-lang.ai.studio","https:\u002F\u002Fgithub.com\u002Flytong760-cell","hanaminikata.com","hello ","2026-11-05 18:26:32",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add lytong760-cell\u002Fcompiler_ko --skill team-agent-orchestration",{"tool":42,"command":43},"bunx","bunx skills add lytong760-cell\u002Fcompiler_ko --skill team-agent-orchestration",{"tool":45,"command":46},"pnpm","pnpm dlx skills add lytong760-cell\u002Fcompiler_ko --skill team-agent-orchestration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fteam-agent-orchestration\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},"01M7B36K22Z7155PTGEGTSDNJ4","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fx-api\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},"01M7B36HCAE9ESGBVS6J0FR52F","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwriting-for-agents\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},"01M7B36DYH4ZFJ3GZHPAEMVQAY","workspace-surface-audit","Audit the active repo, MCP servers, plugins, connectors, env surfaces, and harness setup, then recommend the highest-value ECC-native skills, hooks, agents, and operator workflows. Use when the user wants help setting up Claude Code or understanding what capabilities are actually available in their environment.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fworkspace-surface-audit\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},"01M7B36A1QXMEZT8VZMFVQNR5E","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwizard\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},"01M7B364EK3N88VQQJ6HFATJQE","windows-desktop-e2e","E2E testing for Windows native desktop apps (WPF, WinForms, Win32\u002FMFC, Qt) using pywinauto and Windows UI Automation. Use when writing E2E tests for a Windows native desktop app with pywinauto or UI Automation.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwindows-desktop-e2e\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},"01M7B360YF7GGNAF21KT4QB5PG","wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[]]