Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →automateyournetwork/multivendor-device-query
Query network devices on platforms NetClaw's Cisco- and Juniper-specific servers cannot reach —
Passed 16 of 20 test cases with the skill, and 8 of 20 without it.
and 6 more in the full report
9 fixed9 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
We need to run a unified read-only query to compare system uptime and interface status across a Cisco switch, an Arista router, and a Nokia SR Linux device using a single normalized model. Which server should be queried?
| Checked | Without skill | With skill |
|---|---|---|
| Selects multivendor-cli-mcp for the cross-vendor query | Missed | Passed |
The instructions your model reads when the skill loads.
Query network devices on platforms NetClaw's Cisco- and Juniper-specific servers cannot reach — MikroTik RouterOS, VyOS, SONiC, Nokia SR Linux, Extreme, Huawei, Dell, Ubiquiti EdgeOS, and roughly eighty more.
MCP server: multivendor-cli-mcp (results identify themselves as multivendor-cli)
This skill is wrong for most Cisco and Juniper work. Check here before using it:
| Your device | Use |
|---|---|
| Cisco IOS / IOS-XE / NX-OS / IOS-XR | pyats-* skills — ~2000 Genie parsers, state diffing |
| Juniper Junos | junos-network skill — PyEZ/NETCONF |
| Streaming telemetry, any vendor | gnmi-telemetry skill |
| No direct reachability | radkit-remote-access skill |
| Anything else | this skill |
| "Compare X across Cisco and Arista and Nokia" | this skill (read-only) |
That last row is the exception worth understanding. NAPALM returns one shape across vendors, so this is the only server that can answer a genuinely cross-vendor question. It answers those read-only, even on Cisco and Juniper.
Configuration writes on Cisco and Juniper are refused, naming the correct server. That is deliberate, not a limitation: one write path per platform is what makes "verify the change" mean something. Reads may overlap between servers; writes may not.
| Tool | Purpose |
|---|---|
server_info | Server identity, read-only vs write mode, which platforms have destructive-syntax modelling |
check_command_policy | Would this command be permitted? Answers without touching a device |
list_devices | Inventory, with the source that answered and why |
check_device_readiness | Is this device resolvable, authenticable, and mine to act on? Contacts nothing |
test cases passed, vs 8 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.