monitoring-cpu-usage
Monitor this skill enables AI assistant to monitor and analyze cpu usage patterns within applications. it helps identify cpu hotspots, analyze algorithmic complexity, and detect blocking operations. use this skill when the user asks to "monitor cpu usage", "opt... Use when setting up monitoring or observability. Trigger with phrases like 'monitor', 'metrics', or 'alerts'.
42
29%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/performance/cpu-usage-monitor/skills/monitoring-cpu-usage/SKILL.mdQuality
Discovery
59%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description attempts to cover both CPU-specific analysis and general monitoring, creating an identity conflict. While it has good structural completeness with explicit 'Use when' triggers, the truncation and overly broad trigger terms significantly weaken its effectiveness. The mismatch between the CPU-focused 'what' section and the generic monitoring 'when' section would cause frequent mis-selection.
Suggestions
Narrow the 'Use when' clause to CPU-specific triggers (e.g., 'Use when the user asks about CPU usage, CPU hotspots, algorithmic complexity analysis, or blocking operations') to avoid conflicts with other monitoring skills.
Fix the truncated description to ensure all capabilities and trigger phrases are fully visible.
Remove or qualify the generic terms 'metrics' and 'alerts' in the trigger list, or scope them explicitly to CPU metrics and CPU-related alerts.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (CPU monitoring) and lists some actions like 'identify cpu hotspots, analyze algorithmic complexity, and detect blocking operations', but the description is truncated ('opt...') and mixes in generic monitoring language, reducing clarity of the full capability set. | 2 / 3 |
Completeness | The description answers both 'what' (monitor and analyze CPU usage patterns, identify hotspots, analyze algorithmic complexity, detect blocking operations) and 'when' (explicit 'Use when setting up monitoring or observability' clause with trigger phrases). Despite truncation, both components are present. | 3 / 3 |
Trigger Term Quality | Includes some natural trigger terms like 'monitor cpu usage', 'monitor', 'metrics', 'alerts', and 'cpu hotspots', but the truncation cuts off what appears to be additional trigger phrases. The terms present are a mix of CPU-specific and generic monitoring terms, creating some ambiguity. | 2 / 3 |
Distinctiveness Conflict Risk | The description conflates CPU-specific monitoring with generic monitoring/observability, and the 'Use when' clause mentions broad triggers like 'monitor', 'metrics', or 'alerts' that would easily conflict with any other monitoring-related skill (e.g., network monitoring, application performance monitoring, log monitoring). | 1 / 3 |
Total | 8 / 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 almost entirely boilerplate and vague descriptions with no actionable content. It references a 'cpu-usage-monitor plugin' without explaining what it is, how to invoke it, or providing any concrete code examples, commands, or analysis techniques. The majority of sections contain generic filler text that could apply to any skill and waste token budget without adding value.
Suggestions
Replace the abstract examples with concrete, executable code showing actual CPU profiling techniques (e.g., using cProfile, py-spy, or perf) with real commands and sample output.
Remove boilerplate sections (Instructions, Output, Error Handling, Resources) that contain no substantive content, and consolidate Overview/How It Works/When to Use into a single brief section.
Define what the 'cpu-usage-monitor plugin' actually is — provide its invocation syntax, configuration options, and expected output format with concrete examples.
Add specific code patterns to look for (e.g., nested loops, catastrophic backtracking regex patterns) with before/after optimization examples.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive padding. The 'Overview' section restates the title, 'How It Works' describes vague plugin activation rather than concrete steps, 'When to Use' repeats obvious trigger conditions, and sections like 'Instructions', 'Output', 'Error Handling', and 'Resources' are boilerplate filler with no substantive content. Claude already knows what CPU hotspots are and doesn't need this explained. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance anywhere. The examples describe what 'the skill will' do in abstract terms rather than showing actual analysis techniques, code patterns, or specific tools/commands. References to a 'cpu-usage-monitor plugin' are never explained with actual invocation syntax or configuration. | 1 / 3 |
Workflow Clarity | The 'How It Works' section lists three vague steps (activate plugin, analyze, recommend) with no specifics on how to actually perform any of them. The 'Instructions' section is completely generic boilerplate ('invoke this skill when trigger conditions are met'). No validation checkpoints, no concrete sequencing, no feedback loops. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files and no bundle files to support it. Content is poorly organized with multiple redundant sections (Overview, How It Works, When to Use, Instructions all overlap). Boilerplate sections like 'Output', 'Error Handling', and 'Resources' contain no real information. | 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
3a2d27d
- 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.