The Best Cursor Skills

Start with what you already have: 19 skills ship with Cursor, and two of them (/create-skill, /migrate-to-skills) are how you get most of the rest. After that there are three real sources, in descending order of how much vetting stands behind them — Cursor's reviewed marketplace, well-known organisations publishing their own skills, and community collections.

We haven't run Cursor or installed any of these. Every claim below is read from official documentation, from the repositories themselves, or from the GitHub API, and is dated where it will drift.

The test to apply first

Cursor skills split into two kinds, and mixing them up is the single most common failure in existing roundups.

Cursor-native skills depend on things only Cursor has: parallel subagents, the built-in browser, worktree orchestration, Cursor's hooks, the .cursor/rules/ format. parallel-code-review, which fans four read-only subagents across security, performance, correctness, and readability, is a genuinely excellent skill — and it does nothing useful in an agent without subagents.

Portable skills are plain SKILL.md procedures that assume nothing beyond a competent agent with a shell. These work in Cursor, Claude Code, Codex, OpenClaw, and anything else implementing the standard.

Before installing anything, read its SKILL.md and ask which kind it is. A roundup that recommends a large Claude-Code-oriented framework for Cursor without mentioning the provenance mismatch hasn't done that check for you.

Source 1: the 19 already installed

/automate, /babysit, /canvas, /create-hook, /create-rule, /create-skill, /create-subagent, /cursor-blame, /loop, /migrate-to-skills, /review, /review-bugbot, /review-security, /sdk, /shell, /split-to-prs, /statusline, /update-cli-config, /update-cursor-settings.

Three worth knowing about specifically:

• /create-skill — writes a new skill for you. The right starting point rather than hand-authoring frontmatter.
• /migrate-to-skills — converts eligible rules and slash commands. If you've used Cursor for a while, this is likely the highest-value thing on the list, because it turns configuration you already wrote into skills without you deciding anything. See Cursor skills vs rules.
• /review-security and /review-bugbot — review skills that ship in the box, which is worth knowing before you install a third-party code-review skill for the same job.

Every listicle we found omits the built-ins entirely and recommends installing things that overlap with them.

Source 2: the Cursor Marketplace

cursor/plugins is the public repository behind cursor.com/marketplace — MIT-licensed, 3,021 stars, last pushed 13 August 2026. Cursor states that all marketplace plugins undergo manual review before listing, which is a materially stronger provenance signal than anything else on this page.

Two things to understand before browsing it.

Not every plugin contains skills. Reading the manifests directly, the third-party integrations — Gmail, Google Drive, Google Calendar, Salesforce, HubSpot, Intercom, Docusign, X, Navan, Apollo.io, Ashby, Gong, Circleback, Profound — are predominantly MCP-only: a plugin.json and an mcp.json, no skills/ directory at all. Gmail, which we read in full, is exactly that. Those are useful, but they're tool connections, not skills.

The first-party plugins are where the skills are. From the repository's own plugin table, published by Cursor:

Descriptions above are Cursor's own marketplace copy, quoted rather than assessed — we have not used these. pstack is the one community-authored plugin in that table (author listed as Lauren Tan); the rest are Cursor's.

Several of these are firmly in the Cursor-native category: thermos and orchestrate are built around parallel subagents, and continual-learning is built around AGENTS.md.

Source 3: organisations publishing their own skills

Cross-agent repositories from named organisations, all readable and verifiable. Metadata below via the GitHub API on 16 August 2026:

These are portable rather than Cursor-native, which is the point — they were written to the open standard and work here because of it. The star counts are observable GitHub signals, not usage data; there is no install telemetry for Cursor skills, so nobody can honestly rank these by adoption.

Source 4: community collections

spencerpauly/awesome-cursor-skills — CC0-1.0, 694 stars, last pushed 2 August 2026 — is the most substantial Cursor-specific collection we found, and unusually for an "awesome" list it organises by whether a skill is Cursor-native. Its Cursor-Native section is the interesting part, covering things that genuinely only work here:

• parallel-code-review — four read-only subagents across security, performance, correctness, readability, merged into one report
• parallel-test-fixing — one subagent per failing test, fixed independently
• best-of-n-solving — several approaches attempted in parallel in isolated git worktrees
• visual-qa-testing, responsive-testing, dark-mode-testing, accessibility-auditing — all built on Cursor's built-in browser and its accessibility tree
• suggesting-cursor-rules and suggesting-cursor-hooks — notice a repeated correction, propose a .cursor/rules/ file or a .cursor/hooks.json entry to encode it

Descriptions are the repository's own. We have not run these skills, and a CC0 community list carries no review process — read the SKILL.md before installing, particularly anything that ships scripts.

How to judge one yourself

Cursor has no install-time security scanning. A skill dropped into .cursor/skills/ is a file whose instructions the agent will follow, and any bundled script is code that may end up running. Outside the manually reviewed marketplace, the review is yours.

Worth checking, in roughly this order:

1. Does the SKILL.md say when not to trigger? A description that only lists positive triggers will fire on adjacent tasks.
2. Is it Cursor-native or portable? Look for references to subagents, the browser, worktrees, hooks, .cursor/ paths.
3. Read scripts/ in full. This is the only part that executes.
4. Does it declare what it needs? Environment variables, CLIs, network access, named honestly.
5. When was it last touched? A skill referencing a fast-moving CLI and untouched for a year is a liability, not a bargain.
6. Who published it, and under what licence? A named organisation with a real licence file is a different proposition from an anonymous mega-registry claiming hundreds of skills.

The same checklist, worked through in more detail for two other ecosystems, is on the Claude Code and Hermes pages — the reasoning transfers directly, because the risk model is the same wherever a skill is just a file the agent trusts.

What we deliberately didn't do

We didn't rank these. There is no install or usage telemetry for Cursor skills, star counts measure repository popularity rather than skill quality, and we haven't run any of them — so a numbered list would be presentation, not measurement. What's above is organised by provenance, which is the one thing that is actually observable and does actually predict how much scrutiny you still owe a skill before you install it.

Caveats

• We have not run Cursor or installed any skill listed here. Plugin and skill descriptions are quoted from their publishers.
• Star counts, licences, and push dates are GitHub API snapshots from 16 August 2026 and will drift.
• "Manually reviewed" is Cursor's own description of its marketplace process; the criteria are not published in detail and we have not audited it.
• The built-in skill list is taken from Cursor's documentation as of August 2026 and may change between releases.

Sources

• Cursor — Agent Skills (official docs) — the built-in skill list
• Cursor — Plugins (official docs) — marketplace review
• cursor/plugins (GitHub) — plugin table and manifests read directly
• spencerpauly/awesome-cursor-skills (GitHub) — community collection, README read directly
• Repository metadata (stars, licence, last push) pulled via the GitHub API, 16 August 2026