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 that restates the skill name without providing any meaningful information about what the skill does, how it works, or when it should be selected. It lacks concrete actions, natural trigger terms, explicit 'when to use' guidance, and any distinguishing details that would help Claude select it appropriately from a pool of skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Analyzes application performance profiles to identify CPU, memory, I/O, and network bottlenecks. Generates reports with root cause analysis and optimization recommendations.'
Add a 'Use when...' clause with natural trigger terms like 'performance bottleneck', 'slow application', 'latency', 'throughput issues', 'load testing results', 'profiling', 'response time degradation'.
Remove the redundant duplicate trigger term ('bottleneck identifier' listed twice) and replace with varied, natural phrases users would actually say when they need this skill.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'Bottleneck Identifier' without describing any concrete actions. It does not explain what specific operations or analyses the skill performs. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' clause is just a redundant restatement of the skill name rather than meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'bottleneck identifier' repeated twice. These are not natural keywords users would say — users are more likely to say things like 'find performance bottlenecks', 'slow response times', 'profiling', or 'latency issues'. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic — 'Performance Testing' and 'bottleneck identifier' could overlap with many performance-related skills. There are no distinct triggers or specific scope boundaries to differentiate it. | 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 an empty shell with no substantive content. It consists entirely of generic meta-descriptions ('provides step-by-step guidance,' 'follows industry best practices') without any actual instructions, code, tools, commands, or techniques for identifying performance bottlenecks. It would provide zero value to Claude beyond what the skill's title already conveys.
Suggestions
Add concrete, executable guidance: include specific commands or code for profiling tools (e.g., k6 scripts, JMeter configurations, flame graph generation) with example outputs showing how to interpret bottleneck indicators.
Define a clear workflow with validation steps, e.g.: 1) Run baseline load test, 2) Collect metrics (CPU, memory, latency percentiles), 3) Identify resource saturation points, 4) Validate findings by isolating the suspected bottleneck.
Remove all meta-description sections ('Purpose,' 'When to Use,' 'Capabilities,' 'Example Triggers') that describe the skill rather than teaching the task—these belong in frontmatter or are unnecessary.
Add specific examples of bottleneck patterns (e.g., database connection pool exhaustion, thread contention, memory leaks) with diagnostic commands and remediation steps.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic filler that tells Claude nothing it doesn't already know. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are vacuous. There is no actual technical content—every token is wasted on meta-description rather than instruction. | 1 / 3 |
Actionability | There are zero concrete steps, commands, code snippets, or specific techniques for identifying bottlenecks. The skill describes what it claims to do rather than providing any executable or actionable guidance. | 1 / 3 |
Workflow Clarity | No workflow, sequence of steps, or validation checkpoints are provided. The content merely states it 'provides step-by-step guidance' without actually including any steps. | 1 / 3 |
Progressive Disclosure | There are no references to detailed sub-documents, no structured navigation, and no separation of overview from detail. The content is a shallow placeholder with no depth to disclose. | 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
c8a915c
- 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.