wolf-scripts-agents

Agent coordination, orchestration, and multi-agent workflow management scripts

1.42x

Quality

28%

Does it follow best practices?

Impact

97%

1.42x

Average score across 6 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/agent-coordination/wolf-scripts-agents-majiayu000-claude-skill-regist/SKILL.md

Quality

Discovery

22%

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 too vague and abstract to effectively guide skill selection. It lacks concrete actions, explicit trigger conditions, and natural user-facing keywords. It reads more like a category label than a functional skill description.

Suggestions

Add a 'Use when...' clause specifying explicit triggers, e.g., 'Use when the user needs to coordinate multiple agents, set up agent pipelines, or manage parallel task delegation.'

List specific concrete actions the skill performs, e.g., 'Spawns sub-agents, routes tasks between agents, merges agent outputs, and manages agent lifecycle.'

Include natural keyword variations users might say, such as 'parallel agents', 'delegate tasks', 'agent pipeline', 'sub-agent', 'fan-out', or 'task routing'.

Dimension	Reasoning	Score
Specificity	The description uses vague, abstract language like 'coordination', 'orchestration', and 'management scripts' without listing any concrete actions. It does not specify what the skill actually does (e.g., spawn agents, route tasks, merge results).	1 / 3
Completeness	The description only vaguely addresses 'what' and completely omits 'when' — there is no 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Terms like 'agent', 'multi-agent', 'orchestration', and 'workflow' are somewhat relevant keywords a user might use, but the description lacks common natural variations or specific trigger phrases (e.g., 'parallel tasks', 'delegate to sub-agents', 'agent pipeline').	2 / 3
Distinctiveness Conflict Risk	The mention of 'agent coordination' and 'multi-agent workflow' provides some niche specificity, but 'orchestration' and 'workflow management scripts' are broad enough to overlap with general automation, scripting, or workflow skills.	2 / 3
	Total	6 / 12 Passed

Implementation

35%

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

This skill is comprehensive in scope but severely over-verbose, explaining patterns at length with pseudocode rather than executable code. The good/bad examples section alone is longer than many complete skills and largely restates information already presented. The content would benefit greatly from aggressive trimming, replacing pseudocode with real executable snippets, and splitting detailed reference material into separate files.

Suggestions

Cut content by at least 50%: remove the lengthy good/bad examples section (or move to a separate EXAMPLES.md), eliminate the 'Red Flags' section which states obvious points, and trim the 'After Using This Skill' section which is overly prescriptive.

Replace pseudocode class definitions (WorkflowOrchestrator, MailboxClient with comment-only methods) with either real executable code or remove them entirely and just show usage patterns with CLI commands.

Move detailed role file patterns, message format schemas, and workflow state schemas to separate reference files, keeping only a brief summary and link in the main skill.

Add explicit error recovery steps inline in workflow descriptions (e.g., what happens when a phase fails, how to handle timeout, concrete retry logic) rather than just listing 'Don't skip error handling' in best practices.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~600+ lines. Includes extensive pseudocode class definitions, lengthy good/bad examples with redundant explanations, 'Red Flags' section that over-explains obvious points, and a massive verification checklist. Much of this could be condensed to 1/3 the size without losing actionable content. The good/bad examples alone consume ~150 lines repeating what was already stated.	1 / 3
Actionability	Provides configuration objects, CLI commands, and usage patterns, but most code is pseudocode or illustrative rather than executable (e.g., WorkflowOrchestrator class with comment-only method bodies, incomplete MailboxClient). The CLI examples are concrete and useful, but the core API examples are not copy-paste ready.	2 / 3
Workflow Clarity	The workflow orchestrator section describes sequential phases and state saving, and the integration example shows a complete flow with validation. However, explicit validation checkpoints and error recovery feedback loops are mostly described abstractly (e.g., 'Don't skip error handling') rather than shown concretely. The verification checklist at the end helps but doesn't compensate for missing inline validation steps in the workflow descriptions.	2 / 3
Progressive Disclosure	References related skills (wolf-roles, wolf-governance, etc.) and lists file locations, which is good. However, the document is monolithic with massive inline content that should be split into separate files (e.g., the extensive good/bad examples, the detailed role file patterns, the mailbox system). The 'Related Skills' section is well-structured but the main body doesn't practice what progressive disclosure preaches.	2 / 3
	Total	7 / 12 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (943 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: majiayu000/claude-skill-registry
Commit: 632759f

Reviewed: 1 day 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.