Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

nbox-patch-writes

Estrelas7

Forks1

Atualizado27 de junho de 2026 às 02:01

Update NetBox object fields using nbox's PATCH write commands — interface set description and device set status. Use when the user wants to change an interface description or a device's status in NetBox.

Instalação

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ê.

Executar no Manus

Fonte

lance0

lance0/nbox

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Administradores de redes e sistemas de computadorInformática e Matemática·SOC 15-1244

SKILL.md

readonly

name	nbox-patch-writes
description	Update NetBox object fields using nbox's PATCH write commands — interface set description and device set status. Use when the user wants to change an interface description or a device's status in NetBox.

nbox PATCH writes

Two update write commands modify specific fields on NetBox objects via minimal PATCH bodies. Both follow the same dry-run / confirm / audit lifecycle (see the safe writes skill).

The two PATCH commands

`nbox interface <device> <interface> set description "…"`

Set an interface's description.

nbox --no-tui interface edge01 xe-0/0/1 set description "uplink to core" --dry-run --json
nbox --no-tui interface edge01 xe-0/0/1 set description "uplink to core" --allow-writes --confirm --json

Optional: --message. Run nbox interface <device> <interface> set description --help for the full flag set.

`nbox device <name> set status <value>`

Set a device's status. The status value is validated live against NetBox's OPTIONS choices before any PATCH — a label (e.g. "active") is accepted case-insensitively when it maps unambiguously to one canonical value; an unknown or ambiguous status is a usage error (exit 2) naming the input and listing the allowed values, before any PATCH.

nbox --no-tui device edge01 set status active --dry-run --json
nbox --no-tui device edge01 set status active --allow-writes --confirm --json

Optional: --message. Run nbox device <name> set status --help for the full flag set.

How they work

Minimal PATCH. The plan carries only the field being changed — {"description": "…"} or {"status": "active"}. No other fields are sent.
A no-op (current value already matches) sends no PATCH — the receipt reports no_op: true.
Concurrency. ETag + If-Match on NetBox 4.6+; last_updated + before-hash on pre-4.6. A concurrent writer is caught (412 / hash mismatch) and the write is refused with a "re-run dry-run" message (exit 1).
Choice validation (device status only): the allowed values are enumerated live from NetBox via a read-only OPTIONS request, so nbox never sends an invalid status. The normalization mechanism (src/netbox/choices.rs) is reusable for future REST choice fields.

Reference

Safe writes skill — the universal lifecycle
ADR-0001 — foundation design

Mais deste repositório

mesmo repositório

nbox

lance0/nbox

Query and modify NetBox (DCIM/IPAM) from the shell with the `nbox` CLI — look up devices, interfaces, IPs, prefixes, VLANs, sites, racks, circuits, VRFs, tenants, VMs, and clusters; run cross-object search; use IPAM helpers (next free IP/prefix, prefix utilization, cable-path traces); and safely write (reserve IPs/prefixes, set status/description, manage tags) behind a dry-run/confirm gate. Use when the user asks about NetBox, network inventory, IP addressing, or device/interface/cable details, or wants machine-readable network data or safe mutations. Read-only by default; supports `-o json` / `-o csv` and an MCP server.

2026-07-227

nbox-serve

lance0/nbox

Run nbox as an MCP server (read-only by default; optional local stdio writes with --local-writes, or shared HTTP/OIDC writes with --allow-writes + nbox:write + [serve.vault]) so an agent host can query NetBox over JSON-RPC — stdio or HTTP+OIDC transport, the read tools (search/get/get_interface/history/…), the nbox://{kind}/{ref} resource template, the investigation prompts catalog, and --print-config for install recipes. Use when the user wants to wire NetBox into an MCP host or stand up the server.

2026-06-297

nbox-writes

lance0/nbox

How to safely modify NetBox through nbox's write commands — the universal dry-run / confirm / audit lifecycle shared by all seven safe-write commands (interface description, device status, IP/prefix/ip-range reserve, tag add/remove). Use when the user wants to change NetBox objects, reserve IPs, or manage tags.

2026-06-297

nbox-device-context

lance0/nbox

Pull the full physical context of a device or interface from NetBox with nbox — a device's interfaces/IPs/cables/VLANs/services, an interface's cable-path A↔Z trace, a MAC reverse-resolved to its carrying interface/device, plus rack and site context. Use when the user asks how a device is connected, what's on an interface, where a MAC lives, or what's in a rack/site.

2026-06-287

nbox-ipam-read

lance0/nbox

Answer IP addressing questions from NetBox with nbox's IPAM read commands — look up an IP and its parent prefix/VLAN/scope, check prefix utilization and the prefix tree, preview the next free IP/prefix, and inspect VLANs, IP ranges, aggregates, VRFs, and route targets. Use when the user asks about addressing, allocation, or routing context.

2026-06-287

nbox-search

lance0/nbox

Find NetBox objects across kinds in one query with nbox's ranked, deduped cross-object search — the entry point when the kind or exact reference isn't known yet. Use when the user wants to locate a device/IP/prefix/VLAN/site/etc. by a name fragment, or narrow by site/tenant/role/tag/status/VRF before a detail lookup.

2026-06-287

nbox PATCH writes

Two update write commands modify specific fields on NetBox objects via minimal PATCH bodies. Both follow the same dry-run / confirm / audit lifecycle (see the safe writes skill).

The two PATCH commands

nbox interface <device> <interface> set description "…"

Set an interface's description.

nbox --no-tui interface edge01 xe-0/0/1 set description "uplink to core" --dry-run --json nbox --no-tui interface edge01 xe-0/0/1 set description "uplink to core" --allow-writes --confirm --json

Optional: --message. Run nbox interface <device> <interface> set description --help for the full flag set.

nbox device <name> set status <value>

nbox --no-tui device edge01 set status active --dry-run --json nbox --no-tui device edge01 set status active --allow-writes --confirm --json

Optional: --message. Run nbox device <name> set status --help for the full flag set.

How they work

Minimal PATCH. The plan carries only the field being changed — {"description": "…"} or {"status": "active"}. No other fields are sent.

A no-op (current value already matches) sends no PATCH — the receipt reports no_op: true.

Concurrency. ETag + If-Match on NetBox 4.6+; last_updated + before-hash on pre-4.6. A concurrent writer is caught (412 / hash mismatch) and the write is refused with a "re-run dry-run" message (exit 1).

Choice validation (device status only): the allowed values are enumerated live from NetBox via a read-only OPTIONS request, so nbox never sends an invalid status. The normalization mechanism (src/netbox/choices.rs) is reusable for future REST choice fields.

Reference

Safe writes skill — the universal lifecycle

ADR-0001 — foundation design