[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CSCFFS5VVFA2VH7XW674ZR":3,"skill-same:01M7CSCFFS5VVFA2VH7XW674ZR":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":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7CSCFFS5VVFA2VH7XW674ZR","team-agent-orchestration",null,"Run team-based orchestration for agent squads using work items, ownership, agent Kanban, merge gates, and control pane handoffs.","Henrique1601\u002FSkiilsToIAs","Henrique1601","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F92006691?v=4","01M7CRXVT0GVXVK80JT1GR687S","Henrique Bezerra Dos Santos","01M7CRXVTN5Y8TMWJ1MDSKCQ1T",0,"MIT","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fai-agents\u002Fteam-agent-orchestration\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: team-agent-orchestration\ndescription: \"Run team-based orchestration for agent squads using work items, ownership, agent Kanban, merge gates, and control pane handoffs.\"\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","a73152352c0612252131e5cf84e91312a6cf17dc","ai-agents\u002Fteam-agent-orchestration","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs","https:\u002F\u002Fgithub.com\u002FHenrique1601","https:\u002F\u002Fbezerraportifolio.netlify.app\u002F","Full Stack Developer | React, Next.js, TypeScript, Node.js & IA | Construindo produtos digitais e soluções SaaS","2026-11-15 02:56:04",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Henrique1601\u002FSkiilsToIAs --skill team-agent-orchestration",{"tool":40,"command":41},"bunx","bunx skills add Henrique1601\u002FSkiilsToIAs --skill team-agent-orchestration",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Henrique1601\u002FSkiilsToIAs --skill team-agent-orchestration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fai-agents\u002Fteam-agent-orchestration\u002FSKILL.md",true,[],[49,56,63,71,78,85],{"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},"01M7E2ANBW9V6AVX5JXNCEAWF8","rag-architect-agent","Agente Arquiteto de RAG, Embeddings & Busca Vetorial. Especialista em design e implementação de pipelines de Retrieval-Augmented Generation de alta fidelidade: chunking semântico, modelagem pgvector no PostgreSQL (Neon\u002FSupabase), busca híbrida (cosseno + BM25), reranking, validação via TypeSafe AI e filosofia Ponytail (anti-overengineering).","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fcustom-agents\u002Frag-architect-agent\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},"01M7E29KKF8R02ZRGYE2MJM67G","rag-architecture-patterns","Padrões arquiteturais e implementação de pipelines RAG (Retrieval-Augmented Generation) de alta fidelidade para qualquer projeto ou sistema. Cobre chunking semântico, embeddings, busca híbrida (pgvector + BM25), reranking, validação via TypeSafe AI e filosofia Ponytail (anti-overengineering).","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fai-agents\u002Frag-architecture-patterns\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":67,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7CWRA8E3BJ7CPY8N8EG28J1","skill-repair","Use this to fix and re-install agent skills that have failed installation.\nThis skill provides the necessary context and permissions to surgically update\nthe `manifest.json` after a fix has been applied.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fskill-repair\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7CWR66FZP8FA47WVZ4Z2EXC","security-scan","Scan your Claude Code configuration (.claude\u002F directory) for security vulnerabilities, misconfigurations, and injection risks using AgentShield. Checks CLAUDE.md, settings.json, MCP servers, hooks, and agent definitions.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-scan\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7CWR0QPY58QPTR1P759TFNG","security-review","Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment\u002Fsensitive features. Provides comprehensive security checklist and patterns.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-review\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7CWQXCE40XWT4FZ3VWZFGDP","security-bounty-hunter","Hunt for exploitable, bounty-worthy security issues in repositories. Focuses on remotely reachable vulnerabilities that qualify for real reports instead of noisy local-only findings.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-bounty-hunter\u002FSKILL.md",[],[]]