Skip to content
Kubit Guide home
Kubit Guide home

Kubit Skills

Kubit Skills act as specialized tools that the Model Context Protocol (MCP) server exposes to your coding agent (like Claude or Cursor). This allows the AI to translate your natural language requests into specific Kubit actions, such as fetching traces or generating reports, by sending structured commands to the Kubit platform.

All of our skills are open sourced and you can find the source code here.

Overview

kubit-connect

  • Establish MCP connection through OAuth

  • Select target org and workspace for the session

❯ /kubit-connect [switch <org|workspace> <id-or-name>]

kubit-help

  • Search documentation

  • Get live support or responses in email

  • Report bugs, provide feedback or ask questions

❯ /kubit-help what does /kubit-blame do?

kubit-integrate

  • Turn on Kubit ingestion by sending LLM traces to Kubit

  • Automatically detect the AI Framework (e.g. Langchain, Vercel AI) and Observability SDK (e.g. Langfuse, Braintrust, Langsmith, Arize), if any, in your project

  • Either piggyback to existing Observability SDK through OTel fan-out, or instrument your LLM calls with Kubit OTel SDK.

❯ /kubit-integrate [API_KEY]

kubit-inspect

  • Find and investigate Kubit entities — users, sessions, traces, and events for Agent Activity, or cohorts/segments from analytics report.

  • Use it to debug failures, drill into specific records, or navigate between related entities.

  • Provides both quick summary and in-depth analysis of the inspection results.

❯ /kubit-inspect errors in the last 6 hours

kubit-report

  • Find, open, create, and modify Kubit analytics reports — for trends, aggregates, and behavior analysis across traces, sessions, intents, costs, and users.

  • Support all report types: Agent Activity / Grid, Query, Funnel, Flow, Retention, Cohort.

  • Provide in-depth analytics insights along with anormally detection

❯ /kubit-report build a funnel for user query → intent classification → tool call → response

kubit-blame

Git blame for agents. Given a problematic trace, error cluster, or metric regression, /kubit-blame finds the recent commit(s) most likely responsible.

❯ /kubit-blame why did trace 2b277458fcb fail — what changed?

kubit-dataset

Coming soon. Add a problematic trace into the Golden Data Set (eval) or test suite in your project to make sure what you have just fixed won't regress in the future.

❯ /kubit-dataset add trace 2b277458fcb

kubit-update

Updates the Kubit plugin to the latest version. Checks npm, shows you what changed, asks for confirmation, and runs the installer.

❯ /kubit-update

Next Steps

Powered by Plain