"npx skills" are not recognized as skills

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Whenever I add a skill using npx skills add owner/repo Cursor initially list them under “Skills”, but after a few seconds they get moved into “Rules”.

I have a specific skills where I have added disable-model-innovation. The docs state:

By default, skills are automatically applied when the agent determines they are relevant. Set disable-model-invocation: true to make a skill behave like a traditional slash command, where it is only included in context when you explicitly type /skill-name in chat.
Agent Skills | Cursor Docs

However, my skill is not available whenever I type slash /. Other skills are not available using slash neither.

The skills I am using are working in other tools.

Steps to Reproduce

  • Run npx skills add owner/repo

Expected Behavior

I expect to be able to manually invoke my skills.

Operating System

MacOS

Version Information

Version: 2.5.25 (Universal)
VSCode Version: 1.105.1
Commit: 7150844152b426ed50d2b68dd6b33b5c5beb73c0
Date: 2026-02-24T07:17:49.417Z
Build Type: Stable
Release Track: Default
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Darwin x64 24.6.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report. A couple of things to check:

  1. After running npx skills add, where exactly do the files end up? Can you confirm the path? Is it .agents/skills/<skill-name>/SKILL.md or somewhere else?

  2. Can you share the frontmatter from one of the affected SKILL.md files? Specifically the name, description, and disable-model-invocation fields. The name field has to match the parent folder name exactly. If it doesn’t, Cursor might not recognize it as a valid skill.

  3. A screenshot of Cursor Settings > Rules showing how these show up after the reclassification would help.

According to the docs Agent Skills | Cursor Docs, skills should appear in the “Agent Decides” section under Rules, and /skill-name should work in chat. If they’re being moved to a different section, that usually means Cursor isn’t recognizing them. That can be caused by the file structure or how the frontmatter is being parsed.

Let me know and we’ll dig further.

As I mentioned, the skills are working perfectly in other tools, so I don’t think it’s the formatting?

  1. They exists in `~/.agents/skills//SKILL.md`
  2. `~/.agents/skills/translate/SKILL.md`
---
name: translate
description: Some description
argument-hint: [language-code]
disable-model-invocation: true
---

Instructions...
  1. Screenshot:
1 Like

So this is an easy mistake to make (I made it too).

Cursor does not automatically load skills from ~/.agents/skills. However, .agents/skills is supported for project-level skills. I think it would be less confusing if both the global skills and project-level skills use the same relative load paths. But for now, you can work around this by sym-linking ~/.agents/skills to ~/.cursor/skills.

ln -s ~/.agents/skills ~/.cursor/skills