Modelopt Accessing Mlflow
Query and browse evaluation results stored in MLflow. Use when the user wants to look up runs by invocation ID, compare metrics across models, fetch artifacts (configs, logs, results), or set up the MLflow MCP server. ALWAYS triggers on mentions of MLflow, experiment results, run comparison, invocation IDs in the context of results, or MLflow MCP setup.
mkdir -p ~/.claude/skills/modelopt-accessing-mlflow && curl -fsSL 'https://raw.githubusercontent.com/NVIDIA/Model-Optimizer/main/skills/modelopt-accessing-mlflow/SKILL.md' -o ~/.claude/skills/modelopt-accessing-mlflow/SKILL.md
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Modelopt Accessing Mlflow when an AI agent needs a reusable SKILL.md workflow for this job: Query and browse evaluation results stored in MLflow. Use when the user wants to look up runs by invocation ID, compare metrics across models, fetch artifacts (configs, logs, results), or set up the MLflow MCP server. ALWAYS triggers on mentions of MLflow, experiment results, run comparison, invocation IDs in the context of results, or MLflow MCP setup.
When not to use it
Skip Modelopt Accessing Mlflow when the task is outside the productivity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/modelopt-accessing-mlflow && curl -fsSL 'https://raw.githubusercontent.com/NVIDIA/Model-Optimizer/main/skills/modelopt-accessing-mlflow/SKILL.md' -o ~/.claude/skills/modelopt-accessing-mlflow/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/modelopt-accessing-mlflow/SKILL.md. For a shared project, commit the folder at .claude/skills/modelopt-accessing-mlflow/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Modelopt Accessing Mlflow skill for this task: Use Modelopt Accessing Mlflow when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
71/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeinferred
The skill text mentions Claude or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Accessing MLflow
## MCP Server
[mlflow-mcp](https://github.com/kkruglik/mlflow-mcp) gives agents direct access to MLflow — query runs, compare metrics, browse artifacts, all through natural language.
## ID Convention
When the user provides a hex ID (e.g. `71f3f3199ea5e1f0`) without specifying what it is, assume it is an **invocation_id** (not an MLflow run_id). An invocation_id identifies a launcher invocation and is stored as both a tag and a param on MLflow runs. One invocation can produce multiple MLflow runs (one per task). You may need to search across multiple experiments if you don't know which experiment the run belongs to.
## Querying Runs
```python # Find runs by invocation_id MLflow:search_runs_by_tags(experiment_id, {"invocation_id": "<invocation_id>"})
# Query for example model/task runs MLflow:query_runs(experiment_id, "tags.model LIKE '%<model>%'") MLflow:query_runs(experiment_id, "tags.task_name LIKE '%<task_name>%'")
# Get a config from run's artifacts MLflow:get_artifact_content(run_id, "config.yml")
# Get nested stats from run's artifacts MLflow:get_artifact_content(run_id, "artifacts/eval_factory_metrics.json") ```
NOTE: You WILL NOT find PENDING, RUNNING, KILLED, or FAILED runs in MLflow! Only SUCCESSFUL runs are exported to MLflow.
## Workflow Tips
When comparing metrics across runs, fetch the data via MCP, then run the computation in Python for exact results rather than doing math in-context:
```bash uv run --with pandas python3 << 'EOF' import pandas as pd # ... compute deltas, averages, etc. EOF ```
## Artifacts Structure
``` <harness>.<task>/ ├── artifacts/ │ ├── config.yml # Fully resolved config used during the evaluation │ ├── launcher_unresolved_config.yaml # Unresolved config passed to the launcher │ ├── results.yml # All results in YAML format │ ├── eval_factory_metrics.json # Runtime stats (latency, tokens count, memory) │ ├── report.html # Request-Response Pairs samples in HTML format (if enabled) │ └── report.json # Request-Response Pairs samples in JSON format (if enabled) └── logs/ ├── client-*.log # Evaluation client ├── server-*-N.log # Deployment per node ├── slurm-*.log # Slurm job └── proxy-*.log # Request proxy ```
## Troubleshooting
If the MLflow MCP server fails to load or its tools are unavailable:
1. **`uvx` not found** — install [uv](https://docs.astral.sh/uv/getting-started/installation/): ```bash curl -LsSf https://astral.sh/uv/install.sh | sh ``` 2. **MCP server not configured** — add the config and restart the agent:
**For Claude Code** — add to `.claude/settings.json` (project or user level), under `"mcpServers"`: ```json "MLflow": { "command": "uvx", "args": ["mlflow-mcp"], "env": { "MLFLOW_TRACKING_URI": "https://<your-mlflow-server>/" } } ```
**For Cursor** — edit `~/.cursor/mcp.json` (Settings > Tools & MCP > New MCP Server): ```json { "mcpServers": { "MLflow": { "command": "uvx", "args": ["mlflow-mcp"], "env": { "MLFLOW_TRACKING_URI": "https://<your-mlflow-server>/" } } } } ```
Intended uses
- Use Modelopt Accessing Mlflow when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.