SkillVaultskills Browse all 1,000+ skills

Reliability · Version 1.3.0 · Reviewed 2026-08-02

Metric Contract Reference Generator

Reduce production risk in metric inventory generation and dimension contract documentation with evidence, explicit trade-offs, and a verification plan.

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

Generates a source-backed reference for metric names, types, dimensions, units, aggregation, ownership, and example queries. It grounds the decision in instrumentation source, metric schemas, exporter metadata, dashboards, queries, owners, and retention rules and explicitly prevents documenting display names while stored identifiers, dimension cardinality, or aggregation semantics differ.

₹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

  • Metric inventory generation
  • Dimension contract documentation
  • Telemetry query reference

How Metric Contract Reference Generator works

You provide

Impact window, telemetry, and dependency state

It inspects

Saturation and blast radius behind metric inventory generation

It decides

A dimension contract documentation plan that stabilizes before diagnosing

You verify

Detect, mitigate, and resolve times recorded separately

What it checks first

Metric Contract Reference Generator generates a source-backed reference for metric names, types, dimensions, units, aggregation, ownership, and example queries. It grounds the decision in instrumentation source, metric schemas, exporter metadata, dashboards, queries, owners, and retention rules and explicitly prevents documenting display names while stored identifiers, dimension cardinality, or aggregation semantics differ. Use it when the work involves Metric inventory generation, Dimension contract documentation, Telemetry query reference.

  1. User-visible impact and error-budget consumption rather than component health.
  2. Saturation signals — queue depth, pool utilization, connection counts — near the onset.
  3. Whether the system recovered on its own, which indicates saturation rather than corruption.
  4. The blast radius and what boundary should have contained it.

Failure modes it recognizes

  • Retry amplification turning a partial failure into a total outage.
  • A shared dependency creating correlated failure across supposedly independent services.
  • Slow resource exhaustion invisible until a hard limit is crossed.
  • A rollback blocked by an incompatible migration.

Answers it will reject

  • Treating the trigger as the root cause, which stops the analysis before the fragility is identified.
  • Adding a runbook step where a boundary would remove the failure mode.
  • Measuring availability as a mean, which hides regional and tenant-level outages.

Decision rules it applies

  • Stabilize user impact before completing diagnosis.
  • Bound every retry with a budget, jitter, and a circuit breaker.
  • Prefer removing a failure mode over detecting it faster.

Evidence it asks for

  • Record time-to-detect, time-to-mitigate, and time-to-resolve separately.
  • Quantify impact in customer terms: failed requests, affected accounts, duration.
  • Verify recovery with the same signal that detected the failure.

The method inside

  1. Extract decisions, facts, and unresolved questions needed for metric inventory generation.
  2. Organize dimension contract documentation around the reader's next decision or action rather than the source order.
  3. Draft telemetry query reference with source traceability and no invented behavior.
  4. Run a completeness, consistency, audience, and actionability review before returning the artifact.

Deliverables

  • Metric inventory generation assessment
  • Dimension contract documentation decision and action plan
  • Telemetry query reference 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 metric contract reference generator to our current metric inventory generation work. We need a concrete decision, bounded changes, and evidence that the result is correct.

Expected output

Start with instrumentation source, metric schemas, exporter metadata, dashboards, queries, owners, and retention rules. The highest-risk failure is documenting display names while stored identifiers, dimension cardinality, or aggregation semantics differ. Treat emitted schema and backend metadata as authoritative and label inferred ownership or meaning. Verify the result by resolving each reference entry against live metadata or instrumentation and executing representative queries.

Boundaries and compatibility

Ideal for

  • Metric inventory generation: produce a decision or artifact grounded in supplied evidence.
  • Dimension contract documentation: produce a decision or artifact grounded in supplied evidence.
  • Telemetry query reference: 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.