Repository navigation
docs: teach the agent skill to investigate runs with sqb recall - #1173
Merged
Merged
Conversation
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.
Why
The agent skill never mentioned Recall, so agents had no reason to look at past runs before rerunning commands or reading log files. Agents also need to know that a shared ClickHouse store holds every machine's runs, which makes Recall far more useful than the local store.
Changes
SKILL.md: Recall in the skill description and in "When something fails"; explains the local SQLite store and the shared ClickHouse store, with concrete uses for the shared one; two rows in "Reach for these tools".Verification
sqb recallsubcommand named was run against the waffle shop example.