incidents
Skill1 starsChanged 38 days agoMITView on GitHub
List and read incidents: what the observers detected or people reported, open or resolved, by severity, status or environment. Use when the person asks what's broken, about alerts, about a specific incident id or console link, or wants incidents in one environment.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- itsryanarmani/skillstheir own version, first seen Nov 8, 2026
- pooriaarab/skillstheir own version, first seen Nov 7, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- itsryanarmani/skills★ 1same name
- pooriaarab/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- changesSkill
- environmentsSkill
- investigateSkill
- knowledgeSkill
- rcaSkill
- statusSkill
- tasksSkill
The file
Files
When to use
- "What's broken?" / "Any critical incidents?" / "Open incidents in staging"
- "Show me INC-… " or a
console.rubixkube.ai/incidents/<id>link - "Which incidents are waiting for an answer?"
Tools
list_incidents(open_only=true, severity?, status?, environment_id?, limit?). Open by default, including resolved incidents still waiting for someone to say what fixed them.severity: critical, high, medium, low.status: NEW, QUEUED_FOR_RCA, RCA_IN_PROGRESS, RCA_COMPLETED, RESOLVED, IGNORED.environment_idtakes an id or a name fromlist_environments.get_incident(incident_id)for one incident in full: events, status history,rca_idwhen the RCA is done, the proposed fix.get_incident_resolution(incident_id)for what the platform thinks fixed it, and the numbered candidates while it waits for an answer.list_comments(kind="incident", id)for what people already wrote.
How to answer
Lead with severity and status. Give the incident id and the console link so the person can
open it. If rca_id is empty, the RCA is still running or has not started: say so and offer
to check again later (get_incident) rather than guessing the cause. For changes (close,
edit, retry the RCA, comment) use the changes skill.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

