interface-link-troubleshooting
Skill1 starsChanged 32 days agoApache-2.0View on GitHub
Diagnose physical/logical interface and link problems (interface down, flapping, high error/discard counters, duplex/speed mismatch, no link light) by reading interface state and, where the platform exposes them, counters on a supported platform, and mapping observed state to the platform's own documented likely causes — currently Cisco IOS-XE, Juniper Junos, Arista EOS, and FRRouting (symptom coverage varies by vendor; see references/INDEX.md). Use when an agent needs to investigate why a link isn't behaving as expected — not for configuring interface settings from scratch (that is a create/update operation with a different shape; this skill is read-only diagnosis). Assumes an authenticated CLI/API session against the target device is already available; this skill does not provision or authenticate it.
In this repository40 other files it gives its agents.
- AGENTS.mdAGENTS.md
- alert-monitor-managementSkill
- automation-job-executionSkill
- casb-policy-managementSkill
- casb-posture-assessmentSkill
- certificate-managementSkill
- change-managementSkill
- cloud-security-group-auditSkill
- cmdb-asset-managementSkill
- compute-instance-provisioningSkill
- config-backup-managementSkill
- connector-tunnel-managementSkill
- container-workload-deploymentSkill
- crm-contact-managementSkill
- dcim-asset-managementSkill
- dhcp-scope-managementSkill
- dns-record-managementSkill
- dns-zone-managementSkill
- firewall-managementSkill
- incident-managementSkill
- infrastructure-plan-executionSkill
- ipam-allocationSkill
- load-balancingSkill
- log-querySkill
- metric-querySkill
- network-access-control-managementSkill
- network-health-verificationSkill
- network-state-collectionSkill
- notificationsSkill
- repository-pull-request-managementSkill
- routing-troubleshootingSkill
- sdwan-policy-managementSkill
- sdwan-site-onboardingSkill
- secret-retrievalSkill
- software-upgrade-lifecycleSkill
- vpn-tunnel-managementSkill
- vulnerability-lookupSkill
- waf-managementSkill
- wireless-network-managementSkill
- zero-trust-access-policy-managementSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 27
Not for configuring interface settings (speed, duplex, VLAN membership, description) from scratch — that would be a CRUD-shaped …
- Distinctive: line 81
Read-only diagnosis only. Does not configure, remediate, or reset anything — a caller who needs to act on a diagnosis needs a separate …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Interface / Link Troubleshooting
Diagnoses physical and logical interface/link problems on whichever platform the caller is targeting, by reading interface state and counters and mapping them to that platform's own documented likely causes — not a configuration-change skill.
How this skill works
This skill is diagnostic-shaped, not CRUD-shaped — the "procedure" is a decision tree keyed by symptom, and the useful output is a diagnosis plus the literal evidence that supports it, not a created/updated/deleted record. It is read-only: reading interface state and counters changes nothing on the platform, so it has no confirmation gates. A remediation action (clearing counters, forcing a speed/duplex setting, administratively flapping the interface) is outside it; any such action needs its own confirmation first, like any destructive step.
When to use this skill
- An interface is down, flapping, showing elevated error/discard counters, suspected of a duplex/speed mismatch, or showing no link light, on a supported platform, and the caller needs to identify which documented cause applies.
- Not for configuring interface settings (speed, duplex, VLAN membership, description) from scratch — that would be a CRUD-shaped configuration capability with its own confirmation-gate requirements, separate from this read-only diagnostic one.
Universal concepts (shared interface-state vocabulary, not a wire standard)
Checked against the four platforms listed in references/INDEX.md (Cisco IOS-XE, Juniper Junos,
Arista EOS, FRRouting); they do not extend automatically to a platform not listed there:
- There is no single wire-level standard grounding interface/link state the way RFC 4271 grounds
BGP session state, or RFC 1035/2136/1123 ground DNS. Every listed platform defines its
own state names and, where it documents them, its own error-counter field names and
likely-cause mappings — do not assume a counter name, a status string, or a documented cause from one vendor's file applies
to another's; each vendor's
procedure.mdsays explicitly where something is unverified rather than borrowing another vendor's confirmed behavior. - Administratively disabled vs. operationally down is a distinction every listed platform draws
in some form — an interface an operator has explicitly disabled in configuration is a
different condition, needing a different response, than one that is enabled but not passing link
for some other reason. The exact state string and command differ per platform; see each vendor's
procedure.md. - Where a platform documents one, a mechanism or display artifact can mean the interface's
reported state does not fully explain why it's in that state without a further
check — Cisco's err-disabled state names a specific detected cause that must be read separately
(
show errdisable recovery), and Junos's damping feature can make an interface report down without its state display distinguishing "suppressed" from "actually down for a new reason." Arista's Dynamic Link Flap Damping is documented by name only, with its detail unverified, so it is not confirmed to share this same caveat — don't assume it does until checked. - Beyond these, do not assume any specific error-counter name (CRC, FCS, alignment, symbol, etc.), duplex/speed auto-negotiation display convention, or documented root-cause list is shared across vendors — each is confirmed or explicitly flagged as unconfirmed in that vendor's own file.
See references/INDEX.md for which platforms have a procedure, and each platform file for how it
implements this shape concretely.
Procedure
- Identify the target platform — from the caller's request or the
platformargument. Checkreferences/INDEX.md; if no matching row exists, stop: this skill doesn't cover it yet. - Identify the symptom category — interface down, flapping, high errors/discards, duplex/speed
mismatch, or no link light. This determines which decision-tree entry point in
references/<platform>/procedure.mdto start from; the platform file is organized by symptom, not by a linear operation sequence. - Open
references/<platform>/procedure.mdand follow its decision tree for that symptom exactly — it maps each observed state to that platform's own documented likely causes and the next check to run. - Report the diagnosis — which documented cause the evidence points to, the evidence itself (the literal command/API output that supports it), and any documented next step the platform's own guidance suggests — don't present a diagnosis without the evidence that supports it.
Known limitations
- Currently covers Cisco IOS-XE, Juniper Junos, Arista EOS, and FRRouting — see
references/INDEX.mdfor exact symptom-category coverage per vendor (deliberately partial for some). A platform not listed there needs a new reference file before this skill can be used for it. - Read-only diagnosis only. Does not configure, remediate, or reset anything — a caller who needs to act on a diagnosis needs a separate configuration-change capability, which may not exist yet in this repository.
- Covers physical/logical interface and link-layer symptoms only. A diagnosis that points to a
routing-layer cause (e.g. a route not propagating because the underlying link is down) should hand
off to
routing-troubleshootingrather than this skill trying to cover both layers.
Contributing to this skill
SKILL.md only changes for two reasons: a bug in the universal concepts/router logic above, or
adding a pointer to a newly-supported platform. Platform-specific decision-tree content — a new
documented cause, a corrected CLI/API output pattern, a vendor-specific counter name — belongs in
that platform's own references/<platform>/procedure.md, never here.
Tools
Each platform assumes its own authenticated CLI/API session — see references/INDEX.md for which,
and that platform's procedure.md for the specific read-only checks it uses.
Verification checklist
- Target platform confirmed against
references/INDEX.mdbefore proceeding - Symptom category correctly identified before opening the platform's decision tree
- That platform's own
procedure.mddecision tree was followed for the identified symptom - Diagnosis reported together with the literal evidence (command/API output) that supports it — never a bare conclusion
- No configuration change was made — this skill is read-only; anything beyond reading state is out of scope here
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

