Ops Investigate Alert
Skill Verified ActiveInvestigate a monitoring alert end-to-end. Pulls metrics, logs, traces, and recent code changes to identify root cause. Works with any monitoring MCP.
To provide a structured and automated process for investigating monitoring alerts, helping on-call engineers quickly understand and resolve issues.
Features
- End-to-end alert investigation workflow
- Parses alert details from URLs or names
- Fetches and analyzes metrics, logs, and traces
- Checks recent code changes using GitHub CLI
- Provides a structured investigation summary
Use Cases
- When a monitoring alert fires and root cause analysis is needed
- As a starting point for on-call engineers investigating issues
- To determine if a noisy alert is actionable or a false positive
Non-Goals
- Performing destructive operations like creating deployments or modifying code
- Resolving alerts automatically without human review
- Acting as a general-purpose log or metric querying tool outside of alert investigation
Documentation
- info:READMEThe README file is extensive and describes the broader Spartan AI Toolkit, but the specific skill's purpose is detailed in its SKILL.md.
Installation
First, add the marketplace
/plugin marketplace add spartan-stratos/spartan-ai-toolkit/plugin install toolkit@spartan-marketplaceQuality Score
VerifiedSimilar Extensions
Azure Monitor Query Py
100Azure Monitor Query SDK for Python. Use for querying Log Analytics workspaces and Azure Monitor metrics. Triggers: "azure-monitor-query", "LogsQueryClient", "MetricsQueryClient", "Log Analytics", "Kusto queries", "Azure metrics".
Query Netdata Cloud
100Query Netdata Cloud via its REST API -- metrics, logs (systemd-journal / windows-events / otel-logs), topology graphs (topology:snmp), network flows (flows:netflow), alerts, dynamic configuration (DynCfg), and generic Functions on a node. Use when the user asks about querying Netdata Cloud, fetching metrics from the cloud, querying logs / topology / netflow / sflow / ipfix through Cloud, listing or modifying configurations via DynCfg, calling agent Functions through Cloud, listing spaces/rooms/nodes, or building a curl command against `app.netdata.cloud`. Pairs with the `query-netdata-agents` skill when direct-agent access is needed.
Observability Gap Hunt
98Inspects services, jobs, and code paths for missing or weak logs, metrics, traces, alerts, dashboards, or deployment-linked telemetry, then returns a tightly scoped backlog of observability gaps. Use when a user says `find observability gaps`, `audit telemetry coverage`, `what logs or metrics are missing`, `check alerting coverage`, or asks for a recurring telemetry review. Do NOT use for live incident response, root-cause analysis, generic performance tuning, or a broad code review.
Observability Designer
100Observability Designer (POWERFUL)
Status
100Show DAG state, agent progress, and branch status for an AgentHub session.
Ops Fires
100Production incidents dashboard. Reads ECS health, Sentry errors, CI failures. Offers to dispatch fix agents for active fires.