agentleFS
rubixkube-iorubixkube-io/rubixkube-for-ai/skills/investigate/SKILL.md

investigate

Skill1 starsChanged 37 days agoMITView on GitHub

Walk one incident end to end: what happened, the RCA and its evidence, what people found, what to do next. Use when the person asks why something is broken, wants the root cause, or says "investigate" or "debug" about a service, pod, VM or incident.

129 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use pair-agent, plan-devex-review and 10 more.

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.
  • seek888Skill

    pair-agent

    Pair a remote AI agent with your browser. One command generates a setup key and prints instructions the other agent can follow to connect. Works with OpenClaw, Hermes, Codex, Cursor, or any agent that can make HTTP requests. The remote agent gets its own tab with scoped access (read+write by default, admin on request). Use when asked to "pair agent", "connect agent", "share browser", "remote browser", "let another agent use my browser", or "give browser access". (gstack) Voice triggers (speech-to-text aliases): "pair agent", "connect agent", "share my browser", "remote browser access".

    Also in 10 projects that use this

  • seek888Skill

    plan-devex-review

    Interactive developer experience plan review. Explores developer personas, benchmarks against competitors, designs magical moments, and traces friction points before scoring. Three modes: DX EXPANSION (competitive advantage), DX POLISH (bulletproof every touchpoint), DX TRIAGE (critical gaps only). Use when asked to "DX review", "developer experience audit", "devex review", or "API design review". Proactively suggest when the user has a plan for developer-facing products (APIs, CLIs, SDKs, libraries, platforms, docs). (gstack) Voice triggers (speech-to-text aliases): "dx review", "developer experience review", "devex review", "devex audit", "API design review", "onboarding review".

    Also in 13 projects that use this

  • ShreyRaviSkill

    landing-report

    Read-only queue dashboard for workspace-aware ship. Shows which VERSION slots are currently claimed by open PRs, which sibling Conductor workspaces have WIP work likely to ship soon, and what slot /ship would pick next. No mutations — just a snapshot. Use when asked to "landing report", "what's in the queue", "show me open PRs", or "which version do I claim next". (gstack)

    Also in 7 projects that use this

  • ayudaySkill

    setup-deploy

    Configure deployment settings for /land-and-deploy. Detects your deploy platform (Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, custom), production URL, health check endpoints, and deploy status commands. Writes the configuration to CLAUDE.md so all future deploys are automatic. Use when: "setup deploy", "configure deployment", "set up land-and-deploy", "how do I deploy with gstack", "add deploy config".

    Also in 14 projects that use this

  • ayudaySkill

    cso

    Chief Security Officer mode. Performs OWASP Top 10 audit, STRIDE threat modeling, attack surface analysis, auth flow verification, secret detection, dependency CVE scanning, supply chain risk assessment, and data classification review. Use when: "security audit", "threat model", "pentest review", "OWASP", "CSO review".

    Also in 17 projects that use this

  • ramybarsoumSkill

    document-release

    Post-ship documentation update. Reads all project docs, cross-references the diff, updates README/ARCHITECTURE/CONTRIBUTING/CLAUDE.md to match what shipped, polishes CHANGELOG voice, cleans up TODOS, and optionally bumps VERSION. Use when asked to "update the docs", "sync documentation", or "post-ship docs". Proactively suggest after a PR is merged or code is shipped.

    Also in 18 projects that use this

  • +1 more from seek888

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 116 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    If the incident has an rca_id: get_rca(rca_id).

    line 18
  2. Very specific:

    If the RCA is missing or thin: environment_snapshot(environment_id) for the current state of that source, using the incident's environment …

    line 27
  3. Very specific:

    If there is no RCA yet, say so.

    line 37

“Common” is measured: kept by at least 6 in 10 of the 116 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

  • "Why is checkout crashing?" / "Investigate this OOM" / "What's the root cause of INC-…?"
  • "Debug the payment service" (find the incident first with list_incidents)

Steps

  1. get_incident(incident_id). If the person named a service rather than an id, call list_incidents and pick the matching one; ask if two fit.
  2. If the incident has an rca_id: get_rca(rca_id). Read the root cause, contributing factors, impact, remediation and rollback steps, and the evidence behind each finding.
  3. what_changed(incident_id): deploys, config and scaling changes in the hour before. A change right before the incident is the first suspect.
  4. similar_incidents(incident_id): earlier incidents on the same fingerprint or resource, and how they were resolved.
  5. search_knowledge(<the affected service or resource>) for its recorded history: past incidents, RCAs and changes. ask_knowledge answers a question across all of it.
  6. list_comments(kind="incident", id) for what the team already found.
  7. If the RCA is missing or thin: environment_snapshot(environment_id) for the current state of that source, using the incident's environment (a name works).

How to answer

In this order: what broke and where; the root cause as the RCA states it, with the evidence it cites (quote it, do not paraphrase into certainty); the Tasks already proposed (from the RCA or list_tasks); what you would do next, in one or two steps.

Each answer ends with a next line; follow it rather than guessing the next call. If there is no RCA yet, say so. If the RCA failed, offer retry_rca (see the changes skill). Never guess a cause the evidence does not support. Ask before any write.

The server also offers this as the investigate_incident prompt.

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.