Claude Skill

observability-agent

Query metrics, logs, and traces (Prometheus, Grafana, Loki, Sentry, OpenTelemetry) to diagnose incidents. Use during outages or performance investigations.

LLM Mart · 0 points · 0 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download navinspire-ia-navin-navin_skills_observability-agent-e9c73a3.zip · 0 KB

navinspire-ia/navin 31 4 forks AGPL-3.0 Updated 4d ago

Part of navinspire-ia/navin — 182 skills

Install

skills CLI npx skills add https://github.com/Navinspire-ia/navin/tree/main/navin/skills/observability-agent

Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install navinspire-ia-navin@llmmart

Git git clone https://github.com/Navinspire-ia/navin.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole navinspire-ia/navin collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Observability Agent

Overview

Follow symptoms → signals → cause. Prefer existing dashboards and log queries over random restarts.

Workflow

Define the symptom (error rate, latency, user report) and time window.
Check golden signals: latency, traffic, errors, saturation.
Pull logs/traces for the failing dependency.
Correlate deploys / config changes in the window.
Propose mitigation + durable fix; document with timestamps.

Rules

Redact PII/secrets from log excerpts in chat.
Do not restart prod services without approval.
If tooling APIs are unavailable, guide the user through UI queries.

Files (navin)

SKILL.md 894 B

---
name: observability-agent
description: Query metrics, logs, and traces (Prometheus, Grafana, Loki, Sentry, OpenTelemetry) to diagnose incidents. Use during outages or performance investigations.
metadata: {"navin":{"emoji":"📈","category":"devops"}}
---

# Observability Agent

## Overview

Follow symptoms → signals → cause. Prefer existing dashboards and log queries over random restarts.

## Workflow

1. Define the symptom (error rate, latency, user report) and time window.
2. Check golden signals: latency, traffic, errors, saturation.
3. Pull logs/traces for the failing dependency.
4. Correlate deploys / config changes in the window.
5. Propose mitigation + durable fix; document with timestamps.

## Rules

- Redact PII/secrets from log excerpts in chat.
- Do not restart prod services without approval.
- If tooling APIs are unavailable, guide the user through UI queries.