Hey there,
Thanks for the detailed report. This is a confirmed bug in the CLI’s slash command system.
What’s happening: the CLI has two separate systems that handle skills. The agent context system correctly loads skills from ~/.agents/skills (so the agent can still auto-invoke your skills when they’re relevant to your prompt). However, the / slash command menu only scans .cursor/skills directories, which is why your skills don’t appear when you type /.
This is being tracked internally and the fix is to align the slash command loader with the directories already covered by the agent context system.
In the meantime, two options:
-
Your skills should still work via auto-invocation – try prompting the agent with a task that matches one of your skills (without using
/), and the agent should pick it up automatically -
For
/menu visibility, you can place (or symlink) your skills in~/.cursor/skills/– that directory is recognized by both systems
We’ll follow up when there’s progress on the fix.