Searching Mlflow Docs

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

Searches and retrieves MLflow documentation from the official docs site. Use when the user asks about MLflow features, APIs, integrations (LangGraph, LangChain, OpenAI, etc.), tracing, tracking, or requests to look up MLflow documentation. Triggers on "how do I use MLflow with X", "find MLflow docs for Y", "MLflow API for Z".

Instructions onlyResearch & Analysis

AI-generated overview

Retrieves MLflow documentation from the official docs site by fetching the llms.txt index and target markdown pages.

What it does: This skill defines a two-step workflow for looking up MLflow documentation: first fetching the official llms.txt index to locate relevant page paths, then fetching the corresponding markdown file. It presents results with verbatim code examples rather than summaries. It also lists anti-patterns such as avoiding HTML files, web search, versioned paths, guessed URLs, and external sources.
When to use it: Use it when a user asks about MLflow features, APIs, integrations, tracing, or tracking, or requests a lookup of MLflow documentation. It fits queries phrased as how to use MLflow with a given tool, finding MLflow docs for a topic, or locating the MLflow API for something.
Requirements: Requires network access to mlflow.org and a web-fetch capability for retrieving llms.txt and markdown documentation pages. No scripts, packages, or credentials are included.

MLflow Documentation Search

Workflow

Fetch https://mlflow.org/docs/latest/llms.txt to find relevant page paths
Fetch the .md file at the identified path
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.")

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.")

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.

Source and attribution

Source:mlflow/skillsinsearching-mlflow-docsat commitc55c665

License: No license

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

Report or request removal

Searching Mlflow Docs

MLflow Documentation Search

Workflow

Step 1: Fetch llms.txt Index

Step 2: Fetch Target Documentation

Anti-Patterns

Source and attribution

More from mlflow/skills

Retrieving Mlflow Traces

Mlflow Agent

More in Research & Analysis

Sector Overview

Sector Overview

Idea Generation

Competitive Analysis

Equity Research

Sector Overview