network-interface-health

Diagnose interface errors, drops, CRCs, duplex mismatches, flapping, speed negotiation issues, and counter trends on routers, switches, and Linux hosts.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No known issues

Quality

Content

100%

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

A well-structured, actionable diagnostic skill: concise, executable, with sequenced workflows and explicit verification checkpoints. It is essentially self-contained with no bundle files, and the organization supports easy navigation.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it jumps to commands, a counter table, and a diagnosis flow without explaining what counters or interfaces are, so every token earns its place.	3 / 3
Actionability	Provides copy-paste-ready commands (show interfaces, ip -s link, ethtool -S) and a complete, executable Python parser with named capture groups, plus a counter table mapping symptoms to causes.	3 / 3
Workflow Clarity	Diagnosis flows are explicitly sequenced with verification checkpoints — 'Confirm counters are incrementing, not just historical', 'Recheck after a fixed interval' — giving clear validate/compare feedback loops.	3 / 3
Progressive Disclosure	Self-contained skill with well-organized sections (When to Use, How It Works, Counter Reference, Diagnosis Flow, Examples, Anti-Patterns, See Also) and no deeply nested references; navigation is easy.	3 / 3
	Total	12 / 12 Passed

Description

82%

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 specific, distinctive description with strong natural trigger terms, but it omits an explicit 'Use when…' trigger clause so it answers 'what' far better than 'when'. Adding a one-sentence trigger guidance would raise completeness.

Suggestions

Append a 'Use when…' clause naming explicit triggers (e.g., 'Use when a host or switch shows packet loss, CRCs, drops, flapping, or duplex/speed negotiation problems').

Consider adding common user-facing phrasing like 'interface is flapping' or 'link errors' as explicit trigger terms to reinforce the when-to-use signal.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions and symptoms — 'interface errors, drops, CRCs, duplex mismatches, flapping, speed negotiation issues, and counter trends' — rather than vague language.	3 / 3
Completeness	It clearly answers 'what' the skill does but lacks any 'Use when…' clause or equivalent explicit trigger guidance, which caps completeness at 2 per the rubric.	2 / 3
Trigger Term Quality	Network operators naturally say terms like 'CRCs', 'drops', 'flapping', and 'duplex mismatch' when reporting this class of problem, giving good coverage of real trigger language.	3 / 3
Distinctiveness Conflict Risk	The network-interface-health niche with distinct physical-layer triggers (CRCs, duplex, flapping) is clearly distinguishable and unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Commit: 754b8dd

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