How do I read the configuration values in a shell script?

You can parse the YAML frontmatter using a combination of sed and grep within your Bash hooks to extract specific fields like 'enabled' or 'mode'.

Where should I store plugin settings in my project?

Settings should be stored in the .claude/ directory using the naming convention .claude/plugin-name.local.md to ensure consistency and isolation.

Do I need to commit these settings to Git?

No, these files are intended to be local to the user and project. You should add .claude/*.local.md to your .gitignore to prevent sensitive or local-only data from being committed.

Do settings changes take effect immediately?

Generally, Claude Code requires a restart to pick up changes to hooks or state files that affect the plugin's core behavior or initialization.

Plugin Settings Manager

Name: Plugin Settings Manager
Author: lusya123

bylusya123

Developer Tools

Implements a standardized pattern for project-specific plugin configuration using YAML frontmatter in local Markdown files.

About

This skill provides a robust framework for managing per-project plugin settings and state within the Claude Code ecosystem. By utilizing the .claude/plugin-name.local.md file pattern, it allows developers to store structured configuration data alongside descriptive context without polluting version control. It offers practical implementation patterns for reading settings from Bash hooks, commands, and agents, enabling dynamic behavior such as feature flags, agent state tracking, and environment-specific validation rules while maintaining a clear separation between code and project-specific state.

Key Features

0 GitHub stars
Support for per-project state management in multi-agent workflows
Security-focused best practices for git management and user input
Structured YAML frontmatter parsing for easy data extraction
Integration patterns for Bash hooks, commands, and agent instructions
Standardized .local.md file pattern for project-specific configuration

Use Cases

Configuring project-specific feature flags and validation levels for custom hooks
Storing project-specific metadata and prompts for specialized commands
Managing persistent state and task assignments in multi-agent swarms

About

Key Features

0 GitHub stars
Support for per-project state management in multi-agent workflows
Security-focused best practices for git management and user input
Structured YAML frontmatter parsing for easy data extraction
Integration patterns for Bash hooks, commands, and agent instructions
Standardized .local.md file pattern for project-specific configuration

Use Cases

Configuring project-specific feature flags and validation levels for custom hooks
Storing project-specific metadata and prompts for specialized commands
Managing persistent state and task assignments in multi-agent swarms