rubixkube

Plugin rubixkube from marketplace rubixkube in rubixkube-io/rubixkube-for-ai. Commands read from the repo's manifest — 1 month ago.

Skills (8)

• changes

  Changes to incidents, recorded under the person's name: report a new incident, correct one, close one, answer what fixed it, run the RCA again, comment. Use when the person wants to create or close an incident, retry an RCA, or leave a note for the team.

• environments

  The organization's sources (Kubernetes clusters, VMs, cloud accounts, connected tools), their health, the environments they are labelled with, and the latest infrastructure snapshot of one source. Use when the person asks what is connected, how one environment is doing, or needs an environment id fo

• incidents

  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.

• investigate

  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.

• knowledge

  What RubixKube has recorded about the organization's systems and history: the knowledge graph of resources, incidents, RCAs, changes and people. Use when the person asks about a service's history, who worked on something, what fails most, or any question whose answer is in past incidents rather than

• rca

  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.

• status

  One overview of what RubixKube sees: sources and their health, open incidents by severity, Tasks waiting for someone, RCAs finished in the last day. Use when the person asks what's going on, what needs attention, how production is, or wants a morning summary.

• tasks

  Tasks are the Fixes and Follow-ups an RCA proposes or a person adds. List them, read one, create one, rename or reprioritise, move between statuses, assign. Use when the person asks what to work on, about action items or fixes, or wants to create, assign or close a Task.

Subagents (1)

• rubixkube-investigator

  Read-only investigator for one RubixKube incident. Use when the person wants a thorough look at an incident without changing anything: it reads the incident, its RCA and evidence, the comments and the environment snapshot, and reports back. It never closes, creates or comments.

MCP servers (1)

• rubixkube

  connects to: https://mcp.rubixkube.ai/mcp

Similar plugins