agentleFS
Sign inStart free
poorvith-mppoorvith-mp/skills-developer/skills/reliability/SKILL.md

reliability

Skill0 starsChanged 3 months agoMITView on GitHub

Set SLOs and error budgets, instrument with OpenTelemetry, and build the dashboards that prove them. Use when designing SLIs/SLOs, circuit breakers, or disaster recovery.

8 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    NEVER alert on raw metric thresholds without error budget context.

    line 38
  2. Distinctive:

    NEVER log sensitive PII, credentials, or full request bodies in production.

    line 39
  3. Distinctive:

    NEVER create dashboards without a clear debugging narrative (what question does each panel answer?).

    line 40

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Reliability

Implements comprehensive observability stacks using OpenTelemetry, designs SLO-driven dashboards, and architects actionable alerting systems.

Phased Workflow

Phase 1: Instrumentation & Telemetry Design

  1. Instrument services with OpenTelemetry SDK: distributed traces (spans with context propagation), metrics (counters, histograms, gauges), and structured logs.
  2. Define trace sampling strategy (head-based vs tail-based) balancing cost and visibility.
  3. Standardize log schema: timestamp, service, trace_id, span_id, level, message, structured fields.

Phase 2: SLO/SLI Framework

  1. Define Service Level Indicators (SLIs): availability (success rate), latency (P50/P95/P99), throughput, error rate.
  2. Set Service Level Objectives (SLOs): target thresholds with error budgets (e.g., 99.9% availability = 43.8 min/month budget).
  3. Build burn-rate alerting: alert when error budget consumption rate exceeds sustainable pace.

Phase 3: Dashboard & Alert Architecture

  1. Design golden signal dashboards: Rate, Errors, Duration (RED) per service.
  2. Configure multi-window, multi-burn-rate alerts to minimize false positives.
  3. Implement alert routing with escalation tiers and on-call rotation integration.

Verification & Quality Checklist

  • All services emit traces with proper context propagation across async boundaries.
  • SLOs documented with clear ownership and review cadence (monthly).
  • Alert noise ratio below 10% false positive rate.
  • Dashboards load in under 3 seconds and cover all golden signals.

Anti-Patterns & Constraints

  • NEVER alert on raw metric thresholds without error budget context.
  • NEVER log sensitive PII, credentials, or full request bodies in production.
  • NEVER create dashboards without a clear debugging narrative (what question does each panel answer?).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free