skills.rest
angrybeagles
angrybeaglesCOMMUNITY
Explore all skills by this author →
GitHub

plugin-settings

Parse YAML frontmatter from .claude/plugin-name.local.md files to apply per-project plugin configuration.

Updated Apr 13, 2026
Search Tags:#hooks#configuration#claude-code#yaml-frontmatter#per-project#plugin-settings#local-md
One-click install
npx skills add https://github.com/angrybeagles/weather-dashboard --skill plugin-settings-angrybeagles
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plugin-settings
Source: https://github.com/angrybeagles/weather-dashboard/tree/main/.claude/plugins/marketplaces/claude-plugins-official/plugins/plugin-dev/skills/plugin-settings
Command: npx skills add https://github.com/angrybeagles/weather-dashboard --skill plugin-settings-angrybeagles

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill enables per-project plugin configuration by storing frontmatter-based settings in a dedicated local file that Claude Code plugins can read and apply automatically.

Core Features & Use Cases

  • Per-project configuration: keep plugin behavior isolated to each project via a .claude/*.local.md file.
  • YAML frontmatter + markdown body: separate structured fields from the operational prompts.
  • Hooks/go-to-actions: enable or disable plugin features, set defaults, and describe usage in prompts and tasks.
  • Example scenario: a team configures plugin behavior for different repositories without global changes.

Quick Start

Create a file at .claude/plugin-name.local.md with YAML frontmatter to configure the plugin and enable its hooks.

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 settings are configured by creating a `.claude/plugin-name.local.md` file with YAML frontmatter. This file isolates plugin behavior to the current project without modifying global configurations.

Can I use YAML frontmatter to toggle hooks and enforce defaults for specific repositories?▼

YAML frontmatter allows you to toggle features, enforce defaults, and safely scope behavior for hooks, commands, and agents. This separates structured configuration fields from operational markdown body prompts.

What is the best way to isolate Claude Code plugin behavior across different projects?▼

Using a dedicated `.claude/*.local.md` file isolates plugin behavior per project. This enables teams to configure distinct plugin behaviors for different repositories without triggering global changes.

How do I parse and apply local markdown frontmatter to guide plugin behavior?▼

The skill parses YAML frontmatter from the local markdown file to validate values and apply default fallbacks. The markdown body content provides operational prompts to guide plugin tasks.

Does Claude Code support per-project configuration without changing global plugin settings?▼

Claude Code supports per-project configuration through local markdown files. You can enable or disable plugin features and set defaults scoped exclusively to the current project repository.

Related Skills

Explore More Software Engineering Skills→
dariopalminiodariopalminio
1

header-aggregation

Standardize YAML frontmatter across Markdown spec files with batch processing.

Community
Advanced
fcakyonfcakyon
1.0k

plugin-settings

Store per-project plugin configuration in .claude/*.local.md files with YAML frontmatter.

Community
Intermediate
juanca202juanca202

speckit-git-commit

Automate Git commits after Spec Kit command events.

Community
Basic
BekaChkhiroBekaChkhiro
1

planSettingsReset

Reset Claude Plan Plugin settings to defaults for local or global scopes.

Community
Advanced