plugin settings — Skills — getagentictools

What it does

File location: .claude/plugin-name.local.md in project root

Structure: YAML frontmatter + markdown body

Purpose: Per-project plugin configuration and state

Usage: Read from hooks, commands, and agents

Lifecycle: User-managed (not in git, should be in .gitignore)

Task descriptions

Additional instructions

plugin settings

Source

Repository: https://github.com/anthropics/claude-code

plugin settings FAQ

What does the plugin settings skill do?

This skill should be used when the user asks about "plugin settings", "store plugin configuration", "user-configurable plugin", ".local.md files", "plugin state files", "read YAML frontmatter", "per-project plugin settings", or wants to make plugin behavior configurable. Documents the .claude/plugin-name.local.md pattern for storing plugin-specific configuration with YAML frontmatter and markdown content. File location: .claude/plugin-name.local.md in project root Structure: YAML frontmatter + markdown body

What does plugin settings require?

Use case: Enable/disable hooks without editing hooks.json (requires restart). Important: Settings changes require Claude Code restart. 7. Remind users that changes require Claude Code restart Configuration keys: STATE_FILE, FRONTMATTER, ENABLED, STRICT_MODE, FILE, COORDINATOR, AGENT_NAME, LEVEL.

How do I install plugin settings?

Run: npx -y skills add https://github.com/anthropics/claude-code --skill plugin settings --agent claude-code — the source lives at github.com/anthropics/claude-code.

Maintain plugin settings?

Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.

[![plugin settings on getagentictools](https://getagentictools.com/badge/skills/anthropics-claude-code-plugin-settings.svg)](https://getagentictools.com/skills/anthropics-claude-code-plugin-settings?ref=badge)

npx agentictools info skills/anthropics-claude-code-plugin-settings

The second line is the CLI lookup for this page — handy in READMEs and docs.