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'.

Quality

48%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/performance/cpu-usage-monitor/skills/monitoring-cpu-usage/SKILL.md

Quality

Content

20%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is mostly generic boilerplate with no executable code or commands, and it fails to connect to the bundled scripts that actually exist, instead invoking a non-existent plugin. Its only real merit is a basic three-step sequence in 'How It Works', which still lacks any validation checkpoints.

Suggestions

Reference and show how to run the actual bundled scripts (e.g., `python scripts/cpu_analyzer.py ...`) with concrete invocations instead of describing a non-existent 'cpu-usage-monitor plugin'.

Delete the generic filler sections (Instructions, Output, Resources, Prerequisites) that apply to any skill and add nothing Claude doesn't already know.

Add a validation/verification step to the workflow (e.g., confirm the bottleneck with a profiler run before recommending optimizations) to lift workflow clarity above 2.

Dimension	Reasoning	Score
Conciseness	Large stretches are generic boilerplate Claude already knows — 'Required dependencies installed', 'Invoke this skill when the trigger conditions are met', 'The skill produces structured output relevant to the task', 'Project documentation' — padding the body with unnecessary context, matching the 'verbose; padded with unnecessary context' anchor rather than 'mostly efficient' at 2.	1 / 3
Actionability	The body contains no executable code or commands and only describes tasks ('Analyze the provided Python script for CPU-intensive functions', 'Provide recommendations') while ignoring the bundled scripts, matching 'vague or abstract; no concrete code/commands; describes rather than instructs' rather than the pseudocode/incomplete anchor at 2.	1 / 3
Workflow Clarity	'How It Works' lists a three-step sequence (Initiate CPU Monitoring, Code Analysis, Optimization Recommendations), but there are no validation checkpoints or concrete commands, matching 'steps listed but validation gaps; checkpoints missing' rather than the unclear/missing anchor at 1 or the explicit-validation anchor at 3.	2 / 3
Progressive Disclosure	The body is sectioned (Overview, How It Works, Examples) giving some structure, but it never references the actual bundle files (scripts/cpu_analyzer.py, scripts/example_usage.py) and instead references a non-existent 'cpu-usage-monitor plugin', so content that should point to the bundle is left inline as generic prose, fitting 'some structure but could be better organized' rather than the monolithic anchor at 1 or well-signaled references at 3.	2 / 3
	Total	6 / 12 Passed

Description

77%

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 clearly conveys both the skill's purpose and when to use it, with concrete CPU-analysis actions and explicit triggers. Weaknesses are the broad, conflict-prone trigger terms ('metrics', 'alerts') and missing common variations like 'profiling' or 'cpu load', plus a garbled mid-sentence ('opt...').

Suggestions

Replace broad triggers 'metrics' and 'alerts' with CPU-specific terms like 'cpu load', 'profiling', or 'optimize performance' to reduce conflict with general observability skills.

Fix the corrupted 'opt...' fragment so the description reads as a clean, complete sentence.

Tighten the redundant double-trigger phrasing ('use this skill when...' followed by 'Use when...' and 'Trigger with phrases like...') into a single explicit trigger clause.

Dimension	Reasoning	Score
Specificity	Quotes 'monitor and analyze cpu usage patterns' and 'identify cpu hotspots, analyze algorithmic complexity, and detect blocking operations' — multiple distinct concrete actions, matching the 'lists multiple specific concrete actions' anchor rather than the single-domain anchor at 2.	3 / 3
Completeness	Explicitly states what ('identify cpu hotspots, analyze algorithmic complexity, and detect blocking operations') and when ('use this skill when the user asks to monitor cpu usage', 'Use when setting up monitoring or observability', trigger phrases), answering both with explicit triggers; not capped at 2 because a 'Use when' clause is present.	3 / 3
Trigger Term Quality	Includes 'monitor cpu usage', 'monitor', 'metrics', and 'alerts' — relevant natural terms — but misses common variations like 'profiling', 'cpu load', or 'optimize performance', and 'metrics'/'alerts' are broad; fits 'some relevant keywords but missing common variations' rather than full coverage at 3.	2 / 3
Distinctiveness Conflict Risk	The CPU/hotspot/complexity niche is reasonably clear, but the generic triggers 'metrics' and 'alerts' overlap with general observability/alerting skills, matching 'somewhat specific but could still overlap with similar skills' rather than the unlikely-to-conflict anchor at 3.	2 / 3
	Total	10 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/performance/cpu-usage-monitor/skills/monitoring-cpu-usage/SKILL.md
Commit: 15940c5

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.