Scientific delegation framework for orchestrators — provide observations and success criteria while preserving agent autonomy. Use when assigning work to sub-agents, before invoking the Agent tool, or when preparing delegation prompts for specialist agents.
74
68%
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 ./plugins/agent-orchestration/skills/how-to-delegate/SKILL.mdQuality
Discovery
89%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 is a well-structured description that clearly communicates both what the skill does and when to use it, with explicit trigger conditions. Its main weakness is that the 'what' portion is somewhat abstract — describing a 'framework' rather than listing concrete discrete actions. The trigger terms are strong and domain-appropriate, making it highly distinguishable from other skills.
Suggestions
Add more concrete actions to the 'what' portion, e.g., 'structures task descriptions, defines success criteria, scopes context boundaries, and formats handoff prompts for sub-agents' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('scientific delegation framework for orchestrators') and some actions ('provide observations and success criteria', 'preserving agent autonomy'), but it doesn't list multiple concrete, specific actions — it's more of a conceptual framing than a list of discrete capabilities. | 2 / 3 |
Completeness | Clearly answers both 'what' (scientific delegation framework — provide observations and success criteria while preserving agent autonomy) and 'when' (when assigning work to sub-agents, before invoking the Agent tool, or when preparing delegation prompts for specialist agents) with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms that a user or orchestrator would use: 'delegation', 'sub-agents', 'Agent tool', 'delegation prompts', 'specialist agents', 'orchestrator'. These cover the key vocabulary someone would use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a very specific niche — delegation to sub-agents in an orchestrator context, referencing the Agent tool specifically. This is unlikely to conflict with other skills given its narrow, well-defined scope. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
47%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill has excellent workflow structure with a clear 10-step sequence, verification checkpoints, and conditional execution handling. However, it is significantly over-verbose — nearly every step includes 'Why' explanations and anti-pattern warnings that an orchestrator-level Claude should already understand. The content would benefit greatly from aggressive trimming of explanatory text while preserving the checklist structure and concrete template.
Suggestions
Remove all 'Why' explanation blocks — Claude as orchestrator already understands delegation principles. This alone would cut ~30% of tokens.
Consolidate the 'Core Delegation Principles' and the repeated anti-pattern warnings (no pre-gathering, no prescribing HOW) into a single compact list of 3-4 rules at the top, rather than repeating them across Steps 3, 5, 6, 8, and 10.
Move the detailed prompt template (Step 9) and the domain-skill routing flowchart (Step 1) into separate referenced files to improve progressive disclosure.
Tighten example placeholders — instead of showing both an example and an empty template for each field, provide just the template with a single inline example.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose for what is essentially a delegation checklist. Extensive 'Why' explanations after every step explain concepts an orchestrator-level Claude already knows (e.g., why pre-gathering is bad, why success criteria matter). The mermaid diagrams, repeated anti-pattern warnings, and template scaffolding with example placeholders bloat the content significantly. Much of this could be condensed to a compact checklist. | 1 / 3 |
Actionability | The skill provides a structured worksheet with concrete templates and examples, but it's fundamentally a meta-process (how to prepare a prompt) rather than executable code. The examples are illustrative placeholders rather than copy-paste-ready artifacts. The Agent tool invocation syntax is concrete, but most steps are fill-in-the-blank guidance rather than directly executable. | 2 / 3 |
Workflow Clarity | The 10-step sequence is clearly ordered with explicit dependencies between steps. Step 8 provides a pre-flight verification checklist that serves as a validation checkpoint before delegation. The conditional execution flowchart at the top handles the empty-arguments edge case. The feedback loop of 'verify -> fix -> re-verify' is present in the checklist structure. | 3 / 3 |
Progressive Disclosure | References the agent-orchestration skill at the top for the complete delegation flow, which is good. However, the SKILL.md itself is monolithic — all 10 steps with full explanations, examples, and mermaid diagrams are inline. Much of the detailed guidance (examples, anti-patterns, the prompt template) could be split into referenced files. No bundle files are provided to support progressive disclosure. | 2 / 3 |
Total | 8 / 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 | |
b9f32ec
Table of Contents
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.