plugin-settings

Extract user-configurable settings from .claude/plugin-name.local.md files.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires sed, awk, jq, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill streamlines the process of configuring and managing plugin settings, allowing users to easily customize plugin behavior and state without manual editing of complex files.

Core Features & Use Cases

  • Per-project plugin configuration: Customize settings for individual plugins within a project.
  • YAML frontmatter: Utilize structured YAML for configuration, ensuring consistency and readability.
  • Markdown content: Provide additional context and documentation within the same file.
  • Use Case: When developing a project with multiple plugins, use this skill to set specific configurations for each plugin, such as enabling features, adjusting validation levels, or specifying retry parameters.

Quick Start

To configure the 'my-plugin' plugin, create a .claude/my-plugin.local.md file in your project root and specify your settings.

Frequently Asked Questions about plugin-settings

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

FAQPage Schema
How do I configure plugin settings using YAML frontmatter in markdown files?

Plugin settings are configured by creating a `.claude/plugin-name.local.md` file in your project root. This skill parses the YAML frontmatter and markdown content to extract and manage user-configurable settings for structured plugin configuration.

What's the best way to manage per-project plugin configuration without manual editing?

Managing per-project plugin configuration is streamlined by extracting settings from `.claude/plugin-name.local.md` files. You define structured YAML frontmatter and markdown content, allowing the skill to handle extraction without manual editing of complex configuration files.

Does this plugin settings skill require specific command-line dependencies to parse YAML?

Yes, parsing YAML frontmatter and markdown content requires command-line dependencies. The skill specifically relies on `sed`, `awk`, and `jq` to extract and process user-configurable settings from the `.claude/plugin-name.local.md` files.

Can I use markdown content alongside YAML for plugin configuration context?

Yes, you can use markdown content alongside YAML frontmatter for plugin configuration. The skill utilizes both the structured YAML for settings extraction and the markdown content to provide additional context and documentation within the same configuration file.

How do I set specific validation levels and retry parameters for individual plugins?

To set validation levels or retry parameters for individual plugins, create a `.claude/my-plugin.local.md` file. Specify your desired settings within the YAML frontmatter, and the skill will extract these configurations to customize plugin behavior per project.