Guides
Publishing to the Marketplace
What a listing is, what publishing puts in public, and what a profile page and its karma figure actually count.
The marketplace lists plugins, skills and wallpapers that other people published. This page is about the other side of it: what happens when you publish, and what the store then shows about you.
A listing is something that was published
An entry appears in the store only if it is in the registry’s index.json as an Agent Plugins 1.0.0 plugin.json (plus mcp.json for a connector). That is why every listing carries a publisher, a version, a published date, a readable folder and an install command — there is no second, laxer way in.
The connectors that ship inside the app are not listings. They live in the app’s own seed_catalog.json, nobody can install one, and they appear only on the “built in” wall at the foot of the store. They never count as anyone’s published work, and they never appear on a profile. A built-in reaches the store the same way a stranger’s submission does: through a pull request to the registry.
Nobody reviews it
Submissions pass automated checks only. Every registry entry keeps its “Not human-reviewed” badge, ours included, because the merge is automated. An “Official” badge names the author — it is not a verdict on quality or safety.
What publishing puts in public
Publishing requires signing in with GitHub, because the account is the identity that owns the listing. Two things about you become public and stay public:
- your GitHub username, on the listing and in the pull request, and
- your numeric GitHub account id, in the ownership record.
The sign-in asks for no repository access and stores no token. The details are in the privacy policy, section 7.
Your profile page
Publishing or commenting gives you a page at /marketplace/u/<your GitHub username>. Anyone can open it, signed in or not, and it shows:
| Section | What is on it |
|---|---|
| Header | your username, your GitHub profile picture, the month you first published, and your reach — listings, views, installs, comments |
| Published | every listing you published, with its live counters and vote arrows |
| Comments | where and when you commented — the listing, the date, the score, and a link to the comment on GitHub |
| Your votes | what you upvoted and downvoted. Only you ever see this tab; it does not exist in anyone else’s copy of the page |
The comments tab never shows the text of a comment. It says which listing you wrote under and links out; the words themselves stay on GitHub, where you can edit or delete them at any time.
There is no bio, no banner, no follower count and no edit screen. A profile is a view of what you published, not a thing you fill in.
What karma counts
Karma is the votes, added up:
- listing karma — upvotes minus downvotes on the listings you published,
- comment karma — upvotes minus downvotes on the comments you wrote,
- total — the two added together.
It is recalculated every time a profile is opened and is stored nowhere. One account casts one vote, and a withdrawn vote is deleted, not archived.
Karma names the person the votes were cast for, never the people who cast them. No page anywhere in the store shows who voted on what — only totals. It is a count, not a rating we give, not a review, and not a statement about a person.
If the store’s counters are switched off for a deployment, the karma figures show an en-dash rather than a zero: no measurement is not the same number as no votes.
Taking things back
Removing a listing removes it from your profile. Deleting your votes changes the karma of the people you voted on. Deleting a comment on GitHub removes it from your profile within five minutes, because the list is read from GitHub and held no longer than that.