meraki

Locate a Meraki device by serial, name, or MAC across an organization's networks

Pull and summarize a Meraki network's L3 firewall rules and flag overly-permissive (any/any allow) rules

Sweep an organization's networks, devices, and appliance VPN status for a site-health overview

Use this agent when an MSP needs a read-only health and security audit of a Cisco Meraki organization — sweeping networks, devices, and appliances to surface offline or alerting hardware, appliances with site-to-site VPN peers down, overly-permissive firewall rules, and SSIDs configured with weak or open authentication. Trigger for: Meraki network audit, Meraki health check, offline devices Meraki, VPN down Meraki, firewall review Meraki, open SSID audit, Meraki security posture, org-wide Meraki sweep. Examples: "audit our Meraki org for offline devices and firewall issues", "check every site's VPN and flag any tunnels that are down", "which SSIDs across our Meraki networks are open or using WEP/WPA-Personal"

Use this skill when working with the Cisco Meraki MCP tools -- the full tool catalog, gateway header authentication, Dashboard API v1 structure, Link-header cursor pagination, per-org rate limiting, the read-only / confirm_destructive_action safety model, the meraki_raw_request escape hatch, error handling, and best practices.

Use this skill when working with Cisco Meraki device inventory and lifecycle -- listing devices in a network, getting a device by serial, rebooting, removing, and checking device/uplink status via meraki_raw_request across MX, MS, MR, MV, MG, and MT hardware.

Use this skill when working with the Cisco Meraki MX security appliance -- reviewing and updating L3 outbound firewall rules (meraki_appliance_firewall_l3_get/update) and checking site-to-site VPN status (meraki_appliance_vpn_status_get). Firewall updates replace the entire ruleset and are high-impact.

Use this skill for hands-on Cisco Meraki troubleshooting -- running live tools (ping, cable test, throughput, wake-on-LAN) via meraki_raw_request, rebooting devices, and checking uplink/connectivity status. Explains that live tools ride the meraki_raw_request passthrough because they are not curated tools.