AgentSkills.site

Cursor · Plugin catalog

Cursor Plugins

A plugin is an envelope, not a capability. It can carry skills, subagents, rules, commands, hooks, and MCP servers together — so the useful question about any plugin is what’s inside it. Five of the official marketplace plugins have been read in full here, component by component.

5 inspected · 8 catalogued · 33 listed in the official repository, checked August 20, 2026.

A plugin is not a skill

The two get conflated constantly, and the distinction is packaging. A Cursor skill is one directory containing a SKILL.md — a description telling the agent when the skill is relevant, and instructions to follow once it is. A plugin is a distributable bundle that can contain several of those, plus components a lone skill can’t carry.

Per Cursor’s own documentation, a plugin can bundle any combination of:

ComponentWhat it is
SkillsA packaged procedure the agent selects on relevance or you invoke by name
RulesPersistent guidance and coding standards, as .mdc files
AgentsSubagent configurations a skill can fan work out to
CommandsAgent-executable command files
MCP serversModel Context Protocol integrations that give the agent new tools
HooksAutomation scripts triggered by events

Skills and MCP servers are the two components the portable Agent Plugins standard also covers; rules, agents, commands, and hooks are Cursor’s own additions. Cursor loads both formats — an Agent Plugin declares a plugin.json at its root, a Cursor Plugin declares .cursor-plugin/plugin.json. Every plugin catalogued below is the second kind.

The practical consequence: the word “plugin” tells you nothing about size or substance. In the official repository one plugin is a single skill and another is 44 skills, two subagents, and 23 playbooks. That’s why this page enumerates contents rather than reprinting marketplace one-liners.

How installing one works

Cursor documents one route for every marketplace plugin: open Customize in the sidebar, find the plugin, select Install, and choose project or user scope. That flow is identical for Cursor Plugins and Agent Plugins — Cursor detects the format from the manifest.

Several plugins additionally print a slash command in their own README, in the form /add-plugin <name>. Those are recorded on the individual pages below where the plugin’s README states one, and left out where it doesn’t — it isn’t documented as a universal install path, so it isn’t assumed for plugins that don’t mention it. Skill-level installation, which is a different question, is covered in how to install Cursor skills.

Cursor states that every marketplace plugin is manually reviewed before listing. That is a real provenance signal and a stronger one than any community registry offers — but the criteria aren’t published in detail, and nobody here has audited the process. It is Cursor’s claim about Cursor’s marketplace, reported as such.

Inspected — 5 plugins

What each one actually contains

Every component below was read from the plugin’s own manifest, README, and component frontmatter. Counts are derived from those enumerated lists, not stored separately, so they can’t drift from what’s shown on each page.

  • pstack

    pstack

    44 skills, 2 subagents and 23 playbooks Lauren Tan

    A 44-skill, two-subagent Cursor plugin built around one sticky mode that matches a request to a named playbook and applies a stated engineering principle at each step.

    For For engineers who want a repeatable, auditable procedure attached to a task type — bug fix, perf work, refactor, overnight run — rather than deciding an approach fresh each time. It is a whole process, not a single capability.

    What’s inside pstack →

  • Cursor Team Kit

    cursor-team-kit

    18 skills, 2 subagents and 2 rules Cursor

    Cursor's own 18-skill kit for CI, code review, shipping, and verification, plus two subagents and two TypeScript rules — deliberately built to work without third-party service integrations.

    For Teams that want a ready-made set of CI, review, and shipping workflows in Cursor without wiring up third-party services first. Its README states the kit is designed to be plug and play for exactly that reason.

    What’s inside Cursor Team Kit →

  • Thermos

    thermos

    3 skills and 2 subagents Cursor

    Runs two Cursor subagents in parallel over a branch diff — a correctness/security audit and a strict maintainability rubric — then synthesizes both into one deduplicated, prioritized review.

    For A deliberately harsh, deep review of a branch before merging — past what a general-purpose review gives you. Cursor's built-in /review and /review-bugbot remain the lighter-weight option for a sanity check.

    What’s inside Thermos →

  • PR Review Canvas

    pr-review-canvas

    1 skill Cursor

    A single-skill Cursor plugin that renders a pull request diff as a Cursor Canvas organized by reviewer value — core logic in full, wiring condensed, boilerplate summarized.

    For Reviewing a PR dense enough that reviewer guidance actually helps, or summarizing a stack of PRs for a human reviewer. A plain diff view is enough for anything smaller.

    What’s inside PR Review Canvas →

  • Docs Canvas

    docs-canvas

    1 skill Cursor

    A single-skill Cursor plugin that renders architecture notes, API references, runbooks, or codebase walkthroughs as a navigable Cursor Canvas instead of a flat markdown file.

    For Turning a directory of markdown docs, one large doc, or a codebase question into something scannable rather than a flat top-to-bottom read.

    What’s inside Docs Canvas →

What else is in the repository

Eight more first-party plugins are catalogued but not yet inspected: Orchestrate, Continual Learning, Create Plugin, Agent Compatibility, CLI for Agents, Cursor SDK, Ralph Loop, and Teaching. Until each one has been read component by component it gets no page here — its own marketplace listing is the authority, and this catalog would only be repeating it.

The plugins above are the 13 directories at the root of cursor/plugins, and all of them ship a skills/ directory. The remaining 20 entries in the repository’s plugin table live under third_party/ — Gmail, Google Drive, Salesforce, GitHub, Playwright and the rest — and every one of them ships an mcp.json. Only 1 of the 20 also carries a skills/ directory.

So the marketplace splits cleanly: first-party plugins are where the skills are, and the third-party integrations are tool connections. Both are useful; they answer different questions. Which layer you actually need is the subject of Agent Skills vs MCP.

How this catalog is made

Two tiers, the same ones the skills library uses. Catalogued means the marketplace row was recorded — enough to be honest that the plugin exists. Inspected means the manifest, the README, and every bundled component’s frontmatter were read, and only inspected plugins get a page. A directory existing in the repository is never on its own a reason to publish a page about it.

Nothing here has been run or installed. Version numbers and component lists are snapshots taken on the dates each page states, and they will drift — the plugin’s own repository is authoritative, and every page links straight to it.

Related reading