Verified:GitHub

sre-toil

Identifies and quantifies repetitive operational toil across AKS, ECS, and GitLab infrastructure.

Updated Jul 22, 2026

Search Tags:#automation #jira #ecs #gitlab ci #sre #aks #toil analysis

One-click install

npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill sre-toil-trigent-software-pvt-ltd

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: sre-toil
Source: https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc/tree/main/plugins/ai-sre/skills/sre-toil
Command: npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill sre-toil-trigent-software-pvt-ltd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? SRE teams lose hours each month to repetitive manual work like restarting pods, replaying dead-letter queues, and investigating recurring pipeline failures. This Skill systematically detects, quantifies, and prioritizes that toil so it can be automated away. ## Core Features & Use Cases - Automated Toil Detection: Runs parallel checks against GitLab CI failure patterns, runner reliability, AKS pod restarts and OOMKilled events, ECS stopped tasks, and Terraform/Terragrunt drift. - Quantified Toil Inventory: Produces a per-product baseline table with frequency, time per occurrence, hours per month, and P1/P2 priority for each toil item. - Automation Playbooks & Tracking: Generates root-cause automation plans per P1 item, optionally creates Jira Stories with sub-tasks, and publishes a monthly Confluence toil register. - Use Case: Run a full toil analysis for the Emergency Management product to discover that ANH push notification failures and OOMKilled pod tuning consume over 9 hours per month, then auto-create Jira tickets for the remediation work. ## Quick Start Ask the assistant to run a toil analysis for a product, for example: run /ai-sre:sre-toil em all to analyze Emergency Management toil across pipelines, runners, AKS, and Azure infrastructure.

Frequently Asked Questions about sre-toil

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I measure and reduce SRE toil in my team?▼

Run the toil analysis for your product and area, such as pipelines, runners, AKS, ECS, or Azure. It detects recurring manual work, quantifies hours per month per item, prioritizes P1/P2 items, and generates automation playbooks with root causes and effort estimates.

How to detect recurring GitLab CI pipeline failures automatically?▼

The analysis queries the GitLab API for failed jobs, groups them by job name and runner, and surfaces the top recurring failure patterns. It also checks runner status and reliability across the group to flag capacity or eviction issues.

Does the toil analysis support both AKS and AWS ECS products?▼

Yes. AKS-based products are checked for pod restarts, OOMKilled, and CrashLoopBackOff events, while PSW on AWS is checked for ECS stopped tasks, Aurora connection issues, and SQS DLQ depth. PSW region is detected from arguments as US or Canada.

Can it create Jira tickets and Confluence pages for toil tracking?▼

Yes. After the inventory, it can create a Jira Story with sub-tasks per P1/P2 item labeled toil, sre, and automation, plus a monthly Confluence toil register page with the inventory table and trend data.

What access is required to run the toil analysis?▼

It needs kubectl access to the relevant AKS namespaces, a glab CLI token for GitLab API queries, AWS CLI credentials for ECS products, and Atlassian MCP access for Jira and Confluence creation. Missing access causes those checks to be skipped.