agentleFS
Sign inStart free
rubixkube-iorubixkube-io/rubixkube-for-ai/skills/rca/SKILL.md

rca

Skill1 starsChanged 37 days agoMITView on GitHub

Root cause analyses: the report RubixKube writes for an incident, with the timeline, impact, root cause, contributing factors, remediation and rollback steps, proposed Tasks and evidence. Use when the person asks for the RCA, the root cause, the postmortem, or recent RCAs.

15 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use handoff and tdd.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    Also in 4 projects that use this

  • GoogleSkill

    tdd

    Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If get_incident shows no rca_id, say the RCA is not ready and check again later.

    line 24
  2. Very specific:

    Keep the RCA's structure: root cause, contributing factors, impact, remediation, rollback.

    line 29

“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

When to use

  • "Show me the RCA for INC-…" / "What was the root cause?" / "Recent postmortems"
  • A console.rubixkube.ai/rcas/<id> link

Tools

  • list_rcas(environment_id?, limit?): recent RCAs with the root cause in one line each.
  • get_rca(rca_id): the full report. Get the id from list_rcas or an incident's rca_id.
  • list_comments(kind="rca", id) for feedback people left on it.

Timing

An RCA runs in the background after an incident is created and usually takes a few minutes. If get_incident shows no rca_id, say the RCA is not ready and check again later. If the RCA failed, offer retry_rca (the changes skill).

How to answer

Keep the RCA's structure: root cause, contributing factors, impact, remediation, rollback. Quote the evidence for each claim. Separate what the RCA found from what you infer. Mention the Tasks it proposed and whether they exist already (list_tasks).

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free