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".
44
46%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/performance/resource-usage-tracker/skills/tracking-resource-usage/SKILL.mdQuality
Discovery
92%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 is a well-crafted skill description that clearly articulates what it does, when to use it, and provides explicit trigger phrases. Its main weakness is a moderate overlap risk with adjacent skills in performance monitoring, infrastructure management, or cost optimization domains. The description uses proper third-person voice and is concise without being vague.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and resources: 'Track and optimize resource usage' covering 'CPU, memory, disk, and network I/O' with specific use cases like 'identifying bottlenecks' and 'optimizing costs'. | 3 / 3 |
Completeness | Clearly answers both what ('Track and optimize resource usage across application stack including CPU, memory, disk, and network I/O') and when ('Use when identifying bottlenecks or optimizing costs') with explicit trigger phrases. | 3 / 3 |
Trigger Term Quality | Includes natural trigger phrases users would actually say: 'track resource usage', 'monitor CPU and memory', 'optimize resource allocation'. These cover common variations of how users would express resource monitoring needs. | 3 / 3 |
Distinctiveness Conflict Risk | While it specifies resource monitoring across CPU, memory, disk, and network I/O, it could overlap with more specific performance profiling skills, APM tools, or cost optimization skills. The scope 'across application stack' is somewhat broad and could conflict with infrastructure monitoring or cloud cost management skills. | 2 / 3 |
Total | 11 / 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 descriptive rather than instructive. It reads like a product marketing document explaining what resource monitoring is, rather than a concrete guide Claude can follow. It lacks any executable code, specific commands, concrete examples with actual output, or meaningful validation steps.
Suggestions
Replace the abstract 'How It Works' and 'Examples' sections with concrete, executable commands (e.g., `top -b -n 1`, `vmstat 1 5`, `iostat -x 1`) and show expected output formats that Claude should parse.
Add specific validation checkpoints such as verifying tool availability (`which vmstat || echo 'vmstat not found'`) and checking output format before proceeding to analysis.
Remove the 'Overview', 'When to Use This Skill', 'Best Practices', 'Integration', and 'Resources' sections entirely — they explain concepts Claude already knows and consume tokens without adding actionable value.
Provide concrete analysis patterns: e.g., 'If CPU usage > 80% sustained over 5 samples, flag as bottleneck' with actual threshold values and decision logic rather than abstract descriptions.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive explanation of concepts Claude already knows. The 'Overview', 'How It Works', 'When to Use This Skill', and 'Best Practices' sections are largely redundant padding. The skill explains what monitoring is, what bottlenecks are, and describes its own process at a high level without adding actionable value. | 1 / 3 |
Actionability | No concrete code, commands, or executable examples anywhere. The 'Examples' section describes what the skill 'will do' in abstract terms rather than showing actual commands (e.g., `top`, `vmstat`, `iostat` usage). The 'Instructions' section is a vague 6-step list with no specifics on how to actually collect or analyze metrics. | 1 / 3 |
Workflow Clarity | The workflow steps are vague and lack any validation checkpoints. Steps like 'Collect real-time metrics using system tools' and 'Analyze data for bottlenecks and patterns' provide no concrete guidance on what tools to run, what output to expect, or how to verify results. No feedback loops for error recovery. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with no bundle files to reference. References a directory '${CLAUDE_SKILL_DIR}/metrics/resources/' but no supporting files exist. Content that could be split (error handling, examples, best practices) is all inline with no clear navigation structure. | 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
69c73e9
- 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.