| name | marketplace-operator |
| description | Use when maintaining the Memory Store plugin marketplace, scouting new Memory Store-backed plugin opportunities, checking whether plugins or skills need updates, planning marketplace releases, or designing recurring upgrade routines. Requires Memory Store MCP. |
Marketplace Operator
Operate the Memory Store plugin marketplace as one branded marketplace with multiple Memory Store-built plugins inside it.
This skill is for marketplace maintenance and expansion. It is not a customer-facing GTM campaign skill and it is not a separate marketplace. Use it to decide what Memory Store-backed plugins should exist, whether existing skills need upgrades, and what recurring checks should run.
Product Boundary
- The marketplace is Memory Store.
- The source repo is
julep-ai/mem-plugins.
.agents/plugins/marketplace.json and .claude-plugin/marketplace.json are host adapters for the same marketplace, not separate marketplace products.- The repo may contain many installable plugins under
plugins/<plugin-name>/.
- Each plugin should be authored and presented as built by Memory Store unless the user explicitly asks for another publisher.
- Do not create one marketplace per plugin.
- Do not describe plugins under a local workspace or agency identity in public marketplace metadata.
- Use separate plugins only when install, auth, positioning, or user mental model differs. Use separate skills inside an existing plugin when the workflow shares the same product surface.
Operating Loop
-
Checkin. Call Memory Store checkin with the repo, current user request, and marketplace maintenance goal. Capture thread_id.
-
Recall marketplace context. Recall prior plugin architecture decisions, existing Memory Store plugin ideas, user feedback, product constraints, similar companies/products, and known install/update issues.
