beacon

Solid

Engineering observability and reliability: SLO/SLI design, distributed tracing, alerting, dashboards, capacity planning, toil automation, reliability review. Use for instrumentation or SLO definition.

AI & Automation 72 stars 14 forks Updated today MIT

Install

View on GitHub

Quality Score: 85/100

Stars 20%

Recency 20%

100

Frontmatter 20%

Documentation 15%

100

Issue Health 10%

License 10%

100

Description 5%

100

Skill Content

<!-- CAPABILITIES_SUMMARY: - slo_sli_design: SLO/SLI definition, error budget calculation, multi-window multi-burn-rate alerting (14.4×/6×/3×/1×), error budget consumption policy gates - distributed_tracing: OpenTelemetry instrumentation (semconv 1.28+ stable, tracking 1.40+), span naming, tail-based sampling in Collector, GenAI semantic conventions incl. agent spans (experimental — dual-emission opt-in) - telemetry_pipeline: OpAMP fleet management, OTel Collector orchestration, Declarative Configuration, OTel Profiles (4th pillar, Alpha) strategy assessment - alerting_strategy: Alert hierarchy design, runbooks, escalation policies, alert fatigue reduction, burn rate thresholds - dashboard_design: RED/USE methods, Grafana dashboard-as-code, audience-specific views - capacity_planning: Load modeling, autoscaling strategies, resource prediction - toil_automation: Toil identification, automation scoring, self-healing design - reliability_review: Production readiness checklists, FMEA, game day planning - incident_learning: Postmortem metrics, reliability trends, SLO violation analysis - logging_design: Structured JSON log schema, correlation IDs (trace_id / span_id / request_id), log level policy (DEBUG/INFO/WARN/ERROR), source-side sampling, PII scrub patterns, OpenTelemetry Logs signal integration - golden_signals: Golden Signals (latency / traffic / errors / saturation), RED method for request-driven services (Tom Wilkie), USE method for resource-driven components (Brendan Gre...

Details

Author: simota
Repository: simota/agent-skills
Created: 7 months ago
Last Updated: today
Language: HTML
License: MIT

Integrates with

Anthropic · AI Grafana · Monitoring

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

observability-designer

SLO/SLI design, alert optimization, and dashboard generation for production services. TRIGGER when: user asks to define SLOs, design alerts, create dashboards, reduce alert fatigue, set error budgets, or improve observability; user runs /observability or /slo. DO NOT TRIGGER when: debugging a specific incident (use debugging tools), writing application code, configuring CI/CD pipelines.

0 Updated 2 weeks ago

DROOdotFOO

Web & Frontend Listed

observability-designer

Designs SLIs/SLOs, structured logs, traces, and alert quality for a feature or service. Use when shipping new paths or fixing noisy/missing alerts. Emits OBS_PLAN. Never recommends alert spam or metrics without a user/journey signal.

0 Updated 1 months ago

willianbs

AI & Automation Listed

sota-observability

State-of-the-art observability and reliability engineering (2026). Use when instrumenting code (structured logging, metrics, distributed tracing with OpenTelemetry, SLOs, alerting, health endpoints) or auditing an existing codebase's observability posture (can on-call answer "why is this request slow?" and "what broke at 3am?"). Not for security detections, SIEM, or threat hunting — use sota-detection-engineering. Triggers: logging, metrics, tracing, monitoring, alerting, SLO, SLI, error budget, OpenTelemetry, OTel, Prometheus, Grafana, debugging production, incident, on-call, telemetry, instrumentation, health check, runbook, Sentry, crash reporting, profiling.

15 Updated today

martinholovsky