메뉴
Use when designing, operating, reviewing, or improving production reliability with SLOs, incident command, observability, error budgets, and operational excellence.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
The craft of being a Chief of Staff — gatekeeping, force multiplication, executive briefing, organizational sensing, institutional memory, and meeting/calendar triage. Provides the frameworks and templates that make an executive more effective by managing their capacity, information flow, and decision surface.
Use when exploring adjacent ideas, overlooked angles, or lateral research paths without prematurely collapsing into a single answer.
Shared decision-making and governance methodology for all C-suite profiles. Covers decision frameworks (RAPID, DACI, decision matrices, pre-mortems, red-teaming), strategic thinking patterns (inversion, first principles, second-order effects), stakeholder communication (executive summaries, board decks, strategy memos), and governance frameworks (risk appetite, delegation levels, escalation paths).
CFO methodology for unit economics, financial modeling, pricing strategy, fundraising, budget frameworks, and SaaS metrics. Covers CAC/LTV/payback analysis, revenue projections, cost structures, runway analysis, scenario planning, value-based pricing, cap tables, term sheets, zero-based budgeting, rolling forecasts, ARR/MRR, churn, NDR, Rule of 40, and Magic Number.
CMO methodology — positioning and messaging frameworks (April Dunford's positioning, message hierarchy), customer acquisition strategy (paid, organic, PLG, SLG), brand architecture (brand house vs house of brands), growth modeling (CAC/LTV by channel, cohort analysis), market entry strategy (beachhead, land-and-expand), competitive response (pricing wars, feature races, brand defense).
CLO/General Counsel methodology — regulatory landscape analysis (GDPR, CCPA, AI Act, sector-specific), IP strategy (patent, trademark, trade secret, open source licensing), contract risk assessment (indemnification, liability caps, force majeure), data privacy frameworks (privacy-by-design, DPIAs, data mapping), corporate governance (board responsibilities, fiduciary duties, shareholder rights), employment law (classification, IP assignment, non-competes).
| name | site-reliability-engineering |
| description | Use when designing, operating, reviewing, or improving production reliability with SLOs, incident command, observability, error budgets, and operational excellence. |
| title | Site Reliability Engineering — Methodology |
| type | skill |
| subjects | ["SRE","Reliability Engineering","Incident Management","Observability","Platform 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.
| 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 |
skill_view('site-reliability-engineering') — this file, methodology index| 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 |
All output follows the artifact pyramid convention (three-layer progressive disclosure). The response to any caller is the absolute path to 00-index.md. Not a summary. Not a conversation. A path.
This skill is primarily used by the site-reliability-engineer profile. It works alongside: