# strictPluginOnlyCustomization

> The key that lets add-ons come only from plugins.

**Field:** Artificial Intelligence  
**Category:** Claude Code  
**Also known as:** strictPluginOnlyCustomization setting

## Think of it like

It is like a kitchen where you may only cook from the boxes the shop sells. Home recipes are not allowed.

## Definition

strictPluginOnlyCustomization is a key for managed settings. It blocks skills, agents, hooks and MCP servers that come from user and project files. They can then only come from plugins. Set it to true to lock all four, or to a list such as skills and hooks to lock some. Pair it with the key that picks where plugins come from.

## Example

Lucy's company wants every skill to be reviewed first. IT locks skills to plugins from its own marketplace.

## Example code

```json
{
  "strictPluginOnlyCustomization": ["skills", "hooks"]
}
```

Lock skills and hooks to plugins only.

## Why it matters

A plugin goes through a marketplace a company can check. A file in a repo does not.

## Common mistake

Locking skills but not the plugin stores. Unless the store key is set too, any plugin can still bring them in.

## Three principles

- **Plugins only.** For add-ons.
- **All or some.** true or a list.
- **Pair with marketplaces.** Pick the source.

## Related terms

- [Claude Code Plugin](https://learn.benibix.com/term/ai/claude-code-plugin)
- [strictKnownMarketplaces](https://learn.benibix.com/term/ai/strict-known-marketplaces-setting)
- [Claude Code Skill](https://learn.benibix.com/term/ai/claude-code-skill)

---

Source: https://learn.benibix.com/term/ai/strict-plugin-only-customization-setting
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-16
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
