agent-test-long-runner
Agent skill for test-long-runner - invoke with $agent-test-long-runner
Install with Tessl CLI
npx tessl i github:ruvnet/claude-flow --skill agent-test-long-runner42
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/skillEvaluation — 96%
↓ 0.98xAgent success when using this skill
Validation for skill structure
Discovery
0%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 critically deficient across all dimensions. It provides only a technical invocation command without explaining what the skill does, when to use it, or any natural trigger terms. Claude would have no basis for selecting this skill appropriately from a list of available skills.
Suggestions
Add concrete actions describing what 'test-long-runner' actually does (e.g., 'Executes long-running test suites, monitors test progress, reports results')
Include a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when running extended tests, integration tests, or when test execution time exceeds normal limits')
Remove or supplement the invocation syntax with functional description - the '$agent-test-long-runner' command alone provides no semantic value for skill selection
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for test-long-runner' is completely abstract with no indication of what the skill actually does. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. It only provides an invocation command with no functional description or usage guidance. | 1 / 3 |
Trigger Term Quality | The only potential trigger is the technical invocation command '$agent-test-long-runner'. There are no natural keywords a user would say when needing this skill. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it's impossible to distinguish from other skills. 'Agent skill' could apply to virtually any agent-based functionality. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a persona description than actionable guidance. It tells Claude what kind of agent to be rather than how to actually perform long-running tasks. The content lacks concrete examples, specific workflows, validation steps, or executable code that would help Claude succeed at complex, time-intensive work.
Suggestions
Replace abstract instructions ('Be Thorough', 'Take Your Time') with concrete workflows showing how to break down and checkpoint long-running tasks
Add specific, executable examples for at least one use case (e.g., a step-by-step codebase analysis workflow with validation checkpoints)
Include progress reporting templates or structured output formats that Claude should use during long tasks
Define concrete criteria for when to pause, validate work, or request user feedback during extended operations
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is moderately efficient but includes some unnecessary padding like 'You are a specialized test agent' and generic advice Claude already knows ('quality over speed', 'be thorough'). The capabilities list describes rather than instructs. | 2 / 3 |
Actionability | The skill provides only vague, abstract guidance with no concrete code, commands, or executable examples. Instructions like 'Take Your Time' and 'Be Thorough' are not actionable - they describe attitudes rather than specific actions to take. | 1 / 3 |
Workflow Clarity | No clear workflow or sequence is provided. The numbered 'Instructions' are generic principles, not steps in a process. There are no validation checkpoints or feedback loops for the long-running tasks mentioned. | 1 / 3 |
Progressive Disclosure | The content is reasonably organized with clear section headers, but it's a monolithic file with no references to external resources. For a skill about complex, long-running tasks, there could be links to specific guides for each use case. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
100%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.
- 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.