workspace/skills/auvik-performance/SKILL.md
Auvik time-series performance stats for devices, interfaces, services, and hardware components — plus SNMP poller history for custom OID values. Use when checking device CPU or memory utilization over time, reviewing interface throughput or packet loss, checking service (ping) latency, pulling component-level stats (fan temperature, PSU power), or querying custom SNMP poller values.
npx skillsauth add automateyournetwork/netclaw auvik-performanceInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Query time-series performance statistics from the Auvik monitoring platform: device CPU, memory, bandwidth, and availability; interface throughput and error rates; service (ping) latency; hardware component metrics; and custom SNMP poller values. All data is read-only and sourced from Auvik's collected telemetry.
auvik-mcp (NetClaw MCP, Feature 036)python3 mcp-servers/auvik-mcp/auvik_mcp_server.py (stdio transport)AUVIK_USERNAME + AUVIK_API_KEY| Tool | What It Does |
|------|--------------|
| auvik_get_device_statistics | Time-series device stats (CPU, memory, bandwidth, packet rates) or availability stats (uptime, outage); stat_id, from_time, interval required |
| auvik_get_interface_statistics | Time-series interface stats (bandwidth, utilization, packet loss, discards, multicast, unicast, broadcast); stat_id, from_time, interval required |
| auvik_get_service_statistics | Time-series service (ping) stats — pingTime (latency) or pingPacket (packet loss); stat_id, from_time, interval required |
| auvik_get_component_statistics | Time-series hardware component stats (temperature, power, utilization, capacity); component_type, stat_id, from_time, interval required |
| auvik_get_oid_statistics | Point-in-time current OID values from /v1/stat/oid/deviceMonitor; no time window — returns the most recent polled value |
| auvik_list_snmp_poller_settings | List configured SNMP poller definitions; tenants required; with_devices=true lists devices assigned to a poller |
| auvik_get_snmp_poller_history | Historical SNMP poller time-series; tenants and from_time required; value_type=int requires interval; value_type=string accepts compact |
Tenants = MSP clients. Performance tools accept an optional tenants parameter. Scope to a specific client to avoid cross-tenant data mixing.
Identifier resolution. device and parent_device parameters accept hostnames, IPs, or partial names — resolved automatically to Auvik IDs. The interface parameter on auvik_get_interface_statistics also resolves from name or parent device. Ambiguous matches return ResolutionCandidate[].
from_time and interval are required on all time-series tools. from_time accepts ISO-8601 datetimes or relative shorthand (e.g., -1h, -7d, -30d) which the server converts to ISO-8601. interval must be minute, hour, or day. thru_time is optional — defaults to now.
stat_id enums by tool. Each tool has a fixed set of valid stat_id values:
| Tool | Valid stat_id values |
|------|------------------------|
| auvik_get_device_statistics (standard) | bandwidth, cpuUtilization, memoryUtilization, storageUtilization, packetUnicast, packetMulticast, packetBroadcast |
| auvik_get_device_statistics (availability; set availability=true) | uptime, outage |
| auvik_get_interface_statistics | bandwidth, utilization, packetLoss, packetDiscard, packetMulticast, packetUnicast, packetBroadcast |
| auvik_get_service_statistics | pingTime, pingPacket |
| auvik_get_component_statistics | capacity, counters, idle, latency, power, queueLatency, rate, readiness, ready, speed, swap, swapRate, temperature, totalLatency, utilization |
component_type on auvik_get_component_statistics. Valid values: cpu, cpuCore, disk, fan, memory, powerSupply, systemBoard. Both component_type and stat_id are required.
SNMP poller flow. Custom SNMP polling is a two-step operation: (1) auvik_list_snmp_poller_settings to discover poller IDs and associated devices; (2) auvik_get_snmp_poller_history to pull time-series values for a specific poller. tenants is required on both calls. value_type=int returns numeric time-series (requires interval); value_type=string returns string-valued OID snapshots (use compact=true to reduce payload size).
auvik_get_oid_statistics vs. auvik_get_snmp_poller_history. auvik_get_oid_statistics returns the most recent polled value for any OID on a device — no time window, no interval. Use it for a quick "what is the current value?" check. Use auvik_get_snmp_poller_history for trend analysis over time.
Pagination. auvik_get_oid_statistics and auvik_list_snmp_poller_settings support cursor pagination. Time-series tools return data arrays directly. Use fetch_all=false + page_first for large poller inventories.
gait_branch with name like auvik-perf-check-<device>-2026-06-21auvik_get_device_statistics with stat_id=cpuUtilization, device=<hostname>, from_time=-24h, interval=hourstat_id=memoryUtilization, same device and windowstat_id=bandwidth to check overall traffic loadauvik_get_device_statistics with availability=true, stat_id=uptime, same device and window — confirm no outage periods during the review windowauvik-inventory (auvik_list_interfaces) with parent_device=<hostname> — enumerate interface namesauvik_get_interface_statistics with stat_id=bandwidth, parent_device=<hostname>, from_time=-7d, interval=hourstat_id=packetLoss — identify any interfaces with elevated lossstat_id=packetDiscard — input/output queue drops signal congestionauvik_list_snmp_poller_settings with tenants=<client> — discover available custom pollers and their IDspoller_id=<id>, with_devices=true — confirm which devices report to this pollerauvik_get_snmp_poller_history with tenants=<client>, value_type=int, snmp_poller_setting_id=<id>, from_time=-30d, interval=hourvalue_type=string, compact=trueauvik_get_oid_statistics with device=<hostname>, oid=<oid-string> for a point-in-time readingauvik_get_component_statistics with component_type=fan, stat_id=temperature, parent_device=<hostname>, from_time=-24h, interval=hourcomponent_type=powerSupply, stat_id=powercomponent_type=memory, stat_id=utilizationcomponent_type=disk, stat_id=capacity| Skill | How They Work Together |
|-------|------------------------|
| gait-session-tracking | Mandatory — start a branch before querying, record every turn, close with gait_log |
| auvik-inventory | Discover device and interface names to use as device and parent_device params here |
| auvik-network-alerts | Correlate performance anomalies with alerts that fired in the same time window |
| auvik-lifecycle | High CPU/memory on aging devices combined with EoL status accelerates refresh priority |
| Variable | Required | Description |
|----------|----------|-------------|
| AUVIK_USERNAME | Yes | Auvik user email (Basic-auth username) |
| AUVIK_API_KEY | Yes | Auvik API key (Basic-auth password) |
| AUVIK_BASE_URL | No | Regional cluster URL; defaults to https://auvikapi.us1.my.auvik.com — swap us1 for your region |
| AUVIK_VERIFY_SSL | No | Set false to skip TLS verification (not recommended) |
| AUVIK_TIMEOUT | No | HTTP timeout in seconds (default: 30) |
| AUVIK_MAX_PAGES | No | Pagination safety cap for poller settings (default: 50) |
stat_id, from_time, and interval are required on all time-series tools. Omitting any one returns a ValidationError.component_type is also required on auvik_get_component_statistics — specify the hardware subsystem (e.g., fan, memory) before choosing the stat_id.tenants is required on auvik_list_snmp_poller_settings and auvik_get_snmp_poller_history — the Auvik API enforces this for custom poller endpoints.auvik_get_oid_statistics returns point-in-time data only — it does not accept from_time or interval. Use auvik_get_snmp_poller_history for trend analysis.tools
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.
tools
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.
tools
Federate your NetClaw with other NetClaw operators over the BGP mesh — exchange capability inventories and ask your claw what a peer can do. (US1; remote invocation and chat land in later phases.)
tools
Track token consumption, enforce session budgets, and display cost for every NetClaw interaction.