skills.rest
timgranlundmarsden
timgranlundmarsdenCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

Plugin Settings

Store and read per-project plugin settings from markdown files with YAML frontmatter.

2|1|Updated Apr 9, 2026
Search Tags:#validation#claude code#yaml frontmatter#bash scripting#plugin settings#hook configuration#state files
One-click install
npx skills add https://github.com/timgranlundmarsden/claude-agent-flow --skill plugin-settings-timgranlundmarsden
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Plugin Settings
Source: https://github.com/timgranlundmarsden/claude-agent-flow/tree/main/skills/plugin-settings
Command: npx skills add https://github.com/timgranlundmarsden/claude-agent-flow --skill plugin-settings-timgranlundmarsden

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you store, read, validate, and update per-project plugin settings and state without hardcoding behavior into hooks or commands.

Core Features & Use Cases

  • Project-local configuration: Use .claude/plugin-name.local.md files to keep user-specific settings out of version control.
  • YAML frontmatter parsing: Extract booleans, numbers, strings, and lists from markdown-based configuration files.
  • Hook and agent coordination: Drive deterministic behavior in hooks, commands, and agents using shared settings and state.
  • Validation and safety checks: Validate file structure, required markers, field formats, and common edge cases before acting.
  • Use case: Configure a plugin to toggle strict validation, set size limits, and store task state for multi-agent workflows.

Quick Start

Use this skill to design a .claude/plugin-name.local.md settings file for your plugin and explain how to read and validate it in hooks or commands.

Frequently Asked Questions about Plugin Settings

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I store per-project plugin settings for Claude Code without hardcoding behavior?▼

Store per-project plugin settings in markdown files with YAML frontmatter, keeping configuration data out of hooks and commands for flexible behavior management.

What is the best way to parse YAML frontmatter in markdown for Claude Code hooks?▼

Parse YAML frontmatter from markdown files to extract booleans, numbers, strings, and lists, enabling deterministic hook configuration and shared agent coordination state.

How do I validate plugin configuration fields and state files for edge cases?▼

Validate file structure, required markers, and field formats in plugin settings files to apply safety checks and handle common edge cases before executing hook logic.

Can I keep user-specific Claude Code settings out of version control?▼

Use `.claude/plugin-name.local.md` files to maintain project-local configuration, ensuring user-specific plugin settings and state remain separate from version control.

How does markdown body extraction work for reliable plugin operation?▼

Markdown body extraction separates configuration content from YAML frontmatter, allowing plugins to read descriptive settings and state while validating frontmatter fields independently.

Related Skills

Explore More Software Engineering Skills→
fcakyonfcakyon
1.0k

plugin-settings

Store per-project plugin configuration in .claude/*.local.md files with YAML frontmatter.

Community
Intermediate
JoeyJoziahJoeyJoziah

Hooks Automation

Automate pre- and post-operation hook coordination for Claude Code workflows.

Community
Advanced
juanandresgsjuanandresgs
191

diagnose

Validates hook integrity, state files, and Git health for Claude Code configuration.

Community
Intermediate
jmolzjmolz

Plugin Settings

Manage plugin configurations via YAML frontmatter in .Codex markdown files.

Community
Basic