[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7316730DNX4FFJZ81MM7KJ3":3,"skill-same:01M7316730DNX4FFJZ81MM7KJ3":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7316730DNX4FFJZ81MM7KJ3","network-interface-health",null,"Diagnose interface errors, drops, CRCs, duplex mismatches, flapping, speed negotiation issues, and counter trends on routers, switches, and Linux hosts.","SriramGandhiS\u002FSkills","SriramGandhiS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F211849986?v=4","01M72WQCW12BYX71C6WN584TTA","Sriram S","01M72WQCWTJ2RD0ET1X31AF1RC",1,"MIT","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fskills\u002Fnetwork-interface-health\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: network-interface-health\ndescription: Diagnose interface errors, drops, CRCs, duplex mismatches, flapping, speed negotiation issues, and counter trends on routers, switches, and Linux hosts.\norigin: community\n---\n\n# Network Interface Health\n\nUse this skill when a network symptom might be caused by a physical link, switch\nport, cable, transceiver, duplex setting, or congested interface.\n\n## When to Use\n\n- A host or VLAN has packet loss, latency spikes, or intermittent reachability.\n- A switch or router interface shows CRCs, runts, giants, drops, resets, or flaps.\n- You need to compare both ends of a link before replacing hardware.\n- A change window needs before\u002Fafter interface counter evidence.\n- Monitoring reports rising `ifInErrors`, `ifOutErrors`, or `ifOutDiscards`.\n\n## How It Works\n\nInterface counters are evidence, but the trend matters more than the absolute\nnumber. Capture a baseline, wait a measurement interval, capture again, then\ncompare increments.\n\n```text\nshow interfaces \u003Cinterface>\nshow interfaces \u003Cinterface> status\nshow logging | include \u003Cinterface>|changed state|line protocol\n```\n\nOn Linux hosts:\n\n```text\nip -s link show \u003Cinterface>\nethtool \u003Cinterface>\nethtool -S \u003Cinterface>\n```\n\n## Counter Reference\n\n| Counter | Meaning | Common cause |\n| --- | --- | --- |\n| CRC | Received frame checksum failed | Bad cable, dirty fiber, bad optic, duplex mismatch |\n| input errors | Aggregate receive-side errors | Check sub-counters before concluding |\n| runts | Frames below minimum Ethernet size | Duplex mismatch, collision domain, faulty NIC |\n| giants | Frames larger than expected MTU | MTU mismatch or jumbo-frame boundary |\n| input drops | Device could not accept inbound packets | Burst, oversubscription, CPU path, queue pressure |\n| output drops | Egress queue discarded packets | Congestion, QoS policy, undersized uplink |\n| resets | Interface hardware reset | Flapping, keepalive, driver, optic, power |\n| collisions | Ethernet collision counter | Half duplex or negotiation mismatch |\n\n## Diagnosis Flow\n\n### CRCs Or Input Errors\n\n1. Confirm counters are incrementing, not just historical.\n2. Check both ends of the link. Receive-side errors usually point to the signal\n   arriving on that side, not necessarily the port reporting the error.\n3. Replace patch cable or clean\u002Freplace fiber and optics.\n4. Confirm speed\u002Fduplex settings match on both sides.\n5. Check logs for flap events around the same timestamp.\n\n### Drops\n\n1. Separate input drops from output drops.\n2. Compare interface rate against capacity.\n3. Check QoS policy, queue counters, and whether the link is an oversubscribed\n   uplink.\n4. Treat queue tuning as secondary. First prove whether the link is congested.\n\n### Duplex And Speed\n\nPrefer auto-negotiation on modern Ethernet links when both sides support it. If\none side must be fixed, configure both sides explicitly and document why. Never\nmix fixed speed\u002Fduplex on one side with auto on the other.\n\n```text\nshow interfaces \u003Cinterface> | include duplex|speed\n```\n\n## Safe Parser Example\n\nSlice each interface block from one header to the next. Do not use an arbitrary\ncharacter window; large interface blocks can cause counters to be missed or\nassigned to the wrong port.\n\n```python\nimport re\nfrom typing import Any\n\nHEADER_RE = re.compile(\n    r\"^(?P\u003Cname>\\S+) is (?P\u003Cstatus>(?:administratively )?down|up), \"\n    r\"line protocol is (?P\u003Cprotocol>up|down)\",\n    re.I | re.M,\n)\nERROR_RE = re.compile(r\"(?P\u003Cinput>\\d+) input errors, (?P\u003Ccrc>\\d+) CRC\", re.I)\nDROP_RE = re.compile(r\"(?P\u003Coutput>\\d+) output errors\", re.I)\nDUPLEX_RE = re.compile(r\"(?P\u003Cduplex>Full|Half|Auto)-duplex,\\s+(?P\u003Cspeed>[^,]+)\", re.I)\n\ndef parse_show_interfaces(raw: str) -> list[dict[str, Any]]:\n    headers = list(HEADER_RE.finditer(raw))\n    interfaces = []\n    for index, header in enumerate(headers):\n        end = headers[index + 1].start() if index + 1 \u003C len(headers) else len(raw)\n        block = raw[header.start():end]\n        errors = ERROR_RE.search(block)\n        drops = DROP_RE.search(block)\n        duplex = DUPLEX_RE.search(block)\n        interfaces.append({\n            \"name\": header.group(\"name\"),\n            \"status\": header.group(\"status\"),\n            \"protocol\": header.group(\"protocol\"),\n            \"duplex\": duplex.group(\"duplex\") if duplex else \"unknown\",\n            \"speed\": duplex.group(\"speed\").strip() if duplex else \"unknown\",\n            \"input_errors\": int(errors.group(\"input\")) if errors else 0,\n            \"crc_errors\": int(errors.group(\"crc\")) if errors else 0,\n            \"output_errors\": int(drops.group(\"output\")) if drops else 0,\n        })\n    return interfaces\n```\n\n## Examples\n\n### CRCs On One Switch Port\n\n1. Capture counters on the local port.\n2. Capture counters on the connected remote port.\n3. Replace the cable or optic before changing routing or firewall rules.\n4. Clear counters only after recording the baseline.\n5. Recheck after a fixed interval.\n\n### Internet Slow But LAN Is Fine\n\n1. Check WAN interface drops\u002Ferrors.\n2. Check LAN uplink utilization and output drops.\n3. Check gateway CPU if the WAN link is clean but throughput is still low.\n4. Compare wired and wireless tests before blaming upstream service.\n\n## Anti-Patterns\n\n- Clearing counters before saving a baseline.\n- Looking at only one side of a link.\n- Assuming all historical CRCs are active problems without a time window.\n- Mixing auto-negotiation on one side with fixed speed\u002Fduplex on the other.\n- Treating output drops as a cable problem before checking congestion.\n\n## See Also\n\n- Agent: `network-troubleshooter`\n- Skill: `network-config-validation`\n- Skill: `homelab-network-setup`\n","# Network Interface Health\n\nUse this skill when a network symptom might be caused by a physical link, switch\nport, cable, transceiver, duplex setting, or congested interface.\n\n## When to Use\n\n- A host or VLAN has packet loss, latency spikes, or intermittent reachability.\n- A switch or router interface shows CRCs, runts, giants, drops, resets, or flaps.\n- You need to compare both ends of a link before replacing hardware.\n- A change window needs before\u002Fafter interface counter evidence.\n- Monitoring reports rising `ifInErrors`, `ifOutErrors`, or `ifOutDiscards`.\n\n## How It Works\n\nInterface counters are evidence, but the trend matters more than the absolute\nnumber. Capture a baseline, wait a measurement interval, capture again, then\ncompare increments.\n\n```text\nshow interfaces \u003Cinterface>\nshow interfaces \u003Cinterface> status\nshow logging | include \u003Cinterface>|changed state|line protocol\n```\n\nOn Linux hosts:\n\n```text\nip -s link show \u003Cinterface>\nethtool \u003Cinterface>\nethtool -S \u003Cinterface>\n```\n\n## Counter Reference\n\n| Counter | Meaning | Common cause |\n| --- | --- | --- |\n| CRC | Received frame checksum failed | Bad cable, dirty fiber, bad optic, duplex mismatch |\n| input errors | Aggregate receive-side errors | Check sub-counters before concluding |\n| runts | Frames below minimum Ethernet size | Duplex mismatch, collision domain, faulty NIC |\n| giants | Frames larger than expected MTU | MTU mismatch or jumbo-frame boundary |\n| input drops | Device could not accept inbound packets | Burst, oversubscription, CPU path, queue pressure |\n| output drops | Egress queue discarded packets | Congestion, QoS policy, undersized uplink |\n| resets | Interface hardware reset | Flapping, keepalive, driver, optic, power |\n| collisions | Ethernet collision counter | Half duplex or negotiation mismatch |\n\n## Diagnosis Flow\n\n### CRCs Or Input Errors\n\n1. Confirm counters are incrementing, not just historical.\n2. Check both ends of the link. Receive-side errors usually point to the signal\n   arriving on that side, not necessarily the port reporting the error.\n3. Replace patch cable or clean\u002Freplace fiber and optics.\n4. Confirm speed\u002Fduplex settings match on both sides.\n5. Check logs for flap events around the same timestamp.\n\n### Drops\n\n1. Separate input drops from output drops.\n2. Compare interface rate against capacity.\n3. Check QoS policy, queue counters, and whether the link is an oversubscribed\n   uplink.\n4. Treat queue tuning as secondary. First prove whether the link is congested.\n\n### Duplex And Speed\n\nPrefer auto-negotiation on modern Ethernet links when both sides support it. If\none side must be fixed, configure both sides explicitly and document why. Never\nmix fixed speed\u002Fduplex on one side with auto on the other.\n\n```text\nshow interfaces \u003Cinterface> | include duplex|speed\n```\n\n## Safe Parser Example\n\nSlice each interface block from one header to the next. Do not use an arbitrary\ncharacter window; large interface blocks can cause counters to be missed or\nassigned to the wrong port.\n\n```python\nimport re\nfrom typing import Any\n\nHEADER_RE = re.compile(\n    r\"^(?P\u003Cname>\\S+) is (?P\u003Cstatus>(?:administratively )?down|up), \"\n    r\"line protocol is (?P\u003Cprotocol>up|down)\",\n    re.I | re.M,\n)\nERROR_RE = re.compile(r\"(?P\u003Cinput>\\d+) input errors, (?P\u003Ccrc>\\d+) CRC\", re.I)\nDROP_RE = re.compile(r\"(?P\u003Coutput>\\d+) output errors\", re.I)\nDUPLEX_RE = re.compile(r\"(?P\u003Cduplex>Full|Half|Auto)-duplex,\\s+(?P\u003Cspeed>[^,]+)\", re.I)\n\ndef parse_show_interfaces(raw: str) -> list[dict[str, Any]]:\n    headers = list(HEADER_RE.finditer(raw))\n    interfaces = []\n    for index, header in enumerate(headers):\n        end = headers[index + 1].start() if index + 1 \u003C len(headers) else len(raw)\n        block = raw[header.start():end]\n        errors = ERROR_RE.search(block)\n        drops = DROP_RE.search(block)\n        duplex = DUPLEX_RE.search(block)\n        interfaces.append({\n            \"name\": header.group(\"name\"),\n            \"status\": header.group(\"status\"),\n            \"protocol\": header.group(\"protocol\"),\n            \"duplex\": duplex.group(\"duplex\") if duplex else \"unknown\",\n            \"speed\": duplex.group(\"speed\").strip() if duplex else \"unknown\",\n            \"input_errors\": int(errors.group(\"input\")) if errors else 0,\n            \"crc_errors\": int(errors.group(\"crc\")) if errors else 0,\n            \"output_errors\": int(drops.group(\"output\")) if drops else 0,\n        })\n    return interfaces\n```\n\n## Examples\n\n### CRCs On One Switch Port\n\n1. Capture counters on the local port.\n2. Capture counters on the connected remote port.\n3. Replace the cable or optic before changing routing or firewall rules.\n4. Clear counters only after recording the baseline.\n5. Recheck after a fixed interval.\n\n### Internet Slow But LAN Is Fine\n\n1. Check WAN interface drops\u002Ferrors.\n2. Check LAN uplink utilization and output drops.\n3. Check gateway CPU if the WAN link is clean but throughput is still low.\n4. Compare wired and wireless tests before blaming upstream service.\n\n## Anti-Patterns\n\n- Clearing counters before saving a baseline.\n- Looking at only one side of a link.\n- Assuming all historical CRCs are active problems without a time window.\n- Mixing auto-negotiation on one side with fixed speed\u002Fduplex on the other.\n- Treating output drops as a cable problem before checking congestion.\n\n## See Also\n\n- Agent: `network-troubleshooter`\n- Skill: `network-config-validation`\n- Skill: `homelab-network-setup`\n",{"name":5,"origin":24,"description":7},"community","master","d6ca01da0f24a3b0e26e4a8b7b66cbd25d429f5d","skills\u002Fnetwork-interface-health",0,"https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills","https:\u002F\u002Fgithub.com\u002FSriramGandhiS","https:\u002F\u002Fsriram.website\u002F","Curious guy who keeps tinkering until something works","2026-05-20 16:21:34",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add SriramGandhiS\u002FSkills --skill network-interface-health",{"tool":40,"command":41},"bunx","bunx skills add SriramGandhiS\u002FSkills --skill network-interface-health",{"tool":43,"command":44},"pnpm","pnpm dlx skills add SriramGandhiS\u002FSkills --skill network-interface-health","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fskills\u002Fnetwork-interface-health\u002FSKILL.md",true,[],[49,56,61,67,74,81],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M732609EPJWV13PVTX3GT4TM","webgpu-threejs-tsl","Comprehensive guide for developing WebGPU-enabled Three.js applications using TSL (Three.js Shading Language). Covers WebGPU renderer setup, TSL syntax and node materials, compute shaders, post-processing effects, and WGSL integration. Use this skill when working with Three.js WebGPU, TSL shaders, node materials, or GPU compute in Three.js.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fwebgpu-threejs-tsl\u002Fskills\u002Fwebgpu-threejs-tsl\u002FSKILL.md",[],[],{"skillNo":57,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7325XM47AGWB6K6C4VXKE6B","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fwebgpu-threejs-tsl\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7325WP6DES69JKC840VMFEP","verification-loop","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7325TFQF1DZTQ6J3WGQQ1VR","tdd-workflow","Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Ftdd-workflow\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7325RGV9AY9PK92D2V8KKPW","strategic-compact","Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fstrategic-compact\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7325MZC28SE86E7NMCNEFS4","security-review","Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment\u002Fsensitive features. Provides comprehensive security checklist and patterns.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fsecurity-review\u002FSKILL.md",[],[]]