One-click install
npx skills add https://github.com/susomejias/rembric --skill plugin-settings-susomejias
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Plugin Settings
Source: https://github.com/susomejias/rembric/tree/main/.agents/skills/plugin-settings
Command: npx skills add https://github.com/susomejias/rembric --skill plugin-settings-susomejias

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill eliminates the hassle of managing per-project, user-specific configuration for Claude Code plugins by providing a standardized, gitignored file pattern that avoids hardcoding values or committing sensitive settings to version control.

Core Features & Use Cases

  • Standardized Settings Pattern: Documents the .claude/plugin-name.local.md format that uses YAML frontmatter for structured configuration and a markdown body for freeform context or prompts.
  • Cross-Context Parsing: Includes ready-to-use bash patterns for reading settings files from hooks, commands, and agents, with support for extracting boolean, numeric, and string fields.
  • Production-Ready Guardrails: Provides validation techniques, atomic update patterns, security best practices for sanitizing input and preventing path traversal, and real-world examples from popular plugins like multi-agent-swarm and ralph-wiggum.
  • Use Case: A developer building a Claude Code plugin for code validation can let users set per-project validation strictness, file size limits, and allowed file extensions via a simple .local.md file instead of modifying plugin code.

Quick Start

Use this Skill to implement user-configurable per-project settings for your Claude Code plugin by adopting the .claude/plugin-name.local.md file pattern with YAML frontmatter and bash parsing logic.

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 configuration for Claude Code plugins without hardcoding values?

You can manage per-project plugin configuration by adopting a standardized, gitignored file pattern using YAML frontmatter. This prevents hardcoding values and keeps sensitive settings out of version control while providing structured configuration.

How does YAML frontmatter parsing work for Claude Code plugin settings?

YAML frontmatter parsing for plugin settings uses bash patterns to extract boolean, numeric, and string fields from a structured markdown file. This allows hooks, commands, and agents to read dynamic configuration values across different execution contexts.

What is the best way to read plugin settings files from Claude Code hooks and commands?

The best way to read plugin settings from hooks and commands is using cross-context bash parsing patterns. These patterns extract typed fields like boolean, numeric, and string values from YAML frontmatter, ensuring consistent configuration access across all plugin components.

Can I use a markdown file format for both structured and freeform plugin configuration?

Yes, a markdown file format supports both structured and freeform plugin configuration simultaneously. YAML frontmatter handles structured settings while the markdown body stores freeform context or prompts, combining typed configuration data and flexible contextual instructions in one file.

What security precautions should I take when implementing per-project plugin settings?

Security precautions for per-project plugin settings include sanitizing input, preventing path traversal, and applying validation techniques. Production-ready guardrails also use atomic update patterns to ensure safe configuration reads and writes within Claude Code plugin environments.