🧪 Community ✓ Claude Code ✓ Claude Desktop Standalone • Devops-pack
Devops Pack
DevOps & Reliability — cross-vendor on-call handoffs, incident postmortems, deploy health, and error-budget tracking across whatever incident-management and observability tools you have connected.
Installation
Install this plugin individually:
/plugin marketplace add wyre-technology/msp-claude-plugins --plugin devops-pack Or install all MSP plugins at once:
/plugin marketplace add wyre-technology/msp-claude-plugins Features
- Error Budget Tracking
- Incident Postmortem
- Oncall Handoff
Skills
This plugin provides 3 skills that teach Claude about Devops Pack:
| Skill | Description |
|---|---|
error-budget-tracking | Use this skill when computing or reporting error-budget status across whatever observability tools are connected through the gateway. |
incident-postmortem | Use this skill when assembling a blameless postmortem from an incident across whatever incident-management and observability tools are connected through the gateway. |
oncall-handoff | Use this skill when assembling a proper on-call handoff across whatever incident-management tool (Rootly, PagerDuty, BetterStack) is connected through the gateway. |
Agents
This plugin provides 3 agents for autonomous task execution:
| Agent | Description |
|---|---|
oncall-handoff-builder | Use this agent when an on-call engineer needs a structured shift handoff brief — what's currently paging or unresolved, what happened during the last shift, known-flaky alerts to watch, and anything escalated but not yet actioned — assembled from whatever incident-management tool is connected. |
postmortem-drafter | Use this agent when an engineer, SRE, or incident manager needs a full blameless postmortem drafted from a resolved incident — identified by ID or by a rough time window — reconstructed from the incident tool's event log plus correlated observability and deploy data. |
reliability-scorecard | Use this agent when a team lead, SRE, or engineering manager needs a ranked reliability status across connected services — error-budget burn rate where a formal SLO exists, degrading to raw error-rate/uptime trend reporting where it doesn't — worst service first. |
Commands
Available slash commands:
| Command | Description |
|---|---|
/error-budget | Run the reliability scorecard for one service, or every connected service if omitted - error-budget burn rate where an SLO is defined, trend reporting otherwise |
/oncall-brief | Generate the current on-call handoff brief - what's paging, what's escalated without an owner, last-shift history, and known-flaky alerts to watch |
/postmortem | Draft a blameless postmortem for a given incident (by ID or name), or the most recent significant incident within a time window |
API Reference
| Base URL | |
| Authentication | |
| Rate Limit | |
| Documentation |
Example Usage
Run the reliability scorecard for one service, or every connected service if omitted - error-budget burn rate where an SLO is defined, trend reporting otherwise
/error-budgetGenerate the current on-call handoff brief - what's paging, what's escalated without an owner, last-shift history, and known-flaky alerts to watch
/oncall-briefDraft a blameless postmortem for a given incident (by ID or name), or the most recent significant incident within a time window
/postmortemUsing Skills
/skill devops-pack:error-budget-tracking
Use this skill when computing or reporting error-budget status across whatever observability tools are connected through the gateway.