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.
Why this can grow a startup
Discovery is only half the job. After an agent finds the site, it still needs a clean picture of what actions are actually possible. A capability file reduces bad guesses, improves workflow accuracy, and makes the product easier to use from AI tools without stuffing the answer into one long marketing page.
Company example
Mintlify hosts a root `skill.md` file that summarizes product capabilities, required inputs, workflows, integrations, and constraints for AI agents, and says generation or updates can take up to 24 hours.
Source and metric
Source: Mintlify Docs · Browse Mintlify Docs tactics
Mintlify publishes a root `skill.md` capability file and regenerates it as docs change
Source discovered: May 27, 2026
When to use it
Use this when AI Search, Documentation, Website is relevant to agent enablement, activation, documentation 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, Documentation, Website.
- Define the test around Mintlify publishes a root `skill.md` capability file and regenerates it as docs change.
- 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.