plugin-settings

The plugin-settings skill enables developers and users to manage per-project plugin configuration using a structured and user-friendly approach. By leveraging `.claude/plugin-name.local.md` files, this skill provides a standardized pattern for storing plugin settings and state, combining YAML frontmatter for structured data and markdown body for additional instructions, prompts, or notes. This approach simplifies managing plugin behavior on a per-project basis without affecting version control, as these files are intended to be user-managed and typically ignored by Git.

The skill supports reading settings through various mechanisms, including hooks, commands, and agents. Hooks can parse YAML frontmatter in bash scripts to conditionally enable or configure plugin behavior, while commands and agents can dynamically adapt their execution logic based on the extracted configuration. Key features include the ability to handle boolean, string, numeric, and list-based settings, structured organization of plugin metadata, and a consistent file pattern for all plugins within a project. Users can easily extend or modify the markdown body to include additional instructions or contextual information that supplements the YAML configuration.

Target users include developers building Claude code plugins, team leads coordinating plugin behavior across projects, and advanced users who need per-project customization of plugin features. Use cases involve enabling or disabling plugins, setting operational modes, defining limits such as retries, specifying notification levels, or providing detailed instructions for automated agents. This skill is particularly useful in scenarios where project-specific configurations must be isolated from global settings or version-controlled code, offering flexibility and clarity in plugin management.