plugin-settings

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

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/Wizarck/eligia-skills --skill plugin-settings-wizarck
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-settings
Source: https://github.com/Wizarck/eligia-skills/tree/main/claude-plugins-official/plugins/plugin-dev/skills/plugin-settings
Command: npx skills add https://github.com/Wizarck/eligia-skills --skill plugin-settings-wizarck

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps you store and read plugin-specific configuration and state in project-local Markdown files so behavior can be customized without changing code.

Core Features & Use Cases

  • Project-local configuration: Keep user preferences, state, and task metadata in a Markdown file with YAML frontmatter.
  • Reliable parsing patterns: Read booleans, numbers, strings, and markdown bodies from settings files in hooks, commands, and agents.
  • Safe operational workflow: Use validation, defaults, quick-exit checks, and atomic updates to avoid corrupting user-local state.
  • Use case: Configure a Claude Code plugin per repository so one project runs in strict validation mode while another uses standard behavior.

Quick Start

Ask the skill to help you create and use a .claude/my-plugin.local.md settings file for a project-specific plugin configuration.

Frequently Asked Questions about plugin-settings

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

FAQPage Schema
How do I manage per-project plugin settings in Claude Code?

Per-project plugin settings are managed by creating and reading .claude/plugin-name.local.md Markdown files with YAML frontmatter to store user-specific configuration and state without changing code.

What is the best way to parse YAML frontmatter and markdown bodies from local settings files?

Parsing YAML frontmatter and markdown bodies from local settings files involves extracting booleans, numbers, strings, and text content using reliable patterns to read user preferences in hooks, commands, and agents.

How do I safely update plugin state files to avoid corrupting user-local configuration?

Safely updating plugin state files requires using validation, defaults, quick-exit checks, and atomic updates to prevent corrupting user-local configuration during operational workflows.

Can I configure a Claude Code plugin to run in strict validation mode for one repository and standard behavior for another?

Configuring a Claude Code plugin per repository allows one project to run in strict validation mode while another uses standard behavior by applying project-local Markdown settings files.

Does Claude Code support project-local configuration files for user-specific plugin behavior?

Claude Code supports project-local configuration by reading .claude/plugin-name.local.md files from hooks, commands, and agents to apply user-specific behavior per repository.

Why do my plugin hooks fail to read booleans and numbers from local settings files?

Plugin hooks fail to read booleans and numbers from local settings files when YAML frontmatter parsing is not implemented correctly, requiring proper validation and defaults to handle missing or malformed data.