CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-v3-performance-engineer

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

35

3.20x
Quality

0%

Does it follow best practices?

Impact

96%

3.20x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/agent-v3-performance-engineer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

0%

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

This skill is a verbose, aspirational design document masquerading as an actionable skill. It contains hundreds of lines of non-executable pseudocode TypeScript classes referencing undefined APIs, decorative ASCII art boxes, and vague performance targets with no concrete steps to achieve them. It provides zero actionable guidance that Claude could follow to actually perform performance optimization work.

Suggestions

Replace pseudocode benchmark classes with actual executable commands or scripts (e.g., real npm benchmark commands, actual profiling tool invocations with concrete file paths).

Add a clear step-by-step workflow: what to run first, how to measure baseline, how to apply optimizations, how to validate results, with explicit validation checkpoints.

Remove the ASCII box diagrams and consolidate the performance targets into a single concise table — the same information is repeated multiple times.

Split benchmark suites into separate referenced files and keep SKILL.md as a concise overview with navigation links to detailed benchmark implementations.

DimensionReasoningScore

Conciseness

Extremely verbose at 300+ lines. The ASCII box diagrams are decorative and redundant with the text. The TypeScript benchmark classes are lengthy pseudocode that Claude cannot execute — they describe hypothetical APIs (this.sona.adapt, this.flashAttention, etc.) that don't exist. Massive amounts of token budget spent on non-actionable content.

1 / 3

Actionability

Despite containing extensive TypeScript code blocks, none of it is executable — all methods reference undefined APIs (this.agentDBMemory.hnswSearch, this.standardAttention, this.flashAttention, etc.). There are no concrete commands, real file paths, actual library imports, or copy-paste-ready instructions. The checklists are aspirational rather than actionable.

1 / 3

Workflow Clarity

There is no clear sequential workflow for performing any optimization task. The content presents benchmark class definitions and target matrices but never describes what steps to actually take, in what order, or how to validate results. No feedback loops or error recovery for what are clearly complex, multi-step operations.

1 / 3

Progressive Disclosure

Monolithic wall of text with no references to external files and no bundle files provided. All content is inline with no clear hierarchy or navigation structure. The 'Coordination with V3 Team' section references other agents but provides no links or paths. Content that could be split (each benchmark suite, monitoring, regression) is all dumped into one file.

1 / 3

Total

4

/

12

Passed

Description

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 is an extremely poor skill description that provides virtually no useful information. It only contains an invocation command and a generic label, failing to describe any capabilities, actions, or trigger conditions. Claude would have no basis for selecting this skill appropriately from a list of available skills.

Suggestions

Add concrete actions describing what the skill does, e.g., 'Profiles application performance, identifies bottlenecks, optimizes query execution, and analyzes resource utilization.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user mentions performance optimization, slow queries, latency issues, benchmarking, profiling, or resource bottlenecks.'

Specify the domain or technology scope (e.g., v3 platform, specific language/framework) to make the skill distinctive and reduce conflict risk with other performance-related skills.

DimensionReasoningScore

Specificity

The description contains no concrete actions whatsoever. It only states it's an 'agent skill' with an invocation command, providing zero information about what the skill actually does.

1 / 3

Completeness

Neither 'what does this do' nor 'when should Claude use it' is answered. The description only provides an invocation command with no functional or contextual information.

1 / 3

Trigger Term Quality

The only potentially relevant term is 'performance-engineer' embedded in the agent name, but there are no natural keywords a user would say. No terms like 'optimize', 'benchmark', 'latency', 'profiling', etc.

1 / 3

Distinctiveness Conflict Risk

The description is so vague that it provides no distinguishing characteristics. 'Performance engineer' could overlap with many domains (web performance, database optimization, load testing, etc.) and there's nothing to differentiate it.

1 / 3

Total

4

/

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

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