Make plugin descriptions client-agnostic - #208
Merged
Merged
Conversation
Drop 'Cursor' from plugin descriptions in the marketplace manifest and per-plugin manifests so they read correctly in any agent client, and resync the README table that mirrors them. Co-authored-by: Alex Vandak Maloney <maloney.a12@gmail.com>
github-actions Bot
added a commit
to SmailG/claude-cursor-plugins
that referenced
this pull request
Aug 12, 2026
…cursor/cursor/client-agnostic-plugin-descriptions-4831 chore: sync with cursor/plugins — Merge pull request cursor#208 from cursor/cursor/client-agnostic-plugin-descriptions-4831
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Plugin descriptions assumed the reader's client was Cursor ("Connect Cursor to Gmail...", "interactive Cursor Canvases"). Those strings are surfaced wherever the marketplace is consumed, so this removes the client assumption.
What changed
Rewrote the
descriptionfield in.cursor-plugin/marketplace.jsonand in each per-plugin.cursor-plugin/plugin.json, then resynced the README table (which mirrors the marketplace descriptions).Connect Cursor to X→Connect to X(apollo-io, ashby, circleback, clay, docusign, github, gmail, google-calendar, google-drive, hubspot, intercom, navan, salesforce)pr-review-canvas/docs-canvas: "Cursor Canvas(es)" → "canvas(es)"create-plugin: "new Cursor plugins" → "new agent plugins"agent-compatibility: "plus Cursor agents that audit" → "plus agents that audit"orchestrate: "parallel Cursor cloud agents" → "parallel cloud agents"cursor-team-kit: "Internal workflows used by Cursor developers" → "Internal engineering team workflows"salesforceconfig input: "External Client App you created for Cursor" → "...created for this integration"Deliberately left alone
cursor-sdk, and theorchestratereference to the Cursor SDK. There "Cursor" is the product name of the@cursor/sdkpackage the plugin is about, not an assumption about the client; the package name itself keeps the word regardless.author.name,displayName, plugin/directory names, and the marketplace's own owner and description — those identify Cursor as publisher rather than as the client.description:fields and plugin READMEs, which are a separate surface. Happy to extend the scrub there if wanted.Verification
node scripts/validate-plugins.mjspasses (All plugins validated successfully.).