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

Install with Tessl CLI

npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill monitoring-cpu-usage

What are skills?

Quality

28%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/performance/cpu-usage-monitor/skills/monitoring-cpu-usage/SKILL.md

SKILL.md

Review

Evals

Discovery

50%

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 attempts to cover CPU monitoring capabilities but is severely hampered by truncation, cutting off mid-sentence in the capabilities section. It includes both what and when clauses but the generic trigger terms ('monitor', 'metrics', 'alerts') could cause conflicts with other monitoring-related skills. The CPU-specific focus provides some distinctiveness but needs stronger emphasis in the trigger section.

Suggestions

Fix the truncation issue - complete the full description of capabilities and trigger phrases

Add more CPU-specific trigger terms to the 'Use when' clause, such as 'CPU profiling', 'performance bottleneck', 'CPU spikes', 'processor usage'

Differentiate more clearly from other monitoring skills by emphasizing CPU-specific scenarios in the trigger guidance

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 'Use when...' clause mentioning monitoring/observability and trigger phrases, but the 'what' section is truncated mid-sentence. The description attempts both what and when but neither is fully complete due to truncation.	2 / 3
Trigger Term Quality	Includes some natural keywords like 'monitor', 'metrics', 'alerts', 'cpu usage', but the truncation cuts off what appears to be additional trigger phrases ('opt...'). Missing common variations like 'performance', 'profiling', 'CPU spikes'.	2 / 3
Distinctiveness Conflict Risk	Focuses on CPU monitoring specifically which provides some distinction, but generic triggers like 'monitor' and 'metrics' could easily conflict with other monitoring skills (memory, network, disk). The CPU-specific terms help but aren't emphasized enough in triggers.	2 / 3
	Total	8 / 12 Passed

Implementation

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

This skill content is almost entirely boilerplate with no actionable guidance. It describes what the skill conceptually does but provides zero concrete implementation details - no actual code examples, no specific commands, no tool invocation syntax, and no real workflow steps. The content reads like a marketing description rather than technical instructions for Claude.

Suggestions

Replace abstract examples with concrete code snippets showing actual CPU profiling commands or analysis patterns (e.g., using cProfile, py-spy, or specific static analysis approaches)

Provide the actual syntax for invoking the 'cpu-usage-monitor' plugin with specific parameters and expected output format

Remove generic boilerplate sections (Instructions, Output, Error Handling) that provide no skill-specific information

Add concrete before/after code examples showing specific CPU optimization patterns (e.g., replacing O(n²) loops with O(n) alternatives)

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' abstractly rather than showing actual code patterns, commands to run, or specific implementation details. References to a 'cpu-usage-monitor plugin' with no actual invocation syntax or parameters.	1 / 3
Workflow Clarity	The 'How It Works' section lists vague steps without any concrete validation checkpoints or actual commands. No feedback loops for error recovery. The 'Instructions' section is completely generic ('Invoke this skill when trigger conditions are met') with no actual workflow guidance.	1 / 3
Progressive Disclosure	Content is organized into sections with headers, but it's a monolithic document with no references to external files for detailed content. The structure exists but contains mostly filler content that could be condensed significantly.	2 / 3
	Total	5 / 12 Passed

Validation

81%

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 — 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

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.