Marketplace

What this accomplishes

Browse, install, and submit themes, skills, sub-agents, workflows, and templates from one marketplace, open it from the Marketplace pane in Studio or from Canvas’s own submit and install entry points.

Current availability

This page documents behaviour verified in Miton development builds. Miton is still pre-release and is not publicly downloadable; invited beta users will receive a signed desktop build with automatic updates.

Before you start

• A Miton development build with an active project.
• A connected model and permission to write project files when an install changes the app.

What the marketplace hosts

The marketplace is one catalogue covering five installable content types:

• Themes — a token set (colour, font, radius, spacing, shadow, motion) you can apply to a project’s design.
• Skills — packaged instructions the agent can follow.
• Sub-agents — a sub-agent definition, available from the slash menu once installed.
• Workflows — an exported Automation graph you can run or fork.
• Templates and apps — a starter Canvas project (template), or a finished Canvas project someone is sharing as a published app, carrying its intended *.apps.miton.dev-shaped URL — see one-click publish for what “published” means today.

Browse the catalogue from Marketplace → Browse in Studio, or submit and install directly from Canvas. A separate MCP tab in the same pane discovers Model Context Protocol servers — see MCP client.

Featured, trending, and ratings

• Featured — a curated rail of hand-picked entries, shown above the sortable list on the Templates tab.
• Sort by newest, popular, rating, or trending — trending uses time-decayed install counts, so a burst of recent installs outranks a large but stale total.
• Ratings and reviews — install an entry, then leave a 1–5 star rating and a text review. One review per person per item; submitting again edits your existing review. An automated abuse/spam check screens review text; a review it flags is held out of the public list until a moderator approves or removes it. Anyone can also flag someone else’s review, which routes it the same way.
• Versioning — every entry carries a version. Once you’ve installed something, a later submission with a higher version shows as an update in Marketplace → Installed.

The submit flow

From Canvas, open the submit dialog on a theme, template, or published app:

1. Fill in the title, description, tags, and a licence choice — CC-BY-4.0 (attribution), CC0 (no attribution required), or proprietary (browse-only, no reuse).
2. For templates and apps, choose a kind (template vs a published app) and a visibility — public (listed for anyone), unlisted (reachable only by direct link), or team (visible only to members of your Miton team).
3. Submit. The entry enters the moderation queue at Settings → Safety & Privacy → Marketplace moderation.
4. A moderator approves or rejects the submission. Approved entries appear in Browse; you can see your submission’s status either way.

Install

Installing an entry runs it through one installer shared by all five content types. Each type lands in its own local directory on the machine (themes, skills, sub-agents, workflows, templates), so an install is available to every project on that machine, not scoped to the project you were in when you installed it. Every user-authored string in the payload — theme values, skill or sub-agent markdown, workflow node prompts — passes an automated safety scan before anything is written to disk.

Manage what’s installed, and pick up version updates, from Marketplace → Installed.

What the marketplace does not cover

• Paid content and revenue share — the marketplace does not support selling themes, templates, or components, or splitting revenue with contributors. This is a longer-term, hard-gated piece of work, not something you can turn on today.

What success looks like

You can find, install, and — for templates, apps, and themes — submit content without leaving Miton. Reviews, ratings, and the moderation queue keep the catalogue self-correcting; the abuse check keeps obvious spam out of the public list before a person sees it.

Common failures and recovery

• Confirm Canvas is editing the intended project and page before submitting.
• Check the selected breakpoint, project permissions and model connection.
• If a submission or review isn’t showing up, check its status — pending review, rejected, or flagged — rather than resubmitting.

Related next action

Return to the Canvas overview to choose the next part of the project.