Agent skills marketplaces › Cursor skills

Cursor skills: where to get them, and how to add one

Cursor runs Agent Skills: SKILL.md folders it loads from .agents/skills/ or .cursor/skills/ in your project, ~/.cursor/skills/ for you, and .claude/skills/ and .codex/skills/ for compatibility. Get them from Cursor's Marketplace (inside plugins), with npx skills add owner/repo -a cursor, or by copying a folder. Cursor also ships 19 built-in skills, and teams share skills through a team marketplace.

Read in Cursor's documentation, on cursor.com/marketplace and in the skills CLI's agent table on November 13, 2026.

Where Cursor finds skills

Location	Who gets it
`.agents/skills/`, `.cursor/skills/`	Everyone working in the repository
`apps/web/.cursor/skills/` (any nested folder)	Only when the agent works on files under that folder
`~/.cursor/skills/`, `~/.agents/skills/`	You, on this machine
`.claude/skills/`, `.codex/skills/` and their home-folder versions	Loaded for compatibility with Claude Code and Codex
Plugins from a marketplace	Whoever installed the plugin; listed under Customize › Skills

The compatibility folders matter more than they look. A repository set up for Claude Code already works in Cursor, and so does anything the skills CLI put in .agents/skills/ for Codex or Copilot. Category subfolders are fine too: Cursor walks the folder and finds every SKILL.md.

The 19 built-in skills

Before installing anything, look at what Cursor ships. Type / in Agent chat to run one:

Reviewing: /review, /review-bugbot (likely bugs and regressions), /review-security
Pull requests: /autopilot (watches a PR and handles feedback, conflicts and failing checks), /split-to-prs, /cursor-blame (traces AI-written changes to their prompts)
Making your own: /create-skill, /create-rule, /create-hook, /create-subagent, /migrate-to-skills
Running things: /automate, /loop, /shell, /canvas, /sdk, plus three settings skills: /statusline, /update-cli-config, /update-cursor-settings

/migrate-to-skills converts "Apply Intelligently" rules and your slash commands into skills, so a team moving from .cursor/rules doesn't have to rewrite them by hand.

Which marketplaces install into Cursor

Source	How it gets into Cursor	Good for
Cursor Marketplace	Install a plugin; its skills appear in Customize	Vendor integrations that pair skills with an MCP server (Google Drive, Gmail, Slack, Notion were featured)
Team marketplace	Added by an admin; teammates install from it	Your company's approved skills
skills.sh	`npx skills add owner/repo -a cursor`: `.agents/skills/` in the project, `~/.cursor/skills/` with `-g`	Any public skill on GitHub, pinned in `skills-lock.json`
Tessl	`npx tessl i github:owner/repo --skill name`	Skills with eval scores and Snyk findings
Agensi	Cursor connects to its MCP server; skills load on demand	Paid, expert-written skills
`anthropics/skills` and other repos	Copy the folder into `.cursor/skills/`, or keep it in `.claude/skills/`	Anthropic's document and example skills

One catch from Cursor's docs: skills in a GitHub repository aren't imported on their own through Customize. To use Customize › From GitHub Repository, the repository needs a .cursor-plugin/marketplace.json that packages the skills as a plugin. For a plain skills repo, use the skills CLI or copy the folder. The full list of sources, beyond Cursor, is on the marketplace comparison.

Adding a skill, three ways

From GitHub with the CLI: npx skills add mattpocock/skills --skill grill-me -a cursor. Commit .agents/skills/ and skills-lock.json.
By hand: copy the whole skill folder, scripts included, into .cursor/skills/. Check that the name in its frontmatter matches the folder name; Cursor requires it.
From the Marketplace: open cursor.com/marketplace or Customize, install the plugin, then check Customize › Skills.

Read the skill before any of these. A skill's scripts run with your permissions; Are agent skills safe? has a ten-point check.

Cursor-only settings

Cursor adds frontmatter fields the standard doesn't have: paths (glob patterns, so a React skill only appears for **/*.tsx), disable-model-invocation (only runs when you type its name), and icon and color for using a skill as a Custom Mode that stays on for the whole session. Claude Code reads paths and disable-model-invocation too, but claude.ai and the Skills API reject any field beyond the standard six, so keep a shared skill's frontmatter plain.

Cloud Agents and teammates

Personal skills in Cloud Agents: turn on Sync Skills for Cloud Agents in Settings › Agents. Only ~/.cursor/skills/ syncs, and it stays private to you.
Automations don't load synced skills, even ones set to run as you. Put the skill in the repository's .cursor/skills/.
Admins on Teams and Enterprise can turn syncing off for everyone under Security & Identity.
Sharing: publish the skill to your team marketplace; Cursor keeps a copy in a repository it hosts for your team. Other ways to share across tools are in Sharing skills across a team.

Once a team has a few skills in place, the next question is which ones get used. Zest's Cursor and VS Code extension, from the company that publishes this site, records the skills, models and tokens in each session and shows them per engineer; it's analytics, not a marketplace, and free for 3 seats. Zest

Questions

Does Cursor support agent skills?

Yes. Cursor's Agent loads Agent Skills, folders with a SKILL.md file, from .agents/skills/ or .cursor/skills/ in your project and ~/.cursor/skills/ or ~/.agents/skills/ for you. It picks a skill when the request matches its description, or you type / and the skill's name.

Can Cursor use Claude Code skills?

Yes. For compatibility Cursor also loads .claude/skills/ and .codex/skills/, in the project and in your home folder, so skills a repo already has for Claude Code or Codex work in Cursor without copying.

Is there a Cursor skills marketplace?

Cursor's Marketplace at cursor.com/marketplace lists plugins, which can bundle skills with MCP servers, and teams can run their own team marketplace. For individual skills from GitHub, npx skills add owner/repo -a cursor installs into Cursor's folders.

How do I share a Cursor skill with my team?

Commit it to the repository's .cursor/skills/ or .agents/skills/ folder, or publish it to your team marketplace, where teammates can install it and Cursor keeps a copy in a repository it hosts for the team.

Why doesn't my personal skill work in Cloud Agents?

Personal skills in ~/.cursor/skills/ stay on your machine until you turn on Sync Skills for Cloud Agents under Settings › Agents. Skills in ~/.agents/skills/ never sync, and automations only load skills from the repository's .cursor/skills/ folder.