agent-orchestrator
Meta-skill que orquestra todos os agentes do ecossistema. Scan automatico de skills, match por capacidades, coordenacao de workflows multi-skill e registry management.
52
41%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/agent-orchestrator/SKILL.mdQuality
Discovery
17%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description relies heavily on technical jargon and internal system terminology ('meta-skill', 'orquestra agentes', 'registry management') that users would never naturally use. It lacks a 'Use when...' clause entirely, making it difficult for Claude to know when to select this skill. The description would benefit significantly from concrete examples of what triggers it and plain-language explanations of its capabilities.
Suggestions
Add an explicit 'Use when...' clause describing scenarios that trigger this skill, e.g., 'Use when the user needs to combine multiple skills, route a task to the right agent, or manage available capabilities.'
Replace jargon with natural trigger terms users would actually say, such as 'coordinate tasks', 'find the right tool', 'combine capabilities', 'multi-step workflow'.
List concrete actions in plain language instead of abstract terms, e.g., 'Discovers available skills, routes user requests to the appropriate agent, and chains multiple skills together for complex tasks.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names some actions like 'scan automatico de skills', 'match por capacidades', 'coordenacao de workflows multi-skill', and 'registry management', but these are somewhat abstract and jargon-heavy rather than concrete user-facing actions. It describes domain and some actions but not comprehensively. | 2 / 3 |
Completeness | Provides a vague 'what' (orchestrates agents, scans skills, coordinates workflows) but completely lacks any 'when' clause or explicit trigger guidance. The absence of a 'Use when...' clause caps this at 2, and the weak 'what' brings it to 1. | 1 / 3 |
Trigger Term Quality | Uses technical jargon like 'meta-skill', 'orquestra agentes', 'registry management', 'workflows multi-skill' — these are not natural keywords a user would say. No common user-facing trigger terms are present. | 1 / 3 |
Distinctiveness Conflict Risk | The concept of a meta-skill orchestrator is somewhat distinctive, but terms like 'coordenacao de workflows' and 'management' are generic enough to potentially overlap with other coordination or management skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides genuinely useful, actionable orchestration guidance with concrete commands and clear decision logic for multi-skill coordination. Its main weaknesses are generic boilerplate sections that waste tokens, lack of error handling/validation in the workflow, and inline content that would benefit from being split into reference files. The core workflow is strong but the surrounding content dilutes its effectiveness.
Suggestions
Remove generic boilerplate sections (Best Practices, Common Pitfalls, Limitations, When to Use/Do Not Use) — they add no orchestrator-specific value and waste tokens.
Add error handling to the workflow: what to do if scan_registry.py fails, if match_skills.py returns no valid JSON, or if orchestrate.py encounters missing skills.
Move detailed content (matching algorithm scoring, project management, orchestration patterns) into separate reference files and link from the main skill with one-line summaries.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The core workflow and registry sections are reasonably efficient, but the skill includes significant boilerplate sections (Best Practices, Common Pitfalls, Limitations) that are generic filler adding no value. The 'When to Use' / 'Do Not Use' sections are vague and redundant. The 'Skills Atuais Do Ecossistema' table will become stale. Overall, there's meaningful content but padded with unnecessary generic advice. | 2 / 3 |
Actionability | The skill provides fully executable bash commands for each step (scan_registry.py, match_skills.py, orchestrate.py), concrete JSON examples for project configuration, clear tables explaining result interpretation, and specific scoring criteria for the matching algorithm. Commands are copy-paste ready with real paths. | 3 / 3 |
Workflow Clarity | The mandatory 3-step workflow is clearly sequenced with a decision table for branching (matched: 0/1/2+), and the orchestration patterns are well-explained. However, there are no validation or error-handling steps — what happens if scan_registry.py fails? What if match_skills.py returns malformed JSON? For a skill that runs on every request and involves multi-script coordination, the absence of feedback loops and error recovery caps this at 2. | 2 / 3 |
Progressive Disclosure | There is one reference to 'References/Orchestration-Patterns.md' for deeper detail, which is good. However, the skill is quite long (~200+ lines) with inline content that could be split out (matching algorithm details, project management, orchestration patterns). The registry metadata table and scoring criteria could live in reference files. Structure exists but content splitting is insufficient. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
b938655
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.