tracking-resource-usage
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill tracking-resource-usageTrack 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".
60%
Overall
Validation
Implementation
Activation
Validation
81%| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md line count is 101 (<= 500) | Pass |
frontmatter_valid | YAML frontmatter is valid | Pass |
name_field | 'name' field is valid: 'tracking-resource-usage' | Pass |
description_field | 'description' field is valid (269 chars) | Pass |
description_voice | 'description' uses third person voice | Pass |
description_trigger_hint | Description includes an explicit trigger hint | Pass |
compatibility_field | 'compatibility' field not present (optional) | Pass |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
metadata_field | 'metadata' field not present (optional) | Pass |
license_field | 'license' field is present: MIT | Pass |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_present | SKILL.md body is present | Pass |
body_examples | Examples detected (code fence or 'Example' wording) | Pass |
body_output_format | Output/return/format terms detected | Pass |
body_steps | Step-by-step structure detected (ordered list) | Pass |
Total | 13 / 16 Passed |
Implementation
20%This skill is overly verbose and abstract, explaining concepts Claude already understands while failing to provide any executable code or specific commands. It reads more like a product description than actionable guidance, with examples that describe what 'the skill will do' rather than showing concrete implementation steps.
Suggestions
- Replace abstract descriptions with concrete, executable commands (e.g., 'vmstat 1 5', 'iostat -x 1', 'ps aux --sort=-%mem | head -20') that Claude can actually run
- Remove the 'Overview', 'How It Works', and 'When to Use' sections entirely - Claude doesn't need to be told when to use a skill or how it conceptually works
- Add specific code examples with expected output formats, such as parsing vmstat output or calculating memory leak indicators from /proc/meminfo
- Include validation steps in the workflow, such as 'Verify metrics collection is working: if vmstat returns empty, check permissions with sudo'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive explanation of concepts Claude already knows. The overview, 'How It Works', and 'When to Use' sections are padded with unnecessary context that doesn't add actionable value. | 1 / 3 |
Actionability | No concrete code, commands, or executable examples. The entire skill describes what it will do abstractly ('The skill will...') rather than providing actual commands like 'top -b -n 1' or specific tool invocations. | 1 / 3 |
Workflow Clarity | Steps are listed in the Instructions section but lack validation checkpoints. No feedback loops for error recovery, and the workflow is too abstract to be actionable (e.g., 'Collect real-time metrics using system tools' without specifying which tools or commands). | 2 / 3 |
Progressive Disclosure | Content is organized into sections but is monolithic with no references to external files. The lengthy content could benefit from splitting detailed examples and best practices into separate reference files. | 2 / 3 |
Total | 6 / 12 Passed |
Activation
100%This is a well-crafted skill description that excels across all dimensions. It provides specific capabilities (resource tracking across CPU, memory, disk, network I/O), clear use cases (bottleneck identification, cost optimization), and explicit trigger phrases that users would naturally say. The description uses proper third-person voice and maintains a clear, distinct niche.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Track and optimize resource usage' with explicit resource types 'CPU, memory, disk, and network I/O'. Also mentions 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 provided. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger phrases users would say: 'track resource usage', 'monitor CPU and memory', 'optimize resource allocation'. These are realistic phrases a user would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on resource monitoring and optimization with specific triggers around CPU, memory, disk, and network I/O. The explicit trigger phrases and focus on 'application stack' resources make it unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 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.