agent-performance-benchmarker

Agent skill for performance-benchmarker - invoke with $agent-performance-benchmarker

2.89x

Quality

13%

Does it follow best practices?

Impact

81%

2.89x

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-performance-benchmarker/SKILL.md

Quality

Content

27%

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

The content is a large, monolithic dump of consensus-benchmarking code that is verbose and not directly executable due to undefined dependencies, with no sequenced workflow or external references for navigation.

Suggestions

Trim the body to a concise overview plus a runnable entry-point example, moving the detailed class implementations into reference files.

Make examples executable by providing or stubbing the undefined collaborators (TimeSeriesDatabase, SystemMonitor, PerformanceModel, etc.) so the code is copy-paste ready.

Restructure as a sequenced workflow with explicit validation checkpoints for the long-running benchmark and optimization operations.

Dimension	Reasoning	Score
Conciseness	The body is hundreds of lines of detailed JavaScript implementation that pads and explains a full design rather than distilling only what Claude needs, matching the verbose/padded-with-unnecessary-context anchor.	1 / 3
Actionability	The code is concrete but not executable as written because it depends on many undefined collaborators (TimeSeriesDatabase, SystemMonitor, PerformanceModel, AdaptiveOptimizer), leaving key details missing.	2 / 3
Workflow Clarity	It presents class definitions rather than a clearly sequenced multi-step workflow, and the batch/long-running benchmark operations lack explicit validation checkpoints or feedback loops, capping it at 2.	2 / 3
Progressive Disclosure	It is a monolithic wall of text with all implementation inline and no references to separate files, and no bundle files exist to provide external structure.	1 / 3
	Total	6 / 12 Passed

Description

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is a placeholder-style invocation line rather than a capability description: it conveys no concrete actions, no natural trigger terms, and no usage guidance, making it indistinguishable from other skills.

Suggestions

Replace the templated text with a concrete capability statement, e.g. 'Measures throughput, latency, and resource usage of distributed consensus protocols'.

Add an explicit 'Use when...' clause with natural trigger terms users would say, such as 'benchmarking consensus protocols', 'Raft/Byzantine throughput', or 'consensus latency analysis'.

Use third-person voice describing what the skill does rather than internal invocation mechanics like 'invoke with $agent-performance-benchmarker'.

Dimension	Reasoning	Score
Specificity	The description 'Agent skill for performance-benchmarker - invoke with $agent-performance-benchmarker' names no concrete actions, only a templated invocation line, matching the vague/no-actions anchor.	1 / 3
Completeness	It states neither what the skill does nor when to use it; there is no capability description and no 'Use when...' clause, so both what and when are missing.	1 / 3
Trigger Term Quality	It contains only the slug 'performance-benchmarker' and internal invocation mechanics ('$agent-performance-benchmarker'), with no natural keywords a user would actually say.	1 / 3
Distinctiveness Conflict Risk	The text is a generic template that could describe any agent skill and provides no distinctive triggers, so it would conflict with many skills.	1 / 3
	Total	4 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

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

	Total	15 / 16 Passed

Repository: ruvnet/claude-flow
Path: .agents/skills/agent-performance-benchmarker/SKILL.md
Commit: 26c35b5

Reviewed: about 7 hours 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.