orchestration
Patrones de orquestacion para trabajo paralelo en Savvy AI. Incluye decision matrix subagents vs agent teams, composiciones de equipos pre-configuradas, y mejores practicas. Usar cuando se planifique trabajo paralelo, se coordinen multiples agentes, o se necesite delegar tareas complejas.
80
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
75%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 has good completeness with an explicit 'Usar cuando' clause and is highly distinctive to its niche (Savvy AI agent orchestration). However, it could be stronger on specificity by listing concrete actions rather than just components, and could include more natural trigger term variations that users might actually say.
Suggestions
Add concrete action verbs like 'configure parallel workflows', 'create agent teams', 'set up task delegation' to improve specificity
Include additional trigger term variations such as 'multi-agent', 'concurrent execution', 'workflow coordination' to capture more user phrasings
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (orchestration patterns, parallel work in Savvy AI) and mentions some components (decision matrix, pre-configured team compositions, best practices), but doesn't list concrete actions like 'create agent teams', 'configure delegation rules', or 'set up parallel workflows'. | 2 / 3 |
Completeness | Clearly answers both what (orchestration patterns, decision matrix, team compositions, best practices) AND when with explicit 'Usar cuando' clause specifying parallel work planning, coordinating multiple agents, or delegating complex tasks. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'trabajo paralelo', 'multiples agentes', 'delegar tareas', and 'subagents vs agent teams', but misses common variations users might say such as 'multi-agent', 'concurrent tasks', 'workflow orchestration', or 'agent coordination'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly specific to Savvy AI platform and parallel agent orchestration, with distinct triggers around 'subagents', 'agent teams', and 'trabajo paralelo' that are unlikely to conflict with general coding or document skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong orchestration guide with excellent actionability - the team composition prompts are immediately usable and well-tailored to Savvy AI's architecture. The workflow clarity is excellent with explicit dependencies and file ownership. The main weakness is that it's somewhat verbose for a skill file and could benefit from splitting the detailed team compositions into separate reference files.
Suggestions
Consider moving the 6 detailed team compositions to a separate TEAM_COMPOSITIONS.md file and referencing them from the main skill
Trim the conceptual explanations in 'Agent Teams: Conceptos Clave' - Claude understands these concepts; focus on Savvy-specific configurations
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is generally efficient but includes some explanatory text that Claude would already understand (e.g., explaining what subagents and agent teams are conceptually). The comparison table and team compositions are well-structured, but some sections could be tighter. | 2 / 3 |
Actionability | Provides concrete, copy-paste ready prompts for each team composition, specific file paths for Savvy AI, clear command references, and keyboard shortcuts. The prompts are immediately executable with minimal modification. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with explicit dependencies (e.g., 'Domain Expert -> Data Implementer, UI Builder (paralelo) -> Test Writer'). Each team composition specifies the order of operations and coordination points. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's a monolithic document that could benefit from splitting team compositions into separate files. The 'Referencia Rapida' section at the end is good, but detailed compositions could be referenced rather than inline. | 2 / 3 |
Total | 10 / 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 | |
- 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.