agent-orchestration

Multi-agent orchestration and state management.

Quality

14%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agent/skills/agent-orchestration/SKILL.md

Quality

Discovery

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 is extremely vague and fails to communicate what the skill actually does or when it should be used. It relies on technical buzzwords without providing concrete actions, natural trigger terms, or explicit usage guidance. The description would be nearly useless for Claude to distinguish this skill from others in a large skill library.

Suggestions

Add specific concrete actions the skill performs (e.g., 'Coordinates multiple AI agents, manages conversation handoffs, tracks agent states and task progress').

Include a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user mentions multiple agents, agent coordination, task delegation, or parallel AI workflows').

Replace technical jargon with user-friendly language that describes observable behaviors or outcomes.

Dimension	Reasoning	Score
Specificity	The description uses vague, abstract language ('orchestration', 'state management') without listing any concrete actions. It does not specify what actions the skill performs.	1 / 3
Completeness	Missing both clear 'what' (no specific actions listed) and 'when' (no explicit trigger guidance or 'Use when...' clause). Both components are very weak.	1 / 3
Trigger Term Quality	Contains technical jargon ('multi-agent orchestration', 'state management') that users would rarely say naturally. Missing common variations or user-friendly trigger terms.	1 / 3
Distinctiveness Conflict Risk	While 'multi-agent' provides some specificity, 'orchestration' and 'state management' are broad terms that could overlap with workflow, automation, or general programming skills.	2 / 3
	Total	5 / 12 Passed

Implementation

22%

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

This skill reads as a conceptual overview or design document rather than actionable guidance for Claude. It describes multi-agent patterns at a high level but provides zero executable code, concrete examples, or step-by-step workflows. Claude already understands these architectural concepts; the skill should instead provide specific implementation patterns, code templates, and validation steps.

Suggestions

Add executable code examples showing how to implement stateful graph logic (e.g., a concrete state machine pattern with Python code)

Replace abstract role descriptions with concrete prompts or delegation templates that Claude can actually use

Include a step-by-step workflow with validation checkpoints for the Reflexion Pattern (e.g., 'Execute step -> Check output against criteria -> If fail, log reason and retry with modification')

Remove conceptual explanations Claude already knows and replace with specific, copy-paste-ready implementation patterns

Dimension	Reasoning	Score
Conciseness	The content is relatively brief but includes conceptual explanations that Claude already understands (what nodes are, what roles mean). The emoji headers and attribution footer add unnecessary tokens.	2 / 3
Actionability	The skill is entirely abstract and descriptive with no concrete code, commands, or executable examples. Phrases like 'View complex tasks as a Graph' and 'Assign roles dynamically' describe concepts without showing how to implement them.	1 / 3
Workflow Clarity	Despite being about orchestration and workflows, there are no actual step sequences, validation checkpoints, or concrete processes. The 'Reflexion Pattern' mentions evaluation but provides no actionable implementation.	1 / 3
Progressive Disclosure	The content is organized into logical sections with clear headers, but there are no references to external files for detailed implementation. The structure is reasonable but the content itself lacks depth that would benefit from progressive disclosure.	2 / 3
	Total	6 / 12 Passed

Validation

90%

Warnings & errors only

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: Dokhacgiakhoa/antigravity-ide
Commit: 3395991

Reviewed: 25 days ago

Table of Contents

Discovery Implementation Validation

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.