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
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 extremely weak across all dimensions. It reads as an auto-generated template with no substantive information about what the skill does, relying solely on a repeated trigger phrase and a category label. It provides no concrete actions, no natural trigger terms, and no explicit guidance on when Claude should select this skill.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Generates CPU profiler configuration files, sets sampling rates, configures profiling targets and output formats.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user needs to configure CPU profiling, set up performance benchmarks, create profiler settings, or work with profiling tools like perf, gprof, or VTune.'
Remove the duplicated trigger term and expand with natural language variations users might actually say, such as 'CPU profiling setup', 'profiler settings', 'performance profiling', 'sampling configuration'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions. It only states it is an 'auto-activating skill for Performance Testing' and mentions 'cpu profiler config' as a trigger, but never describes what the skill actually does (e.g., configure profiling settings, generate config files, analyze CPU usage). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming a category, and the 'when' is limited to a duplicated trigger phrase with no explicit 'Use when...' clause or meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger term listed is 'cpu profiler config' repeated twice. There are no natural language variations a user might say, such as 'CPU profiling', 'profiler settings', 'performance profiling configuration', 'benchmark config', or similar terms. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'cpu profiler config' is fairly niche and unlikely to conflict with many other skills, but the lack of specificity about what it does means it could overlap with other performance testing or profiling-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 is an empty template with no actual content about CPU profiler configuration. It contains only generic boilerplate text that could apply to any topic, providing zero actionable guidance, no code examples, no tool-specific instructions, and no real information that would help Claude perform CPU profiler configuration tasks.
Suggestions
Add concrete, executable configuration examples for specific CPU profilers (e.g., perf, py-spy, async-profiler, pprof) with actual command-line invocations and config file snippets.
Define a clear workflow: 1) Select profiler for the target runtime, 2) Configure sampling parameters, 3) Run profiling, 4) Validate output/flamegraph generation, with explicit validation steps.
Remove all boilerplate sections (Purpose, When to Use, Capabilities, Example Triggers) and replace with actionable content like quick-start commands, common configuration patterns, and interpretation guidance.
Add references to detailed materials for advanced topics like continuous profiling setup, production-safe configurations, or specific framework integrations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It explains what the skill does in abstract terms without providing any actual guidance on CPU profiler configuration. Every section restates the same vague concept. | 1 / 3 |
Actionability | There are zero concrete instructions, no code examples, no commands, no configuration snippets, and no specific tools or parameters mentioned. The content describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or sequenced operations. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of boilerplate with no references to detailed materials, no links to configuration examples, and no structured navigation to deeper content. | 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
3076d78
- 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.