plugin-settings

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

1|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/hjemmesidekongen/ai --skill plugin-settings-hjemmesidekongen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-settings
Source: https://github.com/hjemmesidekongen/ai/tree/main/plugins/kronen/skills/plugin-settings
Command: npx skills add https://github.com/hjemmesidekongen/ai --skill plugin-settings-hjemmesidekongen

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a standardized way to manage per-project configuration for plugins, allowing users to customize plugin behavior without altering core plugin code or committing sensitive information.

Core Features & Use Cases

  • Per-Project Configuration: Store settings in .claude/{plugin-name}.local.md files within the project root.
  • YAML Frontmatter: Define structured configuration using YAML in the frontmatter.
  • Markdown Body: Use the Markdown body for prompts or additional context.
  • Feature Toggling: Easily enable or disable plugin features using an enabled flag.
  • Use Case: A developer needs to configure a specific plugin to use a different API endpoint for their current project. They create a .claude/my-plugin.local.md file with the custom endpoint in the YAML frontmatter, and the plugin automatically picks it up.

Quick Start

Create a file named .claude/plugin-name.local.md in your project root with your desired YAML configuration and markdown content.

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 without modifying core code?

You can manage per-project plugin configuration by creating a `.claude/plugin-name.local.md` file in the project root. This standardizes plugin behavior customization without altering core code or committing sensitive information.

What is the best way to store custom API endpoints for a specific project plugin?

The best way to store custom API endpoints is using YAML frontmatter in a `.claude/plugin-name.local.md` file. The plugin automatically picks up the custom endpoint configuration from this local Markdown file during execution.

How do I enable or disable specific plugin features for an individual project?

You can enable or disable plugin features for an individual project by using an `enabled` flag within the YAML frontmatter of your `.claude/plugin-name.local.md` configuration file. This allows per-project feature toggling without affecting global settings.

Does this configuration pattern support providing custom prompts for plugin execution?

Yes, this configuration pattern supports providing custom prompts for plugin execution. You use the Markdown body section of the `.claude/plugin-name.local.md` file to store prompts or provide additional context for the plugin.

Can I use YAML frontmatter to define structured settings in a local configuration file?

Yes, you can use YAML frontmatter to define structured settings in a local configuration file. The system utilizes shell scripts specifically for parsing this YAML frontmatter and validating the file structure of your `.claude/plugin-name.local.md` document.