bottleneck-identifier
Bottleneck Identifier - Auto-activating skill for Performance Testing. Triggers on: bottleneck identifier, bottleneck identifier Part of the Performance Testing skill category.
32
Quality
3%
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
7%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 severely underdeveloped, consisting only of the skill name, a redundant trigger term, and category label. It provides no information about what the skill actually does, what types of bottlenecks it identifies, or when Claude should use it. The description fails to serve its primary purpose of helping Claude distinguish this skill from others.
Suggestions
Add specific actions the skill performs, e.g., 'Analyzes application performance metrics to identify CPU, memory, I/O, and network bottlenecks in distributed systems'
Add a 'Use when...' clause with natural trigger terms like 'slow performance', 'latency issues', 'throughput problems', 'performance profiling', 'system slowdown'
Include the types of systems or contexts this applies to (web applications, databases, microservices) to distinguish from other performance tools
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Bottleneck Identifier') and category ('Performance Testing') without describing any concrete actions. There are no verbs indicating what the skill actually does - no 'analyzes', 'identifies', 'reports', etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and has no 'Use when...' clause or equivalent guidance for when Claude should select this skill. Both the what and when are missing or extremely weak. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just 'bottleneck identifier' repeated twice, which is the skill name itself rather than natural user language. Missing terms users would actually say like 'slow', 'performance issues', 'latency', 'throughput', 'profiling'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'bottleneck identifier' is somewhat specific terminology, the lack of detail about what kind of bottlenecks (CPU, memory, network, database) or what systems it applies to means it could overlap with other performance-related skills. | 2 / 3 |
Total | 5 / 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 content is an empty template with no actual instructional value. It contains only meta-descriptions of what a skill should do without any concrete guidance on bottleneck identification techniques, tools, metrics to analyze, or workflows to follow. The content fails on all dimensions as it provides no actionable information for performance testing or bottleneck analysis.
Suggestions
Add concrete code examples for bottleneck identification using specific tools (e.g., profilers, APM tools, k6 scripts with metrics collection)
Include a clear workflow: 1) Establish baseline metrics, 2) Run load test, 3) Identify resource constraints (CPU/memory/IO/network), 4) Analyze hotspots, 5) Validate improvements
Provide specific metrics and thresholds to look for (e.g., response time percentiles, throughput degradation patterns, resource utilization thresholds)
Remove all generic boilerplate text and replace with actionable techniques for common bottleneck types (database queries, memory leaks, thread contention, network latency)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actionable information. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific techniques for identifying bottlenecks. The content describes what the skill supposedly does rather than instructing how to do it. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. For a bottleneck identification task, there should be clear steps for profiling, measuring, analyzing metrics, and validating findings - none of which are present. | 1 / 3 |
Progressive Disclosure | The content is a shallow placeholder with no actual substance to organize. There are no references to detailed materials, examples, or related documentation that would help with progressive disclosure. | 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
0c08951
- 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.