Searching Mlflow Docs
- 604 installs
- 66 repo stars
- Updated July 30, 2026
- mlflow/skills
searching-mlflow-docs is an agent skill that retrieves current MLflow documentation and verbatim code examples from mlflow.org for developers who need accurate API, tracing, tracking, or third-party integration reference
About
searching-mlflow-docs is a documentation-retrieval skill for the MLflow MLOps platform. It first fetches the official llms.txt index at mlflow.org/docs/latest/llms.txt, identifies the matching page path, then pulls the corresponding Markdown source and returns verbatim code examples for APIs, tracing, experiment tracking, and integrations with LangChain, LangGraph, and OpenAI. Developers reach for searching-mlflow-docs when a coding agent would otherwise hallucinate MLflow APIs or outdated integration patterns. The workflow is read-only against public docs—no local MLflow server required—and triggers on questions like how to use MLflow with a specific framework or where to find an API reference.
- Always starts by fetching the official llms.txt index from mlflow.org/docs/latest/
- Retrieves raw .md source files to guarantee verbatim code blocks
- Prevents outdated or third-party results by never using general web search
- Enforces strict prompt discipline: 'Return all code blocks verbatim. Do not summarize.'
- 5 anti-pattern rules that keep every response accurate and version-current
Searching Mlflow Docs by the numbers
- 604 all-time installs (skills.sh)
- +41 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #1,580 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/mlflow/skills --skill searching-mlflow-docsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 604 |
|---|---|
| repo stars | ★ 66 |
| Last updated | July 30, 2026 |
| Repository | mlflow/skills ↗ |
How do you find current MLflow API docs and examples?
Instantly retrieve accurate, up-to-date MLflow documentation including verbatim code examples for features, APIs, and integrations with LangChain, LangGraph, or O
Who is it for?
Developers wiring MLflow tracking, tracing, or LangChain/LangGraph integrations who need authoritative docs instead of guessed APIs.
Skip if: Developers who need to run experiments, deploy models, or debug a local MLflow server without reading documentation.
When should I use this skill?
The user asks how to use MLflow with a framework, requests an MLflow API reference, or wants official docs for tracing, tracking, or integrations.
What you get
Relevant MLflow doc excerpts, verbatim code blocks, and linked page paths from mlflow.org/docs/latest.
- MLflow doc excerpts
- verbatim code examples
- source page paths
By the numbers
- Uses the official mlflow.org/docs/latest/llms.txt documentation index
- Returns verbatim code examples from Markdown doc pages
Files
MLflow Documentation Search
Workflow
1. Fetch https://mlflow.org/docs/latest/llms.txt to find relevant page paths 2. Fetch the .md file at the identified path 3. Present results with verbatim code examples
Step 1: Fetch llms.txt Index
WebFetch(
url: "https://mlflow.org/docs/latest/llms.txt",
prompt: "Find links or references to [TOPIC]. List all relevant URLs."
)Step 2: Fetch Target Documentation
Use the path from Step 1, always with .md extension:
WebFetch(
url: "https://mlflow.org/docs/latest/[path].md",
prompt: "Return all code blocks verbatim. Do not summarize."
)Anti-Patterns
Do not use `.html` files — Fetch .md source files only.
Do not use WebSearch — Always start from llms.txt; web search returns outdated or third-party content.
Do not use vague prompts — "Extract complete documentation" allows summarization. Use "Return all code blocks verbatim. Do not summarize."
Do not use versioned paths — Always use /docs/latest/, never /docs/3.8/ or other versions unless the user explicitly requests a specific version.
Do not guess URLs — Always verify paths exist in llms.txt before fetching. Never construct documentation paths from assumptions.
Do not follow external links — Stay within mlflow.org/docs. Do not follow links to GitHub, PyPI, or third-party sites.
Do not mix sources — Use only MLflow docs. Do not combine with LangChain docs, OpenAI docs, or other external documentation.
Do not use llms.txt for non-GenAI topics — The llms.txt index covers LLM/GenAI documentation only. For classic ML tracking features, paths may differ.
Related skills
Setup Matt Pocock SkillsScaffold the per-repo configuration that Matt Pocock’s engineering agent skills rely on so they understand the issue tracker, triage labels, and domain documentation la495k196k
Lark AppsConnect Claude, Cursor or custom agents directly to Lark (Feishu) for messaging, document automation, approval workflows and enterprise data access.402k
CavemanSlash token usage by roughly 75% while keeping every technical detail intact when working with Claude Code, Cursor or similar agents.391k94.7k
Lark Skill MakerQuickly turn any Lark/Feishu OpenAPI call or multi-step workflow into a reusable agent skill with its own SKILL.md.386k16k
Running Claude Code Via Litellm CopilotRun Claude Code at a fraction of the cost by routing requests through LiteLLM to the GitHub Copilot Chat API.270k72
Codex PetGenerate a complete Codex Pet spritesheet and metadata from one reference image without needing an OpenAI key or Codex Pro.246k10How it compares
Pick searching-mlflow-docs when you need authoritative, up-to-date MLflow API and integration references instead of general web search or model memory.
FAQ
How does searching-mlflow-docs find MLflow pages?
searching-mlflow-docs fetches https://mlflow.org/docs/latest/llms.txt to list available documentation paths, then retrieves the matching .md source file and surfaces verbatim code examples from the official MLflow docs site.
What MLflow topics does searching-mlflow-docs cover?
searching-mlflow-docs covers MLflow features, APIs, tracing, experiment tracking, and integrations such as LangChain, LangGraph, and OpenAI, returning official documentation excerpts rather than generated summaries.