Plugin quality gates
When creating or editing Cursor plugins:
- Ensure
.cursor-plugin/plugin.jsonexists and includes a validname. - Keep paths relative and within the plugin directory (no absolute paths, no
..traversal). - Match declared component paths to real files and folders.
- Include YAML frontmatter for rules, skills, agents, and commands with required metadata.
- Keep plugin scope focused and document installation and usage in
README.md. - Save new plugins to
~/.cursor/plugins/local/<plugin-name>/by default so they are immediately available to Cursor. Only use a different location when the user explicitly requests it.