Mlflow Agent

作者 mlflowc55c66586a35f7e3f2a377bfc462ef9791fbc3f4無授權條款收錄於 2026年10月9日更新於 2026年10月9日

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.

僅含說明AI & Agents

AI 產生的概覽

依照使用者意圖將 MLflow 相關請求路由到合適的 MLflow 子技能。

功能: 此技能是 MLflow 工作流程的主調度器。它會讀取使用者請求，將意圖對應到指定的子技能，例如追蹤、評估、除錯、追蹤紀錄檢索、指標、入門或文件搜尋，然後呼叫該子技能。當意圖不明確時，它最多提出一個釐清問題，且本身不執行實際工作。
適用情境: 當使用者想使用 MLflow 但未指定特定 MLflow 技能時使用。它適合有關追蹤、評估、除錯或改進代理的請求，以及一般性的 MLflow 任務。
執行需求: 不隨附指令碼或特殊工具；需要能透過 Skill 工具呼叫其他技能，包括所列的 MLflow 子技能。

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

Read the user's request and identify intent
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
If intent is unclear, ask ONE clarifying question, then dispatch
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)