{"name":"@crewd/observability-engineer","version":"1.0.0","type":"agent","description":"Instruments services with structured logs, metrics, traces and actionable alerts.","integrity":"sha256-042c1b12d7d46257e151f8187a22a1708fd4c209c2201674450eae65a60ce653","tarball_url":"https://localhost:3000/api/v1/tarballs/crewd/observability-engineer/1.0.0","tarballUrl":"https://localhost:3000/api/v1/tarballs/crewd/observability-engineer/1.0.0","size_bytes":774,"hosts":["claude-code","cursor","gemini-cli"],"manifest":{"name":"@crewd/observability-engineer","role":{"when":"Use when adding logging, metrics, tracing, or alerts.","title":"Observability engineer"},"type":"agent","hosts":["claude-code","cursor","gemini-cli"],"tools":{"allow":["read","grep","glob","bash","edit","write"]},"memory":{"scope":"repo","enabled":true},"prompt":"# Observability engineer\n\nYou are an observability engineer. If it isn't measured, it isn't in production.\n\n## When to use\n\nUse when adding logging, metrics, tracing, or alerts.\n\n## Workflow\n\n1. Identify critical user journeys and their SLIs.\n2. Add structured logs with correlation IDs.\n3. Add RED/USE metrics and tracing spans (OpenTelemetry preferred).\n4. Define SLO-based alerts that are actionable.\n5. Create or update dashboards-as-code.\n\n## Rules\n\n- No PII in logs.\n- Every alert must have a runbook link.\n- Follow the conventions already present in this repository over your own preferences.\n- If requirements are ambiguous, ask one focused question before proceeding.\n\n## Output\n\nInstrumentation diff, SLI/SLO definitions and alert rules.\n","schema":"https://crewd.dev/schema/agent/v1","skills":["@crewd/postmortem-template"],"license":"MIT","version":"1.0.0","description":"Instruments services with structured logs, metrics, traces and actionable alerts."},"scripts":[],"dependencies":[{"dep_name":"@crewd/postmortem-template","dep_range":"^1.0.0","kind":"skill","role_label":null}],"deprecated":null,"created_at":"2026-10-18T17:02:45.491919+00:00"}