Marketplace

Browse and search public architectures and skills created by the community. Star items for read-only access or fork them to create an independent copy.

Overview

The marketplace is a browse-and-search experience at the top of the Studio sidebar. It has two categories:

• Architectures — complete architecture packages (manifest + skills + templates)
• Skills — standalone skills not tied to a specific architecture (e.g., "add Docker support", "add CI/CD pipeline")

Anyone can publish their architectures or skills to the marketplace, and anyone can discover and use them.

Browsing

The marketplace page has two tabs — Architectures and Skills — each with a searchable grid of cards.

Architecture cards show the name, description, author, tags, number of included skills, and star count. Click through to a detail page with the full description, included skills list, and Star/Fork buttons.

Skill cards show the name, description, author, category tags, and star count. Click through to a detail page with the skill description, template list, and Star/Fork buttons.

Search and filter

• Full-text search across names, descriptions, and tags
• Tag-based filtering (e.g., authentication, messaging, testing, infrastructure)
• Sort by most starred, newest, or recently updated
• Search parameters are reflected in the URL for shareability

Star

Starring an item adds it to your Starred section in the sidebar — a read-only bookmark that auto-updates when the author publishes changes.

Stars are lightweight — just a database row, no data duplication. You can unstar from the marketplace or from the item's context menu in the sidebar.

Fork

Forking creates a full independent copy in your own collection. The fork appears under your Owned section with a 🔀 badge.

• Architecture fork — copies the manifest, all skills, and all templates
• Skill fork — copies the skill definition and templates

Forks track lineage (forked from) for informational purposes, but there is no sync — your fork is fully independent. Deleting the original does not affect your fork.

Sidebar structure

Your sidebar is organized into three sections per category:

SKILLS                           +
  > My Test Skill 🔒                ← owned (created or forked)
  > Forked Docker Skill 🔀

  ★ STARRED
  > Add CI/CD Pipeline  by Author 🌐  ← starred (read-only)

  👥 SHARED
  > Analyze Requirements  by Author 🌐 ← shared via team

ARCHITECTURES                    +
  > My Clean Arch 🔒
  > Forked Microservices 🔀

  ★ STARRED
  > Clean Architecture  by Author 🌐

  👥 SHARED
  > Team Arch           by Colleague 👥

• Owned — items you created or forked. Full read/write access.
• ★ Starred — bookmarks to public items. Read-only. Auto-updates when the author publishes changes.
• 👥 Shared — items shared via team membership. Access level depends on team role.

Publishing

To make your architecture or skill discoverable in the marketplace:

1. Open it in the editor
2. Go to Settings (gear icon)
3. Under Visibility, select Public

The item appears in the marketplace immediately. You can unpublish at any time by setting visibility back to Private or Team.

What happens when you unpublish

• The item is removed from the marketplace
• All stars on the item are removed — users no longer see it in their Starred section
• Existing forks are unaffected — they are independent copies

MCP integration

Your MCP API key gives the server access to all three categories of items:

• Owned skills and architectures (existing behavior)
• Shared skills and architectures (via team membership)
• Starred skills and architectures (public items you've bookmarked)

The AI sees the same unified tool list regardless of source. get_architecture_details and select_architecture include starred and shared architectures alongside your own.

What's next?

• Visibility settings — understand public, private, and team visibility
• Teams — set up team collaboration
• Creating Skills — author your own skills and publish them