Skip to content
Fixter Docs
↑↓ Select⏎ OpenEsc Close

Claude Code plugin

The Fixter plugin adds a guided onboarding command to Claude Code, plus skills for instrumenting a project, reviewing its logging, configuring alerts, and querying telemetry. It is the setup path described in the Onboarding.

Install

Section titled “Install”

In Claude Code, run these one at a time (Claude Code takes one slash command per paste):

/plugin marketplace add fixter-dev/fixter-skills
/plugin install fixter@fixter-skills

Then connect the MCP server, which is what lets the plugin provision credentials and verify telemetry:

claude mcp add --transport http fixter https://mcp.fixter.dev/mcp

Restart Claude Code, authenticate with /mcp, and run /reload-plugins. Most commands degrade to manual instructions without the MCP connection, but alert setup requires it.

The command and the skills

Section titled “The command and the skills”

The plugin ships one slash command and four skills. /fixter:onboard is the command, and it walks the four skills in order. Each skill also runs on its own when you describe that task to your agent, no slash command needed: the trigger phrases below are what the agent matches on.

CommandWhat it does
/fixter:onboardGuided setup end to end: instrumentation, then logging review, then alerts
SkillAsk your agent something likeWhat it does
otel-setup”instrument this for Fixter”Detects your stack and adds OpenTelemetry instrumentation
logging-review”review my logging”Reviews your logging and suggests improvements
alert-setup”set up Fixter alerts”Works out which flows matter and creates alert rules
diagnose”why is checkout failing?”Queries your telemetry to investigate an issue

Onboarding

Section titled “Onboarding”

/fixter:onboard runs the four skills in order and records progress in .fixter/onboarding-state.json, so it resumes where it stopped and can span several sessions. It is worth running more than once: instrumentation has to soak before alert thresholds can be calibrated, so the alert stage often defers on the first pass.

Instrumentation

Section titled “Instrumentation”

The otel-setup skill scans for build files to identify the language and framework, then adds the matching OpenTelemetry packages and environment variables. It covers Java and Kotlin, JavaScript and TypeScript, Python, PHP, Go, Rust, Ruby, and .NET.

You end up sending traces, metrics, and logs, plus LLM spans if your application calls a model API. Logs take one step more than traces: either a log bridge from your existing logging library, or shipping the logs you already write as JSON. Telemetry covers what each signal is for and what is not included.

Other cases it handles:

  • If the project already has OpenTelemetry, it verifies the configuration points at Fixter instead of replacing it.
  • If Datadog, New Relic, Dynatrace, or Elastic APM is already present, it can export to both while you migrate.
  • On Kubernetes it installs the published Fixter collector chart, which brings pod logs and cluster metrics into Fixter with no application changes at all. The environment variables then add your application’s own traces and logs on top. The chart parses JSON pod logs for severity and trace correlation, and auto-routes common database logs (Postgres, MySQL, Kafka and others).

If you sample, sample traces only. Log volume is handled with log levels, not sampling.

Your API key is provisioned through a one-time link that expires after 24 hours. It does not appear in the chat and is not written into your repository.

If the plugin does not work

Section titled “If the plugin does not work”
  • /fixter:onboard does not appear, or a skill never triggers. The plugin did not load. Run /reload-plugins, or restart Claude Code.
  • A skill says the MCP is not connected. It checks for tools such as get_ingestion_credentials. Add the server as above, restart Claude Code, then authenticate with /mcp.
  • Alert setup defers instead of creating rules. Expected on a service with little history. Re-run it after a day, once enough logs have accumulated.

Still stuck? Email info@fixter.dev and one of our founders will help you fix your problem asap.

Section titled “Related”