Cisco Ios Patterns

If you've ever fat-fingered a wildcard mask or locked yourself out by applying an ACL in the wrong direction, this skill is the calm voice reminding you to collect state first and save last. It walks through the IOS config hierarchy, read-only show commands for evidence gathering, and a sensible change-window workflow that treats running-config as volatile until you've validated behavior. The wildcard mask reference alone will save you from permit statements that accidentally match half the internet. It's opinionated about interface hygiene, explicit about rollback paths, and clear that pasting full configs into tickets leaks secrets. Use it when you're building a maintenance checklist or need to explain why "no shutdown" isn't the same as "traffic is flowing."

skills.sh installs: 1.7K
GitHub stars: 229.1K
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/everything-claude-code --skill cisco-ios-patterns --agent claude-code

Installs into .claude/skills of the current project.

Files

Cisco IOS Patterns

Use this skill when reviewing Cisco IOS or IOS-XE snippets, building a change-window checklist, or explaining how to collect evidence from a router or switch without making the incident worse.

When to Use

Reviewing IOS or IOS-XE configuration before a planned change.
Choosing read-only show commands for troubleshooting.
Checking ACL wildcard masks and interface direction.
Explaining global, interface, routing process, and line configuration modes.
Verifying that a change landed in running config and was saved intentionally.

Operating Rules

Treat IOS examples as patterns, not paste-ready production changes. Confirm the platform, interface names, current config, rollback path, and out-of-band access before making changes on a real device.

Prefer this workflow: