devopsby automateyournetwork
Catalyst Center Troubleshooting Workflows
automateyournetwork/catc-troubleshoot
Catalyst Center troubleshooting workflows - device unreachable investigation, client connectivity issues, interface down analysis, site-wide outage triage, wireless roaming problems, integration with pyATS for CLI-level diagnostics.
What it changes
Passed 7 of 12 test cases with the skill, and 2 of 12 without it.
Without skill14%
With skill59%
Checks it passed that the model alone missed
- Invokes pyats_show_logging via $MCP_CALL for device_name DIST-SW-01.
- Passes device_name set to CORE-SW-01 and command set to ping 10.1.10.1.
- Invokes gait_record_turn using $GAIT_MCP_SCRIPT to log the outcome into GAIT.
and 12 more in the full report
10 fixed3 passed either way9 still failing0 broke
- Pass-rate lift
- +45 pp
- Tokens
- +325%
- Agent turns
- 0%
- Response time
- -9%
Model gemini-3.6-flashMeasured 8/16/2026v113 of 22 cases passed with skill · 12 comparable
See it in action
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
PromptWe need to check recent system logging events on switch 'DIST-SW-01' to see exact timestamps when interface TenGigabitEthernet1/0/1 flapped.
What was checked, without and with the skill| Checked | Without skill | With skill |
|---|
| Invokes pyats_show_logging via $MCP_CALL for device_name DIST-SW-01. | Missed | Passed |
|---|
What's inside
The instructions your model reads when the skill loads.
SKILL.md596 linessingle file
Catalyst Center Troubleshooting Workflows
Catalyst Center MCP Server
All Catalyst Center tool calls use this invocation pattern:
CCC_HOST=$CCC_HOST CCC_USER=$CCC_USER CCC_PWD=$CCC_PWD python3 -u $CATC_MCP_SCRIPT
Variable shorthand used throughout this document:
CATC_CMD="CCC_HOST=$CCC_HOST CCC_USER=$CCC_USER CCC_PWD=$CCC_PWD python3 -u $CATC_MCP_SCRIPT"
How to Call Tools
Use the $MCP_CALL protocol handler to invoke MCP tools:
CCC_HOST=$CCC_HOST CCC_USER=$CCC_USER CCC_PWD=$CCC_PWD python3 $MCP_CALL "python3 -u $CATC_MCP_SCRIPT" TOOL_NAME 'ARGS_JSON'
When to Use
- Help desk escalation: user reports "I can't connect"
- NOC alert: device unreachable in Catalyst Center
- Client connectivity complaints (wired or wireless)
- Site-wide outage affecting multiple users
- Wireless roaming issues or poor signal complaints
- Interface down investigations
- Post-change verification when something goes wrong
- Correlation between Catalyst Center data and live device state via pyATS
Troubleshooting Principles
- Define the problem -- What exactly is reported? Single user, multiple users, entire site? Wired or wireless? When did it start?
- Scope the impact -- Use Catalyst Center client counts and device reachability to quantify: how many clients affected? How many devices unreachable?
- Gather data from the controller -- Catalyst Center provides a controller-level view that covers hundreds of devices simultaneously. Start here.
Track record
Benchmark
7 / 12
test cases passed, vs 2 / 12 without
Adoption
- Users
- 0
- Times used
- 0
Safety and source details
SkillSafety
✓ 3 of 3 passed✓Code scan15 of 15 checks clean
0 critical · 0 warning · 0 info — scanner v4 — 8/3/2026
View 15 scanner checks
live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing
✓IntentSafe
LLM judge · does the skill do what it claims
✓ContentClean
LLM judge · policy & harmful-content review
Source
Importedautomateyournetwork / netclaw
workspace/skills/catc-troubleshoot/SKILL.md
License Apache-2.0Imported 8/3/2026Version v1