Description
It can be an alternative of #77
Hub SKILL.md files list sub-skills by topic name only. An agent must currently fetch the hub, infer the right sub-skill from topic names, then fetch the sub-skill. A symptom-to-skill table would make the second step instantaneous, and prevents wrong-branch fetches that waste a round trip before backtracking.
Requirements
- Symptoms should use user-language, not internal Qdrant terminology
- Links should be absolute URLs to SKILL.md files
- Table should appear before any prose in the hub
- Cover multiple phrasings per sub-skill where the same problem can be described differently
Validation
A/B test the updated hub skill against the current version.
Compare whether the symptom-to-skill table helps agents:
- Identify the correct sub-skill faster.
- Reduce wrong-branch fetches and backtracking.
- Reach the relevant leaf skill with fewer navigation steps.
- Complete the task successfully without guessing.
- Use the expected
SKILL.md links.
Use the same prompt/task set for both versions and record navigation path, number of fetched pages, final skill reached, and task outcome.
Description
It can be an alternative of #77
Hub
SKILL.mdfiles list sub-skills by topic name only. An agent must currently fetch the hub, infer the right sub-skill from topic names, then fetch the sub-skill. A symptom-to-skill table would make the second step instantaneous, and prevents wrong-branch fetches that waste a round trip before backtracking.Requirements
Validation
A/B test the updated hub skill against the current version.
Compare whether the symptom-to-skill table helps agents:
SKILL.mdlinks.Use the same prompt/task set for both versions and record navigation path, number of fetched pages, final skill reached, and task outcome.