mlflow
Skills for tracing, evaluating, and improving AI agents with MLflow. Supports the full agent improvement loop: instrument → trace → evaluate → iterate → validate.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Badge for your README
Markdown
[](/listings/mlflow--skills)HTML
<a href="/listings/mlflow--skills"><img src="/api/listings/mlflow--skills/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
Using `skills` installer
npx skills add mlflow/skills
Direct Installation from Source
git clone https://github.com/mlflow/skills.git cp -r mlflow-skills/* ~/.claude/skills/
Change the `~/.claude/skills/` directory to the appropriate location for your coding agent, e.g., `~/.codex/skills/` for Codex.
Project-Level Installation
Add skills to your project for team sharing:
cd your-project git clone https://github.com/mlflow/skills.git .skills/mlflow # Or as a submodule: git submodule add https://github.com/mlflow/skills.git .skills/mlflow
---
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
.claude-plugin/plugin.json · Manifest · 25 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
- {
- "name": "mlflow",
- "displayName": "MLflow Skills",
- "description": "Skills for tracing, evaluating, and improving AI agents with MLflow. Supports the full agent improvement loop: instrument → trace → evaluate → iterate → validate.",
- "version": "1.0.0",
- "author": {
- "name": "MLflow Team"
- },
- "homepage": "https://github.com/mlflow/skills",
- "skills": [
- "./mlflow-agent",
- "./mlflow-onboarding",
- "./mlflow-docs",
- "./mlflow-sagemaker",
- "./mlflow-trace-instrumentation",
- "./mlflow-trace-retrieval",
- "./mlflow-trace-analysis",
- "./mlflow-trace-metrics",
- "./mlflow-evaluation",
- "./mlflow-agent-improvement"
- ],
- "hooks": "./hooks/hooks.json",
- "categories": ["observability", "evaluation", "ai-agents"],
- "minClaudeCodeVersion": "2.0.0"
- }
README.md · README · 275 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
- 
- # MLflow Skills for Coding Agents
- > Turn your favorite coding agent into an LLMOps expert with MLflow skills.
- Build, debug, and evaluate GenAI applications with confidence. These skills give your AI coding assistant deep knowledge of MLflow's tracing, evaluation, and observability features.
- Works with any coding agent that support Skills, including [Claude Code](https://docs.anthropic.com/en/docs/claude-code), [Cursor](https://www.cursor.com/), [Codex CLI](https://github.com/openai/codex), [Gemini CLI](https://github.com/google-gemini/gemini-cli), and [OpenCode](https://github.com/opencode-ai/opencode).
- ## Why MLflow Skills?
- Building production-ready AI agents is hard. You need observability to understand what your agent is doing, evaluation to measure quality, and debugging tools when things go wrong. MLflow provides SDKs and best practices for all of these operations, and with skills we bring them directly into the environment where LLM agent development happens. Now you can go to your favorite coding agent and just ask:
- - *"Add tracing to my LangChain app"* → Instruments your code automatically
- - *"Why did this trace fail?"* → Analyzes spans, finds root causes, suggests fixes
- - *"Evaluate my agent's accuracy"* → Sets up datasets, scorers, and runs evaluation
- - *"Improve my agent and verify your work"* → Gives the coding agent reproducible and verifiable mechanism with MLflow eval to hill climb on quality
- - *"Show me token usage trends"* → Queries metrics and analyze trends
- ---
- ## Available Skills
- | Skill | Description |
- |-------|-------------|
- | **mlflow-agent** | Routes broad MLflow requests to the right skill. |
- | **mlflow-onboarding** | Configures MLflow for GenAI or traditional ML. |
- | **mlflow-docs** | Searches official MLflow documentation. |
- | **mlflow-sagemaker** | Connects to SageMaker Managed MLflow. |
- | **mlflow-trace-instrumentation** | Instruments Python and TypeScript applications. |
- | **mlflow-trace-retrieval** | Finds and filters traces. |
- | **mlflow-trace-analysis** | Analyzes traces, agent failures, and multi-turn sessions. |
- | **mlflow-trace-metrics** | Queries aggregate trace metrics. |
- | **mlflow-evaluation** | Designs scorers and runs GenAI evaluation. |
- | **mlflow-agent-improvement** | Fixes agent behavior with trace-grounded regression tests. |
- ---
- ## Installation
- ### Using `skills` installer
- ```bash
- npx skills add mlflow/skills
- ```
- ### Direct Installation from Source
- ```bash
- git clone https://github.com/mlflow/skills.git
- cp -r mlflow-skills/* ~/.claude/skills/
- ```
- Change the `~/.claude/skills/` directory to the appropriate location for your coding agent, e.g., `~/.codex/skills/` for Codex.
- ### Project-Level Installation
- Add skills to your project for team sharing:
- ```bash
- cd your-project
- git clone https://github.com/mlflow/skills.git .skills/mlflow
- # Or as a submodule:
- git submodule add https://github.com/mlflow/skills.git .skills/mlflow
- ```
- ---
- ## Auto-Suggestion Hook (Optional)
- The `hooks/` directory contains a `UserPromptSubmit` hook that automatically detects MLflow-related patterns in your prompts and surfaces the right skill before the agent responds — no need to remember which skill does what.
- ### Install the Hook
- **Step 1:** Copy the hook somewhere permanent:
- ```bash
- cp hooks/mlflow-suggest-hook.py ~/.claude/hooks/mlflow-suggest-hook.py
- ```
- **Step 2:** Add it to your Claude Code settings (`~/.claude/settings.json`):
- ```json
- {
- "hooks": {
- "UserPromptSubmit": [
- {
- "type": "command",
- "command": "python3 ~/.claude/hooks/mlflow-suggest-hook.py"
- }
- ]
- }
- }
- ```
- **Step 3:** Start a new session. When you ask something like *"Add tracing to my app"*, you'll see:
- ```
- 💡 Use the `mlflow-trace-instrumentation` skill to add MLflow tracing.
- ```
- See [`hooks/README.md`](hooks/README.md) for the full keyword-to-skill mapping and troubleshooting.
- ---
- ## Quick Examples
- ### Instrument Your App with Tracing
- ```
- > Add MLflow tracing to my OpenAI app
- The coding agent will:
- 1. Detect your LLM framework
- 2. Add the right autolog call
- 3. Configure experiment tracking
- 4. Verify traces are being captured
- ```
- ### Debug a Failed Trace
- ```
- > Analyze trace tr-abc123 — why did it return the wrong answer?
- The coding agent will:
- 1. Fetch the trace and examine all spans
- 2. Check assessments for quality signals
- 3. Walk the span tree to find the failure point
- 4. Correlate with your codebase to identify root cause
- 5. Suggest specific fixes
- ```
- ### Evaluate Agent Quality
- ```
- > Set up evaluation for my customer support agent
- The coding agent will:
- 1. Discover existing evaluation datasets
- 2. Help create test cases if needed
- 3. Select appropriate scorers (correctness, relevance, etc.)
- 4. Run evaluation and analyze results
- 5. Generate improvement recommendations
- ```
- ### Query Usage Metrics
- ```
- > Show me token usage trends for the last 7 days
- The coding agent will:
- 1. Query the MLflow metrics API
- 2. Generate time-series breakdowns
- 3. Identify cost spikes or anomalies
- 4. Suggest optimization opportunities
- ```
- ---
- ## Requirements
- - **MLflow 3.8+** (Instructions and code examples are tested with MLflow 3.8)
- ---
- ## Contributing
- We welcome contributions! Here's how to help:
- 1. **Report issues** — Found a skill giving incorrect advice? [Open an issue](https://github.com/mlflow/mlflow-skills/issues)
- 2. **Suggest improvements** — Have ideas for better workflows? We'd love to hear them
- 3. **Add new skills** — See [skill authoring best practices](https://platform.claude.com/docs/en/agents-and-tools/agent-skills/best-practices) and file a pull request
- ### Testing skill behavior
- The test code has two layers: live scenarios exercise skills through Claude; local verifier tests check that the graders accept valid work and reject broken work.
- ```text
- tests/
- configs/
- setup/ # Onboarding, docs, backend prerequisites
- tracing/ # Instrumentation, retrieval, diagnosis, metrics
- evals/ # Evaluation, scorers, alignment, verified repair
- judges/ # Graders used by live scenarios
- scripts/ # Scenario setup and seeded application data
- verifiers/ # Local regression tests for graders and harness
- test_skill.py # Existing YAML scenario runner
- ```
- Config paths for setup scripts and judges remain relative to the repository root. Run live scenarios from the repository root using their grouped paths below; the former flat config paths have moved.
- The YAML scenarios in `tests/configs/` run a real Claude Code participant in a fresh project and Claude home, install the selected repository skills plus the MLflow tracing plugin, and verify its work against a real MLflow server. Each scenario checks a successful native skill invocation or complete skill read, plus an observable task outcome. Task-only prompts test discovery among the skills installed for each scenario. No prompt names a skill or instructs the agent to load one. The dispatcher currently disables automatic invocation, so its required-loading check can expose that discovery limitation. Merely mentioning an API or reporting success does not pass.
- Validated with MLflow 3.17.1. Requires an authenticated `claude` CLI, Git, Node/npm (for Claude tracing and TypeScript), and `uv`. Run a scenario:
- ```sh
- uv run --with mlflow==3.17.1 --with litellm --with pytest --with langgraph --with langchain-core \
- python tests/test_skill.py tests/configs/evals/evaluation_nested.yaml
- ```
- The original general evaluation scenario remains `agent_evaluation.yaml`: it clones `REPO_URL` and checks datasets, registered scorers, evaluation results, application traces, and both evaluation/tracing skill reads. Run it with `REPO_URL=<repository-url>` as a CLI override. The separate `evaluation_nested.yaml` is a deterministic local regression fixture.
- | Config field | Meaning |
- |---|---|
- | `skills` | Installed skills; all are required to load by default. |
- | `required_skills` | Optional subset when other installed skills are only helpers. Sent to the verifier, not the participant. |
- | `judges` | Checks of the participant's actions and actual application results. |
- | `tracking_uri` | Optional external server. Omit for a fresh local server. |
- | `mlflow_port` | Optional fixed-port override. Omit to select a free local port. |
- Default timeouts, `keep_workdir: true`, and `test_runs_dir: /tmp` need not be repeated. Fixtures contain application context, data, and actual deliverable interfaces; prompts are short user requests. Conversational answers are checked by an MLflow judge using `JUDGE_MODEL` (or its default), alongside backend and tool-evidence checks; participants need not write grading JSON. Specialized regression cases still have explicit operational constraints, such as approved smoke inputs and an unavailable backend.
- | Skill/workflow | Scenarios | Observable checks |
- |---|---|---|
- | Onboarding | `onboarding_existing`, `onboarding_unavailable`, `onboarding_classic_ml` | Reuse configuration and experiment; persist smoke trace; report a real connection failure without resetting setup; reload an actual sklearn model and verify held-out predictions |
- | Dispatcher | `dispatcher_scorer` | Load the dispatcher and scorer skill; execute a native scorer against held-out empty/missing/null/valid answers |
- | Documentation | `docs_classic_ml` | Fetch official docs and explain a runnable classic-ML example |
- | SageMaker | `sagemaker_prerequisites` | Execute prerequisite checks; stop when plugin/credentials are missing |
- | Instrumentation | `tracing_test`, `tracing_typescript`, `langgraph_autolog_guidance` | Rerun the delivered entrypoint and require fresh Python/TypeScript inputs and outputs; native graph/model spans without redundant tracing |
- | Trace retrieval | `trace_retrieval` | Exact matching IDs amid time, status and tag distractors |
- | Single-trace diagnosis | `trace_analysis` | Identify the actual failing child span and its timeout inputs |
- | Session diagnosis | `session_analysis` | Ordered turns, first incorrect answer, propagation, evidence, and failed-scorer exclusion |
- | Aggregate metrics | `trace_metrics` | Exact counts and token sums from the real metrics endpoint; distinguish unsupported endpoints from other failures |
- | Diagnosis versus repair | `diagnosis_only`, `agent_debug_trace_first` | Diagnosis preserves source; repair follows trace evidence and verifies refund/general routing |
- | Evaluation | `evaluation_nested`, `evaluation_precomputed`, `evaluation_dry_run` | Nested predictor kwargs; exact six-row scores and mean; reuse dataset/scorer; never rerun precomputed outputs; verify a scored dry run precedes full evaluation; stop after a failed three-row dry run |
- | Scorer design | `scorer_deterministic_suite`, `scorer_model_criteria` | Execute independent criteria on private malformed/near-miss cases; code, built-in and domain judges; preserve model selection |
- | Judge alignment | `scorer_label_alignment`, `scorer_memalign` | Criterion-specific human labels and train/holdout splits; missing-provider blocker; saved native MemAlign training IDs, participant holdout comparison, and separate verifier holdouts |
- Model-backed scenarios require working provider credentials. Set `TEST_JUDGE_MODEL` for `scorer_model_criteria`; for `scorer_memalign`, also set `TEST_EMBEDDING_MODEL` and add `--with dspy`. The repair scenario's existing LLM judge accepts `JUDGE_MODEL`. No credentials or private endpoint names belong in scenario files. Each run retains `environment.json`, `skill-inventory.json`, `verification.json`, participant transcripts, generated files, and the local MLflow store in its printed work directory. Setup failures and skill failures both return nonzero, with different exit codes.
- To run the local scenarios sequentially, excluding those needing a model provider:
- ```sh
- for config in tests/configs/*/*.yaml; do
- case "$config" in
- *scorer_model_criteria*|*scorer_memalign*|*agent_debug_trace_first*|*agent_evaluation*) continue ;;
- esac
- uv run --with mlflow==3.17.1 --with litellm --with pytest --with langgraph --with langchain-core \
- python tests/test_skill.py "$config" || exit 1
- done
- ```
- Supporting verifier regression checks run without Claude or model calls:
- ```sh
- uv run --with mlflow==3.17.1 --with pytest --with langgraph --with langchain-core --with dspy \
- pytest -q tests/verifiers
- ```
- Expected answers are stored outside the project but remain accessible on the same machine; this is not an adversarial sandbox. Investigation grading also requires observed MLflow retrieval. These scenarios are behavioral regression coverage, not a claim of exhaustive platform coverage or a baseline-versus-treatment comparison. Live SageMaker connection, Databricks UC storage/Review App/online monitoring, GEPA prompt optimization, distributed tracing, and every supported framework still require dedicated environments and scenarios. A successful local run does not verify those integrations. The repository currently has no CI workflow that launches the paid Claude scenarios automatically.
- ### Creating a New Skill
- We recommend using the [skill-creator](https://github.com/anthropics/skills/tree/main/skills/skill-creator) from Anthropic's skills repository as a starting point.
- ---
- ## License
- Apache License 2.0 — see [LICENSE](LICENSE) for details.
- ---
- ## Links
- - 📖 [Read MLflow Documentation](https://mlflow.org/docs/latest/)
- - 📖 [Read MLflow Skills Blog](https://mlflow.org/blog/evaluating-skills-mlflow))
- - ⭐️ [Star MLflow on GitHub](https://github.com/mlflow/mlflow)
- ---
- <p align="center">
- <sub>Built with care for the MLflow community</sub>
- </p>
Version history
v1.0.010/27/2026
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.