DreamLake

LLM-Readable Docs

These docs are built to be read by agents as easily as by people. Every page has a markdown twin, and the whole corpus is published in the formats LLM tooling already looks for — so you can point your agent at ML-Dash and have it answer accurately. The ML-Dash pages are part of the DreamLake docs, so they ship in the same site-wide files.

Fetch a single page

Append .md to any docs URL to get the raw markdown — no nav, no chrome:

bash
curl https://docs.dreamlake.ai/ml-dash/guides/experiments.md

Every page also advertises its markdown twin in the HTML head:

html
<link rel="alternate" type="text/markdown" href="/ml-dash/guides/experiments.md" />

The whole site, two ways

  • /llms.txt — a short, linked index of every page (llmstxt.org standard). The entry point an agent reads first to decide what to fetch. ML-Dash pages are listed alongside the rest of the DreamLake docs.
  • /llms-full.txt — every page concatenated into one markdown file. Drop the entire product into a context window in a single request.

Where the skills get it

The DreamLake agent skills do not bundle a copy of these docs; they fetch them. Each skill in the public dreamlake-skills repository lists the docs URLs it needs, and that repository's CI pulls the .md twins above into the skill's reference/ directory on every nightly release, so an installed skill carries exactly the markdown curl returns. Install skills with the dl CLI — dl init once, then dl skill install <name> — or copy them from the latest release tarball; see Skills. To give an agent the ML-Dash pages directly, point it at /llms.txt or at the .md twins it needs.

Always current. Every surface above — the .md pages and both llms files — is generated from the same source on each deploy, so none of them can drift from what you read on the site. The first line of every .md names the page URL, the docs version and the git hash it was built from: <!-- source: https://docs.dreamlake.ai/ml-dash/guides/experiments @ 0.1.101 b50f82d3 -->.