From claude-ecosystem
Manages Claude Code settings including settings.json (user/project/enterprise), permissions, sandbox, plugins, env vars, and tools via docs-management delegation. For config setup and troubleshooting.
npx claudepluginhub melodic-software/claude-code-plugins --plugin claude-ecosystemThis skill is limited to using the following tools:
> **STOP - Before providing ANY response about Claude Code configuration or settings:**
references/audit-framework.mdreferences/claude-code-settings.schema.jsonscripts/schema/__init__.pyscripts/schema/extract_env_vars.pyscripts/schema/generate_schema.pyscripts/schema/tests/__init__.pyscripts/schema/tests/conftest.pyscripts/schema/tests/test_extract_env_vars.pyscripts/schema/validate_schema.pyManages settings for Claude Code, Codex CLI, OpenCode: views files, configures models, permissions, sandbox, hooks, env vars, profiles. Restart agent after edits.
Lists Claude Code components: skills (personal/project/plugin via Python scan), env-vars, sessions, settings, tools. Invoke with /list <action>.
Manages settings for Claude Code (JSON) and Codex CLI (TOML) coding agents, including permissions, sandbox, model selection, profiles, env vars, and hooks.
Share bugs, ideas, or general feedback.
STOP - Before providing ANY response about Claude Code configuration or settings:
- INVOKE
docs-managementskill- QUERY for the user's specific topic
- BASE all responses EXCLUSIVELY on official documentation loaded
Skipping this step results in outdated or incorrect information.
Before responding, verify:
If ANY checkbox is unchecked, STOP and invoke docs-management first.
Central authority for Claude Code configuration and settings. This skill uses 100% delegation to docs-management - it contains NO duplicated official documentation.
Architecture: Pure delegation with keyword registry. All official documentation is accessed via docs-management skill queries.
Keywords: settings, configuration, settings.json, environment variables, permissions, sandbox, enterprise settings, managed-settings.json, user settings, project settings, local settings, tools, hooks configuration, model configuration, plugin settings, precedence
Use this skill when:
Use these keywords when querying docs-management skill for official documentation:
| Topic | Keywords |
|---|---|
| Overview | "settings", "settings.json", "configuration files" |
| User Settings | "user settings", "~/.claude/settings.json" |
| Project Settings | ".claude/settings.json", "project settings" |
| Local Settings | "settings.local.json", "local settings" |
| Enterprise | "managed-settings.json", "enterprise managed policy" |
| Topic | Keywords |
|---|---|
| Settings Table | "available settings", "settings options" |
| Model Setting | "model setting", "model override" |
| Hooks Setting | "hooks setting", "disableAllHooks" |
| Output Style | "outputStyle setting", "output style config" |
| Status Line | "statusLine setting", "status line config" |
| API Key Helper | "apiKeyHelper", "custom script auth" |
| Keybindings | "keybindings.json", "keyboard shortcuts config", "custom keybindings" |
| Plans Directory | "plansDirectory", "plans directory setting", "plan file storage" |
| Turn Duration | "showTurnDuration", "turn duration display", "timing display" |
| Topic | Keywords |
|---|---|
| Permission Settings | "permission settings", "allow deny ask rules" |
| Allow Rules | "permissions allow", "allow tool rules" |
| Deny Rules | "permissions deny", "deny tool rules", "excluding sensitive files" |
| Ask Rules | "permissions ask", "confirmation rules" |
| Default Mode | "defaultMode", "permission modes" |
| Topic | Keywords |
|---|---|
| Sandbox Settings | "sandbox settings", "bash sandboxing" |
| Sandbox Network | "sandbox network", "allowUnixSockets", "allowLocalBinding" |
| Excluded Commands | "excludedCommands", "sandbox exclusions" |
| Auto Allow | "autoAllowBashIfSandboxed", "auto-approve sandboxed" |
| Topic | Keywords |
|---|---|
| Settings Precedence | "settings precedence", "configuration hierarchy" |
| Override Order | "enterprise project user precedence", "settings override" |
| Topic | Keywords |
|---|---|
| Environment Variables | "environment variables", "ANTHROPIC_API_KEY" |
| Model Variables | "ANTHROPIC_MODEL", "model environment" |
| Proxy Variables | "HTTP_PROXY", "HTTPS_PROXY", "proxy configuration" |
| Telemetry Variables | "DISABLE_TELEMETRY", "telemetry settings" |
| Bedrock Variables | "CLAUDE_CODE_USE_BEDROCK", "bedrock environment" |
| Vertex Variables | "CLAUDE_CODE_USE_VERTEX", "vertex environment" |
| Temp Directory | "CLAUDE_CODE_TMPDIR", "temporary directory", "temp file location" |
| Background Tasks | "CLAUDE_CODE_DISABLE_BACKGROUND_TASKS", "disable background tasks", "background process control" |
| Topic | Keywords |
|---|---|
| Plugin Configuration | "plugin configuration", "enabledPlugins" |
| Marketplaces | "extraKnownMarketplaces", "plugin marketplaces config" |
| Topic | Keywords |
|---|---|
| Custom Schema | "settings schema", "JSON schema", "claude-code-settings.schema.json" |
| Schema Location | "custom schema", "extended schema", "SchemaStore" |
| Schema Updates | "update schema", "schema refresh", "/update-settings-schema" |
| Schema Validation | "validate schema", "schema compliance", "draft-07" |
| Topic | Keywords |
|---|---|
| Available Tools | "tools available to Claude", "tool table" |
| Tool Permissions | "tool permissions", "permission required tools" |
What do you want to do?
⚠️ STALENESS WARNING: The lists below are for navigation reference only. ALWAYS query docs-management for the authoritative, current list of settings fields, environment variables, and configuration options. These change with Claude Code releases.
Query Pattern: docs-management: "settings.md file types locations"
Query Pattern: docs-management: "settings.md available settings table"
Categories include: authentication helpers, cleanup, announcements, environment, permissions, hooks, model, output styling, status line. Query docs-management for the complete list of current settings fields.
Query Pattern: docs-management: "settings.md permission settings allow deny ask"
Covers: allow/deny/ask rules, additional directories, default mode, bypass mode controls.
Query Pattern: docs-management: "settings.md sandbox settings network"
Covers: enabled flag, auto-allow behavior, excluded commands, network settings (sockets, binding, proxies).
Query Pattern: docs-management: "settings.md precedence hierarchy"
Order (query docs-management for current precedence rules).
Query Pattern: docs-management: "settings.md environment variables"
Categories: authentication, model config, provider settings, proxy, telemetry, tool behavior.
Query Pattern: docs-management: "settings.md plugin configuration enabledPlugins"
Covers: enabled plugins map, marketplace sources.
Query Pattern: docs-management: "interactive-mode.md tools available to Claude"
Categories: file operations, execution, user interaction, specialized tools, notebook editing.
User asks: "How do I configure permissions?"
1. Invoke docs-management skill
2. Use keywords: "permission settings", "allow deny rules"
3. Load official documentation
4. Provide guidance based EXCLUSIVELY on official docs
User asks: "I want enterprise settings with sandbox and restricted permissions"
1. Invoke docs-management skill with multiple queries:
- "managed-settings.json", "enterprise managed policy"
- "sandbox settings", "bash sandboxing"
- "permission settings", "deny rules"
2. Synthesize guidance from official documentation
User reports: "My settings aren't taking effect"
1. Invoke docs-management skill
2. Use keywords: "settings precedence", "configuration hierarchy"
3. Guide user through precedence rules from official docs
| Issue | Keywords for docs-management |
|---|---|
| Settings not applied | "settings precedence", "configuration hierarchy" |
| Permission denied | "permission settings", "deny rules" |
| Sandbox blocking commands | "sandbox settings", "excludedCommands" |
| Environment variable not working | "environment variables", specific variable name |
| Enterprise policy override | "managed-settings.json", "enterprise policy" |
| Plugin not loading | "plugin configuration", "enabledPlugins" |
| Tool not available | "tools available", "tool permissions" |
This repository has project-level settings in .claude/settings.json including:
When modifying this repository's settings, ensure changes align with the hook-management skill guidance for hook configurations.
This skill provides the validation criteria used by the settings-auditor agent for formal audits.
| Resource | Location | Purpose |
|---|---|---|
| Audit Framework | references/audit-framework.md | Query guides and scoring criteria |
| Category | Points | Key Criteria |
|---|---|---|
| JSON Validity | 20 | Valid syntax, well-formed |
| Schema Compliance | 25 | Only valid settings options |
| Permission Rules | 25 | Valid patterns, appropriate restrictions |
| Environment Config | 15 | Valid env vars, no secrets |
| Precedence Awareness | 15 | Correct scope usage |
Thresholds: 85+ = PASS, 70-84 = PASS WITH WARNINGS, <70 = FAIL
The settings-auditor agent (Haiku model) performs formal audits using this skill:
skills: settings-management/audit-settings commandWhen auditing settings that reference external technologies (scripts, packages, runtimes), the auditor MUST validate claims using MCP servers before flagging findings.
Technologies Requiring MCP Validation:
Validation Rule:
Never flag a technology usage as incorrect without first:
Stale Data Warning:
This plugin provides an extended JSON Schema for Claude Code settings that enables IntelliSense in VS Code.
Add to .vscode/settings.json:
{
"json.schemas": [
{
"fileMatch": ["**/.claude/settings.json", "**/.claude/settings.local.json"],
"url": "./plugins/claude-ecosystem/skills/settings-management/references/claude-code-settings.schema.json"
}
]
}
Add at the top of your settings.json:
{
"$schema": "https://raw.githubusercontent.com/melodic/claude-code-plugins/main/plugins/claude-ecosystem/skills/settings-management/references/claude-code-settings.schema.json"
}
Note: In-file $schema references override workspace settings. Use workspace settings for flexibility.
The schema includes 68+ environment variables with:
enum: ["0", "1"] for boolean flags (type safety)Try it: In your settings.json, type "env": { "A and VS Code will autocomplete ANTHROPIC_API_KEY, ANTHROPIC_MODEL, etc.
The schema tracks Claude Code versions and includes version history:
| Field | Purpose |
|---|---|
x-schema-version | Plugin schema version (e.g., 1.1.0) |
x-claude-code-version | Claude Code version tracked |
x-env-var-count | Number of env vars defined (68+) |
x-last-updated | Last schema update date |
Run /update-settings-schema to sync the schema with latest canonical documentation. This extracts new env vars and settings from the official docs.
Official Documentation (via docs-management skill):
Repository-Specific:
.claude/settings.json.claude/hooks/v1.1.0 (2026-01-16): Added v2.1.4-v2.1.9 keyword registry entries
v1.0.0 (2025-11-26): Initial release
Date: 2026-01-16 Model: claude-opus-4-5-20251101