{% extends "base.html" %} {% block title %}{{ guide_title }} — {{ config.INSTANCE_NAME }}{% endblock %} {% block content %} {# Publication-flow guide. Reached from the action-row CTA on /marketplace ("Submit a plugin" on the curated tab; the flea variant is reachable only as a fallback since flea has a self-service +Upload button). Two distinct flows, one template — `guide_kind` switches the body. #}
← Back to {{ 'Curated Marketplace' if guide_kind == 'curated' else 'Flea Market' }}

{{ guide_title }}

{% if guide_kind == 'curated' %} {# Curated submission guide — publish-by-curator flow. Named Curators are the gatekeepers (security / telemetry hygiene / docs bar). The fast-path callout points users at the Flea Market when they want reach without the review wait. #}

Curated Marketplace submissions go through Named Curators — folks accountable for keeping the bar (security, telemetry hygiene, documentation) consistent across what ships on this shelf.

  1. Find a Curator. Each plugin in the Curated Marketplace lists its curator on its detail page. Reach out to any curator whose published work overlaps with what you're shipping — they're the most likely owner. The See all curators → link on the Curated tab is the directory entry. If no curator's domain matches, ask the {{ instance_brand }} platform team — they'll either adopt the submission or steer it to the right person.
  2. Hand off your skill or plugin. Share the source repo (or a zipped bundle) plus a one-paragraph intro covering what it does, who it's for, and what data it touches. The curator runs it through the review bar (manifest sanity, prompt-injection surface, doc completeness, telemetry posture).
  3. Curator publishes. Once they accept, the curator commits the manifest entry to the curated repo. Your plugin appears on the Curated tab on the next nightly catalog sync (within ~24 h of merge). Iteration after publish goes through the same curator — they own the entry's lifecycle (version bumps, deprecation, takedown).

⚡ Want it live in minutes instead of days?

The Flea Market is the self-service shelf — anyone in the company can upload a skill, agent, or plugin without going through a curator. Same Claude Code reach, faster path, lighter review bar (automated guardrails only; no human gatekeeper).

Submit a skill to Flea Market →
Submit a skill to Flea Market → ← Back to Curated
{% else %} {# Flea publishing guide — self-service flow. No human gatekeeper, automated guardrails only (content quality + security review run server-side at submission time). Lives at /store/new. #}

The Flea Market is self-service. Anyone in the company can upload a skill, agent, or plugin — no curator handoff, no review queue. Automated guardrails check the manifest, content quality, and prompt-injection surface at submission time.

  1. Package what you're shipping. A skill is a single SKILL.md (front-matter + body); an agent is an AGENT.md; a plugin is a folder with a plugin.json manifest and any commands / agents / skills it bundles. Zip the folder (or point at a git URL containing it). If you're starting fresh, the format guide documents each shape with copy-pasteable examples.
  2. Upload via the form. Head to /store/new. Drop the zip (or paste the git URL), fill the metadata form (name, short description, what data it touches, who it's for), submit. The + Upload button on the Flea Market tab is the same form.
  3. Automated review. Server runs content-quality checks (manifest completeness, prose length, distinct-word floor) and a prompt-injection scan. Most submissions pass within seconds. Failures surface inline with the exact field to fix.
  4. Published. Once green, your submission goes live on the Flea Market tab immediately — no nightly-sync delay. Iteration goes through the same form: upload a new version, the form recognises the slug and bumps the version pointer.
+ Upload to Flea Market Browse Curated →
{% endif %}
{% endblock %}