Who it is forA developer who wants to package an internal workflow or tool as a Cursor plugin and has no plugin structure yet.
The problemBuilding a plugin from scratch means guessing the directory layout and manifest format.
The outcomeA new plugin directory with a manifest that passes the create-plugin validation.
What you need first
- Access to the cursor/plugins repository on GitHub
- Cursor set up to use plugins
- Basic familiarity with the .cursor-plugin/plugin.json manifest each plugin needs
Steps
- Open the create-plugin/ directory from the Plugins table in the README.
- Read the README there to see how the scaffold is meant to be used.
- Create your plugin as a standalone directory at the repository root, following the same layout as the other Plugins.
- Make sure the directory contains .cursor-plugin/plugin.json with a name and description.
- Run the validation the create-plugin plugin provides and fix any reported issues.
Prompt for your agent
In the cursor/plugins repo, use the create-plugin plugin to scaffold a new plugin named <plugin-name> as a standalone root directory. Output the file tree and the validation result. Verify that .cursor-plugin/plugin.json exists and that the validation reports no errors.
Caveat. The README does not list the exact scaffold or validation commands, so read the create-plugin/ directory for them before running anything.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page