plugin-settings

Parse and validate YAML frontmatter in .claude/plugin-name.local.md files.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/NGTPTE/TuriX-MarketPlace --skill plugin-settings-ngtpte
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-settings
Source: https://github.com/NGTPTE/TuriX-MarketPlace/tree/main/plugins/plugin-dev/skills/plugin-settings
Command: npx skills add https://github.com/NGTPTE/TuriX-MarketPlace --skill plugin-settings-ngtpte

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, tmux, perl, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you define, read, validate, and maintain per-project plugin configuration and state in a consistent markdown format, so plugin behavior stays predictable without hardcoding settings.

Core Features & Use Cases

  • Frontmatter-based configuration: Store structured settings in .claude/plugin-name.local.md files with YAML frontmatter and markdown body content.
  • Safe parsing and validation: Extract individual fields, handle quoted values, check required markers, and verify booleans, numbers, and body content.
  • Operational workflows: Create settings files, update iteration or status fields atomically, and support hooks, commands, and agents that adapt to project-specific configuration.

Quick Start

Ask the agent to create or read a .claude plugin settings file for your project and apply its YAML frontmatter configuration.

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 Code markdown files?

Per-project plugin configuration is managed by standardizing settings stored in .claude/plugin-name.local.md files using YAML frontmatter for structured data and markdown body content for additional context.

What is the best way to safely parse and validate YAML frontmatter for plugin settings?

Safe parsing and validation of YAML frontmatter involves extracting individual fields, handling quoted values, checking required markers, and verifying booleans, numbers, and body content to ensure predictable plugin behavior.

How do I atomically update iteration or status fields in local markdown configuration files?

Atomic updates to iteration or status fields in local markdown configuration files are supported through command-driven workflows that reliably modify YAML frontmatter without corrupting user-managed settings.

Do I need jq and tmux to standardize plugin settings across projects?

Yes, standardizing plugin settings requires jq, tmux, and perl as dependencies to reliably parse, validate, and atomically update YAML frontmatter and markdown body content in configuration files.

Can I use YAML frontmatter configuration to control hooks and agent coordination?

Yes, YAML frontmatter configuration supports hook control, agent coordination, and command-driven workflows that adapt to project-specific settings stored in local markdown files.

Why does my plugin configuration break when hardcoding settings instead of using local markdown files?

Hardcoding settings breaks plugin configuration because it lacks the safe defaults, validation, and atomic updates provided by standardized YAML frontmatter parsing in per-project local markdown files.