docs(submission): verified Cursor + Copilot marketplace steps and status - #63
Conversation
The runbook's Cursor and VS Code rows said little more than "submit"; both channels now get the same treatment the OpenAI section has — exact, currently-verified steps plus an honest status line. Cursor: owner-only submission at cursor.com/marketplace/publish, manual review of every listing and update, with the manifest-location question (marketplace repo vs root plugin.json) flagged for resolution before submitting. Copilot: Agent Plugins 1.0 went GA 2026-08-12; listing in github/awesome-copilot is what surfaces a plugin under @agentplugins, and the 08-20 CLI-filed intake was closed to redo via the web form — which is still the open action, recorded as such. Addresses theam#48 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
@ophiocus is attempting to deploy a commit to the Monkeys' projects Team on Vercel. A member of the Team first needs to authorize it. |
atamanvega
left a comment
There was a problem hiding this comment.
Thanks @ophiocus — the step-by-step research (Cursor publish rules, awesome-copilot external-plugin flow, the @agentPlugins discovery path) is solid and worth having in SUBMISSION.md. Two status corrections, using events from the last few days you wouldn't have had visibility into:
-
Cursor — already submitted, no open manifest question. The owner submitted the public repo link at
cursor.com/marketplace/publishand the form accepted our root.cursor-plugin/marketplace.json→ subdir plugin (so the "❓ confirm whether the publish form accepts a marketplace repo / may need a root single-plugin manifest" is resolved — it accepted it). It's in manual review now (not yet listed). Please reflect: Cursor = submitted, in review. -
Awesome Copilot — already resubmitted via web form, and rejected. #2731 was the web-form resubmission (not another CLI attempt): it passed automated intake on 08-20, then a maintainer rejected it on 2026-08-26 on curation grounds — their words: the skills are "either overly simplistic … or replicate functionality built into the harness (such as the issue/PR skills)." So there is no open 'resubmit via web form' action — it was submitted and declined. Copilot still works today via install-from-source (verified; README documents it).
Could you update the Status/open-actions sections to: Cursor = submitted/in-review, Awesome Copilot = rejected 2026-08-26 (curation), no further action, Copilot = install-from-source works? The rest is great. 🙏
Cursor: submitted — the publish form accepted the marketplace repo as-is, resolving the manifest-location question — now in manual review. Awesome Copilot: the web-form resubmission (#2731) was made and declined on 2026-08-26 on curation grounds, so the runbook records the rejection and the install-from-source path instead of a phantom open action. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
Both corrected in dff7fed — thank you for the visibility I couldn't have had from outside:
|
atamanvega
left a comment
There was a problem hiding this comment.
Thanks @ophiocus — status corrected accurately: Cursor submitted/in-review, awesome-copilot declined 2026-08-26 (curation) with no open action, Copilot via install-from-source. Merging. 🙏
Addresses #48 — the two channels the issue names get the same exact-steps treatment
SUBMISSION.mdalready gives OpenAI, from a verification pass done today (2026-08-29). The actual submissions stay owner-gated (Cursor's form is owner-only; the awesome-copilot redo belongs to the original submitter), so this PR ships everything an outside contributor can: the verified path, the package-compliance check, and the true current status.Cursor (per cursor.com/docs/reference/plugins and the marketplace announcement):
cursor.com/marketplace/publish; every listing and every update is manually reviewed; marketplace plugins must be open source (we are).fullstack-dev-kit✅ complies with the naming rules; logos are committed inassets/(relative-path reference is the requirement to double-check)..cursor-plugin/marketplace.json(a marketplace), while the portable rootplugin.jsonlives insideplugins/fullstack-dev-kit/— whether the publish form accepts a marketplace repo or wants a root manifest needs confirming at submission time.VS Code / Copilot (per the GitHub changelog, 2026-08-12 and VS Code docs):
@agentPluginsbrowses the configured marketplaces, andgithub/awesome-copilotis one of the two defaults — so listing there is the "surfaces under@agentPlugins" checkbox, no VSIX or publisher account involved.fullstack-dev-kitisn't listed and no new intake exists — the web-form resubmission is the one open action, and it's yours to fire whenever you're ready.The channels table and Next actions are updated to match. Happy to adjust anything — and if it helps, I can prep the awesome-copilot form answers from #2730's body so the redo is a two-minute paste.