SpyBara
Go Premium

Documentation 2025-11-25 03:22 UTC to 2025-11-26 00:04 UTC

1 file changed +25 −7. View all changes and history on the product overview
2025
Thu 27 06:02 Wed 26 00:04 Tue 25 03:22 Mon 24 21:01 Fri 21 00:04 Thu 20 18:02 Wed 19 03:21 Tue 18 18:02 Mon 17 03:24 Sun 16 00:04 Fri 14 21:26 Thu 6 18:02 Tue 4 18:02 Mon 3 21:01 Sun 2 18:01 Sat 1 21:01
Details

692. **Browse plugins**: Use `/plugin` to see available plugins from your marketplace692. **Browse plugins**: Use `/plugin` to see available plugins from your marketplace

703. **Test installation**: Try installing a plugin to verify the marketplace works correctly703. **Test installation**: Try installing a plugin to verify the marketplace works correctly

71 71 

72### Example plugin marketplace

73 

74Claude Code maintains a marketplace of [demo plugins](https://github.com/anthropics/claude-code/tree/main/plugins). These plugins are examples of what's possible with the plugin system.

75 

76```shell Add the marketplace theme={null}

77/plugin marketplace add anthropics/claude-code

78```

79 

72## Configure team marketplaces80## Configure team marketplaces

73 81 

74Set up automatic marketplace installation for team projects by specifying required marketplaces in `.claude/settings.json`:82Set up automatic marketplace installation for team projects by specifying required marketplaces in `.claude/settings.json`:


160### Plugin entries168### Plugin entries

161 169 

162<Note>170<Note>

163 Plugin entries are based on the *plugin manifest schema* (with all fields made optional) plus marketplace-specific fields (`source`, `category`, `tags`, `strict`), with `name` being required.171 Plugin entries are based on the *plugin manifest schema* (with all fields made

172 optional) plus marketplace-specific fields (`source`, `category`, `tags`,

173 `strict`), with `name` being required.

164</Note>174</Note>

165 175 

166**Required fields:**176**Required fields:**


262 "./commands/enterprise/",272 "./commands/enterprise/",

263 "./commands/experimental/preview.md"273 "./commands/experimental/preview.md"

264 ],274 ],

265 "agents": [275 "agents": ["./agents/security-reviewer.md", "./agents/compliance-checker.md"],

266 "./agents/security-reviewer.md",

267 "./agents/compliance-checker.md"

268 ],

269 "hooks": {276 "hooks": {

270 "PostToolUse": [277 "PostToolUse": [

271 {278 {

272 "matcher": "Write|Edit",279 "matcher": "Write|Edit",

273 "hooks": [{"type": "command", "command": "${CLAUDE_PLUGIN_ROOT}/scripts/validate.sh"}]280 "hooks": [

281 {

282 "type": "command",

283 "command": "${CLAUDE_PLUGIN_ROOT}/scripts/validate.sh"

284 }

285 ]

274 }286 }

275 ]287 ]

276 },288 },


285```297```

286 298 

287<Note>299<Note>

288 **Schema relationship**: Plugin entries use the plugin manifest schema with all fields made optional, plus marketplace-specific fields (`source`, `strict`, `category`, `tags`). This means any field valid in a `plugin.json` file can also be used in a marketplace entry. When `strict: false`, the marketplace entry serves as the complete plugin manifest if no `plugin.json` exists. When `strict: true` (default), marketplace fields supplement the plugin's own manifest file.300 **Schema relationship**: Plugin entries use the plugin manifest schema with

301 all fields made optional, plus marketplace-specific fields (`source`,

302 `strict`, `category`, `tags`). This means any field valid in a `plugin.json`

303 file can also be used in a marketplace entry. When `strict: false`, the

304 marketplace entry serves as the complete plugin manifest if no `plugin.json`

305 exists. When `strict: true` (default), marketplace fields supplement the

306 plugin's own manifest file.

289</Note>307</Note>

290 308 

291***309***