Plugin Settings

Organize per-project plugin settings in Markdown files with YAML frontmatter.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/ricable/mcai --skill plugin-settings-ricable
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Plugin Settings
Source: https://github.com/ricable/mcai/tree/main/.agents/skills/plugin-settings
Command: npx skills add https://github.com/ricable/mcai --skill plugin-settings-ricable

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps you store and read per-project plugin configuration in a simple Markdown file instead of scattering settings across scripts, hooks, and ad hoc notes.

Core Features & Use Cases

  • Project-local configuration: Keep plugin settings in a .claude/plugin-name.local.md file with YAML frontmatter and a readable Markdown body.
  • State and behavior control: Toggle features, store iteration or task state, and adapt plugin behavior based on user-defined values.
  • Parsing and validation: Read frontmatter fields, extract body content, validate booleans and numeric limits, and update settings safely with atomic file writes.
  • Use Case: A team enables a plugin only for one repository, sets strict validation mode, and stores task context directly in the file so hooks and commands can respond consistently.

Quick Start

Create a .claude/plugin-name.local.md file with YAML frontmatter and a markdown body, then restart Claude Code so the plugin can load the new settings.

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 configuration in a readable Markdown file?

Store per-project plugin configuration in a Markdown file with YAML frontmatter and a readable body. This approach replaces scattered ad hoc settings by keeping plugin activation and task state organized in a single editable file.

What is the best way to validate booleans and paths in YAML frontmatter for Claude Code?

Validating YAML frontmatter involves parsing fields to check booleans, numeric limits, and file existence. This ensures plugin settings like strict validation mode are correctly typed before being applied to project scenarios.

How do I manage plugin state and behavior control across different repositories?

Manage plugin state and behavior control by storing iteration state and feature toggles in a local Markdown file. This allows hooks and commands to respond consistently based on user-defined values within that specific repository.

Does Plugin Settings support atomic file writes for updating local configuration?

Plugin Settings supports atomic file writes to safely update local configuration. This prevents data corruption during parsing and validation of frontmatter fields and Markdown body content.

How do I parse markdown body content separately from YAML frontmatter for plugin settings?

Parsing markdown body content separately from YAML frontmatter requires extracting body content after reading the header fields. This allows you to handle human-readable configuration notes alongside structured plugin settings.

When do I need a structured configuration file instead of ad hoc notes for Claude Code plugins?

You need a structured configuration file instead of ad hoc notes when team coordination requires consistent plugin behavior. A local Markdown file with YAML frontmatter keeps settings readable and project-specific.