sre

Plugin sre from marketplace claude-sre in kryptophonik/SRE-Skills. Commands read from the repo's manifest — 20 days ago.

Skills (41)

• sre-aws

  Use when the system runs on AWS: Health, CloudWatch metrics and Logs Insights, EC2/EKS/RDS/ELB/ASG/ECS status, CloudTrail, quotas. Read-only profile via AWS CLI or MCP; writes need approval.

• sre-azure

  Use when the system runs on Azure: Resource Health, Azure Monitor, Log Analytics (KQL), AKS/VM/App Service status, Activity Log. Read-only roles via az CLI or Azure MCP; writes need approval.

• sre-capacity-planning

  Use before launches or peak events, or when saturation trends up: forecast demand from metrics, compute headroom, plan load tests, set scaling triggers. Read-only queries.

• sre-change-safety

  Use before, during or right after a deploy, migration or infra change: risk score, freeze and error-budget check, canary/progressive rollout, rollback plan, post-deploy verification.

• sre-chaos-engineering

  Use to design or run a chaos / fault-injection experiment or game day, with hard no-go rules, approval and abort criteria. Manual invocation only. Not for live incident response.

• sre-cloud-cost-review

  Use for cloud or observability cost reviews and spend spikes: idle/oversized resources, storage sprawl, data transfer, commitments, ingest/retention. Read-only; never deletes or resizes without approval.

• sre-database-triage

  Use when Postgres, MySQL/MariaDB or Redis is slow or failing: connection exhaustion, locks, long or slow queries, replication lag, disk/WAL/bloat, Redis memory/eviction, DB CPU. Read-only; kill and failover are gated.

• sre-datadog

  Use when metrics, traces, logs, monitors or SLOs live in Datadog: queries, monitor and SLO review, incidents and events. Read-only MCP or API (read-scoped keys); writes need approval.

• sre-dependency-mapping

  Use for PRRs, reliability reviews, incident blast radius or chaos planning: map upstream/downstream services, criticality, timeouts/retries and single points of failure. Read-only.

• sre-diagnostics

  Use to investigate a live issue read-only: logs/metrics/traces queries, correlation, hypothesis testing, profiling and bottleneck identification. Gives exact commands when tools are unavailable.

• sre-dr-backup-test

  Use when testing backups or DR readiness: backup-restore and failover drills against RTO/RPO, restoring only to new isolated targets after approval, with an evidence record.

• sre-dynatrace

  Use when data lives in Dynatrace: DQL for problems, logs, metrics and entities, Davis problem triage, SLO and health checks. Read-only MCP or DQL for Notebooks.

• sre-emudhra-ca-check

  Use to check whether a TLS/code-signing cert chains through one of the 8 eMudhra intermediate CAs revoked for private-key compromise, Oct 2026 (Mozilla bug 2083449): endpoints, cert files, k8s TLS secrets. Read-only; a match needs a gated reissue.

• sre-engineer

  Use for live problems (incident, alert, latency or 5xx, gated remediation, runbook walk) and for SRE design: observability architecture, reliability reviews, on-call program design, and choosing tools.

• sre-expiry-audit

  Use when asked what expires soon: TLS certs (endpoints, cert-manager), domain registrations, ACM/IAM certs, Secrets Manager rotation, GCP Secret/Certificate Manager, Azure Key Vault. Read-only metadata; flags 30/14/7 days.

• sre-gcp

  Use when the system runs on Google Cloud: Cloud Monitoring, Cloud Logging, GKE/Compute/Cloud Run/Cloud SQL status, audit logs, quotas. Viewer roles via gcloud or MCP allowlist; writes need approval.

• sre-incident-command

  Use when an incident is declared or suspected: declare, assign roles (IC, ops, comms, scribe), set severity, keep the timeline, drive decisions, hand off and close. Debugging goes to sre-engineer.

• sre-incident-communication

  Use when an incident update or stakeholder message is needed: announcements, status updates, resolution notices, executive summaries with severity cadence. Drafts only until approved.

• sre-k8s-safe-remediation

  Use when a fix from sre-k8s-triage needs a kubectl or helm write (rollback, restart, scale, pod delete, Helm rollback): evidence, GitOps/HPA ownership check, preview, explicit approval, verify.

• sre-k8s-triage

  Use when a Kubernetes workload or node is unhealthy: CrashLoopBackOff, Pending, OOMKilled, ImagePullBackOff, node pressure, DNS, probes, stuck rollouts, Helm, and whether a restart is safe. Read-only decision tree.

