CURSOR / PLUGINS
Plugin specification
Official plugins and the spec behind them

A workflow becomes
a package the day
it gets a manifest.

This repository holds official Cursor plugins for developer tools, frameworks, and SaaS products. Each plugin is a standalone directory at the repository root with its own .cursor-plugin/plugin.json manifest.

The layout is the argument. A folder plus a manifest is what separates a shared prompt from something a second person can install without reading how you set it up.

Read the spec github.com/cursor/plugins
continual-learning/.cursor-plugin/plugin.json
{ "name": "continual-learning", "displayName": "Continual Learning", "author": "Cursor", "category": "Developer Tools" }
Field names follow the repository layout described in the README. Values are illustrative. Without a manifest the same folder is instructions you have to explain; with one, the tool can find, validate, and version it.
From the marketplace listing

Continual Learning: incremental transcript-driven memory updates for AGENTS.md using high-signal bullet points only.

One of the official plugins in this repository, authored by Cursor

Selected entriesDescriptions quoted from the marketplace
Continual LearningCursor

Incremental transcript-driven memory updates for AGENTS.md using high-signal bullet points only.

CLI for AgentsCursor

Patterns for designing CLIs that coding agents can run reliably: flags, help with examples, pipelines, errors, idempotency, dry-run.

OrchestrateCursor

Fan large tasks out across parallel cloud agents with planners, workers, verifiers, and structured handoffs.

Agent CompatibilityCursor

CLI-backed repo compatibility scans plus agents that audit startup, validation, and docs against reality.

PR Review CanvasCursor

Render PR diffs as interactive canvases organized for reviewer comprehension, grouping changes by importance.

Create PluginCursor

Scaffold and validate new agent plugins.

Six of the plugins listed in the repository README, with their marketplace descriptions quoted as published. The repository also lists community entries alongside the official ones.

A manifest is a contract

The repository README describes each plugin as a standalone directory at the repository root carrying its own manifest, which is what lets the tool find, validate, and version it.

Standalone directoryOne plugin, one folder, at the repository root.
Own manifest.cursor-plugin/plugin.json travels with the folder.
Official and communityThe README lists Cursor-authored plugins alongside outside contributions.
Marketplace copyEach entry carries the description published in the marketplace.