Hi Juan Antonio,

I would be careful here, because there are two separate systems involved.

On GitHub, renaming the repository should redirect the old repo URL to the new one, as long as you do not later create a new repository with the old name. So jabrena/cursor-rules-java should redirect to jabrena/pillars after the rename.

The part I would not assume is whether skills.sh merges stats based on GitHub’s redirect or whether it keys the listing by the original owner/repo string. If it keys by repo path, then a rename could appear as a new listing until the index catches up, or it could split/lose visible stats.

To reduce the risk, I’d do this in a staged way:

1
1. Do not create a new repo named jabrena/pillars separately.
2
2. Rename the existing GitHub repo in place.
3
3. Keep the old repo name unused so GitHub redirects continue working.
4
4. Check skills.sh after its next index/update cycle.
5
5. If skills.sh creates a duplicate listing, report it as a registry/indexing issue rather than continuing to rename back and forth.
6

I’d also update any install/readme examples to the new repo URL only after confirming how skills.sh displays it.

GitHub’s rename behavior is documented here:

https://docs.github.com/en/repositories/creating-and-managing-repositories/renaming-a-repository

GitHub Docs

Renaming a repository - GitHub Docs

You can rename a repository if you're either an organization owner or have admin permissions for the repository.

Your idea, it is reasonable :)

4. Check skills.sh after its next index/update cycle. 5. If skills.sh creates a duplicate listing, report it as a registry/indexing issue rather than continuing to rename back and forth.

I will do it this week and If I see issues, I will create a ticket like others about reindexing:

https://github.com/vercel-labs/skills/issues

GitHub

Issues · vercel-labs/skills

The open agent skills tool - npx skills. Contribute to vercel-labs/skills development by creating an account on GitHub.

How long to run the reindexing process?

Juan Antonio

Hi Juan Antonio,

I would not give a fixed number of hours unless someone from the skills.sh team confirms the current indexing cadence.

The important distinction is that this may not be just a normal reindex. If the rename creates two visible entries, the issue is probably a canonical repo/stat merge problem:

1
jabrena/cursor-rules-java  -> old indexed repo with install stats
2
jabrena/pillars            -> new GitHub path after rename
3

So after renaming, I’d wait for the next refresh, but I would not rename back and forth or create a new repo with the old name.

If it still looks wrong after that, I’d open the vercel-labs/skills issue with a very specific request:

1
Repo was renamed in-place on GitHub:
2
old: jabrena/cursor-rules-java
3
new: jabrena/pillars
4

5
Please reindex the repository and, if needed, merge/canonicalize the old skills.sh listing so install stats and ranking do not split between the old and new repo paths.
6

That makes the ask clearer than only “please reindex,” because your main risk is duplicate listings or split stats, not only stale content.

Finally, the project was renamed. During this week, I will publish again the changes and I will create the issue as you say to reindex.

Juan Antonio

https://github.com/jabrena/plinth

GitHub

GitHub - jabrena/plinth: Plinth is an AI-native engineering toolkit for modern Java enterprise SDLC, built around reusable Commands, Agents, Skills, and MCP Servers.

Plinth is an AI-native engineering toolkit for modern Java enterprise SDLC, built around reusable Commands, Agents, Skills, and MCP Servers. - jabrena/plinth

Hi @ryux1 ,

I have just created a ticket for it: https://github.com/vercel-labs/skills/issues/1559

GitHub

Listing: Request reindexing for jabrena/cursor-rules-java to jabrena/plinth · Issue #1559 · vercel-labs/skills

Requesting (re-)indexing of jabrena/cursor-rules-java to jabrena/plintch. This week, the repository https://github.com/jabrena/cursor-rules-java was renamed https://github.com/jabrena/plinth to inc...

Juan Antonio

Hi Juan Antonio,

Nice, that seems like the safest route.

Small thing I’d double-check before relying on the issue: make sure the old and new repo names are written exactly the same everywhere in the title/body. That avoids any confusion if someone from the skills repo needs to reindex or canonicalize it.

I’d also avoid reusing the old jabrena/cursor-rules-java repo name for now, so GitHub’s redirect keeps pointing to the renamed repo while skills.sh catches up.

I’m not sure what the indexing cadence is on their side, so opening the issue with the old repo, new repo, and the exact skills.sh page is probably the best way to get it handled cleanly.

No, I renamed the repository jabrena/cursor-rules-java to jabrena/plinth