Plugin Settings

Store per-project Claude Code plugin settings in .claude/plugin-name.local.md files.

1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/Tashima-Tarsh/Disha --skill plugin-settings-tashima-tarsh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Plugin Settings
Source: https://github.com/Tashima-Tarsh/Disha/tree/main/disha/services/integrations/Anthropic/plugins/plugin-dev/skills/plugin-settings
Command: npx skills add https://github.com/Tashima-Tarsh/Disha --skill plugin-settings-tashima-tarsh

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Claude Code plugins often require project-specific configuration that should not be shared across teams or committed to version control, and this skill provides a standardized, safe pattern for managing that per-project plugin state and settings without risking accidental exposure of sensitive data.

Core Features & Use Cases

  • Standardized Settings Pattern: Implements the .claude/plugin-name.local.md convention for user-local, per-project plugin configuration that is automatically excluded from git commits by default.
  • Cross-Component Compatibility: Works with hooks, commands, and agents, supporting both structured YAML frontmatter for configuration values and markdown body content for prompts, task descriptions, or additional context.
  • Production-Ready Utilities: Includes bash scripts for parsing frontmatter, validating settings file structure, and performing atomic updates, plus comprehensive guides for handling edge cases like quoted values, special characters, and file path security.
  • Use Case: A team building a code validation plugin can use this skill to let users set per-project rules (like maximum file size or allowed file extensions) without modifying the plugin's shared source code.

Quick Start

Use the plugin-settings skill to create a .claude/your-plugin.local.md file with your desired plugin configuration for the current project.

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 configuration without committing it to git?

You can store per-project plugin configuration without git commits by using standardized `.claude/plugin-name.local.md` files that are automatically excluded from version control by default.

What is the best way to manage user-local settings for Claude Code plugins?

The best way to manage user-local settings is implementing YAML frontmatter-based configuration in `.local.md` files, providing parsing utilities and validation scripts to safely read and write project-specific overrides.

Can I use YAML frontmatter to configure hooks and commands for specific projects?

Yes, YAML frontmatter works for configuring hooks, commands, and agents, supporting structured configuration values alongside markdown body content for prompts, task descriptions, or additional context.

How do I safely parse YAML frontmatter in bash scripts for plugin settings?

You can safely parse YAML frontmatter in bash scripts using the provided production-ready utilities that handle atomic updates, validate settings file structure, and manage edge cases like quoted values and special characters.

Does this settings management approach work for team environments with different local configurations?

Yes, this approach works for team environments by allowing each user to set per-project rules in local configuration files without modifying the plugin's shared source code or risking accidental exposure of sensitive data.

What are the limitations of using local markdown files for plugin state persistence?

Limitations include handling file path security constraints and ensuring atomic updates during writes, but the provided security guardrails and validation scripts help mitigate risks associated with special characters and edge cases.