Skip to main content
skill CX Codex

mlflow-agent — Claude Code skill: MLflow workflow dispatcher

Reads an MLflow request and invokes the right sub-skill for you: tracing, evaluation, agent debugging or docs lookup. Useful when you don't want to memorize sub-skill names.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add mlflow/skills --skill mlflow-agent -a claude-code
Open on GitHub

What mlflow-agent does

This skill is a dispatcher. It reads the request and picks a sub-skill: instrumentation goes to instrumenting-with-mlflow-tracing, a failing agent to debug-agent, behaviour changes to fix-agent-issue, scoring to agent-evaluation. Then it invokes that skill through the Skill tool.

It never does the work itself — that rule is explicit. One clarifying question is allowed, then it hands off. Ask for evaluation and tracing together and tracing runs first. A debugging request for an already instrumented agent is not sent back to tracing setup.

The routing table covers trace debugging, chat session analysis, trace retrieval, metrics and costs, onboarding, and docs or API questions. The skill carries disable-model-invocation: true, so you call it yourself. Installing it alone gets you little: without the sub-skills from the same repository there is nowhere to route the task.

What it helps with

  • pick the right MLflow sub-skill for a given task
  • start tracing an agent without digging through setup docs
  • find out why an agent fails or answers badly
  • pull metrics and cost numbers out of traces
  • look up an MLflow API answer in the docs

Example prompts for the agent

  • add mlflow to my project
  • evaluate my agent and show me the metrics
  • figure out why my agent fails on this request

How to install mlflow-agent

1Skills CLI (Vercel)

npx skills add mlflow/skills --skill mlflow-agent -a claude-code

2Manually: put the files in place

~/.claude/skills/mlflow-agent/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/mlflow-agent/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about mlflow-agent

How do I install mlflow-agent in Claude?

Run npx skills add mlflow/skills --skill mlflow-agent -a claude-code. The skill file lands at ~/.claude/skills/mlflow-agent/SKILL.md.

What does mlflow-agent do?

It classifies an MLflow request and routes it to a dedicated sub-skill: tracing, evaluation, agent debugging, trace or chat session analysis, metrics, or documentation. It performs no work on its own.

Can I install mlflow-agent on its own?

It routes to sub-skills from the mlflow/skills repository, so on its own the dispatcher has nowhere to send the task.

Source text

SKILL.md · Apache-2.0
---
name: mlflow-agent
description: >
  Master dispatcher for all MLflow workflows. Use this skill when the user wants to do
  anything with MLflow — tracing, evaluating, debugging, or improving an agent.
  Routes to the right MLflow sub-skill automatically.
  Triggers on: "use mlflow", "help with mlflow", "mlflow agent", "add mlflow to my project",
  "trace my agent", "evaluate my agent", or any MLflow task without a specific skill in mind.
disable-model-invocation: true
---

# MLflow Agent

Master dispatcher for MLflow workflows. Reads user intent and invokes the right sub-skill.

## Step 1: Identify the workflow

Use the user's request to choose the relevant skill. Ask at most one clarifying question
if the intent is unclear.

## Step 2: Dispatch

- Tracing / instrumentation → `instrumenting-with-mlflow-tracing`
- Debug or explain an agent failure → `debug-agent`
- Fix or change an agent's behavior → `fix-agent-issue`
- Evaluation / scoring → `agent-evaluation`
- Debug a trace → `analyze-mlflow-trace`
- Debug a chat session → `analyze-mlflow-chat-session`
- Search traces → `retrieving-mlflow-traces`
- Metrics / costs → `querying-mlflow-metrics`
- Getting started → `mlflow-onboarding`
- Docs / API questions → `searching-mlflow-docs`

Invoke the matched skill using the Skill tool.

## Key Rules

- Never do the work yourself — always dispatch to the appropriate sub-skill
- One clarifying question maximum before dispatching
- If the user says "evaluate AND trace", dispatch tracing first, then evaluation
- Do not route an already-instrumented debugging request back to tracing setup
- If the user's request spans multiple skills, handle them in logical order (setup → instrument → evaluate)

© mlflow · Apache-2.0 · mlflow/skills

Similar skills

Everything for AI and ML →

From the same set8

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor