Can I use these settings in Bash scripts?

Yes, this skill provides specific shell patterns using sed and awk to extract YAML frontmatter fields directly into your scripts or hooks.

What is the benefit of using YAML frontmatter in Markdown?

It provides a human-readable way to store structured data like booleans and lists while allowing the rest of the file to serve as documentation or a prompt template.

How do I apply changes to my plugin settings?

Because hooks are loaded at startup, you must restart Claude Code for changes to take effect in your active session.

Where are plugin settings stored?

Settings are stored in the .claude/ directory within your project root using the .claude/plugin-name.local.md format.

Do I need to commit these settings to Git?

No, these files are intended to be local and should be added to your .gitignore to prevent leaking environment-specific or private configurations.

Claude Code Plugin Configuration Manager

Name: Claude Code Plugin Configuration Manager
Author: Activer007

byActiver007

Developer Tools

Implements a standardized pattern for local plugin settings and state management using YAML frontmatter in Markdown files.

About

This skill provides a robust framework for managing per-project configuration and state for Claude Code plugins. By utilizing the .claude/plugin-name.local.md pattern, it enables users to define structured settings in YAML while providing rich context in Markdown. This approach allows plugins to adapt their behavior dynamically through hooks and commands without requiring session-level hardcoding, ensuring that plugin state is persisted locally, kept out of version control, and easily accessible to both AI agents and shell scripts.

Key Features

Standardized .local.md file pattern for project-specific settings
Guidelines for Git-safe local state management
YAML frontmatter parsing for structured configuration data
Bash script integration for reading settings within hooks
0 GitHub stars
Markdown body support for dynamic prompts and context

Use Cases

Defining project-specific validation levels or security policies for automation
Storing agent-specific state and task progress across multiple sessions
Enabling or disabling specific plugin hooks without editing core configuration files

About

Key Features

Standardized .local.md file pattern for project-specific settings
Guidelines for Git-safe local state management
YAML frontmatter parsing for structured configuration data
Bash script integration for reading settings within hooks
0 GitHub stars
Markdown body support for dynamic prompts and context

Use Cases

Defining project-specific validation levels or security policies for automation
Storing agent-specific state and task progress across multiple sessions
Enabling or disabling specific plugin hooks without editing core configuration files