Individual skill
network-device-cli
Use when SSHing into a router, switch, or firewall CLI.
skills/network-device-cli/SKILL.md
Source commit ad1e8ecd0aac04276ea90b6ef2707848d8502e9a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 15
- Repository last updated
- Nov 8, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- bash Repository topic
- cisco Repository topic
- cli Repository topic
- config-management Repository topic
- fortinet Repository topic
- huawei Repository topic
- juniper Repository topic
- mikrotik Repository topic
- network-automation Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 9,306 bytesSKILL.mdcore · 9,306 bytesSKILL.mdcore · 9,306 bytesSKILL.mdcore · 9,306 bytesSKILL.mdcore · 9,306 bytesSKILL.mdcore · 9,306 bytesSKILL.mdcore · 9,306 bytesSKILL.mdcore · 9,306 bytesreferences/config-change-safety.mddoc · 6,018 bytesscripts/ios_session.shruns · 6,348 bytesscripts/legacy-ssh.shruns · 1,489 bytes
Read excerpt
# Network Device CLI (Cisco IOS and other appliances)
## When to Use
- The user gives a host + credentials and asks for a command (ping, show) to be
run **on** the device — router, switch, firewall, appliance.
- An SSH attempt to network gear fails with `Permission denied` or
`no acceptable kex algorithm`.
- You need device-side reachability (can the router reach 8.8.8.8?) rather than
host-side.
- A request wants device config **changed** (interface, VLAN, route, ACL), not
just read — see "Before a config change" below.
- You are rebuilding a device-inventory / automation workflow that must survive
session resets — the inventory (hostname, ip, port, credentials, config_list,