plugin-settings

Manage per-project plugin settings via YAML frontmatter in .claude/plugin-settings.local.md.

15|4|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/damionrashford/media-os --skill plugin-settings-damionrashford
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-settings
Source: https://github.com/damionrashford/media-os/tree/main/.claude/plugins/plugin-dev/skills/plugin-settings
Command: npx skills add https://github.com/damionrashford/media-os --skill plugin-settings-damionrashford

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Per-project plugin configuration is hard to manage when settings live in scattered files; this skill standardizes storage by documenting the .claude/plugin-settings.local.md pattern, enabling centralized, per-project control over plugin behavior with YAML frontmatter and optional markdown body.

Core Features & Use Cases

  • YAML frontmatter based configuration stored at .claude/plugin-settings.local.md
  • Per-project state persistence with optional markdown body for prompts/notes
  • Clear guidance for reading, validating, and updating settings across hooks, commands, and agents

Quick Start

Create or update the file .claude/plugin-settings.local.md with YAML frontmatter to store per-project plugin settings.

Frequently Asked Questions about plugin-settings

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

FAQPage Schema
How do I store per-project plugin settings using YAML configuration?

Store per-project plugin settings by defining YAML frontmatter in the .claude/plugin-settings.local.md file. This pattern standardizes configuration storage, providing centralized control over plugin behavior across hooks, commands, and agents.

What is the .claude plugin pattern for managing configuration?

The .claude plugin pattern manages configuration by using a YAML frontmatter block and an optional markdown body within .claude/plugin-settings.local.md. This approach persists settings and prompts while ensuring consistent behavior across project-specific hooks and agents.

Can I include markdown notes alongside YAML frontmatter in plugin settings?

Yes, you can include an optional markdown body alongside YAML frontmatter in .claude/plugin-settings.local.md. The markdown section allows you to document additional prompts and notes, while the YAML block handles the actual settings persistence.

What's the best way to standardize plugin configuration across hooks and commands?

Standardize plugin configuration by centralizing settings in .claude/plugin-settings.local.md using YAML frontmatter. This method supports reading, validating, and updating settings to ensure consistent behavior across all project hooks, commands, and agents.

Why use YAML frontmatter for per-project plugin configuration instead of scattered files?

YAML frontmatter centralizes per-project plugin configuration into a single .claude/plugin-settings.local.md file, solving the problem of managing scattered settings. This approach provides consistent behavior validation across hooks, commands, and agents.

How do I validate and update per-project plugin settings?

Validate and update per-project plugin settings by modifying the YAML frontmatter in .claude/plugin-settings.local.md. This standardized pattern supports reading, validating, and updating configuration to maintain consistent plugin behavior across agents and hooks.