#2254 Request indexing: pym505/skill-router and pym505/session-handoff

Request indexing: pym505/skill-router and pym505/session-handoff

Both public repositories install successfully with skills CLI 1.6.0, but their skills.sh detail pages currently say the skill is not available in the repository. CLI search also returned no matching results.

Repositories

https://github.com/pym505/skill-router — skill skill-router, root SKILL.md
https://github.com/pym505/session-handoff — skill session-handoff, root SKILL.md

These repositories were published on September 17, 2026. This report does not assume an indexing delay is necessarily a defect; I would appreciate confirmation of the expected process.

Reproduction

In an isolated temporary project, using Node.js 22.22.2 and skills CLI 1.6.0:

npx skills add pym505/skill-router --skill skill-router --agent codex --copy --yes
npx skills add pym505/session-handoff --skill session-handoff --agent codex --copy --yes

Both commands find one skill and complete installation. The installed files match the public Git contents. Metadata validation succeeds. Neither DISABLE_TELEMETRY nor DO_NOT_TRACK is set, and CI mode is not enabled.

Observed telemetry responses

On September 17, I observed the existing CLI fetch calls during one diagnostic reinstall of each updated public package. The observer only logged responses; it did not alter requests or send extra telemetry events.

GitHub repository checks: HTTP 200 for both public repositories.
https://add-skill.vercel.sh/t, event install: HTTP 200 for each source.
skillFiles: {"skill-router":"SKILL.md"} and {"session-handoff":"SKILL.md"} respectively.
Responses contain skillHashes and skillsComputedHash:
- skill-router: 3d25c43b25e3770542ab61bee9d2a6cc0582d49cc6ab9e3dfb1b1587ffb0e415
- session-handoff: 204bcedbf31b4235176d5739968065d1981564e32d5a7ceb2fec8b8d303da39a

Missing listings

The pages return HTTP 200 but their content says the skill is not available in the repository. Installation success and a successful telemetry response therefore have not yet produced a visible listing.

Could you check indexing for these repositories or trigger a re-index if appropriate? Is there an expected propagation window, minimum distinct-user threshold, or other listing requirement that applies here?

Related reports: #2201 and #1683. I could not find an existing report for these two repositories.