Content
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 almost entirely generic boilerplate with no actionable content. It describes what a bottleneck detector would do in abstract terms but provides zero concrete guidance—no profiling commands, no diagnostic code, no specific tools, no example outputs, and no real workflows. Multiple sections ('Prerequisites', 'Instructions', 'Output', 'Error Handling', 'Resources') contain placeholder text that could apply to literally any skill.
Suggestions
Replace abstract descriptions with concrete, executable examples: include actual profiling commands (e.g., `py-spy`, `EXPLAIN ANALYZE`, `vmstat`, `iostat`), specific code snippets for detecting memory leaks, and real diagnostic workflows.
Remove all generic boilerplate sections ('Prerequisites', 'Instructions', 'Output', 'Error Handling', 'Resources') that contain no skill-specific content—they waste tokens without adding value.
Add a concrete multi-step diagnostic workflow with validation checkpoints, e.g.: 1) Run CPU profiler → 2) Analyze hotspots → 3) Check memory with specific tool → 4) Run database EXPLAIN → 5) Verify improvements with benchmarks.
Include at least one complete, copy-paste-ready example showing actual input (e.g., a slow query) and the expected diagnostic output with specific remediation code.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive padding. The 'Overview' section restates the title, 'How It Works' describes abstract steps Claude already knows, 'When to Use' repeats the description, and sections like 'Prerequisites', 'Instructions', 'Output', 'Error Handling', and 'Resources' are generic boilerplate with no substantive content. Nearly every section explains concepts Claude already understands. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance anywhere. The entire skill is abstract descriptions like 'analyze database query performance' and 'profile memory usage patterns' without any actual profiling commands, diagnostic scripts, SQL EXPLAIN examples, or specific tools to use. The 'Instructions' section is completely generic ('Invoke this skill when trigger conditions are met'). | 1 / 3 |
Workflow Clarity | The 'How It Works' section lists three abstract phases with no concrete steps, no validation checkpoints, and no feedback loops. The examples describe what the skill 'will' do in vague terms without specifying how. There is no actionable sequence for diagnosing any type of bottleneck. | 1 / 3 |
Progressive Disclosure | The content is a monolithic wall of vague text with no references to external files, no structured navigation, and no separation of concerns. Multiple sections contain placeholder-quality content that adds no value. There are no bundle files to reference, but the content itself is poorly organized with redundant sections. | 1 / 3 |
Total | 4 / 12 Passed |