Skip to main content
This quickstart takes you from zero to a team plugin marketplace: one repo your org owns that bundles your skills, rules, hooks, and MCP servers, installed automatically for every Devin session and CLI user. For the full background, see Set up your plugin ecosystem.

​
1. Fork the template

Fork CognitionAI/team-marketplace-template. Its layout:
The repo root is itself a plugin — the meta-plugin. Installing the repo installs your whole baseline: its manifest’s requiredPlugins pulls in the plugins every teammate should have, optionalPlugins endorses extras, and forbiddenPlugins blocks what you don’t want.

​
2. Make it yours

  • In the root .devin-plugin/plugin.json, change every git-subdir URL to point at your fork, and edit the required/optional/forbidden lists.
  • Add a plugin per team or concern under plugins/<name>/ — each needs its own .devin-plugin/plugin.json and typically a skills/<name>/SKILL.md. Starting a plugin from scratch? Use CognitionAI/plugin-template.
  • Have an existing repo of skills? Drop each skill folder into a plugin’s skills/ directory — skills inside plugins are ordinary skills, no format change.

​
3. Test locally with the CLI

Local installs are linked, so edits apply on your next session — iterate on a skill, then start a session and invoke it as /<plugin>:<skill>. (Without --local, install adds the plugin to your personal plugins in Devin Cloud, which is what you want once it’s pushed to a repo.)

​
4. Distribute it to everyone

An org or enterprise admin installs the repo from Customize → Plugins: Add plugin → From repository, enter your-org/your-marketplace, and pick the organization or enterprise scope. That adds one required plugin to the scope’s managed manifest:
Everyone in scope gets the baseline automatically in cloud sessions, the CLI, and Devin Desktop. A private repo works as-is: cloud fetches through your Git integration; CLI users fetch with their own git credentials, so they need access to the repo too. See the Plugins guide for scopes, indexing, and MCP connections.

​
5. Evolve and govern

  • Merging to your marketplace repo’s default branch is the release — new sessions pick it up automatically, and Reindex plugins in Customize refreshes what the page shows. See how updates roll out; pin to a sha when you want to control updates.
  • Teams add plugins by PR to the marketplace repo; CI validates the layout.
  • To lock the account down to your approved set only, add "forbiddenPlugins": ["*"] to the managed manifest (Plugin settings → Edit manifest in Customize) and list every approved plugin (including the meta-plugin’s dependencies — transitive deps aren’t exempt) in requiredPlugins/optionalPlugins. Full semantics: dependencies and governance.

​
Next steps