Hey, thanks for the report. This looks like a known bug. The CLI was loading skills from user directories ~/.cursor/skills/ incorrectly. This was fixed recently.
You’re on CLI version 2026.02.13, and the fix shipped after that. Please update the CLI to the latest version and check if your custom skills show up.
A couple things to double-check on your side:
Make sure your custom skills are in ~/.cursor/skills/<skill-name>/SKILL.md (one folder per skill, with a valid SKILL.md that includes YAML frontmatter with name and description)
After updating, try typing / in the CLI chat to see if the skills appear in the list
Try reinstalling the CLI using the install script. It should install the latest available version:
curl https://cursor.com/install -fsS | bash
Then check the version:
agent --version
If it’s still 2026.02.13, that means the new CLI release hasn’t been published yet, and the fix for user skills is still being rolled out. In that case, you’ll need to wait a bit.
Same here. Actually, the project-level skills are also not working. The skill context should be directly injected to the message; however, the cli agent has to search for skill files in the project to manually read them. Basically, skill context injections completely fail in cli env.
