Auvik Network Alerts

Community

automateyournetwork

auvik-network-alerts

Surface and triage Auvik network alerts by severity, status, dismissed state, or time window across MSP tenants. Use when reviewing active alerts, investigating a specific device's alert history, filtering by severity (emergency/critical/warning), checking whether alerts are resolved or still open, or pulling alerts within a date range for incident review.

Overview

Publisher	automateyournetwork
Repository	`netclaw`
Skill name	`auvik-network-alerts`
Stars	680
Forks	189
Bundled files	Instructions only
License	Apache-2.0
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by automateyournetwork on GitHub. Read the source before you install it.

Installation

Install the Auvik Network Alerts AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/auvik-network-alerts
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/auvik-network-alerts

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/automateyournetwork/netclaw.git /tmp/netclaw
mkdir -p .claude/skills
cp -r /tmp/netclaw/workspace/skills/auvik-network-alerts .claude/skills/auvik-network-alerts

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Auvik Network Alerts in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Auvik Network Alerts on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Auvik Network Alerts is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Auvik Network Alerts

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.

MCP Server

Server: auvik-mcp (NetClaw MCP, Feature 036)
Command: python3 mcp-servers/auvik-mcp/auvik_mcp_server.py (stdio transport)
Auth: Basic auth via AUVIK_USERNAME + AUVIK_API_KEY
Read-only: GET operations only — alert state cannot be modified through this skill

Available Tools

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

Key Concepts

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.

Workflow

Morning Alert Triage

Start GAIT branch: gait_branch with name like auvik-alert-triage-2026-06-21
List open alerts: auvik_list_alerts with status=created, dismissed=false
Filter critical/emergency: add severity=critical or severity=emergency for priority triage
Scope to tenant: add tenants=<client> to focus on a specific managed client
Check device context: use auvik-inventory (auvik_list_devices) to get device details for the alerting entity
Record in GAIT: commit alert summary with count, top severities, and any affected devices

Investigate Alerts for a Specific Device

Resolve device name: auvik_list_alerts with entity=<device-name-or-IP> — the resolver identifies the entity
Review full history: omit status filter to see both open and resolved alerts
Check time pattern: pass detected_time_after=<start> + detected_time_before=<end> to narrow to a maintenance window or incident period
Cross-reference lifecycle: use auvik-lifecycle (auvik_list_device_lifecycle) to check if the device is EoL — recurring alerts on EoL hardware signal replacement need
Record in GAIT: commit alert history and investigation findings

Incident Post-Mortem Alert Pull

Define incident window: note start/end times in ISO-8601
Pull all alerts in window: auvik_list_alerts with detected_time_after=<start>, detected_time_before=<end>, tenants=<client>
Review dismissed: re-run with dismissed=true to see if any alerts were silenced during the incident
Correlate with change records: compare alert timestamps with servicenow-change-workflow change records
Record in GAIT: commit post-mortem findings with alert timeline

Integration with Other Skills

Skill	How They Work Together
`gait-session-tracking`	Mandatory — start a branch before querying, record every turn, close with `gait_log`
`auvik-inventory`	Get device details and entity context for alerting assets
`auvik-lifecycle`	Correlate recurring alerts with EoL/warranty status — recurring alerts on end-of-life hardware signal refresh urgency
`auvik-performance`	After identifying alerting devices, pull performance stats to understand the conditions that triggered alerts
`servicenow-change-workflow`	Correlate alert timestamps with approved change records to confirm or rule out change-induced incidents

Environment Variables

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 (default: `50`)

Important Rules

Read-only — this skill cannot dismiss, acknowledge, or modify alert state. Alert management must be done in the Auvik Dashboard.
Refer to devices by name or IP, not by Auvik entity IDs. Pass entity=<hostname-or-IP> and let the resolver do the lookup.
Scope to a tenant in MSP environments to avoid mixing alerts across clients.
Do not conflate dismissed with resolved — a dismissed alert may still indicate an unresolved condition; resolved means Auvik determined the condition cleared.
Record every session in GAIT — triage sessions, post-mortem pulls, and investigation findings all go to the audit trail.

Failure Behavior

If a tool call fails with an authentication or connection error, check that AUVIK_API_KEY, AUVIK_BASE_URL, AUVIK_USERNAME 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.

Frequently asked questions

What does the Auvik Network Alerts AI skill do?

Why use Auvik Network Alerts on TypingMind?

Because you install it once and use it with any model. Auvik Network Alerts is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Auvik Network Alerts in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/auvik-network-alerts. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Auvik Network Alerts?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Auvik Network Alerts?

As many as you like. As long as a model supports skills, you can use Auvik Network Alerts with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Auvik Network Alerts AI skill free?

Yes. It is published on GitHub by automateyournetwork under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Openclaw Ci Limits

openclaw

OrganizationPopular

Manage OpenClaw GitHub Actions and Blacksmith CI capacity, runner-registration budgets, fanout caps, main-push single-flight, shard sizing, hosted-runner offload, queue health, and safe…

Openclaw Debugging

Debug OpenClaw model, provider, tool-surface, code-mode, streaming, and live/Crabbox behavior by choosing the right logs, probes, and proof path before changing code, including fetching stored…

Openclaw Live Updater

openclaw

OrganizationPopular

Maintain the canonical live OpenClaw main checkout, macOS LaunchAgent-managed Gateway, local macOS app, exact-head main CI, and recurring full release validation. Use for fast-forward update…

Openclaw Pr Maintainer

openclaw

OrganizationPopular

Review, triage, repair, or land OpenClaw issues and pull requests with current-source evidence and the native maintainer workflow.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Auvik Network Alerts

MCP Server

Available Tools

Key Concepts

Workflow

Morning Alert Triage

Investigate Alerts for a Specific Device

Incident Post-Mortem Alert Pull

Integration with Other Skills

Environment Variables

Important Rules

Failure Behavior

Frequently asked questions

Related AI Skills

Set up your own AI workspace now