Repository navigation
docs(agents): the skills.sh indexing mechanism, measured end to end - #54
Merged
Merged
Conversation
The open question above the skills.sh section asked how a repository enters the index. Answered with a paper trail (vercel-labs/skills#2284) and a code trail (fire-and-forget telemetry GET behind a four-owner blob allow-list), two local walls that make installs from this machine unregistrable, a control group over four other indexing requests, and the dispatch-only probe whose CI run moved the repo page from 404 to 200. Pages precede the search index; the badge decision stays separate.
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
 |
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.
Closes the open question in the skills.sh section (how a repository enters the index) with the paper trail, the code trail, the two local walls, the control group, and the probe run that moved the repo page from 404 to 200. The badge re-add decision stays separate and is not made here.