What is Cursor Plugins? A catalogue for agent extensions
Cursor Plugins quickstart: inspect before adding
Use the documented create-plugin entry to learn the packaging flow on a disposable project
What you will learn
- Choose a concrete entry
- Follow the authoring path
- Make a reversible trial
Before you start
- A disposable client profile
- One selected plugin
- The pinned repository revision
Turn a promising catalogue entry into a repeatable team decision
Key takeaways
- The documented command targets one plugin.
- Scaffolding still needs review.
- Validation and runtime observation answer different questions.
Choose a concrete entry
The pinned `create-plugin/README.md` documents `/add-plugin create-plugin`. Its manifest declares skills, rules and agents; this is a compact first example because the files are present in the same directory.
Check the plugin name, version, author and component paths in `.cursor-plugin/plugin.json` before using the client command. Client support and permissions must be confirmed in the installed Cursor version.
Follow the authoring path
The create-plugin README starts with a use case and component types, then generates or updates `plugin.json`, adds needed files and runs a pre-submission review. Its scaffold skill is an instruction set, not a built-in guarantee of a valid package.
Run the repository validator on a disposable checkout after making changes. It validates JSON schemas and entry names, but it does not execute every skill or approve a remote service.
Make a reversible trial
A first trial should use one plugin and a throwaway workspace. Record its declared file paths and any prompt, hook or network behavior; remove it if the observed effects exceed the chosen scope.
We did not issue `/add-plugin`, run the scaffold or inspect a live client. The sequence here is a test plan grounded in repository files.
Decision guide
| Criterion | Option A | Option B |
|---|---|---|
| Best when | You need predictable behavior and easy auditing | You need adaptive optimization and have reliable telemetry |
| Main risk | May leave performance on the table | Can become difficult to explain or debug |
Implementation steps
- 1
Open the create-plugin manifest and README at one revision.
- 2
Try the client command only in a disposable environment.
- 3
Run validation and inspect actual side effects.
Copy-ready example
/add-plugin create-plugin
# In a separate source checkout: inspect the manifest and run its validatorFrequently asked questions
Can the validator approve plugin safety?
No. Its source checks schema conformance and matching names, not every command or credential use.
Does adding create-plugin add the entire marketplace?
The documented command names one entry; inspect the client result to confirm what was installed.
Sources
- Cursor Plugins / create-plugin/README.mdSource checked 2026-10-08
- Cursor Plugins / create-plugin/.cursor-plugin/plugin.jsonSource checked 2026-10-08
- Cursor Plugins / create-plugin/skills/create-plugin-scaffold/SKILL.mdSource checked 2026-10-08
- Cursor Plugins / scripts/validate-plugins.mjsSource checked 2026-10-08