network-bgp-diagnostics

Diagnostics-only BGP troubleshooting patterns for neighbor state, route exchange, prefix policy, AS path inspection, and safe evidence collection.

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.

Tight, actionable, and well-structured: executable commands, a complete parser, a sequenced triage flow, and an explicit gate around destructive change-window actions.

Dimension	Reasoning	Score
Conciseness	Lean command blocks, tables, and a complete parser with no padding or explanation of concepts Claude already knows; every section earns its tokens.	3 / 3
Actionability	Provides copy-paste-ready platform commands in fenced blocks and a fully executable Python parser with named groups, rather than vague direction or pseudocode.	3 / 3
Workflow Clarity	The 'Read-Only Triage Flow' is a clear 5-step sequence and the 'Change-Window Only' section gates destructive actions (clearing sessions, policy changes) behind explicit operator approval—a validation checkpoint for risky operations.	3 / 3
Progressive Disclosure	A single cohesive, well-organized SKILL.md with clearly headed sections and no nested external references (only a one-level 'See Also' list of sibling skills); no bundle files exist to create reference depth.	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, leaving the 'when' guidance implied rather than stated.

Suggestions

Append an explicit trigger clause, e.g. 'Use when a BGP session is down, flapping, established with missing routes, or advertising unexpected prefixes.'

Mirror the concrete 'When to Use' triggers from the body into the description so the 'when' is explicit at the skill-discovery layer.

Dimension	Reasoning	Score
Specificity	Names multiple concrete capabilities—'neighbor state, route exchange, prefix policy, AS path inspection, and safe evidence collection'—matching the multiple-specific-actions anchor.	3 / 3
Completeness	'What' is explicit (diagnostics-only BGP troubleshooting patterns for ...), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 2 per the rubric guideline.	2 / 3
Trigger Term Quality	Includes natural operator vocabulary ('BGP troubleshooting', 'neighbor state', 'route exchange', 'prefix policy', 'AS path inspection') that users would actually say when needing this skill.	3 / 3
Distinctiveness Conflict Risk	The 'Diagnostics-only BGP' framing carves a clear, narrow niche unlikely to trigger 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.