feat(skill): allow direct calls to user-named unindexed endpoints#70
Merged
Conversation
The skill's search-first framing led agents to treat "not in Zero's index" as a blocker — refusing a user-named endpoint or silently substituting an indexed capability instead. Add a Direct calls section and scope the search->call loop to discovery, so a user naming a URL is called directly via `zero fetch`. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Broaden the direct-call permission beyond user-named URLs to any endpoint the agent already has — including storefronts/APIs it discovers while browsing (e.g. zeroclick.io) — so unindexed capabilities can be invoked directly. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
A capability token/slug/uid comes only from search or a capability page, so a discovered or user-named URL has none. Show a bare `zero fetch <url>` and note the server attributes the URL on its own when it recognizes it. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The flag row and gotcha said to always pass --capability and claimed omitting it means the run is never recorded. Neither holds for a bare `zero fetch <url>`: you have no token/slug/uid to pass, and the server attributes the URL itself when it resolves. Scope the guidance to "pass it when you have one." Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Problem
The Zero skill's search-first framing ("The flow is always search → inspect → call → review") led agents to treat "not in Zero's index" as a hard blocker. When a user named a specific endpoint that wasn't indexed, the agent would refuse to call it — or silently substitute a different, indexed capability — answering a question the user didn't ask.
zero fetchalready works on arbitrary URLs (the--capability <slug>fallback for direct calls). The capability existed; the skill just never gave the model explicit permission to use it when a user names an endpoint.Change
search → inspect → call → reviewframing to discovery, with a pointer to direct calls when the user already names the endpoint.Deliberately minimal — no spend-posture or confirm-first ceremony. Just: unindexed is fine on user request, and don't substitute.
Versioning
Plugin behavior change →
make minor,1.9.0 → 1.10.0across all four manifests.🤖 Generated with Claude Code