CD performance-analysis
Comprehensive performance analysis, bottleneck detection, and optimization recommendations for Claude Flow swarms
Comprehensive performance analysis, bottleneck detection, and optimization recommendations for Claude Flow swarms
As a process D 46/100 · Unfinished process — References files that are not bundled: $workspaces$claude-code-flow/.claude$commands$analysis$bottleneck-detect.md, $workspaces$claude-code-flow/.claude$commands$analysis$performance-report.md, $workspaces$claude-code-flow/.claude$commands$analysis$performance-bottlenecks.md
The same skill appears in 1 more place: RA-Skills
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 113 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
description-no-whenneither description nor a "## When to Use" section says when to use the skill - warning
missing-refreference to a missing file: $workspaces$claude-code-flow/.claude$commands$analysis$bottleneck-detect.md - warning
missing-refreference to a missing file: $workspaces$claude-code-flow/.claude$commands$analysis$performance-report.md - warning
missing-refreference to a missing file: $workspaces$claude-code-flow/.claude$commands$analysis$performance-bottlenecks.md - warning
missing-refreference to a missing file: ..$swarm-orchestration/SKILL.md - warning
missing-refreference to a missing file: ..$memory-management/SKILL.md
Process rating: all ten parameters 46/100
- 0Tools and files. 5 referenced file(s) missing: $workspaces$claude-code-flow/.claude$commands$analysis$bottleneck-detect.md, $workspaces$claude-code-flow/.claude$commands$analysis$performance-report.md, $workspaces$claude-code-flow/.claude$commands$analysis$performance-bottlenecks.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 135 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3562 tokens
- low The response is described with custom markup (5 tags): a typed call is more reliable
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 113: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +4Structure: 41 headings
- +3Step-by-step instructions: 135 items
- +3Output format is stated explicitly
- +4Has examples (17 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 54.