Skills synced from your claude.ai account (loaded from the syncedSkills folder) are handled differently when their names collide with other commands:
/plugin skills list: a synced skill is now hidden only when a built-in marketplace plugin has exactly the same name. A plugin whose display name matches no longer hides it.
New messages explain when a synced skill cannot use its /name. This happens when a local, project, managed, plugin, MCP or built-in command already holds that name or one too close to it. Examples: "Your claude.ai skill can't use /x in this session.", "/x runs your own skill..., not your claude.ai skill." and "... are taken by other commands, so they don't run your claude.ai skills."
When the clash is with a command you made yourself, the message tells you to rename or delete your own command to free the name.
The /skills dialog shows these notices as a dimmed line under the list. The list shows fewer rows at once to make room for it.
The /skills list rows have a new layout: an icon, a label, and extra columns for a lock, a state word, the source and the size in tokens (N tok). There is also a scroll bar. Typing to search now also matches the displayed label.
A folder in syncedSkills whose name contains ':' is now skipped and logged. The sync never writes such names, so it is not treated as a synced skill.
Why
Before, a synced claude.ai skill could seem to vanish or fail to run when you typed its name, with nothing saying why. You now see which skills are affected and what to rename, and stray or plugin-style folders no longer load as synced skills.
