Files
Cursor Agent c5b04a5445 Make plugin descriptions client-agnostic
Drop 'Cursor' from plugin descriptions in the marketplace manifest and
per-plugin manifests so they read correctly in any agent client, and
resync the README table that mirrors them.

Co-authored-by: Alex Vandak Maloney  <maloney.a12@gmail.com>
2026-08-11 17:37:00 +00:00
..
2026-02-17 23:08:13 +01:00

Create plugin

Meta workflows for creating Cursor plugins that are marketplace-ready.

Installation

/add-plugin create-plugin

Components

Skills

Skill Description
create-plugin-scaffold Scaffold a new plugin directory with manifest, components, and repository wiring
review-plugin-submission Run a pre-submission quality check against marketplace expectations

Rules

Rule Description
plugin-quality-gates Keep plugin manifests, component metadata, and paths valid and consistent

Agents

Agent Description
plugin-architect Design plugin structure and component mix based on a concrete use case

Commands

Command Description
create-plugin Build a new plugin scaffold with the right files and metadata

Typical flow

  1. Use /create-plugin with a plugin name, purpose, and target component types.
  2. Generate or update plugin.json, then add rules/skills/agents/commands as needed.
  3. Run review-plugin-submission before publishing or marketplace submission.

License

MIT