plugin-settings

Name: plugin-settings
Availability: InStock
Author: Airmomo

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

Updated Mar 24, 2026

Search Tags:#hooks #configuration #plugin #settings #claude-code #yaml-frontmatter

Ready to run

npx skills add https://github.com/Airmomo/skills --skill plugin-settings-airmomo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plugin-settings
Source: https://github.com/Airmomo/skills/tree/main/plugin-settings
Command: npx skills add https://github.com/Airmomo/skills --skill plugin-settings-airmomo

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill standardizes per-project plugin configuration by storing declarative settings in a YAML frontmatter within .claude plugin files, enabling predictable behavior, consistency across projects, and simple onboarding.

Core Features & Use Cases

Per-project plugin configuration: store per-repo plugin flags, states, and lifecycle options in .claude/plugin-name.local.md files.
Safe defaults and validation: when a settings file is missing or incomplete, sensible defaults are applied with validation rules.
Workflow integration: hooks, commands, and agents read and apply these settings to govern plugin activation, behavior, and restart requirements.

Quick Start

Create a .claude/my-plugin.local.md file with YAML frontmatter and a Markdown body to configure the plugin for the current project.

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

To manage per-project plugin settings in Claude Code, you store declarative configuration using YAML frontmatter within .claude plugin files. This standardizes per-repo flags, states, and lifecycle options for predictable behavior across projects.

What is the best way to configure hooks and commands for a specific repository?▼

Configuring hooks and commands for a specific repository is best done by defining plugin settings in YAML frontmatter. This ensures safe defaults, validation rules, and workflow integration are applied predictably to govern plugin activation.

How does YAML frontmatter handle missing or incomplete plugin configuration files?▼

When YAML frontmatter plugin configuration files are missing or incomplete, the system automatically applies sensible safe defaults alongside validation rules. This ensures hooks and agents function predictably without requiring manual setup for every option.

Can I use local markdown files to store plugin lifecycle options and states?▼

Yes, you can use local markdown files like .claude/plugin-name.local.md to store plugin lifecycle options and states. The YAML frontmatter within these files provides safe parsing, atomic updates, and security-conscious documentation for project-specific configurations.

Why do my Claude Code hooks not maintain consistent behavior across different projects?▼

Claude Code hooks may lack consistent behavior across projects if they lack standardized per-project plugin settings. Storing declarative configuration in YAML frontmatter within .claude plugin files provides safe defaults, validation, and simple onboarding to resolve this.

Are there limitations to using YAML frontmatter for per-project plugin configuration?▼

Using YAML frontmatter for per-project plugin configuration requires strict adherence to safe parsing and atomic updates to prevent corruption. While it standardizes settings and provides validation, incorrect manual edits in local markdown files can still cause configuration failures.