What does this skill do, and when should you use it?
This skill documents the `.claude/plugin-name.local.md` pattern for plugin configuration and state. Each file combines YAML frontmatter with a Markdown body and can be read by hooks, commands, and agents. It covers naming, parsing, defaults, validation, Git exclusion, permissions, and restart requirements. It suits Claude Code plugin developers who need per-project behavior, but the source does not provide a standalone installation command or complete test evidence.
It guides users to create .claude/plugin-name.local.md files; use sed to extract YAML frontmatter, grep and sed to read fields, and awk to extract the Markdown body; and read Boolean, string, and numeric settings from Bash hooks, commands, and agents. It also demonstrates template generation, input validation, path-traversal checks, file permissions, and default values when a settings file is absent.
- A plugin developer needs per-project enablement, mode, or retry settings stored outside the plugin code.
- A team wants to temporarily activate or deactivate a security-scan hook through an `enabled` field.
- A multi-agent plugin needs to store agent names, task numbers, and coordinator sessions as project-local state.
- A loop-based plugin needs iteration counts, limits, completion promises, and prompt text persisted between runs.
How do you install this skill?
- Do not treat sed/grep extraction as full YAML parsing; complex structures, quoting, duplicate keys, nested values, and malicious content require a strict parser and schema validation.
- Relative paths depend on the current working directory, and body content may be fed back to the model or sent through tmux; establish project scoping, sensitive-data rules, confirmation, permissions, and rollback before adoption.
- jq, optional yq, tmux, and Claude Code restart semantics are assumed inconsistently; validate these requirements separately in the target environment.
- Shell / CLI
- Local filesystem
Bashsedgrepawk
The skill is located at plugins/plugin-dev/skills/plugin-settings/SKILL.md. The README says plugins can be installed through Claude Code's plugin system using /plugin install {plugin-name}@claude-plugins-official, but the source does not identify this skill's standalone marketplace name or provide separate installation steps.
tmp="$(mktemp -d)"
git clone --depth 1 https://github.com/anthropics/claude-plugins-official.git "$tmp"
mkdir -p ~/.claude/skills
cp -R "$tmp/plugins/plugin-dev/skills/plugin-settings" ~/.claude/skills/
rm -rf "$tmp"Generated from the source repository and skill path; it copies only this skill's folder. If the author's install steps above differ, follow those first. To scope it to one project, replace ~/.claude/skills with that project's .claude/skills.
How do you use this skill?
Once installed, send your agent any of these to trigger it:
- How should a plugin store project-local configuration and read YAML frontmatter?
Ask Claude Code a prompt such as “How should a plugin store project-local configuration and read YAML frontmatter?” Create .claude/plugin-name.local.md in the project root with YAML frontmatter and a Markdown body, then read it from a hook, command, or agent. Exit and restart Claude Code after editing so hooks load the new settings.
What are this skill's strengths and limitations?
- Includes copyable file templates and Bash parsing examples.
- Covers defaults, validation, Git exclusion, and permission guidance.
- Explains use from hooks, commands, and agents.
- It is explicitly framed around Claude Code plugin mechanisms, so hooks, commands, agents, and restart behavior need adaptation elsewhere.
- The examples rely mainly on text-command parsing and do not establish support for complex YAML structures.
- The source provides no test suite, platform compatibility matrix, or standalone installation name.
How does this skill compare with similar options?
Side by side with related skills; every score comes from the same FSRS standard.
| Skill | FS score | Stars | Last updated | License |
|---|---|---|---|---|
| Project Plugin Settings Pattern this page ✓ Anthropic · Official | 49 · Use with care | ★ 38k | 11d ago | Apache-2.0 |
| Claude Code Plugin Skill Development ✓ Anthropic · Official | 51 · Use with care | ★ 38k | 11d ago | Apache-2.0 |
| Claude Code Command Builder ✓ Anthropic · Official | 46 · Use with care | ★ 38k | 11d ago | Apache-2.0 |
| Claude Code Agent Development Guide ✓ Anthropic · Official | 54 · Use with care | ★ 38k | 11d ago | Apache-2.0 |
| Claude Code Skill Development ✓ Anthropic · Official | 46 · Use with care | ★ 151k | 11d ago | — |
How did FollowSkills review this skill?
The material documents local user-managed files, gitignore usage, permission guidance, input sanitization, path-traversal checks, and atomic updates, while one example includes user confirmation. However, confirmation, permissions, rollback, and sensitive-data handling are not enforced consistently; some examples feed user-controlled body content back to Claude or send it through tmux, with limited disclosure of data flow and external effects. Points are deducted for these gaps.
The skill supplies Bash examples, defaults, partial validation, and some diagnostic messages, so the main simple path is plausible on static inspection. Dependencies such as jq, yq, and tmux are not consistently declared; sed/grep parsing is not full YAML parsing; missing fields can fail under set -e; and the validator may accept non-strict YAML-like content. No key-path tests are provided, so the score is kept below the static ceiling.
Triggers, naming, configuration purposes, and several hooks/commands/agents scenarios are clearly described. Boundaries remain incomplete: non-fit cases, Claude Code version assumptions, working-directory behavior, complex YAML limits, and Chinese-language support are not specified. Mainland-China network reachability is not discussed, although the core pattern is primarily local.
The material has clear layering across the main skill, examples, references, and utility scripts. It includes a version, repository Apache-2.0 metadata, official organization provenance, maintenance signals, restart guidance, and gitignore advice. It lacks a skill-level changelog, explicit update path or stability policy, complete dependency installation notes, FAQ coverage, and a single stable schema; some documentation is assumed to exist elsewhere.
For simple plugin configuration, the skill provides usable patterns, templates, parsing utilities, validation utilities, and an implementation workflow. Nevertheless, the result is guidance and illustrative code rather than verified drop-in behavior; complex YAML, malformed input, and security edge cases require review and likely revision. Static calibration limits effectiveness to 7.
Concrete source files, commands, scripts, examples, and error messages make the claims partly auditable. There is no committed test suite or CI evidence covering this skill's key paths, and the purported real-world examples are documentation-contained examples rather than independently corroborated execution evidence. The static maximum is therefore used.
Open a dimension to read why it scored that way
Evidence confidence：Low — Mostly static review, author material or a limited demo; useful for discovery, not high-risk decisions.
See the full review method →