Plugin Settings
Configure Local Plugin Settings
Plugin authors need a safe way to store per-project settings without committing user-specific state. This skill explains a local Markdown and YAML frontmatter pattern for Claude, Codex, and Claude Code plugins.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "Plugin Settings" from https://skillstore.io/skills/plugin-settings.md and its manifest at https://skillstore.io/api/skills/plugin-settings/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "Plugin Settings". Create a basic settings plan for a formatter plugin.
Expected outcome:
- A local settings file name and ownership model.
- Recommended fields for enabled state, mode, file size limit, and notes.
- User guidance for gitignore coverage and restart requirements.
Using "Plugin Settings". Review my hook settings parser for safety.
Expected outcome:
- A summary of missing defaults and validation checks.
- Warnings about complex YAML fields and prompt-bearing Markdown content.
- Suggested documentation updates for permissions and local-only storage.
Using "Plugin Settings". Design a setup flow for team plugin preferences.
Expected outcome:
A command flow that asks focused questions, validates responses, writes local settings, and explains how users can update them later.
Security Audit
SafeThis is an official Anthropic documentation skill teaching the .claude/plugin-name.local.md configuration pattern. All 224 static findings were adjudicated as false positives: they are Markdown code fences, standard shebangs, read-only YAML frontmatter parsing with sed/grep/awk/jq, and stderr diagnostic echoes. The two high-severity hits (.env/secret and /sys access) are defensive guards inside an example security hook that DENIES access to sensitive paths, not exfiltration. No network access, dynamic code execution, credential handling, or prompt-injection was found; no net-new semantic findings were added.
Risk Factors
โ๏ธ External commands (50)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/plugin-settings/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/plugin-settings?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/plugin-settings?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/plugin-settings/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/plugin-settings.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
anthropics. (2026). Plugin Settings security audit report (audit version 9) [Author version 0.1.0]. Skillstore. https://skillstore.io/skills/plugin-settings/audits/9BibTeX citation
@techreport{anthropics-plugin-settings-2026,
author = {anthropics},
title = {Plugin Settings security audit report (audit version 9)},
institution = {Skillstore},
year = {2026},
number = {9},
url = {https://skillstore.io/skills/plugin-settings/audits/9},
note = {Author version 0.1.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "Plugin Settings security audit report (audit version 9)"
version: "0.1.0"
type: report
authors:
- name: "anthropics"
date-released: "2026-07-20"
url: "https://skillstore.io/skills/plugin-settings/audits/9"
identifiers:
- type: other
value: "skillstore:plugin-settings:audit:9"
description: "Skillstore immutable audit report identifier"
Compare variants
3 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
plugin-settings
2026-09-09
anthropics-plugin-settings
2026-10-24
davila7-plugin-settings
2026-09-09
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Add Local Configuration
Create a project-local settings pattern for a plugin that needs enabled state, mode, limits, or notes.
Standardize Team Plugin Settings
Document local settings templates and safe defaults so each project can configure plugin behavior consistently.
Read Settings in Hooks
Use settings values to decide whether a hook should run, skip work, or apply stricter validation.
Try These Prompts
Create a basic local settings template for my Claude Code plugin. Include enabled state, mode, Markdown notes, gitignore guidance, and restart guidance.
Design a Claude Code command that asks users for plugin preferences, validates answers, and creates a project-local settings file.
Help me update a Claude Code hook so it reads local plugin settings, validates fields, applies defaults, and handles disabled mode cleanly.
Review my plugin settings workflow for path handling, input sanitization, default behavior, permissions, gitignore coverage, and clear user documentation.
Best Practices
- Keep settings project-local, user-managed, and excluded from version control.
- Validate every setting before using it in hooks, commands, or agents.
- Document restart requirements and provide safe defaults when the file is absent.
Avoid
- Treating Markdown body text as trusted system instructions.
- Using shell parsing for complex nested YAML without validation.
- Storing secrets or shared team policy in local settings files.
Frequently Asked Questions
What problem does this skill solve?
Does it create settings files automatically?
Why use .local.md files?
Can settings be read from hooks?
Are the Bash examples safe for all YAML?
Should settings files contain secrets?
Developer Details
Author
anthropicsLicense
MIT
Author version
v0.1.0
Skillstore revision
r1
Repository
https://github.com/anthropics/claude-code/tree/main/plugins/plugin-dev/skills/plugin-settingsRef
dbe0e719813583400773166a0621f8a9b8185c72
Maintenance freshness
7/20/2026
Usage
7 downloads ยท 261 views
File structure
๐ examples/
๐ create-settings-command.md
๐ example-settings.md
๐ references/
๐ scripts/
๐ parse-frontmatter.sh
๐ validate-settings.sh
๐ SKILL.md