ring:dev-sre

Validate observability implementation for Go, TypeScript, and Python services.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/LucasMalessa/TheRing --skill ring-dev-sre-lucasmalessa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ring:dev-sre
Source: https://github.com/LucasMalessa/TheRing/tree/main/dev-team/skills/dev-sre
Command: npx skills add https://github.com/LucasMalessa/TheRing --skill ring-dev-sre-lucasmalessa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gate 2 validates that developers have implemented observability correctly; it does not implement observability code, only validates it.

Core Features & Use Cases

  • Validates structured logging with trace correlation
  • Verifies OpenTelemetry instrumentation coverage and context propagation
  • Enforces minimum instrumentation thresholds (90%+)
  • Provides remediation guidance and escalation paths when issues are found

Quick Start

Provide unit_id, language, service_type, implementation_agent, and implementation_files to start the SRE validation and receive a detailed report

Frequently Asked Questions about ring:dev-sre

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate observability instrumentation for a service unit?

Validate observability instrumentation by providing the unit_id, language, service_type, implementation_agent, and implementation_files to trigger an SRE validation report covering structured logging and OpenTelemetry context propagation.

What is SRE validation for Dev Cycle Gate 2?

SRE validation for Gate 2 verifies that developers correctly implemented observability code, enforcing a 90% or higher instrumentation threshold without writing any observability code itself.

Does observability validation support Python, TypeScript, and Go services?

Observability validation supports Python, TypeScript, and Go services across API, worker, batch, CLI, and library service types, verifying structured logging with trace correlation and OpenTelemetry instrumentation coverage.

How do I get remediation guidance when OpenTelemetry instrumentation coverage fails validation?

Receive remediation guidance and escalation paths by running the observability validation, which reports specific issues found in structured logging, trace correlation, or OpenTelemetry context propagation within your implementation files.

What input fields are required to verify structured logging and trace correlation?

Verifying structured logging and trace correlation requires the unit_id, language, service_type, implementation_agent, and implementation_files fields to execute the SRE validation process and generate a detailed report.