SkillVaultskills Browse all 1,000+ skills

Reliability · Version 1.3.0 · Reviewed 2026-08-02

Observability Readiness Reviewer

Reduce production risk in change observability review and diagnostic gap analysis with evidence, explicit trade-offs, and a verification plan.

4 method steps 6 documented failure modes 5 diagnostic checks 7 quality gates

Assesses whether a change can be detected, diagnosed, and attributed after release without adding unbounded telemetry. It grounds the decision in changed failure modes, traces, metrics, logs, alerts, correlation fields, dashboards, and operator actions and explicitly prevents instrumentation proving requests happened but not whether the changed decision or side effect was correct.

₹199 one-time

Get this skill archive

Install in your AI coding tool

SkillVault packages this skill in the open Agent Skills format for five leading coding tools.

What this skill helps you do

  • Change observability review
  • Diagnostic gap analysis
  • Time-to-detection readiness

How Observability Readiness Reviewer works

You provide

Current signals, alert rules, and recent incidents

It inspects

Symptom-versus-cause coverage for change observability review

It decides

A diagnostic gap analysis design with bounded label cardinality

You verify

Each page has a documented action and a real trigger

What it checks first

Observability Readiness Reviewer assesses whether a change can be detected, diagnosed, and attributed after release without adding unbounded telemetry. It grounds the decision in changed failure modes, traces, metrics, logs, alerts, correlation fields, dashboards, and operator actions and explicitly prevents instrumentation proving requests happened but not whether the changed decision or side effect was correct. Use it when the work involves Change observability review, Diagnostic gap analysis, Time-to-detection readiness.

  1. Whether alerts are symptom-based (user impact) or cause-based (component state); cause-based alerts generate the most noise.
  2. Cardinality of labels, since unbounded dimensions like user ID or URL destroy a metrics backend.
  3. Whether traces propagate context across async boundaries, because a broken chain hides the slow hop.
  4. The ratio of actionable to total alerts, which predicts whether alerts will be ignored.
  5. Whether the SLO reflects a user journey or an internal component that users never observe.

Failure modes it recognizes

  • Alert fatigue where a noisy alert trains responders to ignore the channel that later carries a real outage.
  • Metric cardinality explosion from a label containing a request ID, causing ingestion cost and query failure.
  • Sampled traces dropping exactly the slow requests that needed investigation.
  • Logs without correlation IDs, making a multi-service request impossible to reconstruct.
  • A dashboard averaging latency, which hides the tail where user pain actually lives.
  • An alert on a threshold that only fires after the error budget is already exhausted.

Answers it will reject

  • Alerting on CPU utilization, which is a resource state rather than user impact and fires without consequence.
  • Adding a dashboard instead of an alert, which requires a human to be watching to be useful.
  • Logging at debug level in production to "have the data", which costs more than the incidents it solves.
  • Reporting availability as a mean, which allows a total regional outage to disappear into the average.

Decision rules it applies

  • Alert on symptoms that users feel; use cause metrics for diagnosis, not for paging.
  • Every page must have a documented action; if the action is "look at it", it is not a page.
  • Measure latency with percentiles and always include p99, since averages hide the tail.
  • Keep label cardinality bounded and known; treat an unbounded dimension as a defect.

Evidence it asks for

  • Define an SLI as a ratio of good events to valid events, with both terms explicitly specified.
  • Use tail-based sampling so slow and failed traces are retained preferentially.
  • Propagate a correlation ID from edge to database and include it in every log line.

The method inside

  1. Map the artifact, actors, boundaries, and invariants relevant to change observability review.
  2. Trace concrete failure or abuse paths for diagnostic gap analysis; do not report checklist items without a mechanism.
  3. Prioritize time-to-detection readiness findings by impact, likelihood, confidence, and cost of correction.
  4. Recommend the smallest defensible change, then define how an independent reviewer can verify it.

Deliverables

  • Change observability review assessment
  • Diagnostic gap analysis decision and action plan
  • Time-to-detection readiness verification checklist

Evidence requirements

  • User-visible symptoms and SLO impact
  • Timeline, telemetry, deploys, and dependency state
  • Current mitigations and operational constraints

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

Apply the observability readiness reviewer to our current change observability review work. We need a concrete decision, bounded changes, and evidence that the result is correct.

Expected output

Start with changed failure modes, traces, metrics, logs, alerts, correlation fields, dashboards, and operator actions. The highest-risk failure is instrumentation proving requests happened but not whether the changed decision or side effect was correct. Require one symptom signal, one causal discriminator, and one owner action for each material failure mode. Verify the result by injecting the failure in a representative environment and following only the proposed telemetry to diagnosis.

Boundaries and compatibility

Ideal for

  • Change observability review: produce a decision or artifact grounded in supplied evidence.
  • Diagnostic gap analysis: produce a decision or artifact grounded in supplied evidence.
  • Time-to-detection readiness: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Replacing incident command authority
  • Calling a trigger the root cause without a causal chain

Agent compatibility

  • GitHub Copilot Agent Skills
  • Cursor Agent Skills
  • Claude Code Skills
  • OpenAI Codex Skills
  • JetBrains Junie Skills

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.