bottleneck-identifier
Bottleneck Identifier - Auto-activating skill for Performance Testing. Triggers on: bottleneck identifier, bottleneck identifier Part of the Performance Testing skill category.
30
0%
Does it follow best practices?
Impact
80%
1.09xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/10-performance-testing/bottleneck-identifier/SKILL.mdQuality
Discovery
0%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 placeholder with no substantive content. It names the skill and its category but provides zero information about what it actually does, what concrete actions it performs, or when it should be selected. The trigger terms are just the skill name repeated, offering no useful signal for skill selection.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Analyzes application performance metrics to identify CPU, memory, I/O, and network bottlenecks in distributed systems. Profiles response times, detects slow database queries, and pinpoints resource contention.'
Add a 'Use when...' clause with natural trigger terms, e.g., 'Use when the user mentions slow performance, latency issues, throughput problems, performance profiling, load testing results, or asks why their application is slow.'
Replace the duplicated trigger term with diverse natural keywords users would actually say, such as 'performance bottleneck', 'slow response', 'high latency', 'resource contention', 'CPU spike', 'memory leak', 'load test analysis'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Bottleneck Identifier') and its category ('Performance Testing') but provides no concrete actions. There is no mention of what the skill actually does—no verbs describing specific capabilities like 'analyzes response times', 'identifies slow queries', or 'profiles CPU usage'. | 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 meaningful 'Use when...' clause—only a self-referential trigger that restates the skill name. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'bottleneck identifier' repeated twice, which is the skill's own name rather than natural keywords a user would say. Missing natural terms like 'slow performance', 'latency', 'throughput', 'profiling', 'performance bottleneck', 'load testing', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is too vague to distinguish this skill from any other performance-related skill. 'Performance Testing' is a broad category, and without specific actions or distinct triggers, it could easily conflict with other performance, profiling, or testing skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is entirely a meta-description placeholder with no actionable content whatsoever. It describes what the skill should do without providing any actual instructions, code, commands, or techniques for bottleneck identification in performance testing. It is essentially an empty shell that would provide no value to Claude.
Suggestions
Replace the meta-description with actual bottleneck identification techniques: specific commands for profiling (e.g., flame graphs, `perf`, `top`), k6/JMeter scripts for load testing, and concrete metrics thresholds to look for.
Add executable code examples for common bottleneck identification workflows, such as a k6 load test script with response time analysis or a JMeter configuration snippet.
Define a clear multi-step workflow: e.g., 1) establish baseline metrics, 2) run load test, 3) analyze results for CPU/memory/IO/network bottlenecks, 4) validate findings with targeted tests.
Remove all self-referential content ('This skill activates when...', 'Example Triggers') which wastes tokens describing the skill rather than teaching Claude how to identify bottlenecks.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic filler that tells Claude nothing useful. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are vague platitudes. The entire file explains what the skill is rather than providing any actual instruction. | 1 / 3 |
Actionability | There is zero concrete, executable guidance—no code, no commands, no specific techniques for identifying bottlenecks. The content only describes the skill abstractly without instructing Claude on how to actually perform bottleneck identification. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or sequenced actions. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no references to supporting files, no structured navigation, and no bundle files to support it. There is no meaningful content to disclose progressively. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%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 |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
22f797a
- Reviewed
Table of Contents
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.