Observability Designer

Generate SLI/SLO frameworks, optimize alerts, and create role-based dashboards for production systems.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/mattstyles333/openclaw-workspace --skill observability-designer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Observability Designer
Source: https://github.com/mattstyles333/openclaw-workspace/tree/main/skills/observability-designer
Command: npx skills add https://github.com/mattstyles333/openclaw-workspace --skill observability-designer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the creation and optimization of observability systems, reducing the manual effort required to define SLIs/SLOs, tune alerts, and build dashboards.

Core Features & Use Cases

  • SLO Framework Generation: Automatically create SLI/SLO definitions, error budgets, and burn rate alerts based on service characteristics.
  • Alert Optimization: Analyze existing alerts for noise, coverage gaps, and redundancy, providing actionable recommendations.
  • Dashboard Generation: Create role-based dashboards with golden signals and service-specific panels.
  • Use Case: A new microservice is launched. Use this Skill to instantly generate its SLO framework, essential alerts, and a Grafana dashboard, ensuring it's observable from day one.

Quick Start

Use the observability designer skill to generate an SLO framework for a critical API service.

Frequently Asked Questions about Observability Designer

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

FAQPage Schema
How do I generate an SLO framework with SLI definitions and error budgets for a new service?

To generate an SLO framework, you need to define SLIs, SLOs, and error budgets based on service characteristics. This Skill automates creating those definitions and corresponding burn rate alerts, ensuring your service is observable from day one.

What is the best way to optimize alert configurations and reduce noise in Prometheus?

Optimizing alert configurations requires analyzing existing alerts for noise, coverage gaps, and redundancy. This Skill evaluates your current alerting rules and provides actionable recommendations to tune them effectively.

Can I automatically create role-based dashboards with golden signals for my microservices?

Yes, you can create role-based dashboards featuring golden signals and service-specific panels. This Skill automates dashboard generation to provide tailored visibility for different operational roles.

Do I need to manually configure monitoring rules when launching a microservice?

You do not need to manually configure monitoring rules for a new microservice. This Skill instantly generates the essential alerts, SLO framework, and dashboard configurations required for production readiness.

When should I use an automated observability strategy instead of manual monitoring setup?

You should use an automated observability strategy when launching new microservices or scaling production systems. It reduces the manual effort required to define SLIs/SLOs, tune alerts, and build dashboards.

How does burn rate alerting work with generated SLI and SLO definitions?

Burn rate alerting works by tracking how quickly your error budget is consumed relative to your SLO targets. This Skill generates burn rate alerts automatically alongside your SLI and SLO definitions.