agent-benchmark-suite

Agent skill for benchmark-suite - invoke with $agent-benchmark-suite

2.17x

Quality

Does it follow best practices?

Impact

89%

2.17x

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-benchmark-suite/SKILL.md

Quality

Content

0%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 is an extremely verbose, non-actionable document that presents hundreds of lines of pseudocode class definitions without any executable instructions, clear workflows, or practical guidance. It reads more like an aspirational architecture document than a skill that teaches Claude how to perform benchmarking. The content violates all four rubric dimensions by being bloated, abstract, unsequenced, and monolithic.

Suggestions

Replace pseudocode class definitions with actual executable commands or scripts that Claude can run to perform benchmarking tasks.

Add a clear step-by-step workflow (e.g., 1. Set up benchmark → 2. Run suite → 3. Validate results → 4. Compare with baseline) with explicit validation checkpoints.

Reduce content by 80%+ by removing class constructors, hypothetical method signatures, and explanatory comments—focus only on what Claude needs to do.

If detailed reference material is needed, split into separate files (e.g., BENCHMARKS.md, REGRESSION.md) and provide a concise overview in SKILL.md with clear links.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~500+ lines. Extensively explains class architectures, constructors, and patterns Claude already knows. The 'Agent Profile' section, repeated explanatory comments, and massive pseudocode class definitions add no actionable value. Most code is non-executable scaffolding illustrating OOP patterns rather than providing real instructions.	1 / 3
Actionability	Despite the volume of code, none of it is executable—it's all pseudocode referencing undefined classes (ThroughputBenchmark, StatisticalRegressionDetector, etc.) and hypothetical MCP methods. The CLI commands reference 'npx claude-flow' but provide no installation, setup, or real usage context. Claude cannot copy-paste and run any of this.	1 / 3
Workflow Clarity	There is no clear step-by-step workflow for performing benchmarking. The content describes class structures and method signatures but never tells Claude 'do step 1, then step 2, then validate.' No validation checkpoints, no error recovery guidance, no sequenced process for the agent to follow.	1 / 3
Progressive Disclosure	Monolithic wall of text with no references to external files and no bundle files provided. All content is inlined in one massive document with no clear navigation structure. The sections are just increasingly large code blocks with no hierarchy or signposting for when to use what.	1 / 3
	Total	4 / 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 all dimensions. It reads as a placeholder or auto-generated stub rather than a functional skill description. It provides no information about what the skill does, when to use it, or what distinguishes it from other skills.

Suggestions

Add concrete actions describing what the benchmark suite does (e.g., 'Runs performance benchmarks, measures execution time, compares results across test runs').

Add an explicit 'Use when...' clause with natural trigger terms (e.g., 'Use when the user asks to run benchmarks, measure performance, or compare test results').

Replace the invocation instruction ('invoke with $agent-benchmark-suite') with functional description content — invocation syntax belongs in the skill body, not the description field.

Dimension	Reasoning	Score
Specificity	The description provides no concrete actions whatsoever. 'Agent skill for benchmark-suite' 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, providing no functional or contextual information.	1 / 3
Trigger Term Quality	The only keyword is 'benchmark-suite', which is a technical/internal name rather than a natural term a user would say. There are no natural language trigger terms like 'run benchmarks', 'performance testing', etc.	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 any number of other skills.	1 / 3
	Total	4 / 12 Passed

Validation

90%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (670 lines); consider splitting into references/ and linking	Warning

	Total	10 / 11 Passed

Repository: ruvnet/claude-flow
Path: .agents/skills/agent-benchmark-suite/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.