Plugin Settings

Manage per-project plugin settings via YAML frontmatter in .claude/plugin-name.local.md.

1|Updated Oct 14, 2025

Search Tags:#automation #claude #plugin #yaml #settings #frontmatter #local.md

Ready to run

npx skills add https://github.com/Invictusprime7/unison-tasks-official --skill plugin-settings-invictusprime7

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Plugin Settings
Source: https://github.com/Invictusprime7/unison-tasks-official/tree/main/claude-code-main/plugins/plugin-dev/skills/plugin-settings
Command: npx skills add https://github.com/Invictusprime7/unison-tasks-official --skill plugin-settings-invictusprime7

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Managing per-project plugin configuration and state using YAML frontmatter stored in .claude/plugin-name.local.md.

Core Features & Use Cases

Centralized per-project settings stored in a single local file that is Git-ignored.
Supports YAML frontmatter fields (enabled, mode, etc.) and a Markdown body for prompts or context.
Flexible templates and patterns for reading/writing settings via hooks, commands, and agents.

Quick Start

Create a file at .claude/plugin-name.local.md with YAML frontmatter describing your plugin settings and a Markdown body for prompts.

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 configuration in Claude without committing secrets to git?▼

Per-project plugin configuration can be managed using YAML frontmatter stored in a gitignored .claude/plugin-name.local.md file. This approach keeps project-specific plugin settings, defaults, and state secure and separate from your repository.

What is the best way to structure YAML frontmatter for Claude plugin settings?▼

The best way to structure YAML frontmatter for Claude plugin settings is to use fields like 'enabled' and 'mode' for configuration, followed by a Markdown body for prompts or context. This structure supports atomic updates and defaults handling.

How do I read and write Claude plugin settings via hooks and commands?▼

You can read and write Claude plugin settings via hooks and commands by using flexible templates and patterns to interact with the YAML frontmatter and Markdown body stored in the .claude/plugin-name.local.md file.

Can I use a local markdown file for enabling and disabling Claude plugins per project?▼

Yes, you can use a local markdown file for enabling and disabling Claude plugins per project. The file uses YAML frontmatter fields such as 'enabled' to control plugin state and defaults handling.

Does Claude plugin settings management support optional resource directories?▼

Yes, Claude plugin settings management supports optional resource directories. The configuration system accommodates these directories alongside the YAML frontmatter and Markdown body for comprehensive per-project customization.