plugin-settings

Parse YAML frontmatter and markdown bodies from `.claude/plugin-name.local.md` files.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/spandios/vibe-utils --skill plugin-settings-spandios
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-settings
Source: https://github.com/spandios/vibe-utils/tree/main/skills/plugin-settings
Command: npx skills add https://github.com/spandios/vibe-utils --skill plugin-settings-spandios

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a standardized pattern for managing per-project plugin configurations and state, ensuring consistency and simplifying user-defined behavior across different development environments.

Core Features & Use Cases

  • Per-Project Configuration: Store settings in .claude/plugin-name.local.md files within your project root.
  • YAML Frontmatter: Define structured settings (e.g., enabled: true, mode: strict) using YAML.
  • Markdown Body: Include additional context, prompts, or instructions within the same file.
  • Hook/Command Integration: Easily read and parse these settings in bash scripts or commands for dynamic behavior.
  • Use Case: A linter plugin can read a .claude/linter.local.md file to apply project-specific linting rules and severity levels, rather than relying on global defaults.

Quick Start

Create a .claude/my-plugin.local.md file in your project root with your desired settings.

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 configurations locally?

Per-project plugin configurations are managed using `.claude/plugin-name.local.md` files, which store structured settings in YAML frontmatter and contextual instructions in the markdown body to ensure consistent behavior across environments.

How do I read YAML frontmatter settings in bash scripts for dynamic behavior?

You can parse YAML frontmatter settings in bash scripts by reading the `.claude/plugin-name.local.md` file to extract values like `enabled`, `mode`, and custom parameters, supporting string, boolean, numeric, and list field types.

What is the best way to store plugin state and settings per project?

The best way to store plugin state is using `.claude/plugin-name.local.md` files with YAML frontmatter, allowing you to define structured settings like `enabled: true` and `mode: strict` alongside markdown context for hooks and commands.

Can I include custom instructions alongside structured plugin settings?

Yes, the `.claude/plugin-name.local.md` file supports a markdown body below the YAML frontmatter, allowing you to include additional context, prompts, or instructions within the same configuration file.

Does this approach support parsing different data types in plugin configuration?

Yes, the parsing techniques support string, boolean, numeric, and list fields within the YAML frontmatter, enabling robust extraction of various data types for real-world plugin integration scenarios.

When do I need a local configuration file for plugin settings?

You need a local configuration file when a plugin requires project-specific settings, such as a linter applying custom linting rules and severity levels instead of relying on global defaults across different development environments.