Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →automateyournetwork/auvik-network-alerts
Surface and triage Auvik network alerts by severity, status, dismissed state, or time window across MSP tenants.
Passed 16 of 19 test cases with the skill, and 6 of 19 without it.
and 12 more in the full report
12 fixed7 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
I need to check recent alerts for host 192.168.10.45. Should I look up its internal Auvik entity ID first or pass the IP directly to the query tool?
| Checked | Without skill | With skill |
|---|---|---|
| Instructs to pass the hostname or IP address directly to the entity parameter | Missed | Passed |
The instructions your model reads when the skill loads.
Surface, filter, and triage alerts generated by the Auvik network monitoring platform. Scope by severity, status, entity (device), tenant, or time window. All operations are read-only — alert dismissal must be performed in the Auvik Dashboard.
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_list_alerts | List alert history; filter by severity, status, dismissed state, entity, time window, or alert definition; resolves device name/IP to Auvik entity ID |
Tenants = MSP clients. Each managed customer is a separate Auvik tenant. Provide tenants=<name-or-domain-prefix> to scope alerts to a single client. Omit to query across all visible tenants.
Identifier resolution. The entity parameter accepts a device name, hostname, or IP address — the server resolves it to the Auvik internal entity ID. If the name matches multiple devices, the tool returns ResolutionCandidate[] so you can narrow the query.
Severity levels. Auvik alerts use five severities in descending urgency: emergency, critical, warning, info, unknown. Filter with the severity parameter.
Status values. An alert may be created (open/active), resolved, paused, or unpaused. Use status=created to see only open alerts.
Dismissed vs. active. Dismissed alerts are hidden in the Dashboard but remain in history. Use dismissed=false to exclude them (recommended for triage); dismissed=true to review what was dismissed and when.
Time windows. detected_time_after and detected_time_before accept ISO-8601 datetime strings (e.g., 2026-06-01T00:00:00Z). Use both to bound a review window for incident post-mortems.
Cursor pagination. auvik_list_alerts auto-aggregates all pages up to AUVIK_MAX_PAGES. Use fetch_all=false for incremental loading on large alert queues.
gait_branch with name like auvik-alert-triage-2026-06-21auvik_list_alerts with status=created, dismissed=falseseverity=critical or severity=emergency for priority triagetest cases passed, vs 6 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.