wolf-scripts-agents
Agent coordination, orchestration, and multi-agent workflow management scripts
Install with Tessl CLI
npx tessl i github:majiayu000/claude-skill-registry-data --skill wolf-scripts-agents52
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 abstract and lacks actionable detail. It names a domain (agent coordination) but fails to specify concrete capabilities or provide explicit trigger conditions. Without a 'Use when...' clause and specific actions, Claude cannot reliably distinguish when to select this skill.
Suggestions
Add specific concrete actions like 'spawn sub-agents, route tasks between agents, aggregate multi-agent results, manage agent lifecycles'
Include a 'Use when...' clause with explicit triggers such as 'Use when the user needs to coordinate multiple agents, run parallel agent tasks, or orchestrate agent workflows'
Add natural trigger terms users might say: 'multiple agents', 'parallel agents', 'agent pipeline', 'sub-agents', 'agent delegation'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses abstract language like 'coordination', 'orchestration', and 'management' without listing any concrete actions. It doesn't specify what operations can be performed (e.g., spawn agents, route tasks, aggregate results). | 1 / 3 |
Completeness | Only vaguely addresses 'what' (agent-related scripts) with no 'when' clause. There's no explicit trigger guidance telling Claude when to select this skill over others. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords ('agent', 'multi-agent', 'workflow', 'orchestration') that users might say, but 'coordination' and 'management scripts' are more technical jargon. Missing natural variations like 'multiple agents', 'agent tasks', or 'parallel agents'. | 2 / 3 |
Distinctiveness Conflict Risk | The 'multi-agent' and 'orchestration' terms provide some specificity, but 'workflow management' is generic and could overlap with task automation, CI/CD, or general scripting skills. | 2 / 3 |
Total | 6 / 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 with excellent workflow clarity and validation checkpoints. However, it is severely over-engineered for a SKILL.md file - the extensive inline code examples, configuration objects, and detailed API documentation should be in separate reference files. The content would be more effective at ~150 lines with references to detailed documentation.
Suggestions
Extract detailed API documentation (AgentExecutor, WorkflowOrchestrator, MailboxClient classes) to separate REFERENCE.md files and link to them
Move the extensive Good/Bad examples to an EXAMPLES.md file, keeping only 1-2 brief examples inline
Consolidate the configuration objects into a single CONFIG.md reference rather than showing full objects inline
Remove explanatory text about patterns Claude already understands (e.g., 'Provides unified interface for...', 'Asynchronous inter-agent communication using...') and jump directly to usage
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~700+ lines. Contains extensive code examples that could be referenced externally, repetitive explanations of patterns Claude already understands (class structures, async patterns), and overly detailed configuration objects that could be summarized. | 1 / 3 |
Actionability | Provides fully executable JavaScript code examples, specific command-line invocations, concrete configuration objects, and copy-paste ready patterns. The code is complete and executable, not pseudocode. | 3 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with explicit validation checkpoints (e.g., 'Validate immediately', 'Only when valid'). The Complete Workflow Example shows clear phase transitions with state saving and validation at each step. Good/Bad examples demonstrate proper vs improper workflow execution. | 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 should be in separate reference files. The 'Related Skills' section is good but the body contains too much detail that could be externalized. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%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 | |
- 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.