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.
Why this can grow a startup
A capability file only helps if the agent can actually fetch it. Reverse proxies often preserve the pretty docs URL while quietly dropping newer AI-discovery paths. Forwarding the skill routes keeps the capability layer reachable, which matters because agents often start at the public hostname, not the upstream docs subdomain where the files were first generated.
Company example
Mintlify tells teams using a reverse proxy to forward `/skill.md`, `/.well-known/skills/*`, and `/.well-known/agent-skills/*` to the Mintlify subdomain so agents can still discover the files.
Source and metric
Source: Mintlify Docs · Browse Mintlify Docs tactics
Mintlify documents three exact proxy paths that should be forwarded for skill discovery to work
Source discovered: May 27, 2026
When to use it
Use this when AI Search, Website, Documentation is relevant to agent enablement, technical seo, docs ops and you can run a bounded test with a free budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
Founder checklist
- Read Mintlify Docs and identify what is directly supported.
- Choose one channel context: AI Search, Website, Documentation.
- Define the test around Mintlify documents three exact proxy paths that should be forwarded for skill discovery to work.
- Set an owner, evidence window, and stop condition before launch.
Explore the context
Apply this with an operator
Turn isolated search tactics into a crawlable visibility system tied to demand and proof.