investigate

Name: investigate
Availability: InStock
Author: vmkteam

Correlate Sentry, Prometheus, Loki, Kibana, and Nomad data to investigate production incidents.

6|Updated Apr 5, 2026

Search Tags:#observability #investigate #prometheus #sentry #root-cause #loki #incident

Ready to run

npx skills add https://github.com/vmkteam/claude-plugins --skill investigate-vmkteam

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/vmkteam/claude-plugins/tree/main/plugins/developer/skills/investigate
Command: npx skills add https://github.com/vmkteam/claude-plugins --skill investigate-vmkteam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Investigate incidents by coordinating data from Sentry, Prometheus, Loki, Kibana, and Nomad to identify root causes across sources.

Core Features & Use Cases

Cross-source diagnostics: Correlate signals from monitoring, logging, and tracing to surface likely root causes.
Symptom-driven workflows: Start from user-reported symptoms and work toward actionable remediation plans with HITL when appropriate.
Incident workflow alignment: Align with production incident practices, including health checks, evidence gathering, and post-mortem readiness.

Quick Start

Describe the incident and time window, then trigger the cross-source investigation with the /investigate command to begin a full analysis.

Frequently Asked Questions about investigate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I investigate a production incident across multiple observability sources?▼

Incident investigation correlates signals from Sentry, Prometheus, Loki, Kibana, and Nomad to identify root causes by cross-referencing metrics, logs, and traces within a unified workflow.

Can I query Prometheus and Loki logs together to find an incident root cause?▼

Yes, cross-source diagnostics query Prometheus metrics and Loki logs simultaneously, correlating events across monitoring and logging platforms to surface the likely root cause of production symptoms.

How do I health-check services and gather evidence for a post-mortem report?▼

Incident workflow alignment performs service health checks, gathers correlated evidence across Sentry, Prometheus, and Kibana, and produces a formal incident report to ensure post-mortem readiness.

Does this investigation workflow require a known root cause to start?▼

No, symptom-driven workflows start from user-reported symptoms without a known root cause, applying cross-source analysis to work toward actionable remediation plans with human-in-the-loop validation.

What is the best way to correlate Sentry errors with Nomad deployment events?▼

Cross-source diagnostics correlate Sentry error tracking with Nomad deployment events, aligning production incident practices to connect application errors with infrastructure changes.

How do I begin a cross-source incident investigation when diagnosing an outage?▼

Describe the incident symptoms and time window, then trigger the cross-source investigation command to initiate a full analysis across Sentry, Prometheus, Loki, Kibana, and Nomad.