Mintlify Docs
9 source-backed GrowthDex tactics connected to Mintlify Docs.
How to use this evidence
Review the linked source and the reported context before treating any tactic as a recommendation. The source hub is a research path, not a promise that the reported outcome will transfer unchanged to your market.
Tactics from Mintlify Docs
Agent-skills index for multi-workflow products
If the product has several workflows, publish separate skill files plus a `/.well-known/agent-skills/index.json` manifest instead of forcing one giant capability blob.
Agent-skills manifest with sha256 integrity
Publish `/.well-known/agent-skills/index.json` with a digest for each skill so agents can verify they fetched the right instructions before they act on them.
llms discovery headers on every page
Add `Link` and `X-Llms-Txt` headers to normal page responses so an agent can find your machine-readable corpus before it starts crawling blindly.
llms-full single-file context export
Publish an `llms-full.txt` file that bundles the important documentation corpus into one fetch for agents that work better with a single large context payload.
One-command skill install from docs URL
Teach users to install the product's skill straight from the docs URL with one command so discovery turns into first use while intent is still warm.
Reverse-proxy forwarding for agent skill paths
If docs sit behind a proxy or custom domain, forward `/skill.md`, `/.well-known/skills/*`, and `/.well-known/agent-skills/*` instead of letting the discovery layer die at the edge.
Root skill.md for product capability discovery
Publish a root `/skill.md` that tells agents what your product can do, which inputs it needs, and which constraints matter instead of forcing them to infer capabilities from scattered docs.
Skill frontmatter with compatibility and tool constraints
Use `skill.md` frontmatter to tell agents which environment assumptions matter and which tools are allowed before they start making things up.
Well-known llms aliases for agent compatibility
Serve `/.well-known/llms.txt` and `/.well-known/llms-full.txt` alongside the root files so agents that follow the well-known convention can discover your corpus without guessing.
Apply this with an operator
Apply evidence from Mintlify Docs to your market context.