detecting-performance-bottlenecks
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill detecting-performance-bottlenecksExecute this skill enables AI assistant to detect and resolve performance bottlenecks in applications. it analyzes cpu, memory, i/o, and database performance to identify areas of concern. use this skill when you need to diagnose slow application performance, op... Use when optimizing performance. Trigger with phrases like 'optimize', 'performance', or 'speed up'.
Validation
81%| Criteria | Description | Result |
|---|---|---|
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 |
Total | 13 / 16 Passed | |
Implementation
7%This skill is essentially a placeholder template with no actionable content. It describes what a bottleneck detection skill would do in abstract terms but provides zero concrete guidance—no profiling commands, no code examples, no specific tools, no diagnostic workflows. The content is padded with generic boilerplate sections that add no value.
Suggestions
Add concrete, executable code examples for profiling CPU, memory, I/O, and database performance (e.g., specific Python profiling commands, SQL EXPLAIN usage, memory profiler snippets)
Replace abstract descriptions with specific diagnostic workflows including actual commands and validation steps (e.g., 'Run `py-spy top --pid <PID>` to identify CPU hotspots')
Remove generic boilerplate sections (Prerequisites, Instructions, Output, Error Handling) that provide no skill-specific guidance
Include specific tool recommendations with usage examples rather than vague references to 'monitoring and logging tools'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive padding and explanations of concepts Claude already knows. Phrases like 'This skill empowers Claude' and generic sections like 'Prerequisites', 'Instructions', 'Output', and 'Error Handling' add no actionable value and waste tokens. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance provided. The entire skill describes what it will do abstractly ('The skill will analyze...') rather than providing actual profiling commands, code snippets, or specific diagnostic steps Claude should take. | 1 / 3 |
Workflow Clarity | The 'How It Works' section lists vague phases without any concrete steps, validation checkpoints, or specific tools/commands. Instructions like 'Invoke this skill when trigger conditions are met' provide no actual workflow guidance. | 1 / 3 |
Progressive Disclosure | Content is organized into sections with headers, but it's a monolithic document with no references to external detailed materials. The structure exists but contains mostly filler content that doesn't warrant the organization. | 2 / 3 |
Total | 5 / 12 Passed |
Activation
82%This description has good trigger term coverage and completeness with explicit 'Use when' guidance, but suffers from a truncated middle section ('op...') and could be more specific about concrete actions. The broad scope covering multiple performance domains (cpu, memory, i/o, database) is both a strength for coverage and a weakness for distinctiveness.
Suggestions
Complete the truncated portion of the description to ensure all capabilities are clearly stated
Add more specific concrete actions beyond 'analyzes' - e.g., 'profiles code execution, identifies memory leaks, optimizes database queries, reduces I/O bottlenecks'
Consider narrowing scope or adding distinguishing details to reduce overlap with specialized database or monitoring skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (performance bottlenecks) and lists some actions (analyzes cpu, memory, i/o, database performance, diagnose slow application performance), but the description is truncated and uses somewhat generic language like 'areas of concern' rather than concrete specific actions. | 2 / 3 |
Completeness | Explicitly answers both what (detect and resolve performance bottlenecks, analyzes cpu/memory/i/o/database) and when (Use when optimizing performance, trigger phrases provided). Has clear 'Use when' clause with explicit triggers. | 3 / 3 |
Trigger Term Quality | Includes good natural trigger terms users would say: 'optimize', 'performance', 'speed up', plus domain terms like 'cpu', 'memory', 'i/o', 'database performance', 'slow application'. These are terms users naturally use when seeking performance help. | 3 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to performance optimization but could overlap with database-specific skills, monitoring skills, or general debugging skills. The broad scope (cpu, memory, i/o, database) increases potential for conflicts with more specialized tools. | 2 / 3 |
Total | 10 / 12 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.