mirror of
https://github.com/magnus919/agent-skills.git
synced 2026-09-11 19:47:12 +03:00
6f67a34ef1
* feat(skill): cross-pollinate the new tool wave into catalog routing Wire the recent tool skill wave into the two-layer routing graph so the new tool skills are reachable from the methodology skills that own their domains, and vice versa: - methodology -> tool down-routes: platform-engineering -> kubernetes, terraform, telemetry, postgres, grafana; site-reliability-engineering -> telemetry, grafana; data-engineering and backend-engineering -> postgres; frontend-engineering -> mobile-development; verification-methodology -> playwright, documents; technical-documentation -> documents - neckbeard: add mobile-development and documents routing rows plus change-surface coverage entries, and cross-link the lightweight test-hardening path to qa-methodology's bounded mutation-review material - collaboration layer: chief-of-staff-methodology -> slack/notion/email, go-to-market -> crm, conditional-customer-success -> crm; fix the dead seo-content-optimization reference in go-to-market (now seo-audit) - references/skill-triggers.md: add trigger rows for the 14 new skills - bring go-to-market's description up to the quality validator's imperative-verb + negative-boundary requirement and regenerate catalogs Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com> * fix(skill): add eval manifest for technical-documentation The eval-coverage ratchet fails on modified skills without a schema-valid manifest once coverage passes 50%. technical-documentation was modified by the routing cross-pollination change and lacked one; add six output-quality cases covering README authorship, API reference generation, CLI help design, agent-facing docs, documentation-site IA, and troubleshooting sections. Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com> --------- Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
5.3 KiB
5.3 KiB
name, description, license, compatibility, metadata
| name | description | license | compatibility | metadata | ||||
|---|---|---|---|---|---|---|---|---|
| site-reliability-engineering | Design, operate, and improve reliable production systems with SLOs, incident command, observability, error budgets, and operational practices. | MIT | Python 3.9+ is required only for the bundled calculation and summary scripts. |
|
Site Reliability Engineering
A comprehensive methodology for designing, operating, and improving reliable production systems. Rooted in Google SRE principles and extended with modern practices for incident command, observability engineering, error budget governance, and operational excellence.
When to Load This Skill
| Trigger | What It Means |
|---|---|
| "Design reliability into this system" | SLO/SLI framework, error budget policy, resilience architecture |
| "Run an incident postmortem" | Blameless postmortem with timeline, 5 Whys, action tracking |
| "Improve our on-call" | Rotation design, alert tuning, toil reduction, escalation policy |
| "Build observability" | The Four Golden Signals, dashboard design, alert rule patterns |
| "Do a reliability review" | Architecture review against SRE principles, risk assessment |
| "I need an incident commander" | Incident command framework, role cards, communication templates |
| "Automate this operational task" | Toil assessment, automation decision tree, runbook pattern |
When not to use
Use release-engineering to plan releases, compose promotion and rollback gates, or coordinate a release train. Use systematic-debugging to find the cause of a specific failure. Operating the telemetry stack itself — Prometheus scrape configs, OpenTelemetry Collector pipelines, Loki ingest and retention, Prometheus rules files — belongs to telemetry; this skill owns the SLI/SLO and alert design those rules implement. Grafana product work — dashboards, panels, Grafana-side alert rules, contact points, notification policies — belongs to grafana.
Reference Files
| Topic | File | When to Load |
|---|---|---|
| SRE Book Chapter Summaries | references/sre-book-chapters.md |
Design engagement, first principles review |
| SLO/SLI Framework | references/slo-sli-framework.md |
Defining reliability targets |
| Error Budget Governance | references/error-budget-governance.md |
Policy design, burn rate alerts |
| Incident Command System | references/incident-command-system.md |
During/after incident, training |
| Blameless Postmortems | references/postmortem-culture.md |
After incident, process design |
| Monitoring & Alerting | references/monitoring-alerting.md |
Observability design, alert rules |
| On-Call Best Practices | references/oncall-best-practices.md |
Rotation design, team sizing |
| Toil Elimination | references/toil-elimination.md |
Automation prioritization, ops review |
| Release Engineering | release-engineering | Release planning, promotion, progressive delivery, and rollback design; use the local reference only for SRE-specific integration context |
| Effective Troubleshooting | references/troubleshooting.md |
Debugging methodology |
| Senior SRE Role Blueprint | references/senior-sre-blueprint.md |
Role definition, KPI framework |
| SRE Communication Guide | references/sre-communication-guide.md |
Stakeholder updates, incident communication |
| Guiding Principles | references/guiding-principles.md |
First principles, philosophy |
| Product-Focused Reliability | references/product-focused-reliability.md |
Product-centric SRE, CUJ-based SLOs, JTBD model |
| Twenty Years of Lessons | references/twenty-years-lessons.md |
Incident-derived tactical lessons, Prodverbs |
| SRE Ecosystem Guide | references/sre-ecosystem-guide.md |
Curated guide to all SRE resources (Workbook, Secure Systems, Classroom, Prodcast, STPA, Video Gallery, Mobaa, fundamentals, AI ops) |
Templates
| Template | File | Purpose |
|---|---|---|
| Incident Commander Checklist | templates/incident-command-checklist.md |
Step-by-step IC response |
| Postmortem Template | templates/postmortem-template.md |
Blameless postmortem document |
| Runbook Template | templates/runbook-template.md |
Operational runbook standard |
| SLO Declaration Template | templates/slo-declaration-template.md |
Service-level objective specification |
| Error Budget Policy | templates/error-budget-policy.md |
Team-level error budget governance |
| On-Call Rotation Template | templates/oncall-rotation.md |
Rotation schedule and escalation |
| Service Review Checklist | templates/service-review-checklist.md |
Pre-launch reliability review |
| Incident Communication Template | templates/incident-communication.md |
Status updates during incidents |
Scripts
| Script | Purpose |
|---|---|
scripts/slo-burn-rate.py |
Calculate error budget burn rate from SLI data |
scripts/postmortem-summary.py |
Generate a postmortem summary from structured data |
Portability
This skill is intentionally host-neutral. Use your agent's normal mechanisms to load the references, templates, and scripts listed here. Do not assume a particular profile system, task orchestrator, memory service, or response-handoff format.