Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →automateyournetwork/auvik-inventory
Auvik device, network, interface, and component inventory across MSP tenants — including entity notes, audit logs, and billing usage.
Passed 14 of 17 test cases with the skill, and 5 of 17 without it.
and 10 more in the full report
12 fixed6 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
When running Auvik usage analysis for client accounting, what are the two supported values for the scope parameter in usage reports?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies client and device as the valid scope parameter values for usage reporting | Missed | Passed |
The instructions your model reads when the skill loads.
Discover and document everything Auvik manages: devices, networks, interfaces, hardware components, entity notes, audit history, and billing usage. Works across MSP multi-tenant environments — scope to a single client or sweep all visible tenants.
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_verify_credentials | Health-check the API connection; verify credentials before any session |
auvik_list_tenants | List all tenants (MSP clients) visible to the API key; source of truth for tenants values |
auvik_list_devices | List or inspect discovered devices at info, detail, or extended level; resolve by name, IP, or ID |
auvik_list_networks | List networks at info or detail level; filter by type, scan status, or associated devices |
auvik_list_interfaces | List network interfaces; filter by parent device name/IP, interface type, or operational status |
auvik_list_components | List hardware components (CPU, memory, disk, fan, PSU); filter by device or component status |
auvik_list_entity_notes | List notes attached to devices, networks, or interfaces; filter by entity name or type |
auvik_list_entity_audits | List audit log entries for managed entities; filter by user, category, status, or date |
auvik_get_usage | Billing/usage data for a date range; scope=client (all devices) or scope=device (single device) |
Tenants = MSP clients. Auvik is built for MSPs — each managed customer is a separate tenant. Most tools accept an optional tenants parameter (a tenant name or domain prefix). Omit it to query across all visible tenants; provide it to scope results to a single client.
Identifier resolution. Pass device names, hostnames, IP addresses, or partial names to device, network, interface, or parent_device parameters — the server resolves them to internal Auvik IDs. If a name matches multiple records, the tool returns ResolutionCandidate[] so you can narrow the query. If you already know the Auvik numeric ID (6+ digits), it is used directly.
Cursor pagination. List tools auto-aggregate all pages up to AUVIK_MAX_PAGES (default 50). The response includes truncated: true and a next_cursor when the cap is hit. Use fetch_all=false + page_first to page manually, or raise AUVIK_MAX_PAGES in .env for large inventories.
detail_level on devices. info returns basic fields; detail adds management status and discovery settings; extended adds richer hardware data but requires the device_type filter (Auvik API enforcement).
auvik_verify_credentials — confirm API key is validtest cases passed, vs 5 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.