Plugin Settings

Implements per-project plugin configuration using YAML frontmatter in .local.md files.

1|1|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/voxxov222/Claude-code- --skill plugin-settings-voxxov222
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Plugin Settings
Source: https://github.com/voxxov222/Claude-code-/tree/main/temp-repo/plugins/plugin-dev/skills/plugin-settings
Command: npx skills add https://github.com/voxxov222/Claude-code- --skill plugin-settings-voxxov222

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Claude Code plugins often need user-configurable behavior and persistent state, but there is no built-in mechanism for per-project settings. This Skill documents the .claude/plugin-name.local.md pattern, letting plugin authors store structured YAML configuration and markdown prompts that hooks, commands, and agents can read at runtime. ## Core Features & Use Cases - Settings File Pattern: Defines the .claude/plugin-name.local.md convention with YAML frontmatter for structured config and a markdown body for prompts or task context. - Bash Parsing Techniques: Provides sed, grep, and awk recipes for extracting frontmatter fields and body content, plus atomic update patterns using temp files. - Real-World Examples: Includes working hook scripts, command templates, and case studies from the multi-agent-swarm and ralph-wiggum plugins. - Use Case: A plugin author building a validation hook can let users toggle strict mode, set file size limits, and enable logging by creating a .local.md file, without editing hooks.json or restarting their workflow logic. ## Quick Start Ask the AI to add user-configurable settings to your Claude Code plugin using the .claude/plugin-name.local.md pattern with YAML frontmatter.

Frequently Asked Questions about Plugin Settings

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

FAQPage Schema
How do I add user-configurable settings to a Claude Code plugin?

Create a `.claude/plugin-name.local.md` file in the project root with YAML frontmatter for structured fields and a markdown body for context. Hooks and commands parse the frontmatter with sed and grep to read values like enabled flags, modes, and limits.

How do I parse YAML frontmatter from a markdown file in bash?

Use `sed -n '/^---$/,/^---$/{ /^---$/d; p; }'` to extract the frontmatter block, then grep and sed to read individual fields. For the markdown body, use `awk '/^---$/{i++; next} i>=2'` to capture everything after the second marker.

Do plugin settings changes require restarting Claude Code?

Yes, changes to `.local.md` settings files require restarting Claude Code to take effect. Hooks cannot be hot-swapped within a running session, so users must exit and relaunch after editing configuration.

Should plugin settings files be committed to git?

No, `.local.md` settings files are user-local and should be added to `.gitignore` with patterns like `.claude/*.local.md`. They contain per-project or per-user configuration that should not be shared across environments.

How do I update a settings file safely from a hook script?

Use atomic updates: write the modified content to a temp file with sed, then move it over the original with `mv`. This prevents file corruption if the process is interrupted mid-write, unlike in-place sed editing.