plugin-settings

Store and apply per-project plugin settings in a local Markdown file with YAML frontmatter.

Updated Mar 27, 2026

Search Tags:#markdown #hooks #configuration #plugin #yaml #local #frontmatter

Ready to run

npx skills add https://github.com/onelee85/my-skills --skill plugin-settings-onelee85

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plugin-settings
Source: https://github.com/onelee85/my-skills/tree/main/claude-plugins-official/plugins/plugin-dev/skills/plugin-settings
Command: npx skills add https://github.com/onelee85/my-skills --skill plugin-settings-onelee85

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Per-project plugin configuration is challenging; this Skill defines a standard pattern to store per-project plugin settings in a local Markdown file with YAML frontmatter, enabling isolated, predictable behavior.

Core Features & Use Cases

Local configuration file at .claude/plugin-name.local.md that uses YAML frontmatter for structured settings and a Markdown body for prompts or context.
Settings are designed to be gitignored to prevent accidental commits of sensitive information and to keep project state separate.
Includes reading, validating, and applying configuration across hooks, commands, and agents, with templates and best practices for safe editing.

Quick Start

Create a file at .claude/plugin-name.local.md with a YAML frontmatter block and a Markdown body to initialize project-specific plugin 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 locally?▼

Store per-project plugin configuration by creating a local Markdown file with YAML frontmatter. This pattern isolates project-specific settings in a dedicated file, enabling predictable plugin behavior without modifying global configurations.

What is the best way to manage local YAML settings for a development environment?▼

Managing local YAML settings is best handled by storing them in a gitignored Markdown file with a YAML frontmatter block. This prevents accidental commits of sensitive information while keeping structured settings and contextual prompts together.

How do I apply project-specific settings during hook execution?▼

Apply project-specific settings during hook execution by reading and validating the local YAML frontmatter configuration file. The Skill provides templates and workflows to safely parse these settings before triggering command workflows or agent coordination.

Does plugin configuration support safe-edit workflows for local files?▼

Plugin configuration supports safe-edit workflows by providing templates and best practices for modifying local Markdown files. This ensures structured YAML frontmatter settings are validated and applied correctly without corrupting the file.

Why should I use YAML frontmatter in a Markdown file for plugin settings?▼

Use YAML frontmatter in a Markdown file for plugin settings to separate structured configuration data from descriptive context. This approach keeps project state isolated and predictable while preventing sensitive information from being committed to version control.

Can I use a local configuration file to isolate plugin behavior across projects?▼

You can isolate plugin behavior across projects by using a dedicated local configuration file. Each project maintains its own Markdown file with YAML frontmatter, ensuring that settings, prompts, and hook executions remain independent and predictable.