Add cursor to universally supported agents list

[quuu]

No description provided.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
skills	Error	Open in v0	Feb 18, 2026 8:53pm

[clemens]

@quuu This is broken for me. .agents/skills don't seem to be picked up by Cursor – and I wouldn't expect it to be picked up as per Cursor's own documentation.

What's noteworthy is that I also couldn't get Skills to be picked up by Cursor when I had .claude/skills/foo symlinked to .agents/skills/foo. .cursor/skills/foo did work, though (even when symlinked).

[quuu]

@clemens i believe their docs are out of date: https://x.com/leerob/status/2024141610796150903

[clemens]

I don't know what's up here: While his post says that it's released, there's absolutely no mention of it in the changelog of that release.

Independent of what's posted where, I've tried it out and it simply doesn't work: Skills are detected when I use .cursor/skills, but not when I use .agents/skills. (FWIW, I've doublechecked and I'm using Cursor 2.5.20 – so that 2.5 changelog should IMO apply.)

So I'm wondering: My guess is that even if .agents/skills actually gets released (e.g. in the next release), I'd be surprised if they'd immediately drop support for .cursor/skills. So wouldn't the most prudent thing be to just revert the directory change and only apply it once it actually works?

[quuu]

@clemens it's officially corrected on their docs: https://cursor.com/docs/context/skills#skill-directories

[quuu]

@clemens would love to figure this out though - FWIW i use cursor and the .agents dir worked for me (also on 2.5)

are your .cursor and .agents conflicting by any chance? any other details you can share about your setup?

[clemens]

That screenshot from their docs is curious: When I looked at the exact same page 2 hours ago, it was still showing me the old directories. When refreshing it now, it suddenly showed me your version.

As for using it, I tried all kinds of flavors using both the npx skills add as well as manually changing things back and forth (symlink, copy & paste, different ways of renaming etc.). What I can tell you for certain (because I've taken it straight from my shell history) is this:

• npx skills@1.4.0 add vercel-labs/agent-skills -a claude-code -a codex -a cursor -y worked (= it found the respective skills in Claude Code CLI, Codex CLI as well as Cursor)
• npx skills add vercel-labs/agent-skills -a claude-code -a codex -a cursor -y worked for Claude Code and Codex, but not Cursor

[clemens]

So here are some screenshots.

After npx skills add vercel-labs/agent-skills -a claude-code -a codex -a cursor -y, here's what I get when trying to access skills in Cursor:

Claude Code and Codex are fine:

With npx skills@1.4.0 add vercel-labs/agent-skills -a claude-code -a codex -a cursor -y, I do find the skills in Cursor:

And Claude Code and Codex are also still fine:

---

For the sake of completeness, here's my Cursor version info:

Version: 2.5.20
VSCode Version: 1.105.1
Commit: 511523af765daeb1fa69500ab0df5b6524424610
Date: 2026-02-19T20:41:31.942Z
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 arm64 25.2.0

Running "Check for Updates" tells me there's no new version available.

I also tried the current Early Access version (2.5.25) as well as the Nightly build (2.6.0-pre.33.patch.0) – but both produced the same result for me when trying to run the current version of skills.

[guillaume-jones]

+1 - As of 2.2.25 Cursor has not yet released the update moving to universal .agents directory. I see the same behavior as @clemens.

The official docs also don't list support for the user-level ~/.agents directory, so this might break the -g command for a while.

I'd suggest reverting this PR until Cursor fully releases this feature, as currently npx skills does not work with Cursor.

[CNanninga]

The use of the global ~/.agents directory vs ~/.cursor should be controllable via an option. Then at least those of us experiencing this could get around it.