[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CSCKKT00C2XK0VFDDW7SE6":3,"skill-same:01M7CSCKKT00C2XK0VFDDW7SE6":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},"01M7CSCKKT00C2XK0VFDDW7SE6","team-builder",null,"Interactive agent picker for composing and dispatching parallel teams","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-builder\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: team-builder\ndescription: Interactive agent picker for composing and dispatching parallel teams\nmetadata:\n  origin: community\n---\n\n# Team Builder\n\nInteractive menu for browsing and composing agent teams on demand. Works with flat or domain-subdirectory agent collections.\n\n## When to Use\n\n- You have multiple agent personas (markdown files) and want to pick which ones to use for a task\n- You want to compose an ad-hoc team from different domains (e.g., Security + SEO + Architecture)\n- You want to browse what agents are available before deciding\n\n## Prerequisites\n\nAgent files must be markdown files containing a persona prompt (identity, rules, workflow, deliverables). The first `# Heading` is used as the agent name and the first paragraph as the description.\n\nBoth flat and subdirectory layouts are supported:\n\n**Subdirectory layout** — domain is inferred from the folder name:\n\n```\nagents\u002F\n├── engineering\u002F\n│   ├── security-engineer.md\n│   └── software-architect.md\n├── marketing\u002F\n│   └── seo-specialist.md\n└── sales\u002F\n    └── discovery-coach.md\n```\n\n**Flat layout** — domain inferred from shared filename prefixes. A prefix counts as a domain when 2+ files share it. Files with unique prefixes go to \"General\". Note: the algorithm splits at the first `-`, so multi-word domains (e.g., `product-management`) should use the subdirectory layout instead:\n\n```\nagents\u002F\n├── engineering-security-engineer.md\n├── engineering-software-architect.md\n├── marketing-seo-specialist.md\n├── marketing-content-strategist.md\n├── sales-discovery-coach.md\n└── sales-outbound-strategist.md\n```\n\n## Configuration\n\nAgents are discovered via two methods, merged and deduplicated by agent name:\n\n1. **`claude agents` command** (primary) — run `claude agents` to get all agents known to the CLI, including user agents, plugin agents (e.g. `ecc:architect`), and built-in agents. This automatically covers ECC marketplace installs without any path configuration.\n2. **File glob** (fallback, for reading agent content) — agent markdown files are read from:\n   - `.\u002Fagents\u002F**\u002F*.md` + `.\u002Fagents\u002F*.md` — project-local agents\n   - `~\u002F.claude\u002Fagents\u002F**\u002F*.md` + `~\u002F.claude\u002Fagents\u002F*.md` — global user agents\n\nEarlier sources take precedence when names collide: user agents > plugin agents > built-in agents. A custom path can be used instead if the user specifies one.\n\n## How It Works\n\n### Step 1: Discover Available Agents\n\nRun `claude agents` to get the full agent list. Parse each line:\n- **Plugin agents** are prefixed with `plugin-name:` (e.g., `ecc:security-reviewer`). Use the part after `:` as the agent name and the plugin name as the domain.\n- **User agents** have no prefix. Read the corresponding markdown file from `~\u002F.claude\u002Fagents\u002F` or `.\u002Fagents\u002F` to extract the name and description.\n- **Built-in agents** (e.g., `Explore`, `Plan`) are skipped unless the user explicitly asks to include them.\n\nFor user agents loaded from markdown files:\n- **Subdirectory layout:** extract the domain from the parent folder name\n- **Flat layout:** collect all filename prefixes (text before the first `-`). A prefix qualifies as a domain only if it appears in 2 or more filenames (e.g., `engineering-security-engineer.md` and `engineering-software-architect.md` both start with `engineering` → Engineering domain). Files with unique prefixes (e.g., `code-reviewer.md`, `tdd-guide.md`) are grouped under \"General\"\n- Extract the agent name from the first `# Heading`. If no heading is found, derive the name from the filename (strip `.md`, replace hyphens with spaces, title-case)\n- Extract a one-line summary from the first paragraph after the heading\n\nIf no agents are found after running `claude agents` and probing file locations, inform the user: \"No agents found. Run `claude agents` to verify your setup.\" Then stop.\n\n### Step 2: Present Domain Menu\n\n```\nAvailable agent domains:\n1. Engineering — Software Architect, Security Engineer\n2. Marketing — SEO Specialist\n3. Sales — Discovery Coach, Outbound Strategist\n\nPick domains or name specific agents (e.g., \"1,3\" or \"security + seo\"):\n```\n\n- Skip domains with zero agents (empty directories)\n- Show agent count per domain\n\n### Step 3: Handle Selection\n\nAccept flexible input:\n- Numbers: \"1,3\" selects all agents from Engineering and Sales\n- Names: \"security + seo\" fuzzy-matches against discovered agents\n- \"all from engineering\" selects every agent in that domain\n\nIf more than 5 agents are selected, list them alphabetically and ask the user to narrow down: \"You selected N agents (max 5). Pick which to keep, or say 'first 5' to use the first five alphabetically.\"\n\nConfirm selection:\n```\nSelected: Security Engineer + SEO Specialist\nWhat should they work on? (describe the task):\n```\n\n### Step 4: Spawn Agents in Parallel\n\n1. Read each selected agent's markdown file\n2. Prompt for the task description if not already provided\n3. Spawn all agents in parallel using the Agent tool:\n   - `subagent_type: \"general-purpose\"`\n   - `prompt: \"{agent file content}\\n\\nTask: {task description}\"`\n   - Each agent runs independently — no inter-agent communication needed\n4. If an agent fails (error, timeout, or empty output), note the failure inline (e.g., \"Security Engineer: failed — [reason]\") and continue with results from agents that succeeded\n\n### Step 5: Synthesize Results\n\nCollect all outputs and present a unified report:\n- Results grouped by agent\n- Synthesis section highlighting:\n  - Agreements across agents\n  - Conflicts or tensions between recommendations\n  - Recommended next steps\n\nIf only 1 agent was selected, skip synthesis and present the output directly.\n\n## Rules\n\n- **Dynamic discovery only.** Never hardcode agent lists. New files in the directory auto-appear in the menu.\n- **Max 5 agents per team.** More than 5 produces diminishing returns and excessive token usage. Enforce at selection time.\n- **Parallel dispatch.** All agents run simultaneously — use the Agent tool's parallel invocation pattern.\n- **Parallel Agent calls, not TeamCreate.** This skill uses parallel Agent tool calls for independent work. TeamCreate (a Claude Code tool for multi-agent dialogue) is only needed when agents must debate or respond to each other.\n\n## Examples\n\n```\nUser: team builder\n\nClaude:\nAvailable agent domains:\n1. Engineering (2) — Software Architect, Security Engineer\n2. Marketing (1) — SEO Specialist\n3. Sales (4) — Discovery Coach, Outbound Strategist, Proposal Strategist, Sales Engineer\n4. Support (1) — Executive Summary\n\nPick domains or name specific agents:\n\nUser: security + seo\n\nClaude:\nSelected: Security Engineer + SEO Specialist\nWhat should they work on?\n\nUser: Review my Next.js e-commerce site before launch\n\n[Both agents spawn in parallel, each applying their specialty to the codebase]\n\nClaude:\n## Security Engineer Findings\n- [findings...]\n\n## SEO Specialist Findings\n- [findings...]\n\n## Synthesis\nBoth agents agree on: [...]\nTension: Security recommends CSP that blocks inline styles, SEO needs inline schema markup. Resolution: [...]\nNext steps: [...]\n```\n","# Team Builder\n\nInteractive menu for browsing and composing agent teams on demand. Works with flat or domain-subdirectory agent collections.\n\n## When to Use\n\n- You have multiple agent personas (markdown files) and want to pick which ones to use for a task\n- You want to compose an ad-hoc team from different domains (e.g., Security + SEO + Architecture)\n- You want to browse what agents are available before deciding\n\n## Prerequisites\n\nAgent files must be markdown files containing a persona prompt (identity, rules, workflow, deliverables). The first `# Heading` is used as the agent name and the first paragraph as the description.\n\nBoth flat and subdirectory layouts are supported:\n\n**Subdirectory layout** — domain is inferred from the folder name:\n\n```\nagents\u002F\n├── engineering\u002F\n│   ├── security-engineer.md\n│   └── software-architect.md\n├── marketing\u002F\n│   └── seo-specialist.md\n└── sales\u002F\n    └── discovery-coach.md\n```\n\n**Flat layout** — domain inferred from shared filename prefixes. A prefix counts as a domain when 2+ files share it. Files with unique prefixes go to \"General\". Note: the algorithm splits at the first `-`, so multi-word domains (e.g., `product-management`) should use the subdirectory layout instead:\n\n```\nagents\u002F\n├── engineering-security-engineer.md\n├── engineering-software-architect.md\n├── marketing-seo-specialist.md\n├── marketing-content-strategist.md\n├── sales-discovery-coach.md\n└── sales-outbound-strategist.md\n```\n\n## Configuration\n\nAgents are discovered via two methods, merged and deduplicated by agent name:\n\n1. **`claude agents` command** (primary) — run `claude agents` to get all agents known to the CLI, including user agents, plugin agents (e.g. `ecc:architect`), and built-in agents. This automatically covers ECC marketplace installs without any path configuration.\n2. **File glob** (fallback, for reading agent content) — agent markdown files are read from:\n   - `.\u002Fagents\u002F**\u002F*.md` + `.\u002Fagents\u002F*.md` — project-local agents\n   - `~\u002F.claude\u002Fagents\u002F**\u002F*.md` + `~\u002F.claude\u002Fagents\u002F*.md` — global user agents\n\nEarlier sources take precedence when names collide: user agents > plugin agents > built-in agents. A custom path can be used instead if the user specifies one.\n\n## How It Works\n\n### Step 1: Discover Available Agents\n\nRun `claude agents` to get the full agent list. Parse each line:\n- **Plugin agents** are prefixed with `plugin-name:` (e.g., `ecc:security-reviewer`). Use the part after `:` as the agent name and the plugin name as the domain.\n- **User agents** have no prefix. Read the corresponding markdown file from `~\u002F.claude\u002Fagents\u002F` or `.\u002Fagents\u002F` to extract the name and description.\n- **Built-in agents** (e.g., `Explore`, `Plan`) are skipped unless the user explicitly asks to include them.\n\nFor user agents loaded from markdown files:\n- **Subdirectory layout:** extract the domain from the parent folder name\n- **Flat layout:** collect all filename prefixes (text before the first `-`). A prefix qualifies as a domain only if it appears in 2 or more filenames (e.g., `engineering-security-engineer.md` and `engineering-software-architect.md` both start with `engineering` → Engineering domain). Files with unique prefixes (e.g., `code-reviewer.md`, `tdd-guide.md`) are grouped under \"General\"\n- Extract the agent name from the first `# Heading`. If no heading is found, derive the name from the filename (strip `.md`, replace hyphens with spaces, title-case)\n- Extract a one-line summary from the first paragraph after the heading\n\nIf no agents are found after running `claude agents` and probing file locations, inform the user: \"No agents found. Run `claude agents` to verify your setup.\" Then stop.\n\n### Step 2: Present Domain Menu\n\n```\nAvailable agent domains:\n1. Engineering — Software Architect, Security Engineer\n2. Marketing — SEO Specialist\n3. Sales — Discovery Coach, Outbound Strategist\n\nPick domains or name specific agents (e.g., \"1,3\" or \"security + seo\"):\n```\n\n- Skip domains with zero agents (empty directories)\n- Show agent count per domain\n\n### Step 3: Handle Selection\n\nAccept flexible input:\n- Numbers: \"1,3\" selects all agents from Engineering and Sales\n- Names: \"security + seo\" fuzzy-matches against discovered agents\n- \"all from engineering\" selects every agent in that domain\n\nIf more than 5 agents are selected, list them alphabetically and ask the user to narrow down: \"You selected N agents (max 5). Pick which to keep, or say 'first 5' to use the first five alphabetically.\"\n\nConfirm selection:\n```\nSelected: Security Engineer + SEO Specialist\nWhat should they work on? (describe the task):\n```\n\n### Step 4: Spawn Agents in Parallel\n\n1. Read each selected agent's markdown file\n2. Prompt for the task description if not already provided\n3. Spawn all agents in parallel using the Agent tool:\n   - `subagent_type: \"general-purpose\"`\n   - `prompt: \"{agent file content}\\n\\nTask: {task description}\"`\n   - Each agent runs independently — no inter-agent communication needed\n4. If an agent fails (error, timeout, or empty output), note the failure inline (e.g., \"Security Engineer: failed — [reason]\") and continue with results from agents that succeeded\n\n### Step 5: Synthesize Results\n\nCollect all outputs and present a unified report:\n- Results grouped by agent\n- Synthesis section highlighting:\n  - Agreements across agents\n  - Conflicts or tensions between recommendations\n  - Recommended next steps\n\nIf only 1 agent was selected, skip synthesis and present the output directly.\n\n## Rules\n\n- **Dynamic discovery only.** Never hardcode agent lists. New files in the directory auto-appear in the menu.\n- **Max 5 agents per team.** More than 5 produces diminishing returns and excessive token usage. Enforce at selection time.\n- **Parallel dispatch.** All agents run simultaneously — use the Agent tool's parallel invocation pattern.\n- **Parallel Agent calls, not TeamCreate.** This skill uses parallel Agent tool calls for independent work. TeamCreate (a Claude Code tool for multi-agent dialogue) is only needed when agents must debate or respond to each other.\n\n## Examples\n\n```\nUser: team builder\n\nClaude:\nAvailable agent domains:\n1. Engineering (2) — Software Architect, Security Engineer\n2. Marketing (1) — SEO Specialist\n3. Sales (4) — Discovery Coach, Outbound Strategist, Proposal Strategist, Sales Engineer\n4. Support (1) — Executive Summary\n\nPick domains or name specific agents:\n\nUser: security + seo\n\nClaude:\nSelected: Security Engineer + SEO Specialist\nWhat should they work on?\n\nUser: Review my Next.js e-commerce site before launch\n\n[Both agents spawn in parallel, each applying their specialty to the codebase]\n\nClaude:\n## Security Engineer Findings\n- [findings...]\n\n## SEO Specialist Findings\n- [findings...]\n\n## Synthesis\nBoth agents agree on: [...]\nTension: Security recommends CSP that blocks inline styles, SEO needs inline schema markup. Resolution: [...]\nNext steps: [...]\n```\n",{"name":5,"metadata":24,"description":7},{"origin":25},"community","main","a73152352c0612252131e5cf84e91312a6cf17dc","ai-agents\u002Fteam-builder","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-builder",{"tool":40,"command":41},"bunx","bunx skills add Henrique1601\u002FSkiilsToIAs --skill team-builder",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Henrique1601\u002FSkiilsToIAs --skill team-builder","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fai-agents\u002Fteam-builder\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",[],[]]