agent-test-long-runner

Agent skill for test-long-runner - invoke with $agent-test-long-runner

0.98x

Quality

Does it follow best practices?

Impact

96%

0.98x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/agent-test-long-runner/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 is an extremely weak description that fails on every dimension. It reads as a placeholder or auto-generated stub, providing no information about what the skill does, when it should be used, or what distinguishes it from other skills. Claude would have no basis for selecting this skill appropriately.

Suggestions

Replace the entire description with concrete actions the skill performs (e.g., 'Runs long-duration test suites, monitors test progress, and reports results').

Add an explicit 'Use when...' clause with natural trigger terms that describe scenarios where this skill is needed (e.g., 'Use when the user needs to run extended test suites, long-running tests, or performance benchmarks').

Remove the invocation syntax ('invoke with $agent-test-long-runner') from the description and focus on capability and trigger information that helps Claude decide when to select this skill.

Dimension	Reasoning	Score
Specificity	The description provides no concrete actions whatsoever. 'Agent skill for test-long-runner' is entirely vague and does not describe what the skill actually does.	1 / 3
Completeness	Neither 'what does this do' nor 'when should Claude use it' is answered. There is no 'Use when...' clause and no description of functionality.	1 / 3
Trigger Term Quality	There are no natural keywords a user would say. 'test-long-runner' is an internal identifier, not a term users would naturally use in requests. The invocation syntax '$agent-test-long-runner' is technical jargon.	1 / 3
Distinctiveness Conflict Risk	The description is so vague that it provides no distinguishing characteristics. 'Agent skill' is completely generic and could apply to any skill.	1 / 3
	Total	4 / 12 Passed

Implementation

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

This skill provides no actionable or unique information beyond what Claude already knows. It reads as a generic motivational prompt rather than a skill that teaches Claude something new or provides concrete guidance for handling long-running tasks. There are no specific tools, commands, code examples, or workflows that would help Claude perform differently than it would by default.

Suggestions

Replace generic advice with concrete, actionable guidance: specify actual tools/commands for progress tracking, checkpointing, or managing long-running operations (e.g., how to break work into phases, save intermediate results, or handle timeouts).

Remove the 'Capabilities' section entirely—it just restates things Claude can already do—and replace with specific techniques or patterns unique to long-running task management.

Add a concrete workflow with validation steps, e.g., 'Phase 1: Scope the task and output a plan → Phase 2: Execute in chunks, writing intermediate results to files → Phase 3: Synthesize and validate completeness'.

Include at least one concrete example showing input, expected intermediate outputs, and final output format rather than just listing abstract use cases.

Dimension	Reasoning	Score
Conciseness	The content is almost entirely generic advice that Claude already knows ('Take Your Time', 'Be Thorough', 'Document Everything'). It explains nothing Claude doesn't already understand and adds no domain-specific knowledge. The capabilities list is just a restatement of general Claude abilities.	1 / 3
Actionability	There are no concrete commands, code examples, specific tools, or executable guidance. Everything is vague direction like 'Deep dive into codebases' and 'Comprehensive research across multiple sources' without any specifics on how to actually accomplish these tasks.	1 / 3
Workflow Clarity	The numbered 'Instructions' are generic platitudes ('Take Your Time', 'Be Thorough', 'Iterate') rather than a meaningful workflow. There are no concrete steps, no validation checkpoints, and no sequenced process for handling long-running tasks.	1 / 3
Progressive Disclosure	The content has some structural organization with clear section headers (Capabilities, Instructions, Output Format, Example Use Cases), but there are no references to external files and the content is a flat list of generalities that doesn't warrant or leverage any progressive disclosure pattern.	2 / 3
	Total	5 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: ruvnet/claude-flow
Commit: f547cec

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