skills.rest
opensesh
openseshCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

Plugin Settings

Manage per-project plugin configurations using `.claude/plugin-name.local.md` files with YAML frontmatter.

Updated Aug 23, 2026
Search Tags:#project-specific#yaml frontmatter#bash scripting#plugin configuration#settings management#local configuration
One-click install
npx skills add https://github.com/opensesh/BOS-2.0 --skill plugin-settings-opensesh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Plugin Settings
Source: https://github.com/opensesh/BOS-2.0/tree/main/.claude/plugins/plugin-dev/skills/plugin-settings
Command: npx skills add https://github.com/opensesh/BOS-2.0 --skill plugin-settings-opensesh

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: Define settings in .claude/plugin-name.local.md files for granular control.
  • YAML Frontmatter: Use YAML for structured settings (booleans, strings, lists).
  • Markdown Body: Include prompts, instructions, or documentation within the same file.
  • Hook/Agent Integration: Scripts and agents can read these settings to adapt their behavior.
  • Use Case: A linter plugin might have different strictness levels or file inclusion rules for different projects, all managed via its .local.md file.

Quick Start

Create a .claude/my-plugin.local.md file in your project root to configure plugin behavior.

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 configuration for individual projects?▼

Manage plugin configuration per project by creating `.claude/plugin-name.local.md` files in your project root, using YAML frontmatter for structured settings and markdown for additional context.

What is the best way to keep project-specific plugin settings out of version control?▼

Use `.local.md` files to define project-specific plugin settings, allowing you to customize plugin behavior locally without committing sensitive information to version control.

Can I use YAML frontmatter to define structured settings for hooks and agents?▼

Yes, YAML frontmatter supports structured settings like booleans, strings, and lists, enabling scripts, hooks, and agents to read and dynamically adapt their behavior.

How do bash scripts parse local plugin configuration files?▼

Bash scripts parse local plugin configuration files by reading the YAML frontmatter and markdown body from `.claude/plugin-name.local.md`, validating the structured settings to adapt plugin behavior.

Does this per-project configuration approach work for adjusting linter strictness across different projects?▼

Yes, a linter plugin can use this approach to define different strictness levels or file inclusion rules for different projects via its `.local.md` configuration file.

Related Skills

Explore More Software Engineering Skills→
mcj-codermcj-coder
1

greenfield-baseline

Automate project scaffolding with quality gates, CI/CD, and repository structure.

Community
Advanced
zach-sourcezach-source

Plugin Settings

Manage per-project plugin configuration and state via `.claude/plugin-name.local.md` files.

Community
Intermediate
LeighAtkinsLeighAtkins

Plugin Settings

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

Community
Intermediate
skogaiskogai

plugin-settings

Store and retrieve per-project plugin configurations using YAML frontmatter in local markdown files.

Official
Intermediate