Network Interface Health
Interface diagnostics with Muse for routers, switches, and Linux hosts: CRCs, drops, duplex mismatches, flapping, and counter trends, with a safe parser example.
- What
- Interface diagnostics with Muse for routers, switches, and Linux hosts: CRCs, drops, duplex mismatches, flapping, and counter trends, with a safe parser example.
- Cost
- Free
- Needs
- Use "Network Interface Health" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: network interface diagnostics that make Muse reason about link health like a network engineer. The core principle is that trends matter more than absolute numbers: capture a baseline, wait a measurement interval, capture again, then compare increments. It ships a counter reference table (CRC means bad cable, dirty fiber, bad optic or duplex mismatch; runts point to duplex mismatch; giants to MTU mismatch; input drops to bursts or queue pressure; output drops to congestion) and a diagnosis flow for the three classic cases: CRCs or input errors (confirm they are incrementing, check both ends of the link, replace the cable before touching routing), drops (separate input from output drops, compare rate against capacity, prove congestion before tuning queues), and duplex/speed (prefer auto-negotiation on modern links, never mix fixed on one side with auto on the other). Includes a safe Python parser for show interfaces output that slices per-interface blocks from header to header instead of using arbitrary character windows, worked examples (CRCs on one switch port, WAN slow but LAN fine), and anti-patterns (clearing counters before saving a baseline, looking at only one side of a link). By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: read-only diagnosis, you still need device access and change windows for fixes; it does not replace monitoring or a network engineer for production incidents. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Network Interface Health" with your Muse. Prerequisites: none to install. Pure guidance; access to a router, switch, or Linux host helps. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/network-interface-health/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Diagnose this interface: [paste show interfaces or ip -s link output]." 3. Ask it to identify which counters are incrementing, what the likely cause is, and the exact next diagnostic step before any fix. Tip: paste two counter captures taken minutes apart and ask "which counters moved and what does the trend mean?" Safety: a skill is plain-text instructions; it runs nothing by itself. Never clear counters before saving a baseline.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.