Unable to add external skills/rules due to naming clash

Support Bug Reports
, , ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When adding new rule(s) one of the options is to add via a GitHub or GitLab repository. Unfortunately Cursor appears to require a globally unique name for what is added here, and the name is determined based on the name of the repo. It is not scoped by the user/org that owns to repo or the VCS provider.

This is especially problematic given the growing convention for vendors to provide these in a repo called “agent-skills” (e.g., infracost/agent-skills, hashicorp/agent-skills) or similar. That means first installed wins and latter users are blocked.

Our only workaround currently is to instruct our customers that are using Cursor to fork our own repos and give it a unique name, and then import.

It would be much better if Cursor followed the conventions of other products that import skills/rules and either didn’t have a globally unique name requirement, or scoped it to provider/owner/repo to avoid clashes.

Steps to Reproduce

  1. Add GitHub - infracost/agent-skills: Infracost AI Agent Skills · GitHub as rules
  2. Now try to add GitHub - hashicorp/agent-skills: A collection of Agent skills and Claude Code plugins for HashiCorp products. · GitHub, you can’t

Expected Behavior

Should be able to install more than one rule set from a 3rd party.

Operating System

MacOS

Version Information

Version: 2.6.22
VSCode Version: 1.105.1
Commit: c6285feaba0ad62603f7c22e72f0a170dc8415a0
Date: 2026-03-27T15:59:31.561Z
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.2.0

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

5

Hey, thanks for the detailed report. I can reproduce it, and the cause is exactly what you described: during import we only use the repo name and drop the owner/org, so a second repo with the same name hits the existing .cursor/rules/imported/<repoName>/ directory.

I’ve logged an internal bug. I can’t share an ETA yet, but I’ll post an update here once I have one. The obvious fix is to include the owner in the directory name, like infracost-agent-skills, so your workaround of forking and renaming on your side is the right move until the fix lands.

If you know any other vendor repos with conflicting names besides agent-skills, send them over. It’ll help us prioritize.