skills.rest
mbarnes-code
mbarnes-codeCOMMUNITY
Explore all skills by this author →
GitHub

Plugin Settings

Manage per-project plugin settings via YAML frontmatter in .claude files.

Updated Jan 21, 2026
Search Tags:#yaml frontmatter#bash scripting#plugin configuration#per-project#settings management#local configuration
One-click install
npx skills add https://github.com/mbarnes-code/multi-agent-vllm --skill plugin-settings-mbarnes-code
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Plugin Settings
Source: https://github.com/mbarnes-code/multi-agent-vllm/tree/main/features/claude-plugins-official/plugins/plugin-dev/skills/plugin-settings
Command: npx skills add https://github.com/mbarnes-code/multi-agent-vllm --skill plugin-settings-mbarnes-code

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a standardized way to manage per-project configurations and state for plugins, allowing for flexible and context-aware plugin behavior without altering core plugin code or committing sensitive information.

Core Features & Use Cases

  • Per-Project Configuration: Store settings in .claude/plugin-name.local.md files within your project root.
  • YAML Frontmatter: Use structured YAML for settings like enabled, mode, max_retries, etc.
  • Markdown Body: Include additional context, prompts, or documentation within the same file.
  • Use Case: Configure a code formatting plugin to use specific rules for one project, while using default rules for others, all managed via a .claude/formatter.local.md file.

Quick Start

Create a .claude/my-plugin.local.md file in your project root with your desired settings.

Frequently Asked Questions about Plugin Settings

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

FAQPage Schema
How do I manage per-project plugin configuration without altering core code?▼

YAML frontmatter provides structured settings like `enabled`, `mode`, and `max_retries` in `.claude/plugin-name.local.md` files, while the markdown body stores additional context, prompts, or documentation alongside the configuration.

How do I set up local settings for a plugin in a specific project?▼

To set up local settings, create a `.claude/my-plugin.local.md` file in your project root directory containing YAML frontmatter for structured variables and markdown for any additional context or documentation.

Can I use bash scripting to parse YAML frontmatter for plugin settings?▼

Yes, bash scripting is utilized to parse and manage the `.claude/plugin-name.local.md` settings files, extracting the YAML frontmatter to enable customizable plugin behavior across different projects.

What is the best way to maintain different plugin settings across multiple projects?▼

The best way to maintain different settings across projects is using `.claude/plugin-name.local.md` files, which enable per-project configuration and state management so each project retains its own specific rules.

Why use local markdown files instead of global configuration for plugin state management?▼

Local markdown files prevent the need to alter core plugin code or commit sensitive information, providing a standardized, context-aware approach to managing plugin state and behavior on a per-project basis.

Related Skills

Explore More Software Engineering Skills→
jeffpeckyjeffpecky

plugin-settings

Manage Claude Code plugin settings in .local.md files with YAML frontmatter.

Community
Intermediate
LeighAtkinsLeighAtkins

Plugin Settings

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

Community
Intermediate
VivekSinghRathore7VivekSinghRathore7

plugin-settings

Manage Claude Code plugin settings via YAML frontmatter and markdown files.

Community
Intermediate
AWS-EducateAWS-Educate

Plugin Settings

Manage per-project AI plugin settings with YAML frontmatter in .claude files.

Official
Intermediate