"Skills should be placed in the .agents/skills/ directory, using a forward slash (/) instead of a backslash. It's not recognized."

Support Help
1

“Skills should be placed in the .agents/skills/ directory, using a forward slash (/) instead of a backslash. It’s not recognized.”

2 Likes
3

Are you saying the forward slash isn’t working for you, even though you’ve added your skills in the ./agents/skills directory? If so, can you give an example of how you’ve formatted the skill?

5

Hey, I need a bit more detail to figure this out:

  1. What OS are you on? Are you using WSL?
  2. What version of Cursor are you on? (Help > About Cursor > Copy)
  3. Did you create the .agents/skills/ folder manually, or via the Cursor UI (/create-skill)?
  4. Can you share the folder structure and the full path to SKILL.md?
  5. Does the skill not show up in Cursor Settings > Rules at all, or does it show up but not work?

If this is Windows or WSL, there’s a known issue with backslashes in paths. Like @Chris_C said, an example of the skill formatting would also help.

6

I found this post because I am having the same issue. It appears that skills in .agents/skills may not be loading correctly as skills, in both the Cursor IDE and agent CLI.

If I look in Cursor Settings > Rules I do see the skill listed under Rules. Note that it is listed in Rules, and not Skills. That may be relevant.

Using the agent CLI, if I use /create-skill, it creates the skill in .cursor/skills/<skill-name>/SKILL.md. However, if I manually create the skill in .agents/skills/SKILL.md, then the skill is not recognized by the agent CLI. It does not appear in the completion menu when I type a “/”, and it is not automatically invoked in the proper situation.

I am on MacOS. I created .agents/skills/ manually. Folder structure:

.agents
└── skills
    └── jsonnet-dependencies
        ├── scripts
        │   └── generate-crd-lib.sh
        └── SKILL.md

4 directories, 2 files

Skill frontmatter:

---
name: jsonnet-dependencies
description: How to add and manage vendored Jsonnet libraries. Use when you are writing Jsonnet code that is likely to exist already in a library. Use when you are writing Kubernetes manifests containing custom resources from operators.
---

# Jsonnet Dependencies
...

Cursor version: latest

Version: 2.5.26
VSCode Version: 1.105.1
Commit: 7d96c2a03bb088ad367615e9da1a3fe20fbbc6a0

Agent CLI version: latest (2026.02.27-e7d2ef6)

3 Likes
7

Same problem as Adam.

I use the Cursor IDE. When my skill is in .cursor/skills/my-skillit is recognized in Cursor Settings as a Skill, and I can trigger it using /my-skill
But when I moved them to .agents/skillsthey weren’t detected as Skills anymore. But they did appear as a Rules, as mentioned above.

Thanks :grinning_face_with_smiling_eyes:

1 Like