observability-auditlisted

Audits an app's observability against spec/project/monitoring-observability/ and produces a severity-classified audit artifact plus an implementation plan for the gaps. The default `audit` operation dispatches the read-only observability-audit-scanner agent, then hard-fails on any missing-or-unwired mandatory pillar (metrics, structured logs, distributed traces, health + SLO + alert), the frontend and third-party floors, and the cardinality and PII-redaction guardrails; runtime-only behaviour is documented verify-at-runtime. The `plan` operation dispatches implementation-plan-author with the findings so a specialist (fullstack-developer) implements the instrumentation — there is no mechanical apply. Invoke to audit observability, check OTel instrumentation, or run an observability best-practices gate; also German. Don't use for Kubernetes probe wiring (deployment-bestpractices-reviewer), the PII/GDPR verdict (gdpr-data-protection-reviewer), or Dockerfile labels (dockerfile-audit). Supports resume.
nolte/claude-shared · ★ 0 · DevOps & Infrastructure · score 76

Install: claude install-skill nolte/claude-shared

# Observability Audit Audit a running application's observability against the portfolio contract, produce a single severity-classified audit artifact, and hand the gaps to a specialist as an implementation plan. The default `audit` operation reports and recommends; the `plan` operation turns the findings into specialist-mapped work packages. **There is no mechanical `apply`** — OTel instrumentation is real code work, so remediation is a plan a specialist implements, not an in-place rewrite. Implements `spec/project/monitoring-observability/` — the spec defines the four mandatory pillars, the frontend and third-party floors, the two mandatory guardrails, the vendor-neutral (OTel/OTLP) core, and the static-vs-runtime carve-out. This skill binds those rules to the on-disk procedure and owns policy, severity, the report, and the plan handover. ## German trigger phrases This skill also triggers on equivalent German-language requests, including: - "Observability auditieren" / "Observability-Best-Practices prüfen" - "OTel-Instrumentierung prüfen" / "Tracing/Logging/Metriken-Abdeckung prüfen" - "Beobachtbarkeit gegen die Spec prüfen" ## User-language policy Detect the user's language from their message and respond in it. The audit artifact uses English section headings (so downstream tooling and the plan author can parse it reliably); prose around the report is localised. ## Inputs - **Repo root**: default is the current working directory. - **Operation**: `audit` (default,