Skip to main content
Plugins are in closed beta. To request access, contact support@cognition.ai. Behavior and configuration may change in future releases.
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>.

​
4. Distribute it to everyone

An org or enterprise admin adds one required plugin to the managed manifest at Settings → Marketplace:
Everyone in scope gets the baseline automatically — cloud sessions and, for the enterprise/account manifest, CLI and Devin Desktop users logged into the account too (org-level manifests reach cloud sessions only). A private repo works as-is: cloud fetches through your Git integration; CLI users fetch with their own git credentials.

​
5. Evolve and govern

  • Merging to your marketplace repo’s default branch is the release — new sessions pick it up automatically. See how updates roll out.
  • 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 and list every approved plugin (including the meta-plugin’s dependencies — transitive deps aren’t exempt) in requiredPlugins/optionalPlugins. Full semantics: governance rules.

​
Next steps