Install Skills in Cursor — Project and User-Level Setup

Cursor added native skills support in January 2026. The integration is seamless — skills apply automatically during code reviews, edits and generation tasks without any extra commands.

Cursor support for AI Agent Skills launched alongside the broader skills.sh ecosystem in January 2026. The integration is deliberately invisible — once skills are installed, they work in the background, applying their patterns during every code generation, edit and review without any explicit invocation needed.

The Two Skill Directories

Cursor follows the same convention as Claude Code:

# User-level skills (every project)
~/.cursor/skills/

# Project-level skills (this project only)
.cursor/skills/

The recommendation for most workflows: install widely useful skills (React patterns, TypeScript strict checking, accessibility audits) at user level so every project benefits. Install project-specific skills (this codebase architecture rules, this team conventions) at project level and commit them to git so every developer on the team gets them automatically.

Installation Methods

The Vercel skills CLI handles Cursor installation automatically:

npx skills add vercel-labs/agent-skills

The CLI detects Cursor at .cursor/ in the project or at ~/.cursor/ in your home directory and routes the install to the appropriate location. For user-level installs, add the -g flag:

npx skills add vercel-labs/agent-skills -g

Manual installation works identically to Claude Code — git clone the repo, copy the skill folder to your chosen directory, done.

Verifying Skills Are Active

Open the Cursor Command Palette (Cmd+Shift+P) and search for "Skills". Cursor shows a list of every loaded skill with its description. Installed skills appear with their full metadata — if your skill is missing or shows an error, the validation failed somewhere.

The most useful debugging signal: ask Cursor to do something the skill should handle and watch whether it applies the patterns. If you installed react-best-practices and ask Cursor to write a React component, the generated code should follow the skill rules. If it does not, the skill did not trigger — usually a description problem.

Team Skill Sharing via Git

The most valuable Cursor skills pattern for teams is committing .cursor/skills/ to git. New developers clone the repo and immediately have every shared team skill installed. Updates propagate via git pull. Skills become a form of executable institutional knowledge that travels with the codebase and gets stronger every time someone adds a new pattern.