CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-orchestration

Multi-agent orchestration and state management.

15

Quality

0%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

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

Quality

Content

0%

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

This skill is essentially a conceptual overview of multi-agent orchestration frameworks that provides no actionable guidance whatsoever. It describes abstract patterns (graph logic, delegation, semantic orchestration, self-correction) using buzzwords and framework references but never gives Claude concrete instructions, code, commands, or examples to actually implement anything. The content teaches Claude concepts it already knows while failing to provide the specific, executable guidance that would make it useful.

Suggestions

Replace abstract descriptions with concrete, executable code examples — e.g., show actual Python code for implementing a state graph with conditional edges, or a specific multi-agent delegation loop with defined message-passing patterns.

Add a clear step-by-step workflow with validation checkpoints, such as: '1. Define the task graph → 2. Assign agent roles → 3. Execute with state tracking → 4. Validate each node output before proceeding → 5. Handle failures with retry logic'.

Remove explanations of concepts Claude already understands (what a planner/coder/reviewer is, what intent detection means) and focus exclusively on project-specific conventions, tool configurations, or custom patterns unique to this workspace.

Either create supporting bundle files (e.g., PATTERNS.md for detailed agent patterns, EXAMPLES.md for worked examples) with clear references, or consolidate into a lean, actionable single file with concrete implementation guidance.

DimensionReasoningScore

Conciseness

The content explains high-level concepts (graph-based thinking, multi-agent delegation patterns, semantic orchestration) that Claude already understands. It's padded with buzzwords, emoji, and framework name-drops without adding actionable knowledge. Phrases like 'Node-Based Thinking: View complex tasks as a Graph of nodes (Steps)' teach Claude nothing new.

1 / 3

Actionability

There is zero executable code, no concrete commands, no specific examples, and no copy-paste-ready guidance. Every bullet point is an abstract description ('Assign roles dynamically', 'Dynamically choose the best tool') rather than a concrete instruction with implementation details.

1 / 3

Workflow Clarity

Despite being about orchestration and workflows, the skill provides no clear sequenced steps, no validation checkpoints, and no feedback loops. The 'Reflexion Pattern' and 'Self-Correction' sections describe concepts abstractly without specifying how to actually implement them step by step.

1 / 3

Progressive Disclosure

The content is a monolithic list of abstract concepts with no references to supporting files, no bundle structure, and no navigation aids. There's no separation between overview and detailed content, and no external references despite the complexity of the topic warranting them.

1 / 3

Total

4

/

12

Passed

Description

0%

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 critically underdeveloped. It relies entirely on abstract technical jargon without specifying concrete actions, use cases, or trigger conditions. It would be nearly impossible for Claude to reliably select this skill from a pool of alternatives, and it risks conflicting with many other skills due to its generic terminology.

Suggestions

List specific concrete actions the skill performs, e.g., 'Spawns and coordinates multiple sub-agents, manages shared state across agent workflows, handles agent communication and task delegation.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user needs to coordinate multiple agents, manage workflow state, or delegate tasks across parallel processes.'

Include domain-specific keywords users might naturally say, such as 'agents', 'parallel tasks', 'workflow coordination', 'task delegation', 'sub-agents', to improve trigger term coverage and distinctiveness.

DimensionReasoningScore

Specificity

The description uses vague, abstract language ('orchestration', 'state management') without listing any concrete actions. It does not specify what the skill actually does in practical terms.

1 / 3

Completeness

The description weakly addresses 'what' with abstract concepts and completely omits any 'when' guidance or explicit trigger clause. Both dimensions are very weak.

1 / 3

Trigger Term Quality

The terms 'multi-agent orchestration' and 'state management' are technical jargon that users are unlikely to naturally say. There are no common user-facing keywords or variations included.

1 / 3

Distinctiveness Conflict Risk

'State management' is extremely broad and could overlap with many skills (database management, session handling, workflow tools, etc.). 'Multi-agent orchestration' is vague enough to conflict with various automation or coordination skills.

1 / 3

Total

4

/

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
Dokhacgiakhoa/antigravity-ide
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.