plugin-settings

Store per-project plugin settings in YAML frontmatter within a local Markdown file.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/astrosteveo/marketplace --skill plugin-settings-astrosteveo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plugin-settings
Source: https://github.com/astrosteveo/marketplace/tree/main/plugins/plugin-dev/skills/plugin-settings
Command: npx skills add https://github.com/astrosteveo/marketplace --skill plugin-settings-astrosteveo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stores per-project plugin settings in a YAML frontmatter file located at .claude/plugin-settings.local.md, enabling consistent, isolated behavior across a codebase while keeping secrets and settings gitignored.

Core Features & Use Cases

  • Per-project configuration: YAML frontmatter in a local markdown file controls plugin behavior read by hooks, commands, and agents.
  • Templates, examples, and best practices: guidance to create, read, validate, and update settings with minimal friction.
  • Safety and lifecycle: settings are user-managed, require a Claude Code restart to take effect, and are not meant for hot-swapping.

Quick Start

Create a file named .claude/plugin-settings.local.md containing YAML frontmatter to enable the plugin, then write a brief Markdown body describing usage. Restart Claude Code after changes for the new settings to load.

Frequently Asked Questions about plugin-settings

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

FAQPage Schema
How do I store per-project plugin settings for Claude Code hooks and agents?▼

You can store per-project plugin settings by creating a YAML frontmatter file at .claude/plugin-settings.local.md. This file is read by hooks, commands, and agents to control plugin behavior consistently across your codebase.

What is the best way to configure plugin behavior locally without committing secrets?▼

Using a gitignored YAML frontmatter file at .claude/plugin-settings.local.md is the best way to configure plugin behavior locally. It isolates settings per-project while keeping secrets and configurations out of version control.

How do I parse YAML frontmatter from a markdown file using shell scripts?▼

You can parse YAML frontmatter from a markdown file using standard shell tools like sed or awk. The plugin-settings approach requires only these standard tools to extract and read configuration values from the file.

Do I need to restart Claude Code after changing per-project plugin settings?▼

Yes, you must restart Claude Code after changing per-project plugin settings for the new configuration to load. These settings are user-managed and are not designed for hot-swapping during an active session.

Can I use YAML frontmatter to activate and persist plugin configurations across different projects?▼

Yes, YAML frontmatter in a local markdown file activates and persists plugin configurations on a per-project basis. Each project gets its own isolated settings file to maintain consistent behavior.

What are the limitations of using a local markdown file for plugin configuration?▼

The main limitation is that settings require a Claude Code restart to take effect and cannot be hot-swapped. Additionally, parsing relies on standard shell tools like sed and awk, which may have edge cases with complex YAML structures.