workspace/skills/meraki-security-appliance/SKILL.md
Cisco Meraki Security Appliance (MX) — firewall rules, site-to-site VPN, content filtering, traffic shaping, security events. Use when auditing Meraki MX firewall rules, troubleshooting site-to-site VPN tunnels, managing content filtering, or investigating Meraki security events and IDS alerts
npx skillsauth add automateyournetwork/netclaw meraki-security-applianceInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
MERAKI_API_KEY, MERAKI_ORG_ID| Operation | API Method | What It Does |
|-----------|-----------|--------------|
| Security center | getNetworkSecurityCenter | Security overview: threat score, events, top threats |
| VPN status | getNetworkVpnStatus | VPN peer connectivity status |
| Firewall rules | getNetworkSecurityFirewallRules | L3 outbound firewall rules |
| Update firewall | updateNetworkSecurityFirewallRules | [WRITE] Modify L3 firewall rules |
| Site-to-site VPN | getNetworkSecurityVpnSiteToSite | VPN mode (hub/spoke/none), hubs, subnets |
| Update VPN | updateNetworkSecurityVpnSiteToSite | [WRITE] Modify VPN configuration |
| Content filtering | getNetworkSecurityContentFiltering | URL categories, blocked URLs, allowed URLs |
| Update filtering | updateNetworkSecurityContentFiltering | [WRITE] Modify blocked/allowed URL lists and categories |
| Security events | getNetworkSecuritySecurityEvents | IDS/IPS events, malware, C2 callbacks |
| Traffic shaping | getNetworkSecurityTrafficShaping | Global bandwidth limits, per-rule shaping |
| Update shaping | updateNetworkSecurityTrafficShaping | [WRITE] Modify bandwidth limits and shaping rules |
When a user asks "show me the firewall rules on the branch MX":
getNetworks (meraki-network-ops) for the branch networkgetNetworkSecurityFirewallRules — all L3 outbound rulesgetNetworkSecurityContentFiltering — URL category blocksgetNetworkSecuritySecurityEvents — recent IDS/IPS hitsWhen investigating "VPN tunnel to HQ is down":
getNetworkVpnStatus — tunnel state for all peersgetNetworkSecurityVpnSiteToSite — mode, hubs, subnetsgetDeviceStatus (meraki-network-ops) — is the MX online?getDeviceUplink — WAN link status (is ISP up?)getNetworkSecuritySecurityEvents — VPN-related errorsWhen auditing web content filtering:
getNetworkSecurityContentFiltering — blocked categories, blocked/allowed URLsgetNetworkSecuritySecurityEvents — users hitting blocked contentupdateNetworkSecurityContentFiltering — requires ServiceNow CRWhen responding to a security alert:
getNetworkSecuritySecurityEvents — IDS/IPS detections, malware, C2getClientDetails (meraki-network-ops) for involved endpointsgetNetworkSecurityFirewallRules — is the threat being blocked?updateClientPolicy to quarantine the endpoint — requires human approval| Skill | How They Work Together |
|-------|----------------------|
| meraki-network-ops | Network/device context for MX operations |
| meraki-monitoring | Live diagnostics on MX appliances |
| fmc-firewall-ops | Cross-platform firewall audit: Meraki MX rules vs Cisco FTD rules |
| aws-network-ops | Hybrid security: Meraki MX on-prem + AWS Network Firewall cloud |
| ise-posture-audit | Meraki client policies + ISE posture for unified access control |
| servicenow-change-workflow | Gate all firewall, VPN, and content filtering changes |
| gait-session-tracking | Record all security investigations and rule changes |
MERAKI_API_KEY — Meraki Dashboard API keyMERAKI_ORG_ID — Meraki organization IDtesting
Human-in-the-loop escalation via HumanRail — route low-confidence agent decisions, pre-destructive operation approvals, and ambiguous incident tickets to real human engineers. Human answers are verified and returned as structured output. Workers are paid via Lightning Network. Use when the agent is uncertain, when a destructive change needs explicit human sign-off beyond a ServiceNow CR, or when an ambiguous ticket requires human triage before automated handling.
testing
Manage EVE-NG node lifecycle. Use when listing nodes, checking runtime state, creating or deleting nodes, starting or stopping nodes or whole labs, verifying node details, or wiping node NVRAM back to factory defaults.
development
Manage EVE-NG labs and platform inventory. Use when listing labs, checking lab metadata, creating or deleting labs, importing or exporting lab archives, checking EVE-NG health or auth, or verifying available node images before build work.
tools
Execute live CLI commands on running EVE-NG nodes over telnet console. Use when running show commands, making live config changes, verifying protocol state, testing connectivity, checking console readiness, or interacting with IOS, Junos, VPCS, EOS, or NX-OS nodes.