config-claude

Configure, reconcile, inspect, and recover personal Claude Code settings, roles, hooks, and MCP integrations.

7|5|Updated Jul 22, 2025
One-click install
npx skills add https://github.com/nebius/nebius-ps-services --skill config-claude-nebius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: config-claude
Source: https://github.com/nebius/nebius-ps-services/tree/main/skills/config-claude
Command: npx skills add https://github.com/nebius/nebius-ps-services --skill config-claude-nebius

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Setting up and maintaining a personal Claude Code environment involves many fragile pieces: native settings.json, CLAUDE.md instructions, read-only agent roles, hook registrations, private task-state directories, and MCP server integrations. Manual edits risk clobbering personal configuration, duplicating hook registrations, or silently breaking idempotency. This Skill performs explicit, patch-only configuration and recovery while preserving every personal value. ## Core Features & Use Cases - Patch-only reconciliation: Applies narrow managed-block updates to CLAUDE.md and settings.json while preserving personal content, formatting, ordering, and values, with byte-level drift detection before every write. - Read-only convergence checker: A redacted structural checker reports each surface as Aligned, Not aligned, or Blocked without printing secrets or modifying files. - Atomic missing-settings recovery: Creates a missing settings.json exclusively via a private hard-link publish that never replaces existing or concurrently created files. - Optional profiles and integrations: Explicitly selected trusted-local permissions, delegation policy, private Task Implementer storage, and user-scope MCP servers (Context7, Playwright, Terraform, MarkItDown, Microsoft Docs, GitHub, OpenAI docs). - Use Case: You installed Claude Code on a new machine and want the repository's three read-only roles, shared hooks, and managed instructions installed without losing your existing model choice, deny rules, or custom preferences. Invoke the skill to inspect, reconcile, and verify convergence. ## Quick Start Ask the agent to use config-claude to inspect your Claude Code setup and reconcile the native instructions, roles, and hooks while preserving your personal settings.

Frequently Asked Questions about config-claude

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure Claude Code settings without losing my personal preferences?

Use patch-only reconciliation that updates one managed block in CLAUDE.md and adds only requested settings.json members. Existing values, formatting, ordering, deny rules, and model choices are preserved, and files are backed up privately before any authorized change.

How do I recover a missing Claude Code settings.json file?

Run the recovery helper with an absolute Claude home path to publish a minimal {} baseline atomically via an exclusive hard link. It never replaces an existing or concurrently created file, and the trusted-local profile requires explicit selection.

Can I use this setup skill from Codex to configure Claude Code?

Yes, the skill is invocable from Codex with $config-claude or natively in Claude Code with /config-claude, but the configuration target is always Claude. It resolves the Claude home from an explicit path, CLAUDE_CONFIG_DIR, or ~/.claude, never from CODEX_HOME.

Does the checker modify my Claude configuration files?

No, the convergence checker is strictly read-only and data-only. It reports each surface as Aligned, Not aligned, or Blocked with redacted reasons and file digests, and it never prints secrets, imports source modules, or starts MCP servers.

Why does full hook setup fail from a standalone skill copy?

Complete hook setup requires the reviewed catalog containing the seven hook owners and the global-context-management runtime scripts. A standalone copy supports native inspection and recovery only, and missing dependencies are reported before any mutation.

How are MCP servers added to Claude Code user scope?

Selected servers from the catalog are added with claude mcp add-json --scope user using literal JSON, keeping secret variable references unexpanded. Registration is verified separately from connectivity, and plugin-owned entries are never duplicated.