/kubit-report, that tells your coding agent how to use the Kubit MCP server for one kind of task. You can also describe the task in plain language, and the agent picks the matching skill.
When to use
Install the plugin
The Kubit plugin installs the skills and adds the Kubit MCP server to Claude Code, Cursor or both./kubit-help to check that the skills loaded. Connect your AI assistant covers the sign-in.
Requirements
/kubit
/kubit is the plain-language entry point. It reads your question and hands it to one skill, or runs an investigation across several. Use it when you don’t know which skill fits, or when the question is “why did this change?”.
How it works
Examples
/kubit why did errors spike on Tuesday?
“Ask Kubit to show failed checkout traces since yesterday”
/kubit-connect
/kubit-connect signs you in to the Kubit MCP server and picks the organization and workspace the other skills work in. Other skills call it for you when they need a workspace, so you run it yourself mainly to switch.
How it works
Example workspaces are read-only and show
[example: read-only, cannot mint api key] next to their name. To send traces, use a workspace you created. /kubit-connect doesn’t create workspaces. /kubit-integrate does.
Examples
/kubit-connect
/kubit-connect switch workspace staging
/kubit-report
/kubit-report finds, opens and creates Kubit reports. It builds the report types the MCP server supports: Query, Funnel, Path, Retention, Inspection and Agent flow. MCP tools reference lists them.
How it works
When your wording could mean an existing report or a new one,
/kubit-report searches first. It doesn’t build several reports in one turn without asking. Every report comes back as a link to the report in Kubit.
When a report shows errors or a regression, /kubit-report suggests /kubit-blame but doesn’t run it. When the rows are traces, sessions or users, it suggests /kubit-inspect to drill in.
Examples
/kubit-report build a funnel for user query, intent classification, tool call, response
/kubit-report create a weekly retention report for users whose first session had zero errors
/kubit-inspect
/kubit-inspect finds specific users, sessions, traces and events, and moves between them. A user has sessions, a session has traces and a trace has events, so you can start at any level and drill down. Use /kubit-report for trends over time.
How it works
/kubit-inspect passes your wording to the MCP server’s inspect tool, which returns the total number of matches, up to 5 sample rows and a CSV export of every match.
After the results,
/kubit-inspect offers the next level down, such as the traces in a session. When the results include failures, it suggests /kubit-blame.
Examples
/kubit-inspect sessions where token cost > $5 in the last 2 hours
/kubit-inspect p95 latency for failed traces today
/kubit-blame
/kubit-blame finds the commits most likely to have caused a trace regression, such as an error spike, sentiment drift or more escalations. It works on traces you already found with /kubit-report or /kubit-inspect, and never fetches metrics itself.
How it works
- Detects your tracing setup. It scans your repo for the tools that shape your spans and asks you to confirm what it found.
- Maps traces to code. It matches agent names, tool names and prompts from the traces to files and lines in your repo. You confirm any match it isn’t sure of.
- Picks the time window. It uses the window from the report or asks you for one.
- Ranks commits. It runs
git logover the mapped code and ranks commits in the window by how close they are in time, how much of the mapped code they touch and how large the change is.
Examples
/kubit-blame why did trace t_abc fail? What changed?
/kubit-blame find the commit behind the sentiment drop in the report I just ran
/kubit-integrate
/kubit-integrate wires Kubit tracing into a Python or Node repo. It detects your tracing setup, creates or picks a workspace, writes an API key to your env file and adds the Kubit SDK. Agent plugin covers it step by step.
Examples
/kubit-integrate
/kubit-integrate turn on Kubit for this Next.js app
/kubit-help
/kubit-help lists the Kubit skills, explains one in detail or suggests the skill for a task you describe. It works before you sign in.
It also sends a bug report, question or feedback to Kubit support. The request includes context from your conversation and project, such as your language, framework, Kubit SDK version, workspace and recent errors. The skill waits about 20 seconds for a reply, then tells you to check your email.
Examples
/kubit-help what does /kubit-blame do?
/kubit-help report a bug: my funnel report fails with a validation error
/kubit-update
/kubit-update updates the plugin. It reads your installed version, checks npm for a newer one, shows the changelog since your version and asks you to confirm before it runs the installer. Restart your client after the update. It works before you sign in.
Examples
/kubit-update
“Check if there’s a new version of Kubit”
Investigation chain
The investigation chain answers “why did this metric change?” in three steps./kubit runs it, starting at the step your question already covers:
The chain carries the workspace, time window, report links and trace IDs from one step to the next. It asks before it runs
/kubit-blame, and stops when a step answers the question or finds no results.
Examples
/kubit why did errors spike on Tuesday?
“Ask Kubit what regressed after Friday’s deploy”
Full-dataset analysis
Full-dataset analysis answers questions about every row of a report or inspection, not only the sample the MCP server returns./kubit-report and /kubit-inspect run it when the result has a CSV export link.
How it works
The skill starts an analyst subagent. The subagent downloads the CSV export, analyzes it with pandas and returns a headline, a compact table and the notable findings. It runs Python throughuv when it’s installed, or in a temporary Python 3 environment otherwise.
The downloaded data stays on your machine, under /tmp/kubit-dataset/, one dataset per workspace. A follow-up question about the same data reuses it, and the next new query replaces it.
Examples
/kubit-inspect top 10 users by total token cost last week
“Which of those traces had the longest tool calls?”
Related
- Connect your AI assistant: sign in to the Kubit MCP server in Claude Code and Cursor.
- MCP tools reference: the tools the skills call and their limits.
- Agent plugin: wire tracing into a repo with
/kubit-integrate.