wolf-scripts-agents

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

1.42x

Quality

47%

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

32%

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 identifies a specific domain (multi-agent systems) but remains too abstract and lacks actionable detail. It fails to provide explicit trigger conditions for when Claude should select this skill, and the capabilities listed are high-level categories rather than concrete actions. The description would benefit significantly from specific examples and a 'Use when...' clause.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user needs to coordinate multiple agents, spawn parallel workers, or manage distributed task execution'

Replace abstract terms with concrete actions: instead of 'orchestration', specify 'spawn sub-agents, route tasks between agents, aggregate results from parallel workers'

Include natural trigger terms users would say: 'parallel agents', 'spawn workers', 'agent-to-agent communication', 'task distribution'

Dimension	Reasoning	Score
Specificity	Names the domain (agent coordination, orchestration, multi-agent workflows) and implies actions (management scripts), but doesn't list concrete specific actions like 'spawn agents', 'route tasks', or 'monitor agent status'.	2 / 3
Completeness	Only addresses 'what' at a high level (agent coordination scripts) but completely lacks any 'when' guidance or 'Use when...' clause. Per rubric guidelines, missing explicit trigger guidance caps this at 2, but the 'what' is also weak, warranting a 1.	1 / 3
Trigger Term Quality	Includes relevant terms like 'agent coordination', 'orchestration', 'multi-agent', and 'workflow' that users might say, but missing common variations like 'spawn agents', 'parallel tasks', 'agent communication', or 'distributed work'.	2 / 3
Distinctiveness Conflict Risk	The multi-agent focus provides some distinction, but 'workflow management scripts' is generic enough to potentially overlap with general automation or scripting skills. Could conflict with task management or general orchestration tools.	2 / 3
	Total	7 / 12 Passed

Implementation

62%

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

This skill provides highly actionable, executable guidance for agent coordination with excellent workflow clarity and validation checkpoints. However, it is severely over-engineered for a SKILL.md file - the content is extremely verbose and would benefit from aggressive condensation, moving detailed code examples to separate reference files while keeping the SKILL.md as a concise overview with pointers.

Suggestions

Reduce content by 60-70% by moving detailed code examples (class definitions, full API examples) to separate reference files like AGENT-EXECUTOR-REFERENCE.md, WORKFLOW-ORCHESTRATOR-REFERENCE.md

Condense the good/bad examples section to 1-2 brief examples instead of extensive multi-page comparisons

Remove explanatory text that describes what classes/methods do - Claude understands code structure; just show the code

Convert the 'Best Practices' section to a compact checklist format instead of verbose do/don't lists

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~700+ lines with extensive code examples that could be condensed. Includes unnecessary explanations of concepts Claude understands (class structures, JSON formats, file system patterns). The good/bad examples section alone is ~150 lines and could be drastically shortened.	1 / 3
Actionability	Provides fully executable code examples with complete JavaScript/bash snippets, specific file paths, concrete configuration objects, and copy-paste ready command line usage. The code examples are complete and executable, not pseudocode.	3 / 3
Workflow Clarity	Multi-step workflows are clearly sequenced with explicit validation checkpoints. The workflow orchestrator pattern shows numbered phases with status indicators, the validation examples show pass/fail states, and there are clear feedback loops (validate → fix → retry) throughout.	3 / 3
Progressive Disclosure	Has some structure with clear sections and references to related skills at the end, but the main content is monolithic with extensive inline code that could be split into separate reference files. The 'Related Skills' section provides good navigation, but the body contains too much detail that should be in separate files.	2 / 3
	Total	9 / 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: 6213d1a

Reviewed: about 5 hours 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.