network-state-collection
Skill1 starsChanged 32 days agoApache-2.0View on GitHub
Capture structured network state before and after a change, or gather evidence while troubleshooting, by parsing command output, learning feature state, querying platform state or snapshots, and comparing saved snapshots. Use when you need observed state data to compare or inspect. Covers Cisco pyATS / Genie, IP Fabric, Forward Networks, Arista CloudVision, Zabbix, Auvik, Cisco ACI APIC, and read-only AWS and Azure cloud network configuration; assumes the chosen tool's access (a pyATS testbed or captured output, or an authenticated platform API client). It reports what was observed; it does not diagnose root causes or approve a change.
In this repository40 other files it gives its agents.
- AGENTS.mdAGENTS.md
- alert-monitor-managementSkill
- automation-job-executionSkill
- casb-policy-managementSkill
- casb-posture-assessmentSkill
- certificate-managementSkill
- change-managementSkill
- cloud-security-group-auditSkill
- cmdb-asset-managementSkill
- compute-instance-provisioningSkill
- config-backup-managementSkill
- connector-tunnel-managementSkill
- container-workload-deploymentSkill
- crm-contact-managementSkill
- dcim-asset-managementSkill
- dhcp-scope-managementSkill
- dns-record-managementSkill
- dns-zone-managementSkill
- firewall-managementSkill
- incident-managementSkill
- infrastructure-plan-executionSkill
- interface-link-troubleshootingSkill
- ipam-allocationSkill
- load-balancingSkill
- log-querySkill
- metric-querySkill
- network-access-control-managementSkill
- network-health-verificationSkill
- notificationsSkill
- repository-pull-request-managementSkill
- routing-troubleshootingSkill
- sdwan-policy-managementSkill
- sdwan-site-onboardingSkill
- secret-retrievalSkill
- software-upgrade-lifecycleSkill
- vpn-tunnel-managementSkill
- vulnerability-lookupSkill
- waf-managementSkill
- wireless-network-managementSkill
- zero-trust-access-policy-managementSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Use to record device state before a change and again after it, to turn raw command output into structured data, or to gather evidence while …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Network State Collection
Parse command output, learn feature state, query platform state or snapshots, and compare saved snapshots to produce evidence of network state.
When to use this skill
Use to record device state before a change and again after it, to turn raw command output into
structured data, or to gather evidence while troubleshooting. Health screens and
post-change verification belong to network-health-verification. Applying changes to devices is outside this skill.
Universal concepts
- Snapshots, or reads of live state, are comparable only when both sides cover the same devices, commands or features, and scope.
- Where volatile fields (counters, timers) are present, they are handled by documented defaults or explicit exclusions, and state being checked is never excluded.
- A collection failure or empty result is incomplete data, not a healthy network.
- An empty difference establishes equality only for the fields actually collected.
- Parser, feature, and device coverage vary by tool and platform; unsupported or uncollected coverage is reported, not substituted or read as healthy.
Procedure
- Identify the requested tool and mode in references/INDEX.md.
- Open the linked tool procedure and follow it exactly, including its confirmation gates.
- Report results using that procedure's own status vocabulary.
Known limitations
Collection and comparison report observed data only. Live collection or discovery is gated in the tool procedure.
Contributing to this skill
Change this router only to correct its shared concepts/routing or add a supported platform pointer. Vendor details belong in that vendor's references. Recheck shared claims before adding a platform.
Tools
A local pyATS/Genie CLI with device transport or the Genie parser library for captured text, or an authenticated API client for the IP Fabric, Forward Networks, Arista CloudVision, Zabbix, Auvik, or Cisco ACI APIC platform, an AWS Network MCP binding, or an Azure CLI session.
Verification checklist
- Tool and mode match an entry in the index.
- Requested collections produced data and evidence, or an explicit failure.
- Both comparison inputs contain collected state.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

