CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-v3-performance-engineer

Agent skill for v3-performance-engineer - invoke with $agent-v3-performance-engineer

48

3.20x
Quality

Does it follow best practices?

Impact

96%

3.20x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

35%

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

The skill body is an over-long, monolithic document of illustrative benchmark scaffolds and decorative target matrices rather than lean, executable guidance. It has sectioning and a regression loop but no progressive file structure and no truly copy-paste-ready code.

Suggestions

Cut the ASCII-art target boxes and de-duplicate the targets (they already appear in the frontmatter hooks and the checklist), keeping only the actionable benchmark logic.

Either implement the helper methods the benchmark classes depend on or replace the class skeletons with minimal, self-contained, runnable benchmark snippets.

Add a validation gate to the benchmarking workflow (run baseline → run optimized → assert target met → only then report success) and split large reference material into referenced files.

DimensionReasoningScore

Conciseness

The ~400-line body is padded with decorative ASCII-art target boxes and repeats the same performance targets across the YAML hooks, the matrix, and the checklists, explaining scaffolding Claude does not need.

1 / 3

Actionability

The TypeScript benchmark classes show real timing patterns (performance.now(), process.memoryUsage()) but call undefined helpers like this.spawn15Agents(), this.standardAttention(), and this.sona.adapt(), so the code is structured yet not copy-paste executable.

2 / 3

Workflow Clarity

A target-achievement checklist and a regression-detection feedback loop exist, but there is no clearly sequenced optimization workflow with explicit validation checkpoints gating the batch benchmarking operations.

2 / 3

Progressive Disclosure

The body is a single monolithic ~400-line file with no references, scripts, or assets directories and no external file links, yet it is reasonably sectioned with headings — content that should be split remains inline.

2 / 3

Total

7

/

12

Passed

Description

7%

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 boilerplate ("Agent skill for X - invoke with $X") that names a domain but conveys no concrete capabilities, no natural trigger terms, and no usage guidance. It reads as a templated placeholder rather than a real skill description.

Suggestions

Replace the boilerplate with concrete actions, e.g. "Benchmarks and optimizes claude-flow v3 performance — Flash Attention speedup, AgentDB HNSW search, memory and startup optimization."

Add an explicit "Use when…" clause naming natural triggers users would say, such as "Use when optimizing agent performance, running benchmarks, or validating speedup targets."

Drop the "$agent-v3-performance-engineer" invocation token from the description; expose natural keywords (benchmark, speedup, latency, memory) instead.

DimensionReasoningScore

Specificity

The description only names a domain ("v3-performance-engineer") and states it is an "Agent skill for" it, with no concrete actions named — matching the vague "Helps with documents" anchor.

1 / 3

Completeness

It weakly gestures at "what" ("Agent skill for v3-performance-engineer") and entirely omits "when" — there is no "Use when…" clause or equivalent trigger guidance, so it fails both halves.

1 / 3

Trigger Term Quality

The only trigger is the literal invocation token "$agent-v3-performance-engineer", which is technical syntax rather than natural language a user would say; there are no natural keywords like "performance", "benchmark", or "speedup".

1 / 3

Distinctiveness Conflict Risk

The specific "v3-performance-engineer" name carves out a clear niche unlikely to conflict with unrelated skills, but the description body itself is generic boilerplate that does not reinforce the distinctiveness.

2 / 3

Total

5

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
ruvnet/claude-flow
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.