bottleneck-identifier
Bottleneck Identifier - Auto-activating skill for Performance Testing. Triggers on: bottleneck identifier, bottleneck identifier Part of the Performance Testing skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill bottleneck-identifierOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially serving as a placeholder rather than a functional skill description. It lacks any concrete actions, meaningful trigger terms, or usage guidance. The only distinguishing element is the category mention, but without specifics about what bottleneck identification actually entails, Claude cannot effectively select this skill.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Analyzes application performance metrics, identifies slow database queries, detects memory leaks, and pinpoints CPU-intensive operations'
Include a 'Use when...' clause with natural trigger terms like 'slow performance', 'latency issues', 'performance degradation', 'why is my app slow', 'response time problems'
Replace the duplicate trigger term with varied natural language users would actually use when experiencing performance issues
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Bottleneck Identifier') and its category ('Performance Testing') without describing any concrete actions. There are no specific capabilities listed like 'analyzes response times', 'identifies slow queries', or 'profiles memory usage'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance. | 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 natural terms users would say like 'slow performance', 'latency issues', 'performance problems', 'why is it slow', etc. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Performance Testing' and 'Bottleneck Identifier' provide some domain specificity, the lack of concrete actions means it could overlap with other performance-related skills. The category mention helps somewhat but isn't sufficient for clear differentiation. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%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 nothing actionable for performance testing bottleneck analysis.
Suggestions
Add concrete code examples for profiling and identifying bottlenecks (e.g., using k6 for load testing, analyzing response time percentiles, CPU/memory profiling)
Include a clear workflow: 1) Establish baseline metrics, 2) Run load tests, 3) Identify resource constraints, 4) Validate with targeted tests
Provide specific metrics and thresholds to look for (e.g., 'CPU > 80% sustained indicates compute bottleneck', 'p99 latency > 2x p50 suggests queuing')
Remove all generic boilerplate text and replace with actionable techniques for common bottleneck types (CPU, memory, I/O, network, database)
| 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
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.