plugin-settings

Store structured YAML plugin settings in project-local markdown files.

3|Updated May 3, 2026
One-click install
npx skills add https://github.com/chloebrett/slay --skill plugin-settings-chloebrett
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-settings
Source: https://github.com/chloebrett/slay/tree/main/.claude/plugins/marketplaces/claude-plugins-official/plugins/plugin-dev/skills/plugin-settings
Command: npx skills add https://github.com/chloebrett/slay --skill plugin-settings-chloebrett

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Managing plugin configurations across different projects can be cumbersome and error-prone, leading to inconsistent behaviors.

Core Features & Use Cases

  • Structured Plugin Configuration: Store plugin settings in .claude/plugin-name.local.md files with YAML frontmatter for clear organization.
  • Per-Project Customization: Enable project-specific adjustments without affecting global settings.
  • Use Case: Developers can adjust plugin parameters for different projects, such as toggling features or setting operational modes, by editing local config files.

Quick Start

Create a .claude/your-plugin.local.md with YAML frontmatter that defines your plugin's settings; then restart Claude for changes to take effect.

Frequently Asked Questions about plugin-settings

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

FAQPage Schema
How do I manage plugin configuration settings for a specific project?

You can manage per-project plugin configuration by creating a `.claude/your-plugin.local.md` file with YAML frontmatter. This stores structured settings locally, allowing project-specific adjustments without affecting global configurations.

What is the best way to store local YAML settings for project plugins?

The best way to store local YAML settings is within `.claude/plugin-name.local.md` files. This approach simplifies per-project configuration management by keeping structured YAML data in specific markdown files for flexible adjustments.

How does project-specific plugin configuration work with markdown files?

Project-specific plugin configuration works by storing structured YAML frontmatter inside local markdown files. This ensures plugin behavior can be tailored, validated, and centrally controlled through project-local files for varying environments.

Can I customize plugin behaviors per project without changing global settings?

Yes, you can customize plugin behaviors per project without altering global settings. By editing local `.claude` markdown files with YAML frontmatter, developers can toggle features or set operational modes for individual projects.

Do I need to restart Claude after updating local plugin settings?

Yes, you need to restart Claude for changes to take effect after updating your local plugin settings. Once you define or modify the YAML frontmatter in your `.claude` configuration file, a restart applies the new parameters.

Why use YAML frontmatter in markdown files for plugin configuration?

Using YAML frontmatter in markdown files provides clear organization for plugin configuration. It simplifies per-project configuration management by storing structured data in specific local files, ensuring behaviors can be validated and centrally controlled.