Community Catalog

  • Desktop, mobile and web
  • All plans
View as Markdown

What it does

Two public catalogs, one behaviour: anyone can publish a prompt or a skill from their own library, and anyone can search, read and install what other AgentsRoom users have published, without leaving the app. Publishing is opt-in and reviewed; installing copies the entry into the library you choose, where it becomes yours to edit. Every approved entry also gets a public page on agentsroom.dev, translated into the 20 app languages, body included: a Chinese reader gets the prompt text in Chinese, not just its title.

Where to find it

  • Prompt Library and Skills Library, sidebar: the Community tab, next to your own scopes.
  • Prompt or skill editor: the Share with the community switch, off by default, next to the Description and Category fields.
  • On the web: agentsroom.dev/prompts and agentsroom.dev/skills, one page per entry, one URL per language.
  • On a card you installed: the Installed from the community catalog badge.

How to use it

Browsing and installing

  1. Open the library and pick the Community tab. Search the community catalog… searches inside the app; the Category selector narrows to one of eleven shelves (Engineering, Code review, Testing, DevOps, Data, Design, Product, Writing, Marketing, Research, Other), and Recent / Popular sorts the list. Each card shows the author's pseudonym (by ...), its install count and, when it has been vetted, Reviewed and featured.
  2. Add asks Where should it go?: This project (shared), This project (personal) or Global (all projects). Confirm with Add to my library. The copy is yours, editable, and unaffected by later changes to the original.
  3. Open the public page shows the entry on the site, useful for sharing a link with someone who does not have AgentsRoom.

Publishing

  1. Open one of your prompts or skills, fill the Description (one line, the only thing a reader sees before opening it, and required to share) and pick a Category.
  2. Turn on Share with the community and save. A copy leaves for review before the local save, so a network failure shows an error instead of losing your work silently.
  3. If similar entries already exist, the editor lists them ("N similar entries already exist") with View, Publish anyway and Keep it local: installing what already exists is usually less work than maintaining a near-duplicate.
  4. A human reviews the entry. On approval it is translated into every app language and appears in the Community tab and on the site. You get an email when the review is done.

Settings

None. Publishing is decided entry by entry, in the editor.

Agent tools (MCP)

  • marketplace_search: search both public catalogs (kind prompt / skill / both, plus query, category, tag, locale, sort, limit). Read-only and unauthenticated: it returns entries with their handle, category, author, install count and body, and it installs nothing. The user installs from the Community tab, or the agent pastes the body.
  • prompts_save / prompts_update: carry the description and category of a prompt, the two fields publishing requires.
  • skills_save: the same for a skill.

No tool publishes anything: an agent cannot push your library to the catalog.

Providers

All providers, no difference. A published prompt or skill is text; the CLI that consumes it is irrelevant.

Mobile

Present, with the same words. Both library sheets have the Community tab with search, categories and sorting, the Share with the community switch in the editor, and the same Where should it go? sheet with its three destinations. One difference: the phone does not show the similar-entries panel while you type, so a near-duplicate is caught at submission time rather than before it.

Limits

  • Publishing requires a signed-in AgentsRoom account. Browsing and installing do not, and work before a phone is even paired.
  • No plan gate: publishing and installing are the same on every plan.
  • A description is mandatory to publish. Without it the switch refuses with "Add a description: it is the only line a reader sees before opening the entry."
  • Entries are scanned for credentials. A hit refuses the publication and names only the type of secret found, never its value, and it is the one failure where the entry is still saved in your own library.
  • Nothing appears in the catalog before a human approves it.
  • A public page is indexed only above a quality bar (a real body and a real description); below it the page exists and can be shared but stays out of search engines.
  • The author is shown as a pseudonym, never as an email address, and an approved entry survives the deletion of its author's account.
  • An entry's public handle never changes when its author renames it, so links and references keep working.

Common questions

  • Is my library published by default? No. The switch is off on every prompt and every skill; nothing leaves until you turn it on.
  • What if my prompt contains an API key? The catalog refuses it and tells you which kind of secret it found. The entry stays in your library.
  • Can I edit something I installed? Yes, the copy is yours. It does not follow the original.
  • Where does an installed entry go? Wherever you pick: this project shared with your teammates, this project but personal, or your global library.
  • Do I need an account to browse? No, only to publish.

Related