find_skills: guide re-discovery / in-scope tools when a skill has no tools#24
Merged
Merged
Conversation
…as no tools When a returned skill lists no tools and its playbook can't complete the task, the model should first check tools already in scope — from other skills in this response, earlier find_skills calls, or directly available — and only re-discover with reworded or additional queries if none fit. Mirrors the QE-side find_skills tool description.
anirudh-bijay-glean
approved these changes
Jun 22, 2026
swarup-padhi-glean
added a commit
that referenced
this pull request
Jun 23, 2026
main advanced to 0.2.32 (#24 merged), so move above it again.
swarup-padhi-glean
added a commit
that referenced
this pull request
Jun 23, 2026
Resolve version-line conflicts in the three plugin manifests to 0.2.33 (above main's 0.2.32). dist rebuilt from merged source; src auto-merged (logging change + #24 find_skills hint). typecheck + 154 tests pass.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When find_skills returns a skill that resolves to no tools (e.g. tool-less UGC skills or servers:[] static skills), the model otherwise gets just the skill's playbook with no signal about what to do next. This adds guidance to the
find_skillstool description: if a returned skill lists no tools and its playbook can't complete the task, first check tools already in scope — from other skills in this response, earlier find_skills calls, or tools you can already call directly — and only re-discover with reworded or additional queries if none fit.