Sync the skill: catalog search takes a scope with no query - #17
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.
Regenerated from
getanyapi-com/anyapisrc/lib/agentSkill.tsafteranyapi#1038deployed (verdict SHIPPED, frontend root 200).The skill told agents that
search_apisrequires a query. Ranked search has taken any non-empty combination ofquery,category, andplatformsince gateway PR #1013; the four adapters shipped that today as@getanyapi/sdk@0.36.0,getanyapi@0.36.0,anyapi-cli@0.9.0andn8n-nodes-anyapi@0.4.0.Three lines, all generated:
search_apisnow reads "Takes any non-empty combination ofquery,category, andplatform, so a scope with no query is a complete search; optionallimit."anyapi search [query] [--category] [--platform], matchinganyapi-cli@0.9.0.metadata.version0.3.0->0.3.1, so the declared version does not drift from a changed body.Not hand-edited: produced by
npm run sync-skillsin the source repository.scripts/check.shpasses, which is the proof the body matches what production serves - it refused this same change before the deploy.Measured against production with no key: