plugin-settings

Name: plugin-settings
Availability: InStock
Author: skogai

Store and retrieve per-project plugin configurations using YAML frontmatter in local markdown files.

Updated May 3, 2026

Search Tags:#automation #state management #configuration #plugin #yaml #settings

Ready to run

npx skills add https://github.com/skogai/marketplace --skill plugin-settings-skogai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plugin-settings
Source: https://github.com/skogai/marketplace/tree/main/plugin-dev/skills/plugin-settings
Command: npx skills add https://github.com/skogai/marketplace --skill plugin-settings-skogai

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill solves the challenge of managing per-project configurations for Claude Code plugins, ensuring that settings are consistent, version-controlled, and easily accessible to hooks, commands, and agents.

Core Features & Use Cases

Structured Configuration: Uses YAML frontmatter for clean, readable, and type-safe plugin settings.
Project-Specific State: Enables per-project behavior customization without polluting global plugin settings.
Use Case: A security-focused plugin can use this to toggle strict validation modes on a per-project basis, ensuring sensitive files are protected only where necessary.

Quick Start

Create a file named .claude/plugin-name.local.md in your project root with your desired YAML configuration and restart Claude Code to apply the 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 in Claude Code?▼

To manage per-project plugin configurations, create a `.claude/plugin-name.local.md` file in your project root with YAML frontmatter. Restart Claude Code to apply the settings, ensuring consistent behavior management for hooks, commands, and agents.

What is the best way to store project-specific plugin settings without affecting global state?▼

Storing project-specific plugin settings in local markdown files with YAML frontmatter isolates configuration from global state. This pattern prevents global pollution by keeping settings-driven logic strictly tied to the current project directory.

How do I use YAML frontmatter to toggle plugin behavior on a per-project basis?▼

You can use YAML frontmatter to toggle plugin behavior by defining configuration keys within the frontmatter block. The plugin then parses this structured configuration to enable or disable features, such as strict validation modes, for that specific project.

Does Claude Code support version-controlled settings for hooks and agents?▼

Yes, Claude Code supports version-controlled settings by storing plugin configurations as YAML frontmatter in local markdown files. This approach makes settings easily accessible to hooks, commands, and agents while remaining version-controlled.

Can I use markdown files for state management across different plugins?▼

Yes, you can use markdown files for state management by standardizing configuration storage with YAML frontmatter. This provides robust parsing patterns that facilitate settings-driven logic across multiple hooks, commands, and agents consistently.

Why are my local plugin settings not applying after updating the YAML configuration?▼

Local plugin settings in YAML frontmatter may not apply if Claude Code was not restarted after modifying the `.claude/plugin-name.local.md` file. Restarting the application ensures the new per-project configurations are properly loaded.