performance-analysis

Comprehensive performance analysis, bottleneck detection, and optimization recommendations for Claude Flow swarms

4.65x

Quality

37%

Does it follow best practices?

Impact

93%

4.65x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.claude/skills/performance-analysis/SKILL.md

Quality

Discovery

32%

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 identifies a specific domain (Claude Flow swarms) and lists three high-level capabilities, which gives it moderate specificity and distinctiveness. However, it lacks an explicit 'Use when...' clause, which significantly hurts completeness, and the trigger terms could be more varied to capture natural user language. Overall, it's a functional but incomplete description that would benefit from explicit trigger guidance and more concrete action details.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about swarm performance, slow agents, throughput issues, or wants to optimize a Claude Flow swarm.'

Include more natural trigger term variations such as 'slow swarm', 'agent throughput', 'swarm profiling', 'task latency', or 'parallel execution performance'.

Make the capabilities more concrete by specifying what is analyzed (e.g., 'Analyzes task completion times, agent utilization rates, and message queue depths') rather than using broad terms like 'comprehensive performance analysis'.

Dimension	Reasoning	Score
Specificity	Names the domain (Claude Flow swarms) and lists some actions (performance analysis, bottleneck detection, optimization recommendations), but these are somewhat high-level and not deeply concrete—e.g., it doesn't specify what kinds of bottlenecks, what metrics are analyzed, or what form recommendations take.	2 / 3
Completeness	The description answers 'what does this do' at a moderate level but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and since the 'when' is entirely absent and the 'what' is only moderately detailed, this scores at the lower end.	1 / 3
Trigger Term Quality	Includes relevant terms like 'performance analysis', 'bottleneck detection', 'optimization', and 'Claude Flow swarms', but misses common natural variations a user might say such as 'slow swarm', 'swarm profiling', 'agent performance', 'throughput', or 'latency'.	2 / 3
Distinctiveness Conflict Risk	The mention of 'Claude Flow swarms' provides some niche specificity, but 'performance analysis' and 'optimization recommendations' are broad terms that could overlap with general performance profiling or optimization skills not specific to swarms.	2 / 3
	Total	7 / 12 Passed

Implementation

42%

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

The skill is highly actionable with concrete, executable commands and code examples, but is severely bloated. It tries to be a comprehensive reference document rather than a concise skill overview with pointers to detailed materials. The lack of progressive disclosure and extreme verbosity significantly undermine its effectiveness as a SKILL.md file.

Suggestions

Move the sample report output, CI/CD YAML, custom analysis scripts, and troubleshooting sections into separate referenced files (e.g., EXAMPLES.md, CI-CD.md, TROUBLESHOOTING.md) and keep only a Quick Start and command summary in SKILL.md.

Cut the 'Metrics Analyzed' section listing all bottleneck categories — Claude doesn't need explanations of what communication latency or cache hit rates are.

Add an explicit multi-step workflow with validation checkpoints for the detect-then-fix process, e.g., '1. Detect → 2. Review output → 3. Apply --fix → 4. Re-detect to verify improvement'.

Remove the 'Performance Impact' percentage estimates and 'Best Practices' prose — these are generic advice that don't add actionable value for Claude.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~400+ lines. Massive amounts of content that could be split into reference files. Includes extensive sample outputs, exhaustive option lists, full CI/CD workflow YAML, complete Node.js scripts, and lengthy best practices sections that pad the document significantly. Much of this (e.g., explaining what bottleneck categories are, listing typical improvement percentages) is filler Claude doesn't need.	1 / 3
Actionability	Provides fully executable CLI commands, MCP integration code, JavaScript scripts, CI/CD YAML configurations, and concrete examples with specific flags and options. Commands are copy-paste ready with real option values.	3 / 3
Workflow Clarity	Individual commands are clear, but there's no explicit multi-step workflow with validation checkpoints for the overall analysis process. The 'analyze and auto-fix' path lacks a validation step (e.g., review results before applying --fix). The best practices section mentions 'always review before applying --fix' but this isn't integrated into the workflow as an explicit checkpoint.	2 / 3
Progressive Disclosure	This is a monolithic wall of text with everything inlined. The 'See Also' section references external files, but the body contains ~400 lines of detailed content (sample reports, full scripts, CI/CD configs, troubleshooting guides) that should be in separate referenced files. No bundle files are provided to support progressive disclosure despite the references at the bottom.	1 / 3
	Total	7 / 12 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (564 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: ruvnet/agentic-flow
Commit: 6a06854

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