Menu
Return a focused, structured health summary for one fabric node (interfaces and BGP), instead of a raw tool dump
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Snapshot a node's state before and after a change, then report exactly what changed and whether the fabric is still healthy
Query one fabric node and return its interface and BGP state as structured JSON
Summarize a single piece of fabric state in a structured way, instead of returning a raw tool dump (replace this with your own one-line, verb-first description that says when to use the skill)
Walk a workshop participant through contributing a skill or lab back to the Skills & Specs Lab via fork and pull request, including GitHub PAT setup
Scaffold a new agentskills.io SKILL.md from a short description, with the right frontmatter, a focused scope, and a quality checklist
| name | network-state-query |
| description | Return a focused, structured health summary for one fabric node (interfaces and BGP), instead of a raw tool dump |
| state | active |
Use this skill when someone asks "is <node> healthy?" or "what is the state of
<node>?" for a node in the Skills & Specs Lab fabric (spine1, spine2,
leaf1, leaf2). This is the reference skill: it sets the quality bar for the
skills you build in Lab 1. Study its shape before writing your own.
The point of a skill over a raw tool: a raw tool (for example the clab
inspectLab tool) hands back a firehose of generic data and leaves you to find
the answer. This skill asks the operational question directly and returns a
scoped, labeled, structured result.
spine1, spine2, leaf1, leaf2. If not,
stop and say so.clab-skills-specs-lab-<node>.docker exec clab-skills-specs-lab-<node> sr_cli "show interface brief"docker exec clab-skills-specs-lab-<node> sr_cli "show network-instance default protocols bgp neighbor"Return exactly this structure (JSON), nothing more:
{
"node": "leaf1",
"interfaces": [
{"name": "ethernet-1/1", "admin": "enable", "oper": "up"},
{"name": "ethernet-1/2", "admin": "enable", "oper": "up"},
{"name": "system0", "admin": "enable", "oper": "up"}
],
"bgp": [
{"peer": "10.1.1.1", "peer_as": 65100, "state": "established", "uptime": "0:12:30"},
{"peer": "10.2.1.1", "peer_as": 65100, "state": "established"}
],
"healthy": true,
"summary": "leaf1: 3/3 interfaces up, 2/2 BGP sessions established."
}
healthy is true only when every fabric interface is up and every BGP
session is established. The one-line summary is what a human reads first.
{"error": "unknown node <name>", "valid": ["spine1","spine2","leaf1","leaf2"]}.{"node": "<node>", "error": "container not running", "hint": "./scripts/deploy.sh"}.active/connect): report healthy: false
and note in summary that the fabric may still be converging; suggest re-running
after 30 seconds.