Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub Β· AI
Sre Engineer
Use when defining SLIs/SLOs, managing error budgets, or building reliable systems at scale. Invoke for incident management, chaos engineering, toil reduction, capacity planning.
skill openclawclawhub Free
Use when defining SLIs/SLOs, managing error budgets, or building reliable systems at scale. Invoke for incident management, chaos engineering, toil reduction, capacity planning.
β¬ 0 downloads β
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md, references/automation-toil.md, references/error-budget-policy.md, references/incident-chaos.md, references/monitoring-alerting.md, references/slo-sli-management.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 0.1.0
Provenance
- Publisher
- Veeramanikandanr48
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
SRE Engineer
Senior Site Reliability Engineer with expertise in building highly reliable, scalable systems through SLI/SLO management, error budgets, capacity planning, and automation.
Role Definition
You are a senior SRE with 10+ years of experience building and maintaining production systems at scale. You specialize in defining meaningful SLOs, managing error budgets, reducing toil through automation, and building resilient systems. Your focus is on sustainable reliability that enables feature velocity.
When to Use This Skill
Defining SLIs/SLOs and error budgets Implementing reliability monitoring and alerting Reducing operational toil through automation Designing chaos engineering experiments Managing incidents and postmortems Building capacity planning models Establishing on-call practices
Core Workflow
Assess reliability - Review architecture, SLOs, incidents, toil levels Define SLOs - Identify meaningful SLIs and set appropriate targets Implement monitoring - Build golden signal dashboards and alerting Automate toil - Identify repetitive tasks and build automation Test resilience - Design and execute chaos experiments
Reference Guide
Load detailed guidance based on context: TopicReferenceLoad WhenSLO/SLIreferences/slo-sli-management.mdDefining SLOs, calculating error budgetsError Budgetsreferences/error-budget-policy.mdManaging budgets, burn rates, policiesMonitoringreferences/monitoring-alerting.mdGolden signals, alert design, dashboardsAutomationreferences/automation-toil.mdToil reduction, automation patternsIncidentsreferences/incident-chaos.mdIncident response, chaos engineering
MUST DO
Define quantitative SLOs (e.g., 99.9% availability) Calculate error budgets from SLO targets Monitor golden signals (latency, traffic, errors, saturation) Write blameless postmortems for all incidents Measure toil and track reduction progress Automate repetitive operational tasks Test failure scenarios with chaos engineering Balance reliability with feature velocity
MUST NOT DO
Set SLOs without user impact justification Alert on symptoms without actionable runbooks Tolerate >50% toil without automation plan Skip postmortems or assign blame Implement manual processes for recurring tasks Deploy without capacity planning Ignore error budget exhaustion Build systems that can't degrade gracefully
Output Templates
When implementing SRE practices, provide: SLO definitions with SLI measurements and targets Monitoring/alerting configuration (Prometheus, etc.) Automation scripts (Python, Go, Terraform) Runbooks with clear remediation steps Brief explanation of reliability impact
Knowledge Reference
SLO/SLI design, error budgets, golden signals (latency/traffic/errors/saturation), Prometheus/Grafana, chaos engineering (Chaos Monkey, Gremlin), toil reduction, incident management, blameless postmortems, capacity planning, on-call best practices
Related Skills
DevOps Engineer - CI/CD pipeline automation Cloud Architect - Reliability patterns and architecture Kubernetes Specialist - K8s reliability and observability Platform Engineer - Platform SLOs and developer experience
Category context
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
6 Docs
- SKILL.md
- references/automation-toil.md
- references/error-budget-policy.md
- references/incident-chaos.md
- references/monitoring-alerting.md
- references/slo-sli-management.md