config-curator

Audit Claude Code settings, skills, and MCP templates for safe pruning.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/crazygit/dot-code-agents --skill config-curator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: config-curator
Source: https://github.com/crazygit/dot-code-agents/tree/main/claude/skills/config-curator
Command: npx skills add https://github.com/crazygit/dot-code-agents --skill config-curator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintains a minimal, well-documented Claude Code configuration baseline by auditing settings, plugins, MCP templates, permissions, and related docs to keep the repository safe and maintainable.

Core Features & Use Cases

  • Enforces official-first components and a compact, high-signal configuration
  • Validates MCP templates, permissions, and documentation while avoiding secrets
  • Guides maintainers to prune unnecessary plugins and configurations for clarity and safety
  • Use Case: during a CLAUDE or codebase audit, run this skill to align claude/settings.json and claude/skills with official guidelines

Quick Start

Review the current claude/settings.json, claude/skills, and related docs to identify items for safe pruning and simplification.

Frequently Asked Questions about config-curator

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

FAQPage Schema
How do I audit Claude Code configuration settings and plugins for safety?

Auditing Claude Code configuration involves reviewing claude/settings.json and claude/skills to prune unnecessary plugins, validate MCP templates, and enforce a minimal, explainable baseline aligned with official documentation.

What is the best way to prune unnecessary MCP templates and plugins from Claude Code?

Pruning MCP templates and plugins requires a minimal-change workflow that validates permissions against official guidelines, removes redundant configurations, and replaces hardcoded secrets with placeholders to maintain repository safety.

Does Claude Code configuration audit support secrets management and placeholders?

Claude Code configuration audit implements secrets management by avoiding direct secret exposure, utilizing placeholders for sensitive values, and validating MCP templates to ensure configurations remain safe and explainable.

When do I need to streamline Claude Code documentation and permissions?

Streamlining Claude Code documentation and permissions is needed during codebase audits to align claude/settings.json and claude/skills with official guidelines, ensuring a compact, high-signal configuration baseline.

Can I modify core agent structures during a Claude Code configuration audit?

Claude Code configuration audits apply a minimal-change workflow that focuses on settings, plugins, and MCP templating without modifying core agent structures, ensuring the baseline remains safe and maintainable.