CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

agent-orchestration

Agent Orchestration Rules

Quality

53%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/agent-orchestration/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-organized, mostly concise instructional skill with a concrete decision table and copy-paste-ready example prompt, scoring well on actionability, workflow clarity, and progressive disclosure. Its main weakness is mild persuasive/illustrative padding in the wrong-right diagrams that keeps conciseness at the midpoint.

DimensionReasoningScore

Conciseness

The body is mostly efficient (compact ASCII diagrams, a tight decision table, short bullet triggers) and assumes Claude knows what agents are, but the wrong/right diagrams and "Key Insight" are persuasive framing beyond pure instruction, fitting the mostly-efficient-but-could-be-tightened anchor.

3 / 5

Actionability

Concrete guidance is provided via a yes/no decision table by task type and a copy-paste-ready example prompt with an explicit agent-invocation pattern ("Spawn agent('implement X per plan')"); it stops at 4 because the guidance is instructional/meta rather than fully executable code covering common cases.

4 / 5

Workflow Clarity

As a single-purpose decision skill the core action is unambiguous (use agents for multi-file/plan-phase tasks, not for single-line fixes), but there is no explicit multi-step sequence with validation checkpoints or feedback loops, fitting the clear-but-minor-validation-gaps anchor; no destructive/batch cap applies here.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent) and the body makes no file references; at under ~50 lines, single-purpose, and with well-organized section headers, it satisfies the simple-skill exception that progressive disclosure scores 5 with just well-organized sections and no need for external files.

5 / 5

Total

16

/

20

Passed

Description

12%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is a bare title that names a domain but supplies no concrete actions, no user-natural trigger phrases, and no use-when guidance, leaving it vague on both what and when. Its one relative strength is a reasonably distinct niche that limits gross conflict with unrelated skills.

Suggestions

Rewrite the description to state 2-3 concrete actions in third person (e.g., "Delegates multi-file implementation tasks to subagents to preserve main-context tokens"), moving it from a noun phrase to action statements.

Add an explicit "Use when..." clause with natural trigger phrases users actually say, such as "Use when the user asks to implement, build, follow the plan, or complete a multi-file feature, and the task is too small to skip but too large to do inline."

Include natural synonyms/keywords (e.g., "implementation agents", "subagents", "context preservation", "do phase X") so the description surfaces for the phrasings in the body's Trigger Words section.

DimensionReasoningScore

Specificity

The description "Agent Orchestration Rules" names a specific domain but provides no concrete action verbs (e.g., spawn, delegate, preserve context), matching the anchor that names the domain with minimal/generic actions; it is above the entirely-vague anchor because the domain is concrete, but below anchor 3 which requires 1-2 specific actions.

2 / 5

Completeness

It lacks any "Use when..." / when clause and the "what" is an extremely vague title noun phrase rather than stated actions, fitting the anchor where both what and when are missing or extremely vague; the guideline caps completeness at 3 for a missing when clause, and here even the what is barely present.

1 / 5

Trigger Term Quality

"Agent Orchestration Rules" is technical meta-jargon rather than language a user would naturally say, and it contains no natural trigger phrases, synonyms, or file extensions, fitting the anchor for no natural keywords / only technical jargon.

1 / 5

Distinctiveness Conflict Risk

"Agent Orchestration Rules" names a somewhat specific niche that is distinguishable from generic file/data skills, but without explicit triggers it could still overlap with other agent- or orchestration-related skills, fitting the somewhat-specific-but-overlap-risk anchor; voice is third person so no specificity penalty applies.

3 / 5

Total

7

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

parcadei/Continuous-Claude-v3

Path

.claude/skills/agent-orchestration/SKILL.md

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.