tracking-resource-usage

Track and optimize resource usage across application stack including CPU, memory, disk, and network I/O. Use when identifying bottlenecks or optimizing costs. Trigger with phrases like "track resource usage", "monitor CPU and memory", or "optimize resource allocation".

Quality

62%

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/resource-usage-tracker/skills/tracking-resource-usage/SKILL.md

Quality

Content

35%Weight 40%Scale 1-3

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

The body is well-sectioned and covers the expected areas, but it is largely abstract prose with no executable commands or code, redundant across Overview/How It Works/Instructions, and fails to point into the bundled scripts it ships. It describes the skill more than it instructs Claude how to execute it.

Suggestions

Replace the abstract Instructions with concrete, runnable commands (e.g. `top -b -n1`, `vmstat 1 5`, `iostat -xz 1`, `ps -eo pid,pcpu,pmem,cmd --sort=-pcpu`) and show how to invoke scripts/data_analyzer.py on captured output.

Collapse the redundant Overview, How It Works, and Instructions sections into a single lean workflow so each token earns its place.

Add explicit validation checkpoints (e.g. confirm metrics were captured before analyzing, sanity-check baseline comparisons) and link the bundled scripts/assets from the body so detail is one level deep.

Dimension	Reasoning	Score
Conciseness	The Overview, How It Works, and Instructions sections restate the same workflow in different words, and phrases like "comprehensive solution" add padding, though it stops short of explaining basic concepts Claude already knows.	2 / 3
Actionability	The Instructions describe rather than direct ("Collect real-time metrics using system tools", "Analyze data for bottlenecks and patterns") with no executable commands or code, even though top/ps/vmstat/iostat and the bundled data_analyzer.py are available but never shown.	1 / 3
Workflow Clarity	A sequenced step list exists (How It Works 1-4 and Instructions 1-6), but there are no explicit validation checkpoints or feedback loops tying analysis results back to a verify step.	2 / 3
Progressive Disclosure	The body is organized into clear sections but is largely monolithic, and the bundled scripts (e.g. scripts/data_analyzer.py) and assets are never linked or signaled from the body, so navigation to detail is missing.	2 / 3
	Total	7 / 12 Passed

Description

90%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that pairs a concrete capability statement with explicit "Use when" guidance and natural trigger phrases. Its only weakness is that the action verbs (track/optimize) are somewhat generic rather than enumerating multiple distinct concrete operations.

Dimension	Reasoning	Score
Specificity	It names the domain and concrete resource types ("CPU, memory, disk, and network I/O") but relies on only two generic verbs ("Track and optimize"), which is less comprehensive than listing several distinct concrete actions.	2 / 3
Completeness	It clearly states what the skill does and follows with an explicit "Use when..." clause plus concrete trigger phrases, answering both what and when.	3 / 3
Trigger Term Quality	It supplies natural phrases a user would actually say ("track resource usage", "monitor CPU and memory", "optimize resource allocation"), giving good coverage of likely triggers.	3 / 3
Distinctiveness Conflict Risk	The resource-monitoring niche is clearly scoped with distinct triggers tied to CPU/memory/disk/network usage, making it unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 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/resource-usage-tracker/skills/tracking-resource-usage/SKILL.md
Commit: c4eafaf

Reviewed: 5 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.