• sre-k8s-upgrade-autopilot

  Plan a Kubernetes minor-version upgrade - scripted preflight, support-status check, go/no-go, gated EKS/GKE/AKS steps, verification after every step. Scripts tested on kind. Use for "upgrade our cluster to 1.xx".

• sre-message-queue-triage

  Use when Kafka, RabbitMQ or SQS/SNS is backing up or dropping messages: consumer lag, DLQ growth, broker disk/under-replication, redelivery storms, poison-pill messages. Read-only; purge, rebalance and resize are gated.

• sre-migration-safety

  Review a SQL schema migration for PostgreSQL or MySQL/MariaDB before it merges. Says which statements lock, rewrite or block writes, and gives the safe pattern for each. Never connects to production.

• sre-observability-cost-cutter

  Use to reduce observability spend. Read-only usage and cost audit (works with Datadog), a ranked savings report with approval-gated changes and rollbacks, and conversion of metric monitors to Prometheus rules checked by promtool.

• sre-observability-query-cookbook

  Use when you need a correct query for golden signals, RED/USE, saturation, error ratio, latency percentiles or SLO burn rate in PromQL, DQL, Datadog or LogQL.

• sre-oncall-audit

  Use before rotation changes, after a migration, or quarterly: read-only audit of PagerDuty/Opsgenie schedules and escalation policies for coverage gaps, single-person layers, DST, loops, unreachable users.

• sre-oncall-handoff

  Use at shift change or when asked for an on-call summary: open incidents, alerts that fired, noisy alerts, ongoing risks, pending changes and follow-ups. Read-only.

• sre-pagerduty-opsgenie

  Use for on-call, incident and handoff tasks in PagerDuty or Opsgenie: who is on call, open incidents/alerts, escalation policies, timelines, capped page counts. Writes need approval.

• sre-php2shell-check

  Use to check PHP hosts/containers for PHP2Shell (CVE-2026-109618, CVE-2026-109619), the Oct 2026 critical unauthenticated RCE pair, CVSS 9.2. Read-only version check (php -v, package manager, X-Powered-By); a hit needs a gated upgrade.

• sre-postmortem-templates

  Use after an incident is resolved to draft or facilitate a blameless postmortem / incident review / RCA with a timeline from paging, monitoring and deploy history. Not for active incidents.

• sre-production-readiness

  Use before a new service or major change goes live: run a production readiness review (PRR) / launch checklist and produce a pass/fail verdict with evidence.

• sre-prometheus-grafana

  Use when metrics, logs or alerts live in Prometheus, Alertmanager, Loki or Grafana: bounded PromQL/LogQL, active alerts, rule linting with promtool, gated silences, dashboards.

• sre-remediation-actions

  Reference of gated recovery procedures (rollback, scale, restart, failover) with risk/reversibility labels, evidence capture and dry-run first. Loaded by sre-engineer before any remediation.

• sre-runbook-templates

  Use when creating or reviewing a runbook: full template with owner, scope, diagnosis, decision points, gated actions with rollback, verification, escalation and last-reviewed date.

• sre-safety-gates

  Shared approval gates for every sre-* skill: read-only first, propose with risk/reversibility, explicit human approval before any prod change, MCP write or external post, verify, stop if worse.

• sre-security-incident-triage

  Use when a security compromise is suspected: leaked credentials, suspicious access, compromised host or container, unexpected infra changes. Preserve evidence, gated containment, hand off to security.

• sre-service-mesh-triage

  Use when Istio or Linkerd sidecars are suspected: 503s from the mesh vs. the app, mTLS handshake failures, retry/circuit-breaker storms, sidecar injection failures, egress blocked by policy. Read-only; fixes hand off to sre-k8s-safe-remediation.

• sre-slo-alerting

  Use when creating or revising SLIs, SLOs, error budget policy, burn-rate alerts or paging policy, and for alert-fatigue reduction. Not for responding to a firing alert (use sre-engineer).

• sre-slo-burn-rate-rules

  Use when authoring or fixing Prometheus SLO burn-rate alert rules: generate 4-tier multiwindow rules from an SLO target and counters, then promtool lint and test. Files only, never deploys. Not for responding to a firing alert (use sre-engineer).

• sre-terraform

  Use for any Terraform change, plan review, drift check or rollback: confirm target, fmt/validate, saved-plan review, state inspection without leaking secrets, gated apply of the reviewed plan.

• sre-toil-review

  Use for quarterly ops reviews or when on-call load is high: inventory repetitive manual work, score frequency x time x risk, and pick automation candidates.

Similar plugins