Agent skill

Netbox Reconcile

by automateyournetwork in automateyournetwork/netclaw

Reconcile NetBox source of truth against live network state - detect IP drift, missing interfaces, undocumented links, cable mismatches, VLAN mismatches, and ticket discrepancies in ServiceNow.

Apache-2.0Auto-check passedBusiness, Finance & HR

Install Netbox Reconcile

skills CLI
$ npx skills add automateyournetwork/netclaw --skill netbox-reconcile -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install automateyournetwork/netclaw netbox-reconcile --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/workspace/skills/netbox-reconcile .claude/skills/netbox-reconcile && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
netbox-reconcile
GitHub stars
676
Token cost
~4.3k tokens
SKILL.md length
1,105 words
Files
1
Skills in repo
120
Repo updated
First seen
Licence
Apache-2.0

At a glance

Reconcile NetBox source of truth against live network state - detect IP drift, missing interfaces, undocumented links, cable mismatches, VLAN mismatches, and ticket discrepancies in ServiceNow.

  • Works in 7 steps: Collect NetBox Intent → Collect Live Device State → Diff Engine → …
  • Validating NetBox accuracy
  • SKILL.md covers Golden Rule, How to Call the Tools, NetBox Tools Reference and Discrepancy Types, plus 6 more sections
  • Calls python3

What it does

Netbox Reconcile is an agent skill from automateyournetwork/netclaw. Reconcile NetBox source of truth against live network state - detect IP drift, missing interfaces, undocumented links, cable mismatches, VLAN mismatches, and ticket discrepancies in ServiceNow. Use when validating NetBox accuracy, checking for config drift, auditing network documentation, or reconciling source of truth after changes

Its SKILL.md is about 4.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Business, Finance & HR. It works with ServiceNow and Model Context Protocol. The repository describes itself as: An AI agent that claws through your network. The licence is Apache-2.0.

When your agent uses it

  • Validating NetBox accuracy
  • Checking for config drift
  • Auditing network documentation
  • Reconciling source of truth after changes

Example prompts

  • “/netbox-reconcile”

Requirements

  • Python 3

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Collect NetBox Intent
  2. Collect Live Device State
  3. Diff Engine
  4. Generate Reconciliation Report
  5. Ticket Critical Discrepancies
  6. Generate Markmap Drift Summary
  7. Record in GAIT

What it can do on your machine

Read from SKILL.md and the folder at commit aa90e7d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • python3

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Netbox Reconcile loads about 4.3k tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 1,105 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~88
When it runs · the whole SKILL.md, loaded when a task matches
~4.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from automateyournetwork/netclaw at commit aa90e7d, republished under its Apache-2.0 licence (© automateyournetwork). 1,105 words, ~4,293 tokens.

