Hi niebag,

I’d separate the two issues a bit.

For skills.sh.json, your file location looks right because it is at the repo root:

1
niebag/skills/skills.sh.json
2

and the skill slugs you used also look like they match the current skills shown on the repo page.

The part that may be confusing is that skills.sh.json only controls how the repo page is displayed/grouped. It does not remove skills from the index, and it does not change what the CLI installs.

The docs also mention that skills.sh picks up skills.sh.json after the repository is seen by telemetry, usually after someone installs from the repo with the skills CLI, and that repo pages are cached:

https://www.skills.sh/docs/customize

Skills

The Agent Skills Directory

Discover and install skills for AI agents.

So I’d try one fresh install after the config was added, then wait for the cache/index to refresh:

1
npx skills add niebag/skills
2

If the page still does not update after that, I’d open an issue with these exact details:

1
Repo: niebag/skills
2
Config file: https://github.com/niebag/skills/blob/main/skills.sh.json
3
Expected: grouped repo page using Engineering / Project Management
4
Actual: default flat list still shown
5
Also stale/removed skills are still listed
6
Last install/test time:
7

For removed skills specifically, I would not expect deleting files from GitHub to immediately remove old telemetry/index entries. That probably needs a reindex or cleanup on the skills.sh side if the stale entries remain visible.

I've tried fresh installs of the skills in a variety of repos but it still does not seem to update the list. I'll open a new issue as per your suggestion, thanks.

Hi niebag,

Thanks for checking. That mostly rules out the normal “install once, wait for cache refresh” path.

One small thing I’d verify before filing the issue: make sure at least one of the fresh installs was run from a normal local shell, not CI, and without telemetry disabled:

1
echo $DISABLE_TELEMETRY
2
echo $DO_NOT_TRACK
3
npx skills add niebag/skills
4

The reason I’d check that is because the repo page update depends on the telemetry service seeing the repo, and installs from CI or installs with telemetry disabled may not trigger that refresh path.

If you already did a normal local install and it still did not update, then I think an issue is the right next step. I’d include the exact stale skill slugs that still appear, the new skill slugs that do not appear, the current skills.sh.json, and the approximate time of the local install so whoever looks at it can compare the index state with the latest repo state.