orchestrator

Intelligent system orchestration for complex tasks using MCP and Pi Agent.

Quality

11%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./public/skills/0xnagato/orchestrator/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 critically weak across all dimensions. It relies entirely on vague buzzwords ('intelligent', 'complex tasks', 'orchestration') without explaining what the skill actually does or when it should be used. The technical terms 'MCP' and 'Pi Agent' are unexplained and would not help Claude select this skill appropriately.

Suggestions

Replace abstract language with specific concrete actions (e.g., 'Coordinates multiple API calls', 'Manages multi-step workflows', 'Executes sequential system commands').

Add an explicit 'Use when...' clause with natural trigger terms users would actually say (e.g., 'Use when automating multi-step processes, coordinating between services, or running sequential operations').

Define what 'MCP' and 'Pi Agent' are or replace with user-understandable terms to improve trigger term quality and distinctiveness.

Dimension	Reasoning	Score
Specificity	The description uses vague, abstract language like 'intelligent system orchestration' and 'complex tasks' without listing any concrete actions. No specific capabilities are described.	1 / 3
Completeness	Missing both clear 'what' (no concrete actions listed) and 'when' (no explicit trigger guidance or 'Use when...' clause). The description fails to answer either question adequately.	1 / 3
Trigger Term Quality	Contains technical jargon ('MCP', 'Pi Agent', 'orchestration') that users would not naturally say. No common user-facing keywords or natural language triggers are present.	1 / 3
Distinctiveness Conflict Risk	'Complex tasks' and 'system orchestration' are extremely generic and could apply to virtually any automation or multi-step skill, creating high conflict risk with other skills.	1 / 3
	Total	4 / 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 provides a high-level conceptual framework for orchestration but lacks the concrete, executable guidance needed to be useful. It describes what to do abstractly without showing how to do it. The example is too vague to be actionable, missing actual command syntax or code.

Suggestions

Add concrete, executable examples showing actual mcporter command syntax (e.g., `mcporter call tavily_search --query "..."`) instead of abstract descriptions

Include a real worked example with actual commands/code that Claude can copy and adapt, not just a conceptual outline

Add validation steps to the workflow (e.g., 'Verify tool availability before calling', 'Check response status')

Provide direct links to referenced skills (coding-agent, web-search) or inline the essential usage patterns

Dimension	Reasoning	Score
Conciseness	Reasonably brief but includes some unnecessary framing ('You are an Intelligent Orchestrator') and vague capability descriptions that don't add actionable value.	2 / 3
Actionability	Extremely vague with no concrete code, commands, or executable examples. Phrases like 'use mcporter to call external MCP tools' provide no actual syntax or usage patterns.	1 / 3
Workflow Clarity	The workflow is abstract and lacks any validation checkpoints. Steps like 'Analyze' and 'Plan' are not actionable, and there's no guidance on error handling or verification.	1 / 3
Progressive Disclosure	References other skills/tools (coding-agent, mcporter, web-search) but doesn't provide clear links or explain how to access them. Structure is simple but navigation to deeper content is unclear.	2 / 3
	Total	6 / 12 Passed

Validation

72%

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 — 8 / 11 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	8 / 11 Passed

Repository: Demerzels-lab/elsamultiskillagent
Commit: 45f9fac

Reviewed: 27 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.