Where should I store the plugin configuration files?

Configuration files should be placed in the project root under the .claude/ directory using the naming convention 'plugin-name.local.md'.

Does this skill require files to be committed to Git?

No, it is a best practice to add .claude/*.local.md to your .gitignore file to keep local preferences and state out of the shared repository.

How do I parse these settings in a bash hook?

The skill provides standardized sed and awk patterns to extract YAML frontmatter fields and the Markdown body directly from the configuration files.

Why do I need to restart Claude Code after changing a setting?

Claude Code hooks are typically initialized at the start of a session; a restart ensures that the bash scripts and agents parse the updated YAML frontmatter.

Plugin Configuration Manager

Name: Plugin Configuration Manager
Author: Microck

byMicrock

•

111

Developer Tools

Implements a standardized pattern for project-specific plugin settings using YAML frontmatter and markdown files.

About

The Configured Agent skill provides a robust architecture for managing local, project-specific settings and state within the Claude Code environment. By utilizing a .claude/plugin-name.local.md file structure, it allows developers to define structured configuration data in YAML frontmatter alongside rich instructional context in Markdown, enabling highly customizable behaviors for hooks, commands, and AI agents without polluting the global environment or version control.

Key Features

Markdown body integration for prompt injection and context
Built-in state management for multi-agent coordination
Standardized .claude/local.md file pattern for per-project settings
YAML frontmatter support for structured configuration data
111 GitHub stars
Bash-compatible parsing patterns for CLI hook integration

Use Cases

Defining project-level strictness or validation rules for automated CLI tools
Maintaining persistent state and task progress for complex multi-agent workflows
Toggling specific repository hooks on or off without modifying global configurations

About

Key Features

Markdown body integration for prompt injection and context
Built-in state management for multi-agent coordination
Standardized .claude/local.md file pattern for per-project settings
YAML frontmatter support for structured configuration data
111 GitHub stars
Bash-compatible parsing patterns for CLI hook integration

Use Cases

Defining project-level strictness or validation rules for automated CLI tools
Maintaining persistent state and task progress for complex multi-agent workflows
Toggling specific repository hooks on or off without modifying global configurations