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 findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/agent-test-long-runner/SKILL.md

Quality

Content

7%Scale 1-3

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, specific, or novel guidance. It is entirely composed of generic motivational instructions ('take your time', 'be thorough') and vague capability descriptions that Claude already understands. There is nothing concrete — no tools, no commands, no code, no specific workflows — that would change Claude's behavior in any meaningful way.

Suggestions

Define what 'long-running' actually means in practice: specific tool usage patterns, checkpointing strategies, how to handle context limits, or how to break large tasks into sub-tasks with concrete examples.

Replace vague instructions like 'Be Thorough' and 'Iterate' with concrete, executable workflows — e.g., a step-by-step process for codebase analysis with specific commands to run and validation checkpoints.

Add at least one complete, copy-paste-ready example showing the agent's expected input and output for a specific use case, rather than listing abstract use cases.

Remove all generic advice that Claude already knows (quality over speed, document everything, communicate progress) and focus only on novel, task-specific guidance.

Dimension	Reasoning	Score
Conciseness	The content is padded with vague, generic advice that Claude already knows ('Take Your Time', 'Be Thorough', 'Document Everything'). The capabilities list, instructions, and example use cases are all generic platitudes that add no specific knowledge or actionable guidance. Nearly every token is wasted.	1 / 3
Actionability	There are no concrete commands, executable code, specific tools, APIs, or precise instructions. Everything is abstract direction like 'Deep dive into codebases' and 'Continuously improve and refine your work' — none of which tells Claude what to actually do differently.	1 / 3
Workflow Clarity	The numbered 'Instructions' are not a workflow — they are vague behavioral guidelines ('Take Your Time', 'Iterate') with no sequencing, no validation checkpoints, and no concrete steps for any task.	1 / 3
Progressive Disclosure	The content is organized with clear section headers and is not a wall of text, but there are no references to external files and the content is short enough that progressive disclosure isn't really needed. The structure is adequate but the content itself is too thin to benefit from it.	2 / 3
	Total	5 / 12 Passed

Description

0%Scale 1-3

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 provides no information about what the skill does, when it should be used, or what distinguishes it from other skills. It reads as a placeholder rather than a functional description.

Suggestions

Replace the entire description with concrete actions the skill performs, e.g., 'Runs long-duration test suites and monitors their progress' or whatever the actual functionality is.

Add an explicit 'Use when...' clause with natural trigger terms that describe the scenarios where this skill should be selected, 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, as this is implementation detail that doesn't help Claude decide when to select the 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. The description only states it's an 'agent skill' and how to invoke it, with no explanation of purpose or trigger conditions.	1 / 3
Trigger Term Quality	The only terms present are 'test-long-runner' and '$agent-test-long-runner', which are internal identifiers rather than natural keywords a user would say. No natural language trigger terms are included.	1 / 3
Distinctiveness Conflict Risk	The description is so generic ('agent skill') that it provides no distinguishing characteristics. Without knowing what it does, it could conflict with virtually any other agent skill.	1 / 3
	Total	4 / 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
Path: .agents/skills/agent-test-long-runner/SKILL.md
Commit: 913f9ea

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