Manage Cursor skills for your team
Approve a skill once and it lands in Cursor on every developer's machine, at the approved version. Ban one and it's removed everywhere. Every run is recorded in a tamper-evident audit log.
- Skills, every project
- ~/.cursor/skills
- Skills, in a repository
- .cursor/skills
- Also installed
- Subagents, slash commands
- Blocks at invocation
- No hook to refuse a skill; banned skills are removed
Cursor takes skills, subagents and commands, globally and per repository, and skillsvault installs all three. Its project rules in .cursor/rules are always-on context, so skillsvault scans them but doesn't manage them.
Set it up
Paste this into Cursor. It reads the setup guide, installs what it needs and asks you to sign in once:
Or by hand, from a terminal:
Questions
- Where does Cursor look for skills?
- For every project: ~/.cursor/skills. Inside a repository: .cursor/skills.
- Can skillsvault block a skill in Cursor?
- skillsvault removes banned skills from Cursor's folders on every machine and never installs them. Cursor has no hook that can refuse a skill at the moment it runs, so a skill someone copies in by hand isn't stopped at invocation; skillsvault's scan reports it.
- What does skillsvault install into Cursor?
- Your organisation's approved skills, subagents (~/.cursor/agents) and slash commands (~/.cursor/commands), each at the version the registry approves.
- Is it free?
- Free for one developer. Teams pay per member: €20 a month on Team, €40 on Business.
One registry for all of them
The same approved list reaches every agent your team uses.
Start with the skills you already have
skillsvault scan lists every skill on this machine across all your agents and flags the risky ones. It runs locally, with no account.