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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill cpu-profiler-configOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, functioning more as a label than a useful skill description. It provides no information about what actions the skill performs, relies on redundant and narrow trigger terms, and lacks any explicit guidance on when Claude should select it. The description would be nearly useless for skill selection among multiple options.
Suggestions
Add specific actions the skill performs, e.g., 'Configures CPU profiling settings, analyzes profiler output, identifies performance bottlenecks, generates optimization recommendations'
Add a 'Use when...' clause with explicit triggers like 'Use when the user needs to set up CPU profiling, analyze CPU performance data, or optimize code execution speed'
Expand trigger terms to include natural variations: 'CPU profiling', 'profile performance', 'CPU bottleneck', 'execution time analysis', 'performance optimization'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - only states it's 'auto-activating' for 'Performance Testing' without explaining what it actually does with CPU profiler configuration. | 1 / 3 |
Completeness | Fails to answer 'what does this do' beyond naming itself, and the 'when' is only implied through trigger terms without explicit guidance. No 'Use when...' clause present. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('cpu profiler config' listed twice) and overly technical. Missing natural variations users might say like 'profile CPU', 'CPU performance', 'profiling', or 'benchmark'. | 1 / 3 |
Distinctiveness Conflict Risk | The 'CPU profiler config' focus is somewhat specific, but 'Performance Testing' category is broad and could overlap with other performance-related skills. The lack of detail makes conflict assessment difficult. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%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, providing zero actionable guidance, no code examples, no configuration snippets, and no workflow for the stated purpose.
Suggestions
Add concrete CPU profiler configuration examples (e.g., perf, py-spy, async-profiler) with executable commands and sample output
Include a clear workflow: how to start profiling, capture data, analyze results, and interpret flame graphs
Provide specific configuration options and flags for common profilers with explanations of when to use each
Add links to reference documentation for different profiler tools and advanced configuration scenarios
| 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
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.