Mlflow Agent

mlflow/skills/mlflow-agent

by mlflowc55c66586a35f7e3f2a377bfc462ef9791fbc3f4No licenseListed Oct 9, 2026Updated Oct 9, 2026

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.

Instructions onlyAI & Agents
AI-generated overview

Routes MLflow-related requests to the appropriate MLflow sub-skill based on the user's intent.

What it does
This skill acts as a master dispatcher for MLflow workflows. It reads the user's request, maps the intent to a named sub-skill such as tracing, evaluation, debugging, trace retrieval, metrics, onboarding, or documentation search, and then invokes that sub-skill. It asks at most one clarifying question when intent is unclear and does not perform the work itself.
When to use it
Use it when the user wants to do something with MLflow but has not named a specific MLflow skill. It fits requests about tracing, evaluating, debugging, or improving an agent, and general MLflow tasks.
Requirements
No scripts or special tooling are shipped; it requires the ability to invoke other skills, including the named MLflow sub-skills, through a Skill tool.

MLflow Agent

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

Trigger

Use when the user wants to do anything with MLflow but hasn't specified which skill to use.

Process

  1. Read the user's request and identify intent
  2. Map to the appropriate skill:
    • 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
  3. If intent is unclear, ask ONE clarifying question, then dispatch
  4. 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)

Source and attribution

Source:mlflow/skillsinmlflow-agentat commitc55c665

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal