reliability 플러그인
Availability targets, SLOs, incidents, postmortems, a static status page, on-call, a backup inventory with restore tests, and a change record per server, with gate checks on the service catalogue and the backup inventory.
reliability 플러그인 설치 방법
두 명령을 모두 Claude Code 안에서 실행하십시오. 첫 번째는 마켓플레이스를 한 번 추가하고, 두 번째는 플러그인을 설치합니다.
/plugin marketplace add uncovertechtalent/cto-powersuit
/plugin install reliability@cto-powersuitreliability 구성 요소
플러그인 파일에서 읽어온 8개의 항목입니다.
Skills 8
작업이 일치하면 Claude가 로드합니다- backup-inventory
Walk a team through a backup inventory, one data store at a time: where the backup lives, the schedule and retention, which identities can delete or overwrite it, whether a copy sits outside the reach of production administrators, the date and result of the last restore test, and the measured restore time against its target. Writes docs/sre/backups.md and a restore-test runbook per store. Use when nobody can say where the backups are, who can delete them, or when a restore was last tried. Activates on "/backup-inventory", "backup inventory", "where do our backups live", "who can delete our backups", "can we restore", "restore test", "backup audit", "ransomware backups".
- host-log
Keep a change record on every server that people or agents change over ssh. Each host holds /<hostname>.log with one line per change, and every ssh connection prints an AGENTS line that points at it, so the next person or agent reads the host's history before touching anything. Covers the rule, the line format, appending safely from stdin, setup on Linux with sudo and on macOS or hosts without sudo, appliances, and the hosts to leave out. Use before and after any change on a remote host, and when a host joins the fleet. Activates on "host log", "server log", "hostname.log", "AGENTS banner", "change record for a server", or any ssh change on a host that prints an AGENTS line.
- incident
Run an incident from declaration to close: set the severity and the roles (incident lead, comms, operations), keep a timestamped log, post public updates to the incident records and the status page, resolve and close it, and hand over to the postmortem skill. Use when users see errors, slowness or wrong data, when an alert pages on a user-facing symptom, or when someone asks whether this is an incident. Activates on "/incident", "declare an incident", "we have an incident", "is this an incident", "site is down", "start incident", "update the status page", "resolve the incident".
- nines-per-service
Pick an availability target per service from user impact, tier and serial dependencies, check it against the allowed downtime per 30 days, quarter and year and against the product of its dependencies' availabilities, and write it into the service catalogue. Use when a service has no target yet, when a target looks arbitrary, or before a tier change or a customer commitment. Activates on "/nines-per-service", "how many nines", "availability target", "pick an SLO target", "99.9 or 99.99", "allowed downtime", "dependency ceiling".
- on-call
Set up on-call for the services in the catalogue: the rotation, the escalation policy, the handover checklist and the paging rules (page only on user-facing symptoms, every alert links a runbook), with an audit of the existing alert rules, written to docs/sre/on-call.md. Use when a team starts on-call, when pages wake people for causes users never see, or when nobody can say who answers a page tonight. Activates on "/on-call", "on-call rotation", "set up on-call", "escalation policy", "paging rules", "alert fatigue", "who gets paged".
- postmortem
Write a blameless postmortem for one incident: summary, impact in minutes, users and requests, a timeline with a source for every time, contributing factors as mechanisms, what went well and what went poorly, and action items with one owner and a due date each, linked from the incident record. Use when a sev1 or sev2 incident is closed, when an incident used a large share of the error budget, or when the same problem comes back. Activates on "/postmortem", "write the postmortem", "incident review", "post-incident review", "retro for the outage", "blameless review".
- slo
Define a service level objective for one service: the SLI as good events over valid events with exact queries, the target and window, the error budget, multiwindow burn-rate alerts and an error-budget policy, written to a docs page and linked from the service catalogue. Use when a service has a target and no way to measure it, when alerts page on causes users never see, or when releases and reliability work compete for the same time. Activates on "/slo", "define an SLO", "write an SLO", "error budget", "burn rate alert", "SLI for", "error budget policy".
- status-page
Set up a static status page built from published records: the service catalogue in services/*.yml and the incident records in incidents/incidents.json, turned into one HTML page and a JSON file by a standard-library script that runs in the deploy job. Use when users need one place to see whether a service works and what happened before, or when a hosted status tool is more than the team needs. Activates on "/status-page", "status page", "set up a status page", "public incident history", "build the status page", "where do users see outages".
Claude Code에서 reliability 사용하기
Skills는 명령어가 필요하지 않습니다. 요청이 설명과 일치하면 Claude가 이를 읽습니다.
업데이트, 비활성화 또는 삭제
- 플러그인 업데이트 (shell)
- claude plugin update reliability@cto-powersuit
- marketplace 새로고침
- /plugin marketplace update cto-powersuit
- 일시적으로 비활성화
- /plugin disable reliability@cto-powersuit
- 삭제
- /plugin uninstall reliability@cto-powersuit
reliability의 스킬
- backup-inventoryuncovertechtalent/cto-powersuit
Walk a team through a backup inventory, one data store at a time: where the backup lives, the schedule and retention, which identities can delete or overwrite it, whether a copy sits outside the reach of production administrators, the date and result of the last restore test, and the measured restore time against its target. Writes docs/sre/backups.md and a restore-test runbook per store. Use when nobody can say where the backups are, who can delete them, or when a restore was last tried. Activates on "/backup-inventory", "backup inventory", "where do our backups live", "who can delete our backups", "can we restore", "restore test", "backup audit", "ransomware backups".
8스타 - host-loguncovertechtalent/cto-powersuit
Keep a change record on every server that people or agents change over ssh. Each host holds /<hostname>.log with one line per change, and every ssh connection prints an AGENTS line that points at it, so the next person or agent reads the host's history before touching anything. Covers the rule, the line format, appending safely from stdin, setup on Linux with sudo and on macOS or hosts without sudo, appliances, and the hosts to leave out. Use before and after any change on a remote host, and when a host joins the fleet. Activates on "host log", "server log", "hostname.log", "AGENTS banner", "change record for a server", or any ssh change on a host that prints an AGENTS line.
8스타 - incidentuncovertechtalent/cto-powersuit
Run an incident from declaration to close: set the severity and the roles (incident lead, comms, operations), keep a timestamped log, post public updates to the incident records and the status page, resolve and close it, and hand over to the postmortem skill. Use when users see errors, slowness or wrong data, when an alert pages on a user-facing symptom, or when someone asks whether this is an incident. Activates on "/incident", "declare an incident", "we have an incident", "is this an incident", "site is down", "start incident", "update the status page", "resolve the incident".
8스타 - nines-per-serviceuncovertechtalent/cto-powersuit
Pick an availability target per service from user impact, tier and serial dependencies, check it against the allowed downtime per 30 days, quarter and year and against the product of its dependencies' availabilities, and write it into the service catalogue. Use when a service has no target yet, when a target looks arbitrary, or before a tier change or a customer commitment. Activates on "/nines-per-service", "how many nines", "availability target", "pick an SLO target", "99.9 or 99.99", "allowed downtime", "dependency ceiling".
8스타 - on-calluncovertechtalent/cto-powersuit
Set up on-call for the services in the catalogue: the rotation, the escalation policy, the handover checklist and the paging rules (page only on user-facing symptoms, every alert links a runbook), with an audit of the existing alert rules, written to docs/sre/on-call.md. Use when a team starts on-call, when pages wake people for causes users never see, or when nobody can say who answers a page tonight. Activates on "/on-call", "on-call rotation", "set up on-call", "escalation policy", "paging rules", "alert fatigue", "who gets paged".
8스타 - postmortemuncovertechtalent/cto-powersuit
Write a blameless postmortem for one incident: summary, impact in minutes, users and requests, a timeline with a source for every time, contributing factors as mechanisms, what went well and what went poorly, and action items with one owner and a due date each, linked from the incident record. Use when a sev1 or sev2 incident is closed, when an incident used a large share of the error budget, or when the same problem comes back. Activates on "/postmortem", "write the postmortem", "incident review", "post-incident review", "retro for the outage", "blameless review".
8스타 - slouncovertechtalent/cto-powersuit
Define a service level objective for one service: the SLI as good events over valid events with exact queries, the target and window, the error budget, multiwindow burn-rate alerts and an error-budget policy, written to a docs page and linked from the service catalogue. Use when a service has a target and no way to measure it, when alerts page on causes users never see, or when releases and reliability work compete for the same time. Activates on "/slo", "define an SLO", "write an SLO", "error budget", "burn rate alert", "SLI for", "error budget policy".
8스타 - status-pageuncovertechtalent/cto-powersuit
Set up a static status page built from published records: the service catalogue in services/*.yml and the incident records in incidents/incidents.json, turned into one HTML page and a JSON file by a standard-library script that runs in the deploy job. Use when users need one place to see whether a service works and what happened before, or when a hosted status tool is more than the team needs. Activates on "/status-page", "status page", "set up a status page", "public incident history", "build the status page", "where do users see outages".
8스타
reliability 플러그인 질문
reliability 플러그인은 어떻게 설치하나요?
Claude Code에서 /plugin marketplace add uncovertechtalent/cto-powersuit를 실행한 다음 /plugin install reliability@cto-powersuit을 실행하십시오.
reliability 플러그인에는 무엇이 포함되나요?
reliability은(는) 8개 스킬을(를) 묶습니다.
reliability 플러그인을 어떻게 업데이트하거나 삭제하나요?
shell에서 claude plugin update reliability@cto-powersuit를 사용하여 업데이트하거나 /plugin의 Installed 탭에서 수행하세요. 삭제하려면 /plugin uninstall reliability@cto-powersuit을 사용하세요.
reliability 플러그인의 라이선스는 무엇인가요?
플러그인 manifest에 명시된 대로 MIT입니다.