← Back to Skills Marketplace
wimi321

Claude Settings Editor

by wimi321 · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ Security Clean
131
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install claude-settings-editor
Description
Use when the user wants to update Claude settings, hooks, permissions, MCP server toggles, or other JSON config safely and with scope awareness.
README (SKILL.md)

Claude Settings Editor

Use this skill for settings.json, local overrides, and hook configuration.

Workflow

  1. Choose the correct settings file by scope: user, project, or local.
  2. Read the current file before editing.
  3. Apply the smallest valid JSON change.
  4. Keep permissions, hooks, plugins, and MCP configuration syntactically valid.
  5. Explain scope, precedence, and any risky config changes.

Guardrails

  • Do not replace a config file wholesale unless necessary.
  • Preserve unrelated user settings.
  • Warn before widening permissions or changing automation hooks broadly.

Example Requests

  • Update project hooks without breaking existing settings.
  • Change Claude permissions and MCP toggles in the right settings file.

Inputs

  • Requested configuration change
  • Desired scope
  • Existing settings state

Outputs

  • Validated JSON config edits
  • Scope explanation
  • Risk notes for sensitive changes

Success Criteria

  • Only the intended file was changed.
  • JSON remains valid.
  • Unrelated settings were preserved.

Non-Goals

  • Blind full-file rewrites
  • Silent permission broadening

Source Provenance

Derived from src/skills/bundled/updateConfig.ts.

Usage Guidance
This skill appears to do what it says (make small, scoped JSON edits to Claude settings) and has no installs or secret requirements, but it leaves which files to read/write unspecified. Before installing or granting the agent access: (1) confirm exactly which file paths the skill will be allowed to access; (2) require explicit user confirmation before any write; (3) back up target config files and test on non-production copies; (4) prefer a prompt that supplies the exact path and scope to the agent rather than leaving scope discovery to the agent; and (5) enable logging/auditing of any changes so you can review edits after they occur.
Capability Analysis
Type: OpenClaw Skill Name: claude-settings-editor Version: 1.0.0 The skill bundle describes a utility for managing Claude configuration files, such as settings.json, hooks, and MCP server toggles. The instructions in SKILL.md include explicit safety guardrails, such as performing minimal JSON edits, preserving unrelated settings, and warning the user before widening permissions. No malicious code, data exfiltration logic, or harmful prompt-injection instructions were found.
Capability Assessment
Purpose & Capability
The skill's name/description (edit Claude settings/hooks/permissions) align with the runtime instructions (read chosen settings file, apply minimal JSON edits). However, the registry metadata lists no required config paths even though the runtime workflow expects reading and writing settings files; that mismatch should be clarified.
Instruction Scope
SKILL.md explicitly tells the agent to 'choose the correct settings file by scope' and to 'read the current file before editing' and to write edits. Those actions are appropriate for the stated goal, but the instructions do not constrain or enumerate specific file paths, nor do they require explicit user confirmation before performing writes—this gives the agent broad discretion to access filesystem locations unless the integrating environment enforces limits.
Install Mechanism
No install spec and no code files — the skill is instruction-only, so nothing is written to disk or downloaded during install.
Credentials
The skill requests no environment variables, credentials, or config paths. That is proportionate for a local-config editing helper; the only gap is the lack of declared config paths when the instructions imply file access.
Persistence & Privilege
always is false and the skill does not request persistent presence or system-wide config changes. It does instruct file edits within its scope, which is expected for this purpose.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install claude-settings-editor
  3. After installation, invoke the skill by name or use /claude-settings-editor
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial extraction from local Claude Code source
Metadata
Slug claude-settings-editor
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Claude Settings Editor?

Use when the user wants to update Claude settings, hooks, permissions, MCP server toggles, or other JSON config safely and with scope awareness. It is an AI Agent Skill for Claude Code / OpenClaw, with 131 downloads so far.

How do I install Claude Settings Editor?

Run "/install claude-settings-editor" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Claude Settings Editor free?

Yes, Claude Settings Editor is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Claude Settings Editor support?

Claude Settings Editor is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Claude Settings Editor?

It is built and maintained by wimi321 (@wimi321); the current version is v1.0.0.

💬 Comments