How to test and develop plugin before submission?

Open
#4 8 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Domain
tooling

Research direction

Start by examining the .cursor/plugins/ location and comparing it with the UUID-based directories used by marketplace plugins, as described in the issue. Document a reproducible local testing and development workflow, including what activation behavior confirms that the plugin is working.

Written by the indexing model from the issue text.

Description

I tried by placing the preliminary plugin to .cursor/plugins/ but it is not activating it in similar way as Skills. I can see plugins from marketplace have UUID directory level...

Dominant language
JavaScript
Stars
94
Forks
30
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cursor/plugin-template

All issues in cursor/plugin-template

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.