performance-analysis

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

4.65x

Quality

61%

Does it follow best practices?

Impact

93%

4.65x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/performance-analysis/SKILL.md

Quality

Content

65%

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

The body is highly actionable with executable commands and concrete examples, but it is a long monolithic reference that conflates overview with deep detail. Workflow sequencing lacks validation feedback loops, and detailed reference material is inlined rather than progressively disclosed into separate files.

Suggestions

Move the detailed command syntax, sample report output, and metric catalogs into separate reference files (e.g. REFERENCE.md, REPORTS.md) and keep SKILL.md as a concise overview with signaled links.

Add explicit validation/checkpoint steps for the --fix auto-optimization flow (e.g. 'review detected issues, apply incrementally, re-run detection to confirm improvement').

Trim repetition across Quick Start, Core Capabilities, and Troubleshooting so each capability is documented once and cross-referenced.

Dimension	Reasoning	Score
Conciseness	The ~550-line body is mostly useful reference content but is verbose and repetitive (bottleneck detection recurs in Quick Start, Core Capabilities, and Troubleshooting), fitting the 'mostly efficient but could be tightened' anchor rather than the lean anchor.	2 / 3
Actionability	It provides fully executable copy-paste commands ('npx claude-flow bottleneck detect --fix --threshold 15') plus complete JavaScript and YAML examples, matching the 'fully executable code/commands; copy-paste ready' anchor.	3 / 3
Workflow Clarity	Sequences exist (CI/CD workflow, monitoring loop) but it is primarily a CLI reference with no explicit validation checkpoints or fix→retry feedback loops, matching the 'sequence present but checkpoints missing or implicit' anchor.	2 / 3
Progressive Disclosure	No bundle files exist and the body is a monolithic wall of inline reference material (full sample reports, metric catalogs, command syntax) that could be split out; the only references are 'See Also' links to external absolute paths, matching the 'content that should be separate is inline' anchor.	2 / 3
	Total	9 / 12 Passed

Description

57%

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 appropriately scoped to Claude Flow swarms and names its core capabilities, but it reads more like a capability summary than a trigger-rich skill description. It lacks an explicit 'Use when...' clause and natural user phrasing variations, which weakens trigger quality and completeness.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when swarm performance is slow, when profiling agent operations, or when the user mentions bottlenecks or optimization.'

Include natural-language variations users would actually say (e.g. 'slow swarm', 'profiling', 'speed up agents') alongside the technical terms.

Make the actions more concrete (e.g. 'detect communication, memory, and network bottlenecks') instead of the generic 'performance analysis' category.

Dimension	Reasoning	Score
Specificity	The description names three actions ('performance analysis, bottleneck detection, and optimization recommendations') but these are high-level categories rather than granular concrete operations, matching the 'names domain and some actions, but not comprehensive' anchor rather than the multiple-specific-actions anchor.	2 / 3
Completeness	It clearly answers 'what does this do' but provides no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	It contains relevant keywords ('performance', 'bottleneck', 'optimization') but omits natural variations a user might say such as 'slow', 'profiling', or 'speed up', fitting the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	The phrase 'for Claude Flow swarms' scopes it to a clear niche with distinct triggers unlikely to conflict with unrelated skills, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	9 / 12 Passed

Validation

75%

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 — 12 / 16 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
relative_links	Relative link issues: 5 suspicious	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	12 / 16 Passed

Repository: ruvnet/agentic-flow
Path: .claude/skills/performance-analysis/SKILL.md
Commit: d069fff

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