Plugin Settings

Configure per-project plugin behavior via YAML frontmatter in .claude plugin-local files.

43|9|Updated Nov 16, 2025
One-click install
npx skills add https://github.com/ssdeanx/AgentStack --skill plugin-settings-ssdeanx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Plugin Settings
Source: https://github.com/ssdeanx/AgentStack/tree/main/.github/skills/plugin-settings
Command: npx skills add https://github.com/ssdeanx/AgentStack --skill plugin-settings-ssdeanx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, grep, sed, awk, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Per-project plugin configuration is tedious without a reusable pattern; this skill provides a structured approach to store per-project state in .claude plugin-local files using YAML frontmatter and a Markdown body for prompts and usage context.

Core Features & Use Cases

  • YAML frontmatter driven configuration for hooks, commands, and agent behavior
  • Per-project state, defaults, templates, and best practices to ensure safe changes
  • Clear guidance for reading, writing, and restarting Claude Code after edits

Quick Start

Create .claude/my-plugin.local.md with YAML frontmatter and a Markdown body for prompts and usage instructions.

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

Per-project plugin behavior is configured by storing YAML frontmatter in .claude plugin-local files, which enables toggles, modes, and stateful settings with defaults for hooks, commands, and agents.

What is the best way to manage stateful settings for Claude Code hooks and commands?

Managing stateful settings for hooks and commands is best handled by writing YAML frontmatter in Markdown files, providing a structured approach with defaults, templates, and best practices to ensure safe changes.

Can I use YAML frontmatter to toggle plugin modes in .claude local files?

Yes, YAML frontmatter can be used in .claude local files to toggle plugin modes, validate fields, and apply stateful configurations across hooks, commands, and agents with clear defaults.

Do I need bash and sed to parse YAML frontmatter for Claude Code plugins?

Yes, parsing and validating YAML frontmatter for Claude Code plugins requires bash, grep, sed, and awk dependencies to extract settings and prevent misconfigurations in local files.

Why does editing plugin settings require restarting Claude Code?

Editing plugin settings requires restarting Claude Code to apply the updated YAML frontmatter, ensuring the new toggles, modes, and stateful configurations are properly loaded into the active environment.

How do I prevent misconfigurations when writing YAML frontmatter for plugin settings?

To prevent misconfigurations when writing YAML frontmatter, use provided templates and examples, validate fields during parsing, and follow structured best practices for storing per-project state in .claude files.