plugin-settings

What problem does it solve? Claude Code plugins often need user-configurable behavior and persistent state, but there is no built-in settings mechanism. This Skill documents the .claude/plugin-name.local.md pattern so plugins can store per-project configuration and state in a structured, human-readable file. ## Core Features & Use Cases - Settings File Pattern: Defines a standard file structure combining YAML frontmatter for structured fields with a markdown body for prompts and context. - Bash Parsing Techniques: Provides sed, grep, and awk patterns for extracting frontmatter fields and markdown bodies from hooks, commands, and agents. - Real-World Examples: Includes working implementations from the multi-agent-swarm and ralph-loop plugins, plus validation and parsing utility scripts. - Use Case: A plugin author wants users to toggle strict validation mode per project. They create a .claude/my-plugin.local.md template, parse the enabled and strict_mode fields in a hook, and let users change behavior without editing hooks.json. ## Quick Start Ask the AI to add a configurable settings file to your plugin using the .claude/plugin-name.local.md pattern with YAML frontmatter and a hook that reads it.