plugin-settings

Defines .local.md files with YAML frontmatter for Claude Code plugin settings and persistent state management workflows.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/aah-stack/anthropic --skill plugin-settings-aah-stack
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plugin-settings
Source: https://github.com/aah-stack/anthropic/tree/main/plugins/plugin-dev/skills/plugin-settings
Command: npx skills add https://github.com/aah-stack/anthropic --skill plugin-settings-aah-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, tmux, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill solves the challenge of managing user-specific plugin configuration and persistent state by providing a structured local settings pattern for Claude Code plugins.

Core Features & Use Cases

  • Local Configuration Pattern: Defines how plugins use.claude/plugin-name.local.md files with YAML frontmatter and markdown content for per-project settings.
  • Settings Integration: Provides guidance for reading configuration from hooks, commands, and agents while supporting enabled flags, validation, and defaults.
  • Use Case: A plugin developer can use this Skill to create configurable behavior, store agent state, or manage project-specific options without committing local settings to version control.

Quick Start

Use the plugin-settings skill to design a configurable Claude Code plugin that reads and applies project-local 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 local settings for Claude Code plugins?▼

Plugin local settings are managed using .claude/plugin-name.local.md files containing YAML frontmatter and markdown content. This pattern supports per-project configuration, enabled flags, and persistent state without committing local settings to version control.

Can I read plugin configuration from hooks and commands in Claude Code?▼

Yes, configuration is read from hooks, commands, and agents by parsing YAML frontmatter. The pattern supports enabled flags, validation, and defaults, allowing configurable behavior and project-specific options across plugin execution workflows.

What is the best way to store per-project state for a Claude Code plugin?▼

Per-project state is stored using .claude/plugin-name.local.md files with YAML frontmatter. This approach keeps user-specific configuration out of version control while allowing hooks and agents to read and apply persistent state reliably.

Do I need jq and tmux to configure Claude plugin settings?▼

Yes, jq and tmux are required dependencies. jq handles parsing and validating YAML frontmatter configuration, while tmux supports the helper scripts that manage settings workflows and per-project state operations reliably.

Why use YAML frontmatter in markdown files for plugin configuration?▼

YAML frontmatter provides structured configuration that jq can parse and validate, while the markdown body supports human-readable documentation. This dual format enables automated hooks and developer guidance within a single local settings file.