메뉴
Design, operate, and improve reliable production systems with SLOs, incident command, observability, error budgets, and operational practices.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | site-reliability-engineering |
| description | Design, operate, and improve reliable production systems with SLOs, incident command, observability, error budgets, and operational practices. |
| license | MIT |
| compatibility | Python 3.9+ is required only for the bundled calculation and summary scripts. |
| metadata | {"source_repo":"https://github.com/magnus919/hermes-profiles","source_commit":"867a555"} |
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.
| 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 |
| 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 | references/release-engineering.md | Deployment pipeline design |
| 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) |
| 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 |
| 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 |
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.
Spec-Driven Development (SDD) methodology for AI software factories — where structured specifications are the input, AI agents generate the code, and quality gates enforce correctness at each pipeline phase. Use when designing a spec → review → decompose → implement → verify pipeline that any AI coding tool (Claude Code, Cursor, Hermes Agent, Devin, OpenHands) can follow.
Query your Jellyfin media server from the terminal — recently added media, search, item details, next-up episodes, library browsing, server info, and stats. Use when the user asks about Jellyfin, media server, movies, TV shows, next episodes, or their media library.
Multi-agent structured debate system. Spawn a panel of expert agents to debate any question, with convergence-aware iteration and typed synthesis output. Run via `agent-council` CLI. Compatible with any AI agent harness that supports agentskills.io skills (Claude Code, Cursor, Hermes Agent, OpenHands, etc.).
Reference for the Agent Skills open format — the directory structure, SKILL.md frontmatter schema, naming conventions, progressive disclosure model, and best practices for creating skills. Use this whenever creating, reviewing, or editing skills in this repository to ensure they follow the standard spec.
Verify work against explicit criteria using evidence, reproducible checks, and clear pass, conditional, or blocked verdicts. Use before declaring an artifact, implementation, or claim complete.
Manage Linear teams, projects, cycles, issues, comments, workflow state, and documents from a terminal through Linear's public GraphQL API. Use when a user asks to list, search, inspect, create, update, move, or comment on Linear work, or to find Linear documents. Do not use to embed a live agent inside Linear or to build an MCP integration.
