Repository navigation
docs: remove the skills.sh badge, which asserts a listing that does not exist - #34
Merged
Merged
Conversation
…does not exist The badge rendered "resource not found" in red, its link target is a 404, and the site's search API returns zero rows for euthyna. Correcting the URL would not make the claim true, so it comes out.
Nineteen days of a false claim in the README survived because a computed badge reports itself only to a reader. Recorded with the measurements, plus the sibling provenance badge that is still unverified from this machine.
…y differ The npm version badge computes its value and only pins the colour, which is a different failure mode from the fully static provenance badge. Saying "a hard-coded colour cannot falsify itself" blurred the two.
|
Sorry @modusensus, you've used your own review budget of 250,000 diff characters for the last 7 days. You can request another review in 4 days by commenting |
Reviewer's GuideThe PR removes a README badge that advertised a nonexistent skills.sh listing and adds detailed, measured documentation explaining the finding, badge behavior, related unverified provenance claim, and maintenance pitfalls; no CI checker is introduced. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
"All the READMEs use it" is an over a couple of dozen fragments out of a 738-match search. Say what was inspected, and record the suffix-free URL forms to use if a listing ever exists.
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.
What this fixes
The README badge block carried an
Agent skills installsbadge. It is red because the listingit points at does not exist. Measured 2026-10-11, through the local proxy (
curlcannot build aTLS session on this machine):
skills.sh/b/slow-stack/euthyna.svg308→www.skills.sh, HTTP 200,aria-label="custom badge: resource not found",fill="#dd4343"skills.sh/b/slow-stack/euthyna(no suffix)resource not foundhttps://www.skills.sh/slow-stack/euthyna(the link target)…/slow-stack/euthyna/euthynaGET /api/search?q=euthyna{"skills":[],"count":0}GET /api/search?q=superpowersinstalls;/b/obra/superpowersrendersSkills / 3.4MSo the endpoint works and this repository has no index entry. Two independent defects were
measured, one of form and one of substance: the
.svgsuffix is not the form the badge routeaccepts (
/b/obra/superpowers.svg→resource not foundwhere the suffix-free URL renders),and correcting it would still answer
resource not foundforslow-stack/euthyna.eafd69d(2026-09-22) added the badge, and nothing in the repository — not AGENTS.md, not atest, not a note — recorded a measurement behind it.
grep -rn 'skills\.sh'hit README alone.Changes
README.md: the badge and its link come out. Not recoloured, not retargeted — the claim isfalse, and a green-looking badge over a nonexistent listing would be worse than no badge.
AGENTS.md: a### skills.shsection under Verified host facts with the readings above,the finding that
.agents/skills/is a container theskillsCLI discovers (so this isnot a layout problem), and an explicit non-claim about how a repository enters the site's
index — that was not established. Plus a pitfalls row for the general shape, and the
breakdown of the three tiers sitting in that one badge block: computed value with a pinned
colour (a wrong number still renders the project's blue), fully static label and value
(nothing can contradict it), and computed all the way down (the only kind that turns red).
npm provenance verifiedbadge is also unverifiedfrom this machine. Both Rekor hosts reset at CONNECT through the proxy, so the
logIndexthebadge links to was never read. It is static, so it renders as passing on an assertion
nobody has checked from outside this machine — flagged in the same section rather than left
looking like a result.
Not in this PR
No CI guard for README badges/links. Chosen deliberately: this round fixes the one claim that
was measured false. A
check-license-text.mjs-shaped badge checker (exit non-zero onresource not found, exit 2 on "could not fetch") is the right next step if a second one everappears, and it would add a job that can go red on outbound-network jitter.
Verification
Suite run locally on this branch:
node --test→tests 246 / pass 245 / fail 0 / skipped 1(the skip is the bsdtar-keyed exploit expectation, as recorded for Git Bash on this machine).
Docs-only change;
docs-pairandskill-mirrorguards pass.Summary by Sourcery
Remove the nonexistent skills.sh listing claim and document the evidence and verification limitations behind the change.
Bug Fixes:
Enhancements:
Documentation: