monitoring-cpu-usage
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill monitoring-cpu-usageMonitor 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'.
Validation
81%| Criteria | Description | Result |
|---|---|---|
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 |
Total | 13 / 16 Passed | |
Implementation
7%This skill content is largely boilerplate with no actionable guidance. It describes what CPU monitoring conceptually does rather than providing concrete tools, commands, code patterns, or analysis techniques. The content explains obvious concepts, repeats itself across sections, and lacks any executable examples or specific implementation details.
Suggestions
Replace abstract descriptions with concrete code examples showing actual CPU profiling commands (e.g., `cProfile`, `py-spy`, `perf`) and how to interpret their output
Remove generic boilerplate sections (Instructions, Output, Error Handling, Prerequisites) that provide no skill-specific value
Add executable examples showing before/after code optimizations with specific patterns like 'replace nested loops with hash lookups' with actual code
Specify what the 'cpu-usage-monitor plugin' actually is and how to invoke it, or remove the reference if it doesn't exist
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive padding explaining concepts Claude already knows. Sections like 'Overview', 'How It Works', 'When to Use This Skill' repeat the same information in different ways. The 'Instructions', 'Output', and 'Error Handling' sections are generic boilerplate that add no value. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance provided. Examples describe what 'the skill will' do in abstract terms rather than showing actual code analysis patterns, specific commands to run, or real optimization examples. References to a 'cpu-usage-monitor plugin' without any usage instructions. | 1 / 3 |
Workflow Clarity | The 'How It Works' section lists vague steps without any concrete validation checkpoints or actual commands. No clear sequence for how to actually perform CPU analysis, no feedback loops for verifying optimizations work, and no specific tools or methods identified. | 1 / 3 |
Progressive Disclosure | Content is organized into sections with headers, but it's a monolithic document with no references to external detailed materials. The structure exists but contains mostly filler content that could be dramatically condensed or split appropriately. | 2 / 3 |
Total | 5 / 12 Passed |
Activation
50%This description attempts to cover both capabilities and triggers but is undermined by truncation and generic monitoring terminology. The CPU-specific focus provides some distinctiveness, but the broad 'monitoring or observability' trigger phrase and common terms like 'metrics' and 'alerts' create conflict risk with other monitoring skills.
Suggestions
Fix the truncated description to include complete capability list and trigger terms
Make triggers more CPU-specific (e.g., 'CPU bottleneck', 'processor usage', 'CPU profiling') rather than generic monitoring terms
Differentiate from other monitoring skills by explicitly stating what this skill does NOT cover (e.g., memory, network, disk I/O)
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | 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 and incomplete, preventing full assessment of capabilities. | 2 / 3 |
Completeness | Has a 'what' section describing CPU monitoring capabilities and a 'Use when' clause with trigger phrases, but the description is clearly truncated mid-sentence ('opt...'), making it incomplete. The 'when' guidance exists but is generic. | 2 / 3 |
Trigger Term Quality | Includes some natural keywords like 'monitor', 'metrics', 'alerts', 'cpu usage', and 'monitor cpu usage', but the truncation cuts off what appears to be additional trigger terms. Missing common variations like 'performance', 'profiling', or 'CPU spikes'. | 2 / 3 |
Distinctiveness Conflict Risk | Focuses on CPU-specific monitoring which provides some distinction, but the generic 'monitoring or observability' trigger and terms like 'metrics' and 'alerts' could easily conflict with other monitoring skills (memory, network, application monitoring). | 2 / 3 |
Total | 8 / 12 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.