MCP Server Builder
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
Agent Orchestrator workflow skill. An agent skill from diegosouzapw/awesome-omni-skills.
Install Agent Orchestrator
$ npx skills add diegosouzapw/awesome-omni-skills --skill agent-orchestrator -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install diegosouzapw/awesome-omni-skills agent-orchestrator --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/diegosouzapw/awesome-omni-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/agent-orchestrator .claude/skills/agent-orchestrator && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "agent-orchestrator" agent skill from https://github.com/diegosouzapw/awesome-omni-skills/tree/main/skills/agent-orchestrator into .claude/skills/agent-orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-orchestrator", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/diegosouzapw/awesome-omni-skills/tree/main/skills/agent-orchestratorType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add diegosouzapw/awesome-omni-skills --skill agent-orchestrator -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install diegosouzapw/awesome-omni-skills agent-orchestrator --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/diegosouzapw/awesome-omni-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/agent-orchestrator .agents/skills/agent-orchestrator && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "agent-orchestrator" agent skill from https://github.com/diegosouzapw/awesome-omni-skills/tree/main/skills/agent-orchestrator into .agents/skills/agent-orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-orchestrator", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add diegosouzapw/awesome-omni-skills --skill agent-orchestrator -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install diegosouzapw/awesome-omni-skills agent-orchestrator --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/diegosouzapw/awesome-omni-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/agent-orchestrator .cursor/skills/agent-orchestrator && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "agent-orchestrator" agent skill from https://github.com/diegosouzapw/awesome-omni-skills/tree/main/skills/agent-orchestrator into .cursor/skills/agent-orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-orchestrator", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/diegosouzapw/awesome-omni-skills.git --path skills/agent-orchestrator--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add diegosouzapw/awesome-omni-skills --skill agent-orchestrator -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install diegosouzapw/awesome-omni-skills agent-orchestrator --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/diegosouzapw/awesome-omni-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/agent-orchestrator .gemini/skills/agent-orchestrator && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "agent-orchestrator" agent skill from https://github.com/diegosouzapw/awesome-omni-skills/tree/main/skills/agent-orchestrator into .gemini/skills/agent-orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-orchestrator", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install diegosouzapw/awesome-omni-skills agent-orchestratorInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add diegosouzapw/awesome-omni-skills --skill agent-orchestrator -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/diegosouzapw/awesome-omni-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/agent-orchestrator .github/skills/agent-orchestrator && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "agent-orchestrator" agent skill from https://github.com/diegosouzapw/awesome-omni-skills/tree/main/skills/agent-orchestrator into .github/skills/agent-orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-orchestrator", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add diegosouzapw/awesome-omni-skills --skill agent-orchestrator -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install diegosouzapw/awesome-omni-skills agent-orchestrator --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/diegosouzapw/awesome-omni-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/agent-orchestrator .opencode/skills/agent-orchestrator && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "agent-orchestrator" agent skill from https://github.com/diegosouzapw/awesome-omni-skills/tree/main/skills/agent-orchestrator into .opencode/skills/agent-orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-orchestrator", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
agent-orchestrator- GitHub stars
- 159
- Token cost
- ~4.7k tokens
- SKILL.md length
- 1,875 words
- Files
- 9 (incl. scripts, references)
- Skills in repo
- 39
- Repo updated
- First seen
- Licence
- MIT
At a glance
Agent Orchestrator workflow skill. An agent skill from diegosouzapw/awesome-omni-skills.
- Works in 7 steps: Execute estes passos ANTES de processar… → Os scripts usam paths relativos… → Confirm the user goal, the scope of the… → …
- The user needs Meta-skill que orquestra todos os agentes do ecossistema
- SKILL.md covers Overview, When to Use This Skill, Operating Table and Workflow, plus 5 more sections
- Runs Python scripts from its folder; calls python; reaches github.com
What it does
Agent Orchestrator is an agent skill from diegosouzapw/awesome-omni-skills. Agent Orchestrator workflow skill. Use this skill when the user needs Meta-skill que orquestra todos os agentes do ecossistema. Scan automatico de skills, match por capacidades, coordenacao de workflows multi-skill e registry management and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
Its SKILL.md is about 4.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including scripts and reference files (for example `ORIGIN.md`, `metadata.json` and `references/capability-taxonomy.md`).
It sits in Agent Workflows. The repository describes itself as: Public repository of AI coding skills, curated improved best-practice skills, and runtime surfaces for CLI, API, MCP, and A2A. The licence is MIT.
When your agent uses it
- The user needs Meta-skill que orquestra todos os agentes do ecossistema
Example prompts
- “/agent-orchestrator”
Requirements
- Python 3
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Execute estes passos ANTES de processar qualquer request do usuario.
- Os scripts usam paths relativos automaticamente - funciona de qualquer diretorio.
- Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
- Read the overview and provenance files before loading any copied upstream support files.
- Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
- Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
- Validate the result against the upstream expectations and the evidence you can point to in the copied files.
What it can do on your machine
Read from SKILL.md and the folder at commit c3af004. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 4 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Agent Orchestrator loads about 4.7k tokens when it runs, and up to ~6.5k if it reads all its reference files. Until then it costs about 95 tokens; SKILL.md has 1,875 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from diegosouzapw/awesome-omni-skills at commit c3af004, republished under its MIT licence (© diegosouzapw). 1,875 words, ~4,740 tokens.
Download SKILL.mdSave it as
.claude/skills/agent-orchestrator/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.- name
- agent-orchestrator
- description
- Agent Orchestrator workflow skill. Use this skill when the user needs Meta-skill que orquestra todos os agentes do ecossistema. Scan automatico de skills, match por capacidades, coordenacao de workflows multi-skill e registry management and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
- version
- 0.0.1
- category
- ai-agents
- tags
- orchestration, multi-agent, workflow, automation, agent-orchestrator, meta-skill, que, orquestra
- complexity
- advanced
- risk
- caution
- tools
- claude-code, antigravity, cursor, gemini-cli, codex-cli, opencode
- source
- community
- author
- renat
- date_added
- 2026-04-14
- date_updated
- 2026-04-25
Agent Orchestrator
Overview
This public intake copy packages plugins/antigravity-awesome-skills-claude/skills/agent-orchestrator from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.
Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.
This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.
Agent Orchestrator
Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: How It Works, Principio: Zero Intervencao Manual, Passo 1: Auto-Discovery (Varredura), Passo 2: Match De Skills, Passo 3: Orquestracao (Se Matched >= 2), Passo Rapido (Atalho).
When to Use This Skill
Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.
- When you need specialized assistance with this domain
- The task is unrelated to agent orchestrator
- A simpler, more specific tool can handle the request
- The user needs general-purpose assistance without domain expertise
- Use when the request clearly matches the imported source intent: Meta-skill que orquestra todos os agentes do ecossistema. Scan automatico de skills, match por capacidades, coordenacao de workflows multi-skill e registry management.
- Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
Operating Table
| Situation | Start here | Why it matters |
|---|---|---|
| First-time use | metadata.json | Confirms repository, branch, commit, and imported path through the external_source block before touching the copied workflow |
| Provenance review | ORIGIN.md | Gives reviewers a plain-language audit trail for the imported source |
| Workflow execution | references/capability-taxonomy.md | Starts with the smallest copied file that materially changes execution |
| Supporting context | references/orchestration-patterns.md | Adds the next most relevant copied source file without loading the entire package |
| Handoff decision | ## Related Skills | Helps the operator switch to a stronger native skill when the task drifts |
Workflow
This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.
- Execute estes passos ANTES de processar qualquer request do usuario.
- Os scripts usam paths relativos automaticamente - funciona de qualquer diretorio.
- Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
- Read the overview and provenance files before loading any copied upstream support files.
- Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
- Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
- Validate the result against the upstream expectations and the evidence you can point to in the copied files.
Imported Workflow Notes
Imported: Workflow Obrigatorio (Toda Solicitacao)
Execute estes passos ANTES de processar qualquer request do usuario. Os scripts usam paths relativos automaticamente - funciona de qualquer diretorio.
Imported: Overview
Meta-skill que orquestra todos os agentes do ecossistema. Scan automatico de skills, match por capacidades, coordenacao de workflows multi-skill e registry management.
Imported: How It Works
Meta-skill que funciona como camada central de decisao e coordenacao para todo o ecossistema de skills. Faz varredura automatica, identifica agentes relevantes e orquestra multiplos skills para tarefas complexas.
Examples
Example 1: Ask for the upstream workflow directly
Use @agent-orchestrator to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.
Example 2: Ask for a provenance-grounded review
Review @agent-orchestrator against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.
Example 3: Narrow the copied support files before execution
Use @agent-orchestrator for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.
Example 4: Build a reviewer packet
Review @agent-orchestrator using the copied upstream files plus provenance, then summarize any gaps before merge.Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.
Best Practices
Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.
- Provide clear, specific context about your project and requirements
- Review all suggestions before applying them to production code
- Combine with other complementary skills for comprehensive analysis
- Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
- Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
- Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
- Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.
Imported Operating Notes
Imported: Best Practices
- Provide clear, specific context about your project and requirements
- Review all suggestions before applying them to production code
- Combine with other complementary skills for comprehensive analysis
Troubleshooting
Problem: The operator skipped the imported context and answered too generically
Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills-claude/skills/agent-orchestrator, fails to mention provenance, or does not use any copied source files at all.
Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Check the external_source block first, then restate the provenance before continuing.
Problem: The imported workflow feels incomplete during review
Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task.
Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.
Problem: The task drifted into a different specialization
Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.
Related Skills
@00-andruia-consultant- Use when the work is better handled by that native specialization after this imported skill establishes context.@00-andruia-consultant-v2- Use when the work is better handled by that native specialization after this imported skill establishes context.@10-andruia-skill-smith- Use when the work is better handled by that native specialization after this imported skill establishes context.@10-andruia-skill-smith-v2- Use when the work is better handled by that native specialization after this imported skill establishes context.
Additional Resources
Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.
| Resource family | What it gives the reviewer | Example path |
|---|---|---|
references | copied reference notes, guides, or background material from upstream | references/capability-taxonomy.md |
examples | worked examples or reusable prompts copied from upstream | examples/n/a |
scripts | upstream helper scripts that change execution or validation | scripts/match_skills.py |
agents | routing or delegation notes that are genuinely part of the imported package | agents/n/a |
assets | supporting assets or schemas copied from the source package | assets/n/a |
Show full SKILL.md (701 more words)Show less
Imported Reference Notes
Imported: Detalhes Em References/Orchestration-Patterns.Md
Imported: Principio: Zero Intervencao Manual
- SEMPRE faz varredura antes de processar qualquer solicitacao
- Novas skills sao auto-detectadas e incluidas ao criar SKILL.md em qualquer subpasta
- Skills removidas sao auto-excluidas do registry
- Nenhum comando manual e necessario para registrar novas skills
Imported: Passo 1: Auto-Discovery (Varredura)
python agent-orchestrator/scripts/scan_registry.pyUltra-rapido (<100ms) via cache de hashes MD5. So re-processa arquivos alterados. Retorna JSON com resumo de todos os skills encontrados.
Imported: Passo 2: Match De Skills
python agent-orchestrator/scripts/match_skills.py "<solicitacao do usuario>"Retorna JSON com skills ranqueadas por relevancia. Interpretar o resultado:
| Resultado | Acao |
|---|---|
matched: 0 | Nenhum skill relevante. Operar normalmente sem skills. |
matched: 1 | Um skill relevante. Carregar seu SKILL.md e seguir. |
matched: 2+ | Multiplos skills. Executar Passo 3 (orquestracao). |
Imported: Passo 3: Orquestracao (Se Matched >= 2)
python agent-orchestrator/scripts/orchestrate.py --skills skill1,skill2 --query "<solicitacao>"Retorna plano de execucao com padrao, ordem dos steps e data flow entre skills.
Imported: Passo Rapido (Atalho)
Para queries simples, os passos 1+2 podem ser combinados em sequencia:
python agent-orchestrator/scripts/scan_registry.py && python agent-orchestrator/scripts/match_skills.py "<solicitacao>"Imported: Skill Registry
O registry vive em:
agent-orchestrator/data/registry.jsonImported: Locais De Busca
O scanner procura SKILL.md em:
.claude/skills/*/(skills registradas no Claude Code)*/(skills standalone no top-level)*/*\(skills em subpastas, ate profundidade 3)
Imported: Metadata Por Skill
Cada entrada no registry contem:
| Campo | Descricao |
|---|---|
| name | Nome da skill (do frontmatter YAML) |
| description | Descricao completa (triggers inclusos) |
| location | Caminho absoluto do diretorio |
| skill_md | Caminho absoluto do SKILL.md |
| registered | Se esta em .claude/skills/ (true/false) |
| capabilities | Tags de capacidade (auto-extraidas + explicitas) |
| triggers | Keywords de ativacao extraidas da description |
| language | Linguagem principal (python/nodejs/bash/none) |
| status | active / incomplete / missing |
Imported: Comandos Do Registry
#### Imported: Scan Rapido (Usa Cache De Hashes)
python agent-orchestrator/scripts/scan_registry.py
#### Imported: Tabela De Status Detalhada
python agent-orchestrator/scripts/scan_registry.py --status
#### Imported: Re-Scan Completo (Ignora Cache)
python agent-orchestrator/scripts/scan_registry.py --forceImported: Algoritmo De Matching
Para cada solicitacao, o matcher pontua skills usando:
| Criterio | Pontos | Exemplo |
|---|---|---|
| Nome do skill na query | +15 | "use web-scraper" -> web-scraper |
| Keyword trigger exata | +10 | "scrape" -> web-scraper |
| Categoria de capacidade | +5 | data-extraction -> web-scraper |
| Sobreposicao de palavras | +1 | Palavras da query na description |
| Boost de projeto | +20 | Skill atribuida ao projeto ativo |
Threshold minimo: 5 pontos. Skills abaixo disso sao ignoradas.
Imported: Match Com Projeto
python agent-orchestrator/scripts/match_skills.py --project meu-projeto "query aqui"Skills atribuidas ao projeto recebem +20 de boost automatico.
Imported: Padroes De Orquestracao
Quando multiplos skills sao relevantes, o orchestrator classifica o padrao:
Imported: 1. Pipeline Sequencial
Skills formam uma cadeia onde o output de uma alimenta a proxima.
Quando: Mix de skills "produtoras" (data-extraction, government-data) e "consumidoras" (messaging, social-media).
Exemplo: web-scraper coleta precos -> whatsapp-cloud-api envia alerta
user_query -> web-scraper -> whatsapp-cloud-api -> resultImported: 2. Execucao Paralela
Skills trabalham independentemente em aspectos diferentes da solicitacao.
Quando: Todas as skills tem o mesmo papel (todas produtoras ou todas consumidoras).
Exemplo: instagram publica post + whatsapp envia notificacao (ambos recebem o mesmo conteudo)
user_query -> [instagram, whatsapp-cloud-api] -> aggregated_resultImported: 3. Primario + Suporte
Uma skill principal lidera; outras fornecem dados de apoio.
Quando: Uma skill tem score muito superior as demais (>= 2x).
Exemplo: whatsapp-cloud-api envia mensagem (primario) + web-scraper fornece dados (suporte)
user_query -> whatsapp-cloud-api (primary) + web-scraper (support) -> resultImported: Gerenciamento De Projetos
Atribuir skills a projetos permite boost de relevancia e contexto persistente.
Imported: Arquivo De Projetos
agent-orchestrator/data/projects.jsonImported: Operacoes
Criar projeto: Adicionar entrada ao projects.json:
{
"name": "nome-do-projeto",
"created_at": "2026-02-25T12:00:00",
"skills": ["web-scraper", "whatsapp-cloud-api"],
"description": "Descricao do projeto"
}Adicionar skill a projeto: Atualizar o array skills do projeto.
Remover skill de projeto: Remover do array skills.
Consultar skills do projeto: Ler o projects.json e listar skills atribuidas.
Imported: Adicionando Novas Skills
Para adicionar uma nova skill ao ecossistema:
- Criar uma pasta em qualquer lugar sob
skills root: - Criar um
SKILL.mdcom frontmatter YAML:
---
name: minha-nova-skill
description: "Descricao com keywords de ativacao..."
---
#### Imported: Documentacao Da Skill
- Pronto! O auto-discovery detecta automaticamente na proxima solicitacao.
Opcionalmente, para discovery nativo do Claude Code:
4. Copiar o SKILL.md para .claude/skills/<nome>/SKILL.md
Imported: Tags De Capacidade Explicitas (Opcional)
Adicionar ao frontmatter para matching mais preciso:
capabilities: [data-extraction, web-automation]Imported: Ver Status De Todos Os Skills
python agent-orchestrator/scripts/scan_registry.py --statusImported: Interpretar Status
| Status | Significado |
|---|---|
| active | SKILL.md com name + description presentes |
| incomplete | SKILL.md existe mas falta name ou description |
| missing | Diretorio existe mas sem SKILL.md |
Imported: Skills Atuais Do Ecossistema
| Skill | Capacidades | Status |
|---|---|---|
| web-scraper | data-extraction, web-automation | active |
| junta-leiloeiros | government-data, data-extraction | active |
| whatsapp-cloud-api | messaging, api-integration | active |
| social-media, api-integration | partial |
Esta tabela e atualizada automaticamente via scan_registry.py --status.
Imported: Common Pitfalls
- Using this skill for tasks outside its domain expertise
- Applying recommendations without understanding your specific context
- Not providing enough project context for accurate analysis
Imported: Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
© diegosouzapw, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 8 other files (scripts, references) in skills/agent-orchestrator of diegosouzapw/awesome-omni-skills.
- SKILL.md
- ORIGIN.md
- metadata.json
- references/capability-taxonomy.md
- references/orchestration-patterns.md
- scripts/match_skills.py
- scripts/orchestrate.py
- scripts/requirements.txt
- scripts/scan_registry.py
Open the folder on GitHubat commit c3af004
Compare with similar skills
Agent Orchestrator next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Agent Orchestrator this skilldiegosouzapw/awesome-omni-skills | 159 | — | ~4.7k | Automated safety check: Pass | MIT | |
| MCP Server Builderanthropics/skills | 180k | 63 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Hook Development for Claude Code Pluginsanthropics/claude-plugins-official | 38k | 10 repos | ~4.1k | Automated safety check: Notes | Apache-2.0 | |
| Using Superpowersfarm-fe/farm | 5.6k | 36 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Executing Plans Inlineobra/superpowers | 297k | 2 repos | ~5.1k | Automated safety check: Pass | MIT | |
| Skill CreatorAzure/azqr | 796 | 89 repos | ~8.2k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
- Official
Hook Development for Claude Code Plugins
anthropics/claude-plugins-official
Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.
Using Superpowers
farm-fe/farm
A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Executing Plans Inline
obra/superpowers
Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.
- Official
Skill Creator
Azure/azqr
Create new skills, modify and improve existing skills, and measure skill performance.
- Official
Claude Code Agent Development
anthropics/claude-plugins-official
Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.
More from diegosouzapw/awesome-omni-skills
All 39 skills in this repoContent Creator
diegosouzapw/awesome-omni-skills
Content Creator workflow skill. An agent skill from diegosouzapw/awesome-omni-skills.
Helm Chart Scaffolding
diegosouzapw/awesome-omni-skills
Helm Chart Scaffolding workflow skill. An agent skill from diegosouzapw/awesome-omni-skills.
Prompt Engineering
diegosouzapw/awesome-omni-skills
Prompt Engineering Patterns workflow skill. An agent skill from diegosouzapw/awesome-omni-skills.
Prompt Engineering Patterns
diegosouzapw/awesome-omni-skills
Prompt Engineering Patterns workflow skill. An agent skill from diegosouzapw/awesome-omni-skills.
Prompt Library
diegosouzapw/awesome-omni-skills
📝 Prompt Library workflow skill. An agent skill from diegosouzapw/awesome-omni-skills.
Protocol Reverse Engineering
diegosouzapw/awesome-omni-skills
Protocol Reverse Engineering workflow skill. An agent skill from diegosouzapw/awesome-omni-skills.
Related
Categories
Questions about Agent Orchestrator
What does Agent Orchestrator do?
Agent Orchestrator workflow skill. An agent skill from diegosouzapw/awesome-omni-skills. Agent Orchestrator is an agent skill from diegosouzapw/awesome-omni-skills. Agent Orchestrator workflow skill.
When should I use Agent Orchestrator?
Agent Orchestrator fits situations like: the user needs Meta-skill que orquestra todos os agentes do ecossistema.
How do I install Agent Orchestrator in Claude Code?
Run `npx skills add diegosouzapw/awesome-omni-skills --skill agent-orchestrator -a claude-code`. Or copy the skill folder (skills/agent-orchestrator in diegosouzapw/awesome-omni-skills) into .claude/skills/agent-orchestrator in your project. Claude Code loads it when a task matches its description.
How do I install Agent Orchestrator in Codex?
Run `npx skills add diegosouzapw/awesome-omni-skills --skill agent-orchestrator -a codex`. Or copy the skill folder (skills/agent-orchestrator in diegosouzapw/awesome-omni-skills) into .agents/skills/agent-orchestrator in your project. Codex loads it when a task matches its description.
Can I use Agent Orchestrator in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add diegosouzapw/awesome-omni-skills --skill agent-orchestrator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/agent-orchestrator, .gemini/skills/agent-orchestrator, .github/skills/agent-orchestrator and .opencode/skills/agent-orchestrator in your project.
What does Agent Orchestrator need to run?
Going by SKILL.md and its folder, Agent Orchestrator needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.
Does Agent Orchestrator access the network?
SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Agent Orchestrator safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Agent Orchestrator use?
Agent Orchestrator is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Agent Orchestrator use?
About 4.7k tokens (SKILL.md is roughly 19k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.8k tokens, read only when the agent opens those files.
What are the alternatives to Agent Orchestrator?
Skills that share tags, products or a category with Agent Orchestrator: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Agent Orchestrator?
diegosouzapw (a GitHub user) maintains it in diegosouzapw/awesome-omni-skills, which has 159 GitHub stars. The repository holds 39 skills in this directory. The repository was last updated on July 8, 2026.
Source: diegosouzapw/awesome-omni-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.