networking-ops-edho-ferdian

Reviews, designs, troubleshoots, and automates network configurations across five operational modes.

2|Updated Sep 6, 2026
One-click install
npx skills add https://github.com/edhoferdian/EEF --skill networking-ops-edho-ferdian-edhoferdian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: networking-ops-edho-ferdian
Source: https://github.com/edhoferdian/EEF/tree/main/.agents/skills/networking-ops-edho-ferdian
Command: npx skills add https://github.com/edhoferdian/EEF --skill networking-ops-edho-ferdian-edhoferdian

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires netmiko, and includes references (resource) components.

What problem does it solve? Network work spans many disconnected tasks — auditing a pasted Cisco config, designing VLAN segmentation, diagnosing why DNS fails, scripting a change across dozens of switches, or planning a homelab — and mistakes in any of them can cause outages or lock operators out of their own gear. This Skill consolidates all of that into one mode-detected workflow with consistent safety rules. ## Core Features & Use Cases - Five auto-detected modes: config review with an evidence-based severity ladder (Critical/High/Medium/Low plus PASS/WARNING/BLOCK verdict), network design for homelab or enterprise/multi-site, read-only OSI-layer troubleshooting, device operations with change-window discipline, and homelab build-out planning. - Safe automation patterns: Netmiko-based SSH collection and guarded change scripts with preflight validation — destructive-command detection, duplicate IP and subnet overlap checks, credential hygiene, bounded concurrency, and dry-run-by-default posture. - Vendor-aware guidance: concrete Cisco IOS/IOS-XE command patterns plus conceptual maps for UniFi, pfSense/OPNsense, and MikroTik UIs, with explicit staleness caveats. - Use Case: A user pastes a switch config and asks "cek config Cisco ini" — the Skill enters config-review mode, quotes the exact offending lines (e.g. snmp-server community public), assigns severities, and returns a BLOCK verdict with safe remediations. ## Quick Start Ask the assistant to review this Cisco switch configuration for security issues before tonight's maintenance window.

Frequently Asked Questions about networking-ops-edho-ferdian

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a Cisco config for security issues?

Paste the running configuration or proposed change snippet and ask for a review. The config-review mode parses interfaces, ACLs, VTY, AAA, SNMP, and logging blocks, then reports findings on a Critical-to-Low severity ladder with quoted evidence and a PASS, WARNING, or BLOCK verdict.

How to automate network changes across multiple switches with Python?

Use the Netmiko-based automation patterns: validate candidate configs with preflight checks first, collect state read-only over SSH with bounded concurrency and per-device failure isolation, then apply changes only behind an explicit operator flag with before/after captures.

Does this support Juniper, Arista, or MikroTik devices?

Concepts like change windows, preflight validation, and BGP/interface diagnosis generalize to any vendor, but concrete command syntax is Cisco IOS/IOS-XE only. MikroTik, UniFi, and pfSense/OPNsense get conceptual UI guidance with explicit staleness caveats, not verified click-paths.

Why is my BGP neighbor stuck in Active state?

Active state means TCP to the peer is not completing. Check routing to the peer's source address, update-source configuration, ACLs blocking port 179, and whether both directions route to loopbacks if loopback peering is used — the most common cause.

Can it push configuration changes to live devices?

Only in device-operations mode, and never by default. Any state-changing command requires a maintenance window, config backup, rollback plan, and an explicit operator flag; saving to startup config is always a separate, later, approved step.

What are the limitations of the troubleshooting mode?

Troubleshooting is strictly read-only and will never suggest removing ACLs, firewall rules, or authentication to isolate a cause. It provides the layer-by-layer diagnostic logic, but live evidence gathering requires device access the user already has or the automation reference's scripted collection.