slo-implementation

What This Skill Does

The slo-implementation skill acts as a comprehensive SRE (Site Reliability Engineering) co-pilot within the OpenClaw ecosystem. It provides a standardized framework for engineering teams to define, track, and enforce service reliability. By automating the transition from abstract reliability goals to concrete technical implementation, this skill bridges the gap between business objectives and infrastructure reality. It empowers users to define Service Level Indicators (SLIs), establish Service Level Objectives (SLOs), and mathematically derive error budgets, ensuring that innovation velocity remains balanced with service stability. The skill facilitates the creation of complex Prometheus-compatible queries for availability, latency, and durability, providing a structured approach to managing production health.

Installation

To integrate this skill into your environment, use the OpenClaw command-line interface or the integrated package manager. Run the following command:

clawhub install openclaw/skills/skills/anton-abyzov/sw-slo-implementation

Ensure that you have appropriate permissions to apply configuration files if you intend to push these definitions to your monitoring stack directly.

Use Cases

• Service Reliability Audits: Use this skill to evaluate your existing infrastructure and determine if your current monitoring coverage is sufficient to meet business SLAs.
• Error Budget Management: Automatically calculate how much room you have for error within a rolling 28-day window before triggering a feature freeze.
• Alerting Strategy: Transition from reactive, symptom-based alerting to proactive, budget-based alerting by defining thresholds that account for the user experience.
• Cross-Team Communication: Standardize terminology across product and engineering teams using the provided SLI/SLO/SLA hierarchy for improved alignment.

Example Prompts

1. "Analyze my current API traffic and help me construct a 99.9% availability SLI using this Prometheus expression."
2. "Generate a YAML error budget policy that triggers a slack alert when we have consumed 80% of our monthly error budget for the checkout service."
3. "Calculate the monthly downtime allowed for a 99.99% latency target and explain how this impacts our deployment strategy for the next quarter."

Tips & Limitations

• Start Simple: Don't try to track too many SLOs initially. Start with high-impact services (e.g., login, checkout) before expanding to background workers.
• Context Matters: Remember that an SLI is a measurement, not a goal. Your SLO should reflect the user experience, not just the technical feasibility.
• Query Complexity: While this skill provides excellent templates, always validate your PromQL expressions against your actual metrics data to ensure labels and metric names match your specific instrumentation.
• Rolling Windows: The standard 28-day window is recommended for most web services, but high-velocity environments may require shorter intervals for tighter feedback loops.