performance-analysis

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

4.65x

Quality

57%

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

61%Weight 40%Scale 1-5

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

The content is highly actionable with executable commands and integration examples, but it is verbose and monolithic — sample reports and output formats are inlined rather than split into reference files, and the risky `--fix` flow lacks explicit validation checkpoints. Splitting reference material into bundle files and tightening the inline samples would raise the weaker dimensions.

Suggestions

Move the full output-format block, sample markdown report, and CI/CD/script examples into reference files under references/ and link to them one level deep, leaving SKILL.md as an overview.

Add an explicit validation checkpoint workflow for `--fix`: detect → review flagged issues → apply incrementally → re-run detection to confirm improvement, with a stop-on-regression step.

Trim repeated command-example sets and the decorative emoji output block to reduce token weight without losing actionable detail.

Dimension	Reasoning	Score
Conciseness	The body avoids explaining concepts Claude already knows, but inlines a full emoji output-format block, a complete sample markdown report, and repeated command-example sets that could be trimmed; it is mostly efficient but noticeably heavy.	3 / 5
Actionability	Provides copy-paste-ready `npx claude-flow` commands with documented options, MCP integration snippets, a Node automation script, and CI/CD YAML — fully executable and covering the common cases.	5 / 5
Workflow Clarity	A Quick Start sequence (detect → report → fix) exists, but `--fix` is a batch auto-optimization and validation checkpoints appear only as implicit best-practice bullets rather than enforced workflow steps, capping this dimension at 3.	3 / 5
Progressive Disclosure	No bundle files exist (references/scripts/assets are absent) and the skill is a single monolithic ~550-line SKILL.md with sample reports and output formats inlined; "See Also" links point to external paths rather than one-level-deep bundle references.	2 / 5
	Total	13 / 20 Passed

Description

53%Weight 40%Scale 1-5

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 conveys a clear domain and several action categories but stays generic and omits any explicit trigger guidance, so it lands at the midpoint on most dimensions. Adding a "Use when..." clause with natural trigger phrases would lift completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user reports slow swarm execution, high latency, or asks to profile/optimize Claude Flow swarm performance."

Replace generic verbs with concrete actions (e.g. "Detects communication, memory, and network bottlenecks and emits prioritized optimization recommendations") and drop the filler word "Comprehensive".

Include natural synonyms users actually say ("slow", "profiling", "metrics", "latency") to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (performance analysis for Claude Flow swarms) and 2-3 action categories — "performance analysis, bottleneck detection, and optimization recommendations" — but these are high-level verb-categories rather than concrete specific actions, and "Comprehensive" is filler.	3 / 5
Completeness	Provides a clear "what" but no "Use when..." clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Contains relevant keywords ("performance", "bottleneck", "optimization") but misses common natural variations users would say ("slow", "profiling", "metrics", "latency") and leans on jargon ("Claude Flow swarms").	3 / 5
Distinctiveness Conflict Risk	"for Claude Flow swarms" pins a clear niche with mostly distinct triggers, with only minor overlap risk against closely related sibling skills like swarm-orchestration and memory-management.	4 / 5
	Total	13 / 20 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: e993605

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.