cloud-reliability
/cloud-reliability
Apply SRE in cloud and hybrid environments: shared responsibility, managed services, multi-cloud observability, and platform trends from Google SRE 2e and sre.google/cloud. Use for cloud architecture and ops model design.
- Author
- mawero83 ↗
- Repository
- google-sre-skills ↗
- Licence
- MIT
- Last repository change
- 30.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 3
No signals detected. Repository changed on 30.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Apply SRE in cloud and hybrid environments: shared responsibility, managed services, multi-cloud observability, and platform trends from Google SRE 2e and sre.google/cloud. Use for cloud architecture and ops model design.
Original author description
Apply SRE in cloud and hybrid environments: shared responsibility, managed services, multi-cloud observability, and platform trends from Google SRE 2e and sre.google/cloud. Use for cloud architecture and ops model design.
How it works
- When to use
- Principles
- Workflow
- Decision guide
- Output template
- Anti-patterns
- Related skills
- Canonical references
- Agent notes
SKILL.md preview
--- name: cloud-reliability description: >- Apply SRE in cloud and hybrid environments: shared responsibility, managed services, multi-cloud observability, and platform trends from Google SRE 2e and sre.google/cloud. Use for cloud architecture and ops model design. --- # Cloud Reliability **Domain:** `ai` **Sources:** SRE Book 2e Ch3/22, https://sre.google/cloud/ ## When to use - Cloud migration reliability design - Shared responsibility debates - Hybrid/multi-cloud observability ## Principles - Cloud shifts undifferentiated work but not accountability for user journeys. - Managed services need explicit SLIs mapping provider SLAs ≠ your CUJ SLOs. - OpenTelemetry and portable telemetry reduce lock-in of insight. - Design for provider failure domains and control-plane outages. ## Workflow 1. Map CUJs to cloud components + shared responsibility. 2. Translate provider SLAs into your error budget math carefully. 3. Instrument app-level SLIs above infrastructure metrics. 4. Plan for control-plane and identity failures. 5. Test restore/failover across zones/regions you claim. ## Decision guide - If relying on provider SLA alone → insufficient for customer SLO. ## Output template ```markdown # Cloud reliability map - CUJ → components: - Shared responsibility notes: - App SLIs vs provider metrics: - Failure drills: ``` ## Anti-patterns - Assuming multi-AZ checkbox equals tested failover. ## Related skills `monitoring-observability`, `disaster-planning`, `sli-slo-design` ## Canonical references - [SRE on Google Cloud](https://sre.google/cloud/) - [SRE Book 2e](https://sre.google/books/) ## Agent notes - Prefer live data (metrics, tickets, pages) over generic advice. - Cite which Google SRE source informed a recommendation when useful. - Keep outputs tactical: decisions, owners, next actions.
Files in this package (2)
- SKILL.md 2 KB
- reference.md 1 KB
Versions
The database has no other skills named cloud-reliability.
Database snapshot: 13.11.2026 · package version b965c80d8896 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100sre-in-diverse-environments
Adapt SRE practices for startups, solo SRE, hybrid/legacy, and constrained orgs — from SRE Book 2e Ch22. Use when classic Google-scale patterns do not fit and you need pragmatic reliability. - 100sre-foundations
Teach and apply core Google SRE foundations: reliability as a feature, software engineering applied to operations, sociotechnical systems, and when SRE is the right model. Use when onboarding SREs, explaining what SRE is, framing reliability work, or starting a learning path. - 91sre-reliability-engineering
Use when building reliable and scalable distributed systems. - 90reliability-sre
Apply SRE principles (SLO, Error Budget, Chaos Engineering). Use when: sre, reliability, slo, sli, error budget, chaos engineering, postmortem, incident, oncall. - 100sre-expert
Expert-level site reliability engineering, SLOs, incident management, and operational excellence. Use when the user mentions reliability, monitoring, incident management, SLOs, or observability, or when the task involves SRE Fundamentals, Reliability Practices, SRE Principles, or On-Call. - 90google-cloud-waf-reliability
Evaluates, designs, and improves the reliability, resilience, availability, fault tolerance, and disaster recovery (DR) of Google Cloud workloads based on the design principles and recommendations in the Reliability pillar of the Google Cloud Well-Architected Framework. Use when…