CtrlK
BlogDocsLog inGet started
Tessl Logo

how-to-delegate

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.

60

Quality

68%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./plugins/agent-orchestration/skills/how-to-delegate/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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 process and verification checkpoints, but is severely undermined by verbosity. Nearly every step includes a 'Why' explanation and extensive examples that an orchestrator-level Claude doesn't need. The content would be roughly 60% shorter and equally effective as a lean checklist with the template and a few critical constraints.

Suggestions

Remove all 'Why' explanation blocks — Claude as orchestrator already understands delegation principles. Convert to a compact checklist with inline constraints only where non-obvious.

Collapse the 'Core Delegation Principles' section into 3-4 bullet-point rules without the 'Reason' paragraph, and remove the mermaid diagrams which add visual complexity but little actionable value.

Extract the prompt template (Step 9) and example fills into a separate TEMPLATE.md reference file to reduce the main skill's token footprint.

Remove placeholder example text (e.g., '[Example: "Fix authentication..."]') from every field — one or two examples total suffice to establish the pattern.

DimensionReasoningScore

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 instructions.

2 / 3

Workflow Clarity

The 10-step workflow is clearly sequenced 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 pattern.

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

Description

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 strong description that clearly defines its niche in multi-agent delegation and provides explicit trigger guidance via a 'Use when' clause with relevant terms. The main weakness is that the 'what' portion could be more concrete about the specific actions or outputs the skill produces, relying somewhat on abstract concepts like 'scientific delegation framework' and 'preserving agent autonomy' rather than listing tangible deliverables.

Suggestions

Make the capabilities more concrete by listing specific outputs, e.g., 'Structures delegation prompts with clear observations, constraints, and success criteria' rather than the abstract 'scientific delegation framework'.

DimensionReasoningScore

Specificity

The description names the domain ('scientific delegation framework for orchestrators') and some actions ('provide observations and success criteria', 'preserving agent autonomy'), but these are somewhat abstract rather than listing multiple concrete, specific actions like 'create delegation prompts', 'structure task breakdowns', 'define acceptance criteria'.

2 / 3

Completeness

Clearly answers both 'what' (scientific delegation framework providing observations and success criteria while preserving agent autonomy) and 'when' (explicit 'Use when' clause covering assigning work to sub-agents, before invoking the Agent tool, or preparing delegation prompts).

3 / 3

Trigger Term Quality

Includes strong natural trigger terms that users/orchestrators would actually use: 'sub-agents', 'Agent tool', 'delegation prompts', 'specialist agents', 'orchestrators', 'assigning work'. These cover the key vocabulary someone would use when needing this skill.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive niche — focuses specifically on agent-to-agent delegation patterns with clear triggers like 'Agent tool', 'sub-agents', and 'delegation prompts'. Unlikely to conflict with other skills given its narrow, well-defined scope.

3 / 3

Total

11

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
Jamie-BitFlight/claude_skills
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.