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.
Why this can grow a startup
A complex product becomes easier to use when each workflow can describe itself cleanly. Separate skill files let an agent load only the relevant instructions, while a discovery index keeps the set organized. That usually produces cleaner tool use than one oversized capability file that tries to cover everything at once.
Company example
Mintlify supports multiple skill files in a skills directory and exposes them through `/.well-known/skills/` and the recommended `/.well-known/agent-skills/index.json` discovery endpoint.
Source and metric
Source: Mintlify Docs · Browse Mintlify Docs tactics
`GET /.well-known/agent-skills/index.json` returns a manifest of available skills
Source discovered: May 27, 2026
When to use it
Use this when AI Search, Documentation, Integrations is relevant to agent enablement, developer experience, 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, Integrations.
- Define the test around `GET /.well-known/agent-skills/index.json` returns a manifest of available skills.
- 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.