cpu-profiler-config
Cpu Profiler Config - Auto-activating skill for Performance Testing. Triggers on: cpu profiler config, cpu profiler config Part of the Performance Testing skill category.
36
Quality
3%
Does it follow best practices?
Impact
100%
1.00xAverage 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/cpu-profiler-config/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, functioning more as a category label than a useful skill description. It provides no information about what actions the skill performs, contains redundant trigger terms, and lacks any guidance on when Claude should select this skill. The description would be nearly useless for skill selection among multiple options.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Configures CPU profiler settings, sets sampling rates, defines profiling targets, and generates profiler configuration files.'
Add a 'Use when...' clause with natural trigger terms like 'Use when the user needs to set up CPU profiling, configure performance sampling, or create profiler settings for applications.'
Include natural keyword variations users might say: 'CPU profiling', 'profiler setup', 'performance profiling config', 'sampling configuration'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - only states it's 'Auto-activating skill for Performance Testing' without describing what it actually does (e.g., configure profiler settings, analyze CPU usage, generate reports). | 1 / 3 |
Completeness | Fails to answer both 'what does this do' and 'when should Claude use it'. There's no explanation of capabilities and no 'Use when...' clause or equivalent guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('cpu profiler config' repeated twice) and overly technical. Missing natural variations users might say like 'profile CPU', 'CPU performance', 'profiling configuration', or 'optimize CPU'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'cpu profiler config' is somewhat specific to CPU profiling configuration, but 'Performance Testing' is broad and could overlap with other performance-related skills. The lack of specific actions makes differentiation harder. | 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 is an empty template with no actual content about CPU profiler configuration. It contains only generic boilerplate text that could apply to any skill topic, with no executable code, configuration examples, specific tools (like perf, py-spy, async-profiler), or actionable guidance. The skill fails to teach Claude anything about CPU profiling.
Suggestions
Add concrete configuration examples for specific CPU profilers (e.g., Linux perf, py-spy, async-profiler) with executable commands
Include a workflow showing how to configure, run, and interpret CPU profiler output with validation steps
Remove generic boilerplate sections ('Purpose', 'Capabilities', 'Example Triggers') and replace with actual technical content
Add specific configuration options, sampling rates, output formats, and common pitfalls for CPU profiling
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about CPU profiler configuration. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, configuration examples, or specific instructions are provided. The content describes what the skill does abstractly but never shows how to actually configure a CPU profiler. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps for CPU profiler configuration. | 1 / 3 |
Progressive Disclosure | No references to detailed documentation, no links to configuration files or examples, and no structured navigation. The content is a shallow placeholder with no depth or organization. | 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.