菜单
Cisco Meraki switching (read-only) — port configuration and status, VLANs, ACLs, QoS, STP, link aggregation, routing interfaces via Cisco's official Meraki MCP. Use when inspecting Meraki switch ports, auditing switch ACLs, or investigating port errors
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/automateyournetwork/netclaw --skill meraki-switch-ops命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Turn a network topology into one stylized, AI-generated still image via a self-hosted ComfyUI instance — reuses the same topology model as threejs-network-viz (any of 8 topology-source integrations, or a freeform description). Use when the operator asks for a stylized, flashy, or AI-generated image/picture/illustration of a network topology. Stills only — no video/animation.
Zoom meeting intelligence — correlates a live or referenced Zoom meeting discussion against NetClaw's historical meeting record (via the official Zoom Meetings MCP) and today's actual network state. Use when someone in a Zoom meeting references a past discussion or incident ('didn't we have this issue before?'), or asks to search prior meetings for a topic. Does not itself recognize live in-meeting questions — that happens automatically inside zoom-rtms-mcp's own extractor (spec 118) before this skill is ever invoked.
Manage Lantronix out-of-band (OOB) infrastructure via Percepxion central management platform: device inventory, serial port inspection via SLC CLI, firmware compliance, config management, security auditing, and closed-loop incident remediation. Use during outages, maintenance windows, compliance cycles, and AI-assisted automation workflows.
基于 SOC 职业分类
正在显示 SKILL.md
| name | meraki-switch-ops |
| description | Cisco Meraki switching (read-only) — port configuration and status, VLANs, ACLs, QoS, STP, link aggregation, routing interfaces via Cisco's official Meraki MCP. Use when inspecting Meraki switch ports, auditing switch ACLs, or investigating port errors |
| version | 2.0.0 |
| license | Apache-2.0 |
| tags | ["cisco","meraki","switch","port","vlan","acl","qos","stp","read-only"] |
https://mcp.meraki.com/mcp (remote HTTP, no local install)MERAKI_DASHBOARD_API_KEY — use a read-only dashboard keysemantic_search (discover) and execute_api (invoke)All 431 mutating Meraki operations (174 POST, 186 PUT, 71 DELETE) are absent from the
capability catalogue. Only non-deprecated GETs are built in, so updateNetwork,
rebootDevice, blinkDeviceLeds and friends return Capability not found.
Do not attempt writes and do not offer them. There is no ServiceNow CR path here because there is nothing to gate — a change must be made in the Meraki dashboard directly.
Two capability IDs may be called directly; everything else must be discovered:
execute_api → getOrganizations — find accessible org IDsexecute_api → getOrganizationNetworks — find network IDs in the chosen orgsemantic_search → describe the intent in words → returns ranked capability_idsexecute_api → the chosen capability_id + its required parametersDiscover, do not guess. An earlier version of this skill hardcoded 80 method names and
54 of them did not exist in the Meraki API at all — they failed regardless of server.
semantic_search is the guard against that: it can only return IDs that exist.
One page only. execute_api returns a single page. Request a bounded page size when
supported, and never present a page as the complete dataset.
Empty is not absent. n=0 means this network reported none, never none exist.
Live proof from a real sandbox org: getOrganizationDevices returns 0 devices while
the same org has a fully configured network with 15 SSIDs.
Three distinct errors, three different fixes:
| Error | Meaning | Fix |
|---|---|---|
Capability not found | ID is mutating, deprecated, or invented | semantic_search for a real one |
Resource not found | valid ID, wrong org/network/serial | re-derive the ID from step 1–2 |
Invalid parameters | valid ID, missing a required parameter | read the capability's parameters |
Never report any of the three as "no data" — none of them mean that.
| Capability ID | Verified result |
|---|---|
getNetworkSwitchAccessControlLists | 1 ACL set on a real network |
There are 50 real switch capabilities. The ones you will reach for most:
getDeviceSwitchPorts, getDeviceSwitchPortsStatuses, getDeviceSwitchPortsStatusesPackets,
getNetworkSwitchAccessPolicies, getNetworkSwitchRoutingMulticast,
getDeviceSwitchRoutingInterfaces, getDeviceSwitchRoutingStaticRoutes,
getDeviceSwitchWarmSpare. Confirm each with semantic_search before calling.
Port capabilities are per-device and need a serial, not a network ID. Get serials from
getOrganizationDevices (org-wide) — and note that an org with 0 devices returns 0
serials, which is not the same as "the switches have no ports".
getOrganizations → getOrganizationNetworks → getOrganizationDevicesgetDeviceSwitchPorts — VLAN, type, PoE, STP guard, isolationgetDeviceSwitchPortsStatuses — link state, speed, duplex, errors, discardsgetNetworkSwitchAccessControlLists and getNetworkSwitchAccessPolicies — ACL/802.1XgetDeviceSwitchPortsStatuses — identify ports with errors or discardsgetDeviceSwitchPortsStatusesPackets — packet-level breakdown per portsemantic_search "switch port cable test results" — physical-layer evidencegetDeviceLossAndLatencyHistory via meraki-monitoring| Skill | How They Work Together |
|---|---|
meraki-network-ops | Network and device inventory for switch discovery |
meraki-monitoring | Loss/latency history and live tools for switch uplinks |
meraki-security-appliance | Trace a VLAN from switch port to firewall rule |
gait-session-tracking | Record all switch audits |
MERAKI_DASHBOARD_API_KEY — Meraki Dashboard API key (read-only recommended)