plugin-settings

Manage per-project plugin configurations using .local.md files with YAML frontmatter.

1|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/FacuM/yolo-agent --skill plugin-settings-facum
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-settings
Source: https://github.com/FacuM/yolo-agent/tree/main/.claude/skills/plugin-settings
Command: npx skills add https://github.com/FacuM/yolo-agent --skill plugin-settings-facum

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the need for project-specific plugin configurations, allowing users to customize plugin behavior without altering global settings or committing sensitive information to version control.

Core Features & Use Cases

  • Per-Project Configuration: Store settings in .claude/plugin-name.local.md files for granular control.
  • YAML Frontmatter: Use structured data for settings like enabled, mode, max_retries.
  • Markdown Body: Include additional context, prompts, or documentation within the same file.
  • Use Case: Configure a linter plugin to use strict rules for a critical project while using lenient rules for a quick prototype, all managed via a local settings file.

Quick Start

Create a new file named .claude/my-plugin.local.md in your project's root directory 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 plugin settings for a specific project without changing global configuration?

You can manage project-specific plugin settings by creating a `.claude/plugin-name.local.md` file in your project's root directory. This local configuration approach uses YAML frontmatter for structured settings and markdown body for additional context, keeping global settings untouched.

What is the best way to store per-project plugin configuration and keep sensitive data out of version control?

Using `.local.md` files for per-project plugin configuration ensures sensitive data stays out of version control. The `.local` suffix designates local files that customize plugin behavior and persist state without being committed to the repository.

How do I create a local configuration file to override plugin behavior using YAML and markdown?

Create a file named `.claude/my-plugin.local.md` in your project root. Add YAML frontmatter for structured settings like `enabled`, `mode`, and `max_retries`, then use the markdown body to include additional prompts or documentation for dynamic adaptation.

Can I use bash scripts to parse YAML frontmatter from local markdown files for agent workflows?

Yes, this approach supports parsing via bash scripts to integrate local configuration files into agent workflows. Scripts can extract YAML frontmatter settings from `.local.md` files to enable dynamic adaptation and state persistence during execution.

Does this local configuration pattern work for customizing linter rules differently across multiple projects?

Yes, this pattern supports per-project configuration overrides like applying strict linter rules for a critical project while using lenient rules for a quick prototype. Each project maintains its own `.local.md` settings file for granular control.