Download SKILL.mdSave it as .claude/skills/netbox-reconcile/SKILL.md (or your agent's skills folder).
name
netbox-reconcile
description
Reconcile NetBox source of truth against live network state - detect IP drift, missing interfaces, undocumented links, cable mismatches, VLAN mismatches, and ticket discrepancies in ServiceNow. Use when validating NetBox accuracy, checking for config drift, auditing network documentation, or reconciling source of truth after changes
license
Apache-2.0
user-invocable
true

NetBox Reconciliation

Golden Rule

NetBox is READ-WRITE. The MCP has full API access to create and update devices, IPs, interfaces, VLANs, and cables. However, during reconciliation, discrepancies are reported and ticketed first — they are NEVER auto-corrected without explicit human approval. NetBox is the intended state. If reality differs from NetBox, either the network is wrong or NetBox needs updating. NetClaw can update NetBox when explicitly authorized by the operator.

How to Call the Tools

NetBox MCP Server
bash
python3 $MCP_CALL "python3 -u $NETBOX_MCP_SCRIPT" TOOL_NAME '{"param":"value"}'
pyATS MCP Server (for live device state)
bash
PYATS_TESTBED_PATH=$PYATS_TESTBED_PATH python3 $MCP_CALL "${PYATS_PYTHON:-python3} -u $PYATS_MCP_SCRIPT" TOOL_NAME '{"param":"value"}'

NetBox Tools Reference

ToolPurposeKey Parameters
netbox_get_objectsBulk query objects by typeobject_type, filters (dict), limit, brief
netbox_get_object_by_idGet single object by IDobject_type, object_id
netbox_search_objectsGlobal text searchquery, object_types
netbox_get_changelogsAudit trail of NetBox changesfilters
Object Types
Object TypeContains
dcim.devicesDevices: name, role, platform, site, status
dcim.interfacesInterfaces: name, type, enabled, MAC, MTU, mode (access/tagged), untagged_vlan, tagged_vlans
ipam.ip-addressesIP addresses: address (CIDR), assigned_object, status, role
dcim.cablesPhysical cables: A-side termination, B-side termination, type, length
ipam.vlansVLANs: vid, name, site, tenant, status
ipam.prefixesPrefixes: prefix (CIDR), VRF, site, status
dcim.sitesSites: name, region, physical_address

Discrepancy Types

CodeNameSeverityDescription
IP_DRIFTIP Address DriftCRITICALDevice IP differs from NetBox assignment
MISSING_INTERFACEMissing InterfaceHIGHInterface exists in NetBox but not on device (or vice versa)
UNDOCUMENTED_LINKUndocumented LinkHIGHCDP/LLDP shows a neighbor connection not documented in NetBox cables
CABLE_MISMATCHCable MismatchHIGHNetBox cable endpoints do not match CDP/LLDP neighbor data
VLAN_MISMATCHVLAN MismatchMEDIUMDevice VLAN assignment differs from NetBox
STATUS_MISMATCHInterface Status MismatchMEDIUMNetBox shows enabled but device shows down (or vice versa)
MTU_MISMATCHMTU MismatchLOWDevice MTU differs from NetBox interface MTU

Severity order: CRITICAL > HIGH > MEDIUM > LOW


Full Reconciliation Workflow

Step 1: Collect NetBox Intent
1A: Get Device Inventory from NetBox
bash
python3 $MCP_CALL "python3 -u $NETBOX_MCP_SCRIPT" netbox_get_objects '{"object_type":"dcim.devices","filters":{"status":"active"},"brief":true}'

This returns all active devices. Match against the pyATS testbed to determine which devices can be reconciled.

1B: Get Interfaces from NetBox (per device)
bash
python3 $MCP_CALL "python3 -u $NETBOX_MCP_SCRIPT" netbox_get_objects '{"object_type":"dcim.interfaces","filters":{"device":"R1"}}'

Extract per interface:

  • Name, type, enabled status
  • MTU, MAC address
  • Mode (access/tagged), untagged VLAN, tagged VLANs
  • Description, label
1C: Get IP Addresses from NetBox (per device)
bash
python3 $MCP_CALL "python3 -u $NETBOX_MCP_SCRIPT" netbox_get_objects '{"object_type":"ipam.ip-addresses","filters":{"device":"R1"}}'

Extract per IP:

  • Address (CIDR notation)
  • Assigned interface
  • Status (active, reserved, deprecated)
  • Role (primary, secondary, loopback, VIP)
1D: Get Cables from NetBox (per device)
bash
python3 $MCP_CALL "python3 -u $NETBOX_MCP_SCRIPT" netbox_get_objects '{"object_type":"dcim.cables","filters":{"device":"R1"}}'

Extract per cable:

  • A-side: device, interface
  • B-side: device, interface
  • Cable type, length, color
1E: Get VLANs from NetBox
bash
python3 $MCP_CALL "python3 -u $NETBOX_MCP_SCRIPT" netbox_get_objects '{"object_type":"ipam.vlans","filters":{"site":"main-site"}}'
Step 2: Collect Live Device State
2A: Get Interfaces from Device
bash
PYATS_TESTBED_PATH=$PYATS_TESTBED_PATH python3 $MCP_CALL "${PYATS_PYTHON:-python3} -u $PYATS_MCP_SCRIPT" pyats_run_show_command '{"device_name":"R1","command":"show ip interface brief"}'
bash
PYATS_TESTBED_PATH=$PYATS_TESTBED_PATH python3 $MCP_CALL "${PYATS_PYTHON:-python3} -u $PYATS_MCP_SCRIPT" pyats_run_show_command '{"device_name":"R1","command":"show interfaces"}'

Extract per interface:

  • Name, admin status (up/down), protocol status (up/down)
  • IP address, subnet mask
  • MTU, speed, duplex
  • Description
2B: Get IP Addresses from Device
bash
PYATS_TESTBED_PATH=$PYATS_TESTBED_PATH python3 $MCP_CALL "${PYATS_PYTHON:-python3} -u $PYATS_MCP_SCRIPT" pyats_run_show_command '{"device_name":"R1","command":"show ip interface"}'

Extract per interface:

  • Primary IP address and mask
  • Secondary IP addresses (if any)
2C: Get Neighbor Data from Device
bash
PYATS_TESTBED_PATH=$PYATS_TESTBED_PATH python3 $MCP_CALL "${PYATS_PYTHON:-python3} -u $PYATS_MCP_SCRIPT" pyats_run_show_command '{"device_name":"R1","command":"show cdp neighbors detail"}'
bash
PYATS_TESTBED_PATH=$PYATS_TESTBED_PATH python3 $MCP_CALL "${PYATS_PYTHON:-python3} -u $PYATS_MCP_SCRIPT" pyats_run_show_command '{"device_name":"R1","command":"show lldp neighbors detail"}'

Extract per neighbor:

  • Local interface -> Remote device, remote interface
  • Remote platform, remote IP
2D: Get VLAN Data from Device
bash
PYATS_TESTBED_PATH=$PYATS_TESTBED_PATH python3 $MCP_CALL "${PYATS_PYTHON:-python3} -u $PYATS_MCP_SCRIPT" pyats_run_show_command '{"device_name":"R1","command":"show vlan brief"}'
bash
PYATS_TESTBED_PATH=$PYATS_TESTBED_PATH python3 $MCP_CALL "${PYATS_PYTHON:-python3} -u $PYATS_MCP_SCRIPT" pyats_run_show_command '{"device_name":"R1","command":"show interfaces switchport"}'
Step 3: Diff Engine

Compare NetBox intent vs device reality for each discrepancy type.

3A: IP_DRIFT Detection

For each interface with an IP in NetBox:

NetBox:  GigabitEthernet1 -> 10.1.1.1/30
Device:  GigabitEthernet1 -> 10.1.1.5/30
Result:  IP_DRIFT (CRITICAL) - GigabitEthernet1: NetBox=10.1.1.1/30, Device=10.1.1.5/30

Comparison logic:

  1. Get all IPs from NetBox for device R1 (Step 1C)
  2. Get all IPs from device R1 (Step 2B)
  3. For each NetBox IP assignment:
    • Find the matching interface on the device
    • Compare the IP address and prefix length
    • If different -> IP_DRIFT (CRITICAL)
    • If interface exists but has no IP -> IP_DRIFT (CRITICAL)
  4. For each device IP not in NetBox -> IP_DRIFT (CRITICAL) - undocumented IP
3B: MISSING_INTERFACE Detection
NetBox:  GigabitEthernet3 (enabled)
Device:  GigabitEthernet3 does not exist
Result:  MISSING_INTERFACE (HIGH) - GigabitEthernet3 exists in NetBox but not on device

Comparison logic:

  1. Get interface list from NetBox (Step 1B)
  2. Get interface list from device (Step 2A)
  3. For each NetBox interface not found on device -> MISSING_INTERFACE (HIGH)
  4. For each device interface not found in NetBox -> MISSING_INTERFACE (HIGH) with note "undocumented"
  5. Filter out virtual/internal interfaces that are platform-specific (Null0, NVI0, etc.)
CDP:     R1:GigabitEthernet2 -> SW1:GigabitEthernet0/1
NetBox:  No cable record for R1:GigabitEthernet2
Result:  UNDOCUMENTED_LINK (HIGH) - R1:Gi2 -> SW1:Gi0/1 discovered via CDP but not in NetBox

Comparison logic:

  1. Get CDP/LLDP neighbors from device (Step 2C)
  2. Get cable records from NetBox (Step 1D)
  3. For each CDP/LLDP neighbor:
    • Search NetBox cables for a matching A-side/B-side pair
    • If no cable exists -> UNDOCUMENTED_LINK (HIGH)
Show full SKILL.md (454 more words)Show less
3D: CABLE_MISMATCH Detection
NetBox:  R1:GigabitEthernet1 -> R2:GigabitEthernet1
CDP:     R1:GigabitEthernet1 -> R3:GigabitEthernet0
Result:  CABLE_MISMATCH (HIGH) - R1:Gi1 NetBox says R2:Gi1 but CDP says R3:Gi0

Comparison logic:

  1. For each NetBox cable involving this device:
    • Look up the corresponding CDP/LLDP entry for the local interface
    • Compare the remote device and remote interface
    • If different -> CABLE_MISMATCH (HIGH)
3E: VLAN_MISMATCH Detection
NetBox:  GigabitEthernet2 untagged_vlan=10
Device:  GigabitEthernet2 access vlan 20
Result:  VLAN_MISMATCH (MEDIUM) - GigabitEthernet2: NetBox VLAN=10, Device VLAN=20

Comparison logic:

  1. Get interface VLAN assignments from NetBox (Step 1B, look at untagged_vlan and tagged_vlans)
  2. Get interface switchport data from device (Step 2D)
  3. Compare access VLAN, trunk allowed VLANs, and native VLAN
  4. If different -> VLAN_MISMATCH (MEDIUM)
3F: STATUS_MISMATCH Detection
NetBox:  GigabitEthernet3 enabled=true
Device:  GigabitEthernet3 administratively down
Result:  STATUS_MISMATCH (MEDIUM) - GigabitEthernet3: NetBox=enabled, Device=admin-down
3G: MTU_MISMATCH Detection
NetBox:  GigabitEthernet1 MTU=9000
Device:  GigabitEthernet1 MTU=1500
Result:  MTU_MISMATCH (LOW) - GigabitEthernet1: NetBox MTU=9000, Device MTU=1500
Step 4: Generate Reconciliation Report

Produce a severity-sorted discrepancy table:

NetBox Reconciliation Report - R1
Date: YYYY-MM-DD HH:MM UTC
NetBox Device: R1 | pyATS Device: R1 (devnetsandboxiosxec8k.cisco.com)

CRITICAL:
  [C-001] IP_DRIFT: GigabitEthernet1 - NetBox=10.1.1.1/30, Device=10.1.1.5/30
  [C-002] IP_DRIFT: Loopback0 - NetBox=1.1.1.1/32, Device=2.2.2.2/32

HIGH:
  [H-001] UNDOCUMENTED_LINK: Gi2 -> SW1:Gi0/1 (CDP) - no cable in NetBox
  [H-002] MISSING_INTERFACE: GigabitEthernet4 in NetBox but not on device

MEDIUM:
  [M-001] VLAN_MISMATCH: Gi3 - NetBox VLAN=10, Device VLAN=20
  [M-002] STATUS_MISMATCH: Gi5 - NetBox=enabled, Device=admin-down

LOW:
  [L-001] MTU_MISMATCH: Gi1 - NetBox MTU=9000, Device MTU=1500

Summary: 2 Critical | 2 High | 2 Medium | 1 Low
Overall: CRITICAL - immediate attention required
Step 5: Ticket Critical Discrepancies

For each CRITICAL discrepancy, open a ServiceNow incident:

bash
python3 $MCP_CALL "python3 -u $SERVICENOW_MCP_SCRIPT" create_incident '{"short_description":"NetBox Drift: IP_DRIFT on R1 GigabitEthernet1","description":"NetBox reconciliation detected IP address drift on R1 GigabitEthernet1.\n\nNetBox intent: 10.1.1.1/30\nDevice reality: 10.1.1.5/30\n\nThis is a CRITICAL discrepancy. Either the device configuration is incorrect and needs remediation, or NetBox needs to be updated to reflect the current state.\n\nDiscovery method: NetClaw automated reconciliation\nDate: YYYY-MM-DD HH:MM UTC","urgency":"2","impact":"2","category":"Network"}'

For HIGH discrepancies, create incidents at lower urgency:

bash
python3 $MCP_CALL "python3 -u $SERVICENOW_MCP_SCRIPT" create_incident '{"short_description":"NetBox Drift: UNDOCUMENTED_LINK R1:Gi2 -> SW1:Gi0/1","description":"NetBox reconciliation found a physical link (via CDP) between R1:GigabitEthernet2 and SW1:GigabitEthernet0/1 that has no cable record in NetBox.\n\nAction required: Add cable record to NetBox or investigate if this link is authorized.\n\nDiscovery method: NetClaw automated reconciliation","urgency":"3","impact":"3","category":"Network"}'
Step 6: Generate Markmap Drift Summary

Create a visual mind map of all discrepancies for human review:

bash
python3 $MCP_CALL "node $MARKMAP_MCP_SCRIPT" markmap_generate '{"markdown_content":"# NetBox Reconciliation - R1\n## CRITICAL\n### IP_DRIFT\n- Gi1: NetBox=10.1.1.1/30 vs Device=10.1.1.5/30\n- Lo0: NetBox=1.1.1.1/32 vs Device=2.2.2.2/32\n## HIGH\n### UNDOCUMENTED_LINK\n- Gi2 -> SW1:Gi0/1 (no cable in NetBox)\n### MISSING_INTERFACE\n- Gi4 (in NetBox, not on device)\n## MEDIUM\n### VLAN_MISMATCH\n- Gi3: NetBox VLAN=10 vs Device VLAN=20\n### STATUS_MISMATCH\n- Gi5: NetBox=enabled vs Device=admin-down\n## LOW\n### MTU_MISMATCH\n- Gi1: NetBox=9000 vs Device=1500"}'
Step 7: Record in GAIT
bash
python3 $MCP_CALL "python3 -u $GAIT_MCP_SCRIPT" gait_record_turn '{"user_text":"Reconcile NetBox source of truth against R1 live state","assistant_text":"NetBox reconciliation complete for R1.\n\nDiscrepancies found: 2 CRITICAL, 2 HIGH, 2 MEDIUM, 1 LOW\n\nCRITICAL:\n- IP_DRIFT: Gi1 (10.1.1.1/30 vs 10.1.1.5/30)\n- IP_DRIFT: Lo0 (1.1.1.1/32 vs 2.2.2.2/32)\n\nServiceNow incidents created for all CRITICAL and HIGH findings.\nMarkmap drift summary generated.\n\nOverall: CRITICAL - immediate human review required."}'

Display the audit trail:

bash
python3 $MCP_CALL "python3 -u $GAIT_MCP_SCRIPT" gait_show '{"commit":"HEAD"}'

Fleet-Wide Reconciliation

To reconcile all devices, first list the inventory:

bash
PYATS_TESTBED_PATH=$PYATS_TESTBED_PATH python3 $MCP_CALL "${PYATS_PYTHON:-python3} -u $PYATS_MCP_SCRIPT" pyats_list_devices '{}'

Then query NetBox for all active devices:

bash
python3 $MCP_CALL "python3 -u $NETBOX_MCP_SCRIPT" netbox_get_objects '{"object_type":"dcim.devices","filters":{"status":"active"},"brief":true}'

Run Steps 1-7 for each device that exists in both the pyATS testbed and NetBox. Produce a fleet summary:

Fleet Reconciliation Summary - YYYY-MM-DD
Devices Reconciled: 5/5

+---------+----------+------+--------+-----+----------+
| Device  | CRITICAL | HIGH | MEDIUM | LOW | Overall  |
+---------+----------+------+--------+-----+----------+
| R1      | 2        | 2    | 2      | 1   | CRITICAL |
| R2      | 0        | 1    | 0      | 0   | HIGH     |
| SW1     | 0        | 0    | 3      | 2   | MEDIUM   |
| SW2     | 0        | 0    | 0      | 1   | LOW      |
| FW1     | 0        | 0    | 0      | 0   | CLEAN    |
+---------+----------+------+--------+-----+----------+

Total Discrepancies: 2 CRITICAL | 3 HIGH | 5 MEDIUM | 4 LOW
ServiceNow Incidents Created: 5 (2 CRITICAL + 3 HIGH)
Overall Fleet Status: CRITICAL

Sort devices by severity (CRITICAL first) for triage prioritization.


NetBox Changelog Audit

After reconciliation, check NetBox changelogs to understand when the source of truth was last updated:

bash
python3 $MCP_CALL "python3 -u $NETBOX_MCP_SCRIPT" netbox_get_changelogs '{"filters":{"object_type":"dcim.interface","limit":20}}'

This helps determine whether discrepancies are due to recent device changes (device drifted) or stale NetBox data (NetBox was never updated).


Integration with Other Skills

SkillIntegration Point
pyats-topologyProvides CDP/LLDP neighbor data used for UNDOCUMENTED_LINK and CABLE_MISMATCH detection
pyats-health-checkRun health check first; reconciliation adds NetBox cross-reference layer
servicenow-change-workflowCRITICAL and HIGH discrepancies auto-open ServiceNow incidents
markmap-vizDrift summary mind map for visual human review
drawio-diagramColor-code topology links by reconciliation status (green=match, red=mismatch, yellow=undocumented)
GAITFull reconciliation session recorded in audit trail

When to Use

  • Scheduled: Weekly or monthly source-of-truth validation
  • Post-change: After every configuration change, verify NetBox still matches reality
  • Incident response: When investigating an outage, check if NetBox data is accurate for the affected devices
  • New device onboarding: Verify NetBox was populated correctly after adding a new device
  • Audit/compliance: Demonstrate that infrastructure documentation matches reality

Failure Behavior

  • If a tool call fails with an authentication or connection error, check that GAIT_MCP_SCRIPT, MARKMAP_MCP_SCRIPT, NETBOX_MCP_SCRIPT, PYATS_MCP_SCRIPT, PYATS_TESTBED_PATH, SERVICENOW_MCP_SCRIPT are set and valid before assuming a data or device problem.
  • On a tool error (timeout, unreachable host, malformed response), report the failure and its error message directly to the user rather than fabricating or guessing at results.
  • For a confirmed read-only call, check connectivity and retry once if appropriate. For any call that changes state or sends a message, a timeout does not prove the action failed: inspect current state or delivery status before retrying, preserve the required approval/change gates, and do not repeat an action whose outcome is unknown.

© automateyournetwork, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in workspace/skills/netbox-reconcile of automateyournetwork/netclaw.

Open the folder on GitHubat commit aa90e7d

Compare with similar skills

Netbox Reconcile next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Netbox Reconcile compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Netbox Reconcile this skillautomateyournetwork/netclaw676—~4.3kAutomated safety check: PassApache-2.0
Creating Financial ModelsChen-zexi/open-ptc-agent7293 repos~1.3kAutomated safety check: PassMIT
Stock APIzhangxiangliang/stock-api2k—~507Automated safety check: PassMIT
Tradingview MCPatilaahmettaner/tradingview-mcp5k—~1.3kAutomated safety check: PassMIT
Dr Manhattanguzus/dr-manhattan204—~2kAutomated safety check: PassApache-2.0
Agentic Trading DeskOft3r/agentic-trading-desk306—~5.1kAutomated safety check: PassMIT

Similar skills

  • Creating Financial Models

    Chen-zexi/open-ptc-agent

    This skill provides an advanced financial modeling suite with DCF analysis, sensitivity testing, Monte Carlo simulations, and scenario planning for investment decisions

    729 GitHub starsUsed in 3 repos~1.3k tokens
    Business, Finance & HRAuto-check passed
  • Stock API

    zhangxiangliang/stock-api

    Fetch real-time stock quotes, K-line (candlestick) history, and search symbols for China A-shares, Hong Kong, and US markets.

    2k GitHub stars~507 tokensUpdated today
    Business, Finance & HRAuto-check passed
  • Tradingview MCP

    atilaahmettaner/tradingview-mcp

    AI Trading Intelligence — live prices, 30+ technical indicators, backtesting (6 strategies), walk-forward overfitting detection, trade logs, equity curves, licensed news sentiment (Marketaux), and…

    5k GitHub stars~1.3k tokensUpdated yesterday
    Business, Finance & HRAuto-check passed
  • Dr Manhattan

    guzus/dr-manhattan

    Trade prediction markets (Polymarket, Kalshi, Opinion, Limitless, Predict.fun) using a unified CCXT-style API.

    204 GitHub stars~2k tokensUpdated 2 mo ago
    Business, Finance & HRAuto-check passed
  • Agentic Trading Desk

    Oft3r/agentic-trading-desk

    Personal trading desk for short-term technical analysis on stocks/ETFs via Robinhood MCP.

    306 GitHub stars~5.1k tokensUpdated 1 mo ago
    Business, Finance & HRAuto-check passed
  • Earnings Analysis

    Wind-Alice/AliceMarket

    Create professional equity research earnings update reports (8-12 pages, 3,000-5,000 words) analyzing quarterly results for companies already under coverage.

    134 GitHub starsUsed in 3 repos~2.2k tokens
    Business, Finance & HRAuto-check passed

More from automateyournetwork/netclaw

All 120 skills in this repo
  • EVE-NG Lab Topology Design

    automateyournetwork/netclaw

    Entry point for designing EVE-NG network labs: classifies the request, gathers missing requirements, proposes options and validates the resulting topology.

    676 GitHub stars~612 tokensUpdated yesterday
    Auto-check passed
  • ACI Policy Change Deployment

    automateyournetwork/netclaw

    Deploys Cisco ACI policy changes only behind an approved ServiceNow Change Request, capturing pre and post-change fault baselines and rolling back automatically on a fault delta.

    676 GitHub stars~4.2k tokensUpdated yesterday
    Auto-check passed
  • Cisco ACI Fabric Health Audit

    automateyournetwork/netclaw

    Runs a phased health audit of a Cisco ACI fabric through MCP tools: node status, links, tenant and policy review, faults and endpoint learning.

    676 GitHub stars~2.9k tokensUpdated yesterday
    Auto-check passed
  • Anta Validation

    automateyournetwork/netclaw

    Validate Arista EOS network state against ANTA's pre-built 208-test catalogue, with structured pass/fail verdicts.

    676 GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed
  • Arista Cvp

    automateyournetwork/netclaw

    Arista CloudVision Portal (CVP) automation via REST API — device inventory, events, connectivity monitoring, tag management (4 tools).

    676 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check: notes
  • AWS Cloud Monitoring

    automateyournetwork/netclaw

    AWS CloudWatch monitoring — metrics, alarms, log queries, VPC flow log analysis, network performance.

    676 GitHub stars~1k tokensUpdated yesterday
    Auto-check passed

Questions about Netbox Reconcile

What does Netbox Reconcile do?

Reconcile NetBox source of truth against live network state - detect IP drift, missing interfaces, undocumented links, cable mismatches, VLAN mismatches, and ticket discrepancies in ServiceNow. Netbox Reconcile is an agent skill from automateyournetwork/netclaw. Reconcile NetBox source of truth against live network state - detect IP drift, missing interfaces, undocumented links, cable mismatches, VLAN mismatches, and ticket discrepancies in ServiceNow.

When should I use Netbox Reconcile?

Netbox Reconcile fits situations like: validating NetBox accuracy; checking for config drift; auditing network documentation; reconciling source of truth after changes.

How do I install Netbox Reconcile in Claude Code?

Run `npx skills add automateyournetwork/netclaw --skill netbox-reconcile -a claude-code`. Or copy the skill folder (workspace/skills/netbox-reconcile in automateyournetwork/netclaw) into .claude/skills/netbox-reconcile in your project. Claude Code loads it when a task matches its description.

How do I install Netbox Reconcile in Codex?

Run `npx skills add automateyournetwork/netclaw --skill netbox-reconcile -a codex`. Or copy the skill folder (workspace/skills/netbox-reconcile in automateyournetwork/netclaw) into .agents/skills/netbox-reconcile in your project. Codex loads it when a task matches its description.

Can I use Netbox Reconcile in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add automateyournetwork/netclaw --skill netbox-reconcile -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/netbox-reconcile, .gemini/skills/netbox-reconcile, .github/skills/netbox-reconcile and .opencode/skills/netbox-reconcile in your project.

What does Netbox Reconcile need to run?

Going by SKILL.md and its folder, Netbox Reconcile needs the command-line tools its instructions call (python3). Our summary lists: Python 3.

Does Netbox Reconcile access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Netbox Reconcile safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Netbox Reconcile use?

Netbox Reconcile is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Netbox Reconcile use?

About 4.3k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Netbox Reconcile?

Skills that share tags, products or a category with Netbox Reconcile: Creating Financial Models (Chen-zexi/open-ptc-agent, 729 stars), Stock API (zhangxiangliang/stock-api, 2k stars), Tradingview MCP (atilaahmettaner/tradingview-mcp, 5k stars) and Dr Manhattan (guzus/dr-manhattan, 204 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Netbox Reconcile?

automateyournetwork (a GitHub user) maintains it in automateyournetwork/netclaw, which has 676 GitHub stars. The repository holds 120 skills in this directory. The repository was last updated on October 9, 2026.

Source: automateyournetwork/netclaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.