Plugin Settings

Configure per-project plugin behavior via YAML frontmatter in .claude/plugin-name.local.md.

Updated Jan 19, 2026

Search Tags:#claude #configuration #plugin #settings #yaml-frontmatter #per-project #local-md

Ready to run

npx skills add https://github.com/kgadek/kgadek-claude-plugin --skill plugin-settings-kgadek

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Plugin Settings
Source: https://github.com/kgadek/kgadek-claude-plugin/tree/main/ai-spec/2026-01-21-sdd-inspirations/references/anthropics-claude-plugins-official/plugins/plugin-dev/skills/plugin-settings
Command: npx skills add https://github.com/kgadek/kgadek-claude-plugin --skill plugin-settings-kgadek

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Plugin Settings pattern provides a safe, per-project mechanism to configure Claude Code plugins without embedding settings in code or risking cross-project leakage.

Core Features & Use Cases

Per-project configuration files: .claude/plugin-name.local.md with YAML frontmatter to persist settings separate from code.
Frontmatter-driven behavior: hooks, commands, and agents read and apply defaults, validations, and prompts.
Templates and references: provides examples, templates, and guidelines to accelerate adoption and onboarding.

Quick Start

Create a per-project .claude/my-plugin.local.md file with YAML frontmatter and a Markdown body, then restart Claude Code to apply changes.

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 in Claude Code?▼

Per-project plugin configuration is managed by storing YAML frontmatter in a local .claude/plugin-name.local.md file, keeping settings separate from code to prevent cross-project leakage.

What is the best way to safely customize Claude plugin behavior for a specific repository?▼

The safest way to customize plugin behavior is using a per-project Markdown file with YAML frontmatter, which allows hooks, commands, and agents to read and apply settings with sensible defaults.

How do I get started with YAML frontmatter configuration for Claude plugins?▼

Create a .claude/my-plugin.local.md file containing YAML frontmatter and a Markdown body, then restart Claude Code to apply the new plugin settings.

Can I use local Markdown files to prevent plugin configuration leakage across projects?▼

Yes, storing plugin configuration in local .md files prevents cross-project leakage by keeping project-specific settings isolated in their respective repository directories.

Do I need any dependencies to apply per-project plugin settings?▼

No dependencies are required; the configuration pattern uses YAML frontmatter in local Markdown files, which hooks, commands, and agents read directly to validate and apply settings.

Why does my Claude plugin configuration not apply across different projects?▼

Plugin configuration does not apply across projects because settings are intentionally stored in per-project .local.md files to ensure isolation and prevent cross-project leakage.