Description
During hands-on testing, the skills hierarchy worked for browsing, but was less effective when the agent already had a concrete task or symptom to resolve.
The search URL is currently not prominent enough:
https://skills.qdrant.tech/search?query=...
As a result, agents may follow the hierarchy through several intermediate pages instead of jumping directly to the most relevant skill.
Proposed change
Surface the search URL as a primary navigation path for known-task or known-symptom queries.
For example, add a short “Start with search” section to the root page:
For specific tasks, symptoms, or troubleshooting questions, start with the skills search endpoint:
`https://skills.qdrant.tech/search?query=<your-query>`
Use hierarchical navigation when exploring an area broadly.
Validation
A/B test the updated approach against the current navigation flow to check whether surfacing search more prominently improves task completion, reduces navigation hops, and helps agents reach relevant leaf skills faster.
Description
During hands-on testing, the skills hierarchy worked for browsing, but was less effective when the agent already had a concrete task or symptom to resolve.
The search URL is currently not prominent enough:
https://skills.qdrant.tech/search?query=...As a result, agents may follow the hierarchy through several intermediate pages instead of jumping directly to the most relevant skill.
Proposed change
Surface the search URL as a primary navigation path for known-task or known-symptom queries.
For example, add a short “Start with search” section to the root page:
Validation
A/B test the updated approach against the current navigation flow to check whether surfacing search more prominently improves task completion, reduces navigation hops, and helps agents reach relevant leaf skills faster.