Skills in `~/.agents/skills` are not loaded by the CLI

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

Skills in ~/.agents/skills are not loaded by the CLI - they are loaded by the GUI though.

Steps to Reproduce

  1. Add any skill to ~/.agents/skills directory
  2. Open Cursor CLI
  3. Try to call the skill with /

Expected Behavior

All skills from ~/.agents/skills directory are loaded

Operating System

MacOS

Version Information

2026.03.18-f6873f7

Does this stop you from using Cursor

No - Cursor works, but with this issue

2 Likes
5

I created skill in Cursor ( using /create-skill)
I check CLI and it’s still normal.

image
image1376×584 79.3 KB

6

@thepKz That’s expected because skills created with /create-skill are created in standard Cursor directories, not in ~/.agents/skills.

1 Like
11

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:

  1. 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

  2. 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.

2 Likes
13

Thank you for checking and confirming. I look forward for the fix.

I will try symlink solution, although last time I’ve checked when I symlinked skill to ~/.cursor/skills(I wanted to avoid copying skills from git repository, so I symlinked them) it wasn’t properly loaded by Cursor. I will check that again, if I will confirm that symlink don’t work I can create a separate thread.

1 Like
17

Hey @str!

This should be fixed in the next CLI release. :ok_hand: Thanks for the feedback!

18

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.