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 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 reports results' or whatever the actual functionality is).

Add an explicit 'Use when...' clause with natural trigger terms that describe scenarios where this skill should be selected.

Remove the invocation syntax ('invoke with $agent-test-long-runner') from the description and replace it with user-facing language describing the skill's purpose and capabilities.

Dimension	Reasoning	Score
Specificity	The description contains 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 for test-long-runner' could be anything and offers no clear niche or distinct triggers.	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 is essentially a collection of generic motivational instructions with no actionable, concrete, or executable guidance. It tells Claude to 'be thorough' and 'take your time' without providing any specific tools, commands, workflows, or domain knowledge that Claude doesn't already possess. The skill adds virtually no value to Claude's context window.

Suggestions

Replace the generic capabilities list and instructions with concrete, executable workflows for at least one specific long-running task (e.g., a step-by-step codebase analysis process with specific commands and validation checkpoints).

Remove all advice Claude already knows (e.g., 'quality over speed', 'document everything') and replace with domain-specific knowledge or tool-specific instructions that Claude wouldn't have by default.

Add concrete code examples or command sequences for the claimed use cases, such as a specific approach to security auditing with tool invocations and output formats.

Define a clear workflow with validation steps for at least one complex task, including how to handle errors and when to checkpoint progress.

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 and example use cases add no actionable information. Nearly every line could be removed without loss.	1 / 3
Actionability	There are no concrete commands, code examples, executable steps, or specific instructions. Everything is abstract direction like 'deep dive into codebases' and 'comprehensive research across multiple sources' with no indication of how to actually do any of it.	1 / 3
Workflow Clarity	The numbered 'Instructions' are generic platitudes (e.g., 'Iterate', 'Communicate Progress') rather than a sequenced workflow. There are no validation checkpoints, no concrete steps, and no feedback loops for any process.	1 / 3
Progressive Disclosure	The content has some structural organization with headers and sections, but there are no references to external files and no bundle to support deeper content. The sections themselves are shallow and don't warrant splitting, but the content is at least not a wall of text.	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: 9d4a9ea

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