Description
The skill description currently has two gaps that cause an agent to fetch it alongside qdrant-monitoring even for reactive diagnosis tasks:
- It doesn't signal that the file is a navigation hub (links to sub-skills only).
- It doesn't distinguish its use case (proactive tuning) from
qdrant-monitoring's use case of diagnosing active production issues.
Recommended change
Possible solutions could be the following, but needs testing:
- Signal the file structure in the description (for example, add: Navigation hub – ")
- Replace "use when you want to improve the speed and efficiency" with phrasing that scopes it to proactive tuning.
- Cross-reference the
qdrant-monitoring skill ("For diagnosing an active production slowdown, use qdrant-monitoring instead." - or something along those lines.)
Description
The skill description currently has two gaps that cause an agent to fetch it alongside
qdrant-monitoringeven for reactive diagnosis tasks:qdrant-monitoring's use case of diagnosing active production issues.Recommended change
Possible solutions could be the following, but needs testing:
qdrant-monitoringskill ("For diagnosing an active production slowdown, use qdrant-monitoring instead." - or something along those lines.)