skills.rest
Poorgramer-Zack
Poorgramer-ZackCOMMUNITY
Explore all skills by this author →
GitHub

Plugin Settings

Store per-project plugin configuration in a local YAML frontmatter file.

2|Updated Mar 19, 2026
Search Tags:#hooks#agents#plugin#yaml#settings#frontmatter#local.md
One-click install
npx skills add https://github.com/Poorgramer-Zack/copilot-cli-things --skill plugin-settings-poorgramer-zack
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Plugin Settings
Source: https://github.com/Poorgramer-Zack/copilot-cli-things/tree/main/plugins/plugin-dev/skills/plugin-settings
Command: npx skills add https://github.com/Poorgramer-Zack/copilot-cli-things --skill plugin-settings-poorgramer-zack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing per-project plugin configuration can be tedious and error-prone when settings drift between environments. This Skill provides a simple, portable method to store per-project state and behavior in a local markdown file using YAML frontmatter, enabling hooks and agents to read and enforce configuration consistently.

Core Features & Use Cases

  • Store per-project plugin configuration in .github/plugin-name.local.md with YAML frontmatter for structured settings.
  • Read and write plugin state from Copilot CLI hooks and agents, while keeping sensitive data out of version control.
  • Use cases include enabling/disabling plugins, toggling validation modes, and tuning behavior on a per-project basis.

Quick Start

Create a file at .github/plugin-name.local.md containing a YAML frontmatter block and a plain Markdown body to begin configuring the plugin.

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 for Copilot CLI hooks and agents?▼

Per-project plugin configuration can be managed by storing settings in a local markdown file with YAML frontmatter, enabling hooks and agents to read and enforce configuration consistently across repositories.

What is the best way to store per-project plugin state outside of version control?▼

Storing per-project plugin state in a local markdown file using YAML frontmatter keeps sensitive data out of version control while providing structured settings for predictable behavior and fast restoration after restarts.

How do I create a local YAML frontmatter file to configure plugin settings?▼

Create a file at .github/plugin-name.local.md containing a YAML frontmatter block and a plain Markdown body to begin configuring the plugin with structured settings.

Can I use YAML frontmatter to toggle validation modes for specific repositories?▼

Yes, YAML frontmatter in a local markdown file allows you to enable or disable plugins, toggle validation modes, and tune behavior on a per-project basis for Copilot CLI extensions and agents.

Does per-project plugin configuration support restart guidance and validation operations?▼

Per-project plugin configuration implements frontmatter parsing, update operations, validation, and restart guidance to ensure safe, repeatable configuration workflows across repository environments.

Why does plugin configuration drift between environments and how can I prevent it?▼

Plugin configuration drifts when settings differ between environments, but storing configuration in a local YAML frontmatter file provides a portable method to prevent drift and apply predictable behavior across repositories.

Related Skills

Explore More Software Engineering Skills→
hjemmesidekongenhjemmesidekongen
1

plugin-settings

Manage plugin-specific configuration via YAML frontmatter in .claude/plugin-name.local.md files.

Community
Basic
AvaTar-ArTsAvaTar-ArTs

plugin-settings

Configure per-project plugin settings via YAML frontmatter in .claude/*.local.md files.

Community
Intermediate
fcakyonfcakyon
1.0k

plugin-settings

Store per-project plugin configuration in .claude/*.local.md files with YAML frontmatter.

Community
Intermediate
ricablericable

Plugin Settings

Organize per-project plugin settings in Markdown files with YAML frontmatter.

Community
Advanced