manage-slos

Assist with Harness Service Reliability Management (SRM) tasks that the MCP server currently supports: pulling recent deployments for incident correlation, generating on-call handover reports from deployment/execution history, and drafting operational runbooks. Use when asked about SLOs, error budgets, burn-rate alerts, on-call handover, runbooks, or incident triage. Do NOT use for DORA metrics (use dora-metrics instead) or chaos experiments (use chaos-experiment instead). Trigger phrases: SLO, SLI, error budget, burn rate, on-call handover, runbook, service reliability, incident response, on-call shift.

Version

2.0.0

License

Apache-2.0

Compatibility

Requires Harness MCP v2 server (harness-mcp-v2). NOTE: SRM CRUD resources (`slo`, `slo_alert`, `monitored_service`) are NOT currently exposed by the MCP server. Creating/managing SLOs and monitored services must be done in the Harness UI. This skill focuses on the incident-correlation and reporting workflows that the MCP server does support today (via `execution`, `service`, `environment`).