Download for macOS
Skill

searching-mlflow-docs

@mlflow Updated 2026-10-23

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

Install

With your agent

Install OMGSkills skill "mlflow/skills:searching-mlflow-docs" into this agent's normal skills directory: use the OMGSkills MCP get_skill tool, install only the pinned_install commit and path, verify SKILL.md against pinned_install.skill_md_sha, and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.

Manual command

git clone https://github.com/mlflow/skills /tmp/skills && ln -s /tmp/skills/searching-mlflow-docs ~/.claude/skills/searching-mlflow-docs

From README

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 Step 2: Fetch Target Documentation Use the path from Step 1, always with .md extension: 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.