plugin-settings

Apply per-project plugin settings from YAML frontmatter in .claude/plugin-settings.local.md to Claude Code hooks.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/dobrinz123/claude-skills-share --skill plugin-settings-dobrinz123
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-settings
Source: https://github.com/dobrinz123/claude-skills-share/tree/main/plugins/plugin-dev/skills/plugin-settings
Command: npx skills add https://github.com/dobrinz123/claude-skills-share --skill plugin-settings-dobrinz123

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Solve the need for per-project plugin behavior by storing per-project configuration in a dedicated YAML frontmatter file at .claude/plugin-settings.local.md, keeping settings isolated from source control while enabling consistent tooling across projects.

Core Features & Use Cases

  • Per-project configuration files: Use YAML frontmatter in .claude/plugin-settings.local.md to enable/disable and set options.
  • Structured settings: Frontmatter fields like enabled, mode, and numeric values for deterministic behavior.
  • Prompt-body context: Markdown body can store prompts, notes, or usage instructions for agents/hooks to load.
  • Easy integration: Hooks and commands read these files to adjust behavior automatically across projects.

Quick Start

Create .claude/plugin-settings.local.md in your project root with YAML frontmatter to enable and configure the plugin.

Frequently Asked Questions about plugin-settings

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure per-project plugin settings for Claude Code hooks?

You can configure per-project plugin settings by creating a YAML frontmatter file at .claude/plugin-settings.local.md in your project root. This file stores structured fields like enabled, mode, and numeric values to adjust hook behavior automatically.

What is the best way to keep plugin configuration isolated from source control?

Using a dedicated local settings file like .claude/plugin-settings.local.md isolates plugin configuration from source control. The local file pattern keeps your YAML frontmatter settings project-specific while maintaining consistent tooling behavior.

Can I use YAML frontmatter to enable or disable Claude Code hooks per project?

Yes, YAML frontmatter supports an enabled field to toggle hooks on or off. You can also define mode and numeric options in the frontmatter to achieve deterministic plugin behavior across different project roots.

How do I store agent prompts or usage notes alongside plugin configuration?

The markdown body of the .claude/plugin-settings.local.md file stores prompt-body context, notes, or usage instructions. Agents and hooks can load this markdown body alongside the structured YAML frontmatter settings.

Does plugin configuration require any special dependencies to parse YAML settings?

No external dependencies are required. The plugin-settings skill relies on simple shell utilities to parse the YAML frontmatter and can access optional scripts, references, and assets directories when they are present in the project.

What are the limitations of using a local markdown file for hook configuration?

The local markdown file pattern is project-specific and isolated from source control, meaning configurations are not shared across repositories. You must create and maintain a separate .claude/plugin-settings.local.md file in each project root.