agent-performance-analyzer

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

1.00x

Quality

Does it follow best practices?

Impact

99%

1.00x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/agent-performance-analyzer/SKILL.md

Quality

Discovery

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 essentially a label with an invocation command, providing no meaningful information about what the skill does, when to use it, or what domain it covers. It fails across all dimensions due to extreme vagueness and lack of any actionable detail. It would be nearly impossible for Claude to correctly select this skill from a pool of available options.

Suggestions

Describe specific concrete actions the skill performs, e.g., 'Profiles application code, identifies performance bottlenecks, measures execution time, and generates optimization recommendations.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about slow code, performance profiling, benchmarking, latency issues, or CPU/memory usage analysis.'

Specify the domain or technology scope (e.g., web apps, Python code, database queries) to make the skill clearly distinguishable from other performance-related skills.

Dimension	Reasoning	Score
Specificity	The description provides no concrete actions whatsoever. 'Agent skill for performance-analyzer' is entirely vague and does not describe what the skill actually does—no specific capabilities, operations, or outputs are mentioned.	1 / 3
Completeness	The description fails to answer both 'what does this do' and 'when should Claude use it.' There is no explanation of capabilities and no 'Use when...' clause or equivalent trigger guidance.	1 / 3
Trigger Term Quality	The only potentially relevant term is 'performance-analyzer,' which is a tool name rather than a natural keyword a user would say. There are no natural language trigger terms like 'profiling,' 'bottleneck,' 'latency,' 'benchmark,' etc.	1 / 3
Distinctiveness Conflict Risk	'Performance-analyzer' is generic enough to conflict with many possible skills (code profiling, web performance, database optimization, etc.). Without specifics, it's impossible to distinguish this skill from others in a similar domain.	1 / 3
	Total	4 / 12 Passed

Implementation

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 conceptual overview document masquerading as an actionable skill. It describes what a performance analyzer would do in abstract terms but provides zero concrete, executable guidance — no real commands, no actual tools, no specific code, no measurable procedures. The content is heavily verbose, explaining general software engineering concepts Claude already understands, while failing to provide the specific, novel instructions that would make this skill useful.

Suggestions

Replace abstract workflow steps with concrete, executable commands or code — e.g., specific profiling tools to run, actual shell commands for collecting metrics, real scripts for analysis.

Remove sections that describe general concepts Claude already knows (bottleneck types, best practices like 'continuous monitoring') and focus only on project-specific procedures and tool usage.

Add validation checkpoints with concrete success/failure criteria — e.g., 'If P95 latency exceeds X ms, investigate Y using command Z'.

Either provide actual bundle files with scripts/tools that implement the analysis, or reference specific real tools and provide executable examples of their usage.

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive explanations of general concepts Claude already knows (what bottleneck types are, what KPIs are, what continuous monitoring means). Lists of abstract categories like 'Detection Methods' and 'Optimization Strategies' add no actionable value. The content is heavily padded with organizational boilerplate.	1 / 3
Actionability	No executable code, no concrete commands, no specific tools or APIs. Everything is abstract description — 'Gather execution metrics', 'Profile resource usage', 'Compare against baselines' — without any indication of how to actually do these things. The code blocks contain numbered lists of vague steps, not executable instructions. The optimization examples are hypothetical narratives, not reproducible procedures.	1 / 3
Workflow Clarity	The three-phase workflow (Data Collection, Analysis, Recommendation) consists entirely of vague numbered lists with no concrete actions, no validation checkpoints, no error handling, and no feedback loops. There is no way for Claude to follow these 'steps' as actual instructions since they describe categories of activity rather than specific actions to take.	1 / 3
Progressive Disclosure	Monolithic wall of text with no references to external files and no bundle files. All content is inline regardless of depth or relevance. Sections like 'Advanced Features' mention ML-based prediction and A/B testing with zero supporting detail or references, making them empty promises rather than useful navigation points.	1 / 3
	Total	4 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: ruvnet/ruflo
Commit: 48ca369

Reviewed: 5 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.