collecting-infrastructure-metrics

Collect comprehensive infrastructure performance metrics across compute, storage, network, containers, load balancers, and databases. Use when monitoring system performance or troubleshooting infrastructure issues. Trigger with phrases like "collect infrastructure metrics", "monitor server performance", or "track system resources".

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/infrastructure-metrics-collector/skills/collecting-infrastructure-metrics/SKILL.md

Quality

Content

35%

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

The body is reasonably organized and conceptually complete but lacks any executable, copy-paste-ready guidance or validation checkpoints, and it does not leverage the bundled scripts. It reads as an abstract overview rather than actionable instructions.

Suggestions

Add concrete, executable examples: show actual Prometheus scrape configs, Datadog/datadog.yaml snippets, or aws cloudwatch CLI commands, and link to the scripts in scripts/ (e.g. configure_prometheus.py) instead of only describing them.

Insert explicit validation checkpoints into the Instructions workflow (e.g. verify agent is reachable, confirm metrics are being scraped, validate dashboard renders) with a fix-and-retry loop before moving to the next step.

Tighten or relocate redundant prose: merge the overlapping How It Works and Instructions lists, and move the Best Practices/Integration detail into reference files to reduce the inline token footprint and improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly organized but padded with conceptual prose (Overview, How It Works, When to Use, Best Practices, Integration) and redundant step lists (How It Works vs Instructions); it could be tightened without losing meaning, so it sits above the verbose level-1 anchor but below the lean level-3 anchor.	2 / 3
Actionability	The content describes rather than instructs ("Configure Prometheus to collect CPU, memory, disk I/O, and network bandwidth metrics") with no executable code, commands, or config snippets anywhere, matching the 'vague/abstract; describes rather than instructs' anchor; the bundled scripts listed in scripts/README.md are never invoked or linked.	1 / 3
Workflow Clarity	Steps are sequenced (How It Works 1-4, Instructions 1-6) and an Error Handling section exists, but there are no explicit validation checkpoints or feedback loops in the workflow, which caps clarity at 2 for infrastructure-configuration operations.	2 / 3
Progressive Disclosure	The ~93-line body is a monolithic single file with sectioned structure but no signaled one-level-deep references to the bundled scripts or any reference files; content that could be split out stays inline.	2 / 3
	Total	7 / 12 Passed

Description

90%

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 well-formed description with explicit 'what' and 'when' guidance plus natural trigger phrases and a distinct infrastructure-monitoring niche. The only weakness is that it describes one action across many layers rather than enumerating multiple distinct capabilities.

Dimension	Reasoning	Score
Specificity	The description states a single action ("Collect comprehensive infrastructure performance metrics") applied across six named layers (compute, storage, network, containers, load balancers, databases) rather than listing multiple distinct concrete actions; this matches the 'names domain and some actions' anchor and falls short of the multi-action level-3 example.	2 / 3
Completeness	It clearly answers what (collect metrics across the listed layers) and when ("Use when monitoring system performance or troubleshooting infrastructure issues") with explicit trigger phrases, matching the level-3 anchor.	3 / 3
Trigger Term Quality	Explicit natural phrases a user would say are provided ("collect infrastructure metrics", "monitor server performance", "track system resources"), giving good coverage of likely trigger language.	3 / 3
Distinctiveness Conflict Risk	The infrastructure-metrics niche across named layers with dedicated trigger phrases is a clear, distinct scope 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/infrastructure-metrics-collector/skills/collecting-infrastructure-metrics/SKILL.md
Commit: 15940c5

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