How do I install the Claude Config Management skill?

Run npx skillmds add majiayu000/claude-config-management in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Claude Config Management safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Claude Config Management?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Claude Config Management free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Claude Config Management?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Claude Config Management by majiayu000

Name: Claude Config Management
Rating: 4.2 (5 reviews)
Author: majiayu000

Claude Config Management

Use when configuring, maintaining, troubleshooting, or optimizing Claude Code extensions including skills, commands, hooks, MCP servers, or agents. Provides best practices and prevents common mistakes.

majiayu000 7e374ce 2 files · 3.7 KB Updated Sep 9, 2026 567 repo stars

File contents

Claude Code Configuration Management

Critical Constraints

Context Budget: MCP servers consume tokens before you work. A single server with 20 tools can use 14,000+ tokens. Keep active servers under 10.

Precedence Rule: Deny rules always win over allow rules at any level. More specific settings override broader ones.

Performance Threshold: If startup exceeds 30 seconds, clean ~/.claude.json of old project metadata.

Quick Decision Framework

I need to...	Use	Not
Enforce rules deterministically	Hook	Skill (probabilistic)
Provide domain expertise	Skill	Command (user-invoked)
Create user-triggered action	Command	Skill (auto-triggered)
Connect external service	MCP Server	Hook
Orchestrate multi-step tasks	Agent	Single command

File Locations

Content	Location
Project overview	CLAUDE.md (root)
Team settings	.claude/settings.json
Personal overrides	.claude/settings.local.json
MCP servers (team)	.mcp.json
Skills	.claude/skills/[name]/SKILL.md
Commands	.claude/commands/[name].md
Reference docs	.claude/docs/

Anti-Patterns to Avoid

Skills: Vague descriptions → Claude can't determine when to activate. Fix: Include trigger conditions.

Commands: Complex multi-step workflows → Belongs in skill. Fix: Keep commands simple (3-5 max).

Hooks: Complex inline commands → Hard to debug. Fix: Use script files.

MCP: Too many servers → Context exhaustion. Fix: Use McPick for selective enabling.

CLAUDE.md: Code style rules → Expensive enforcement. Fix: Use linters instead.

Verification Commands

/mcp              # MCP server status
/doctor           # Full diagnostics
/context          # Context usage breakdown
claude mcp list   # List configured servers

Maintenance Schedule

Weekly: Review /context, clear accumulated sessions
Monthly: Audit CLAUDE.md, check extension updates, clean ~/.claude.json
Quarterly: Full audit, remove unused extensions, update team docs

Detailed Reference

For complete procedures, checklists, and troubleshooting: → Read .claude/docs/config-management-reference.md

For finding and evaluating new extensions: → Read .claude/docs/resource-discovery-reference.md or use /discover

---name: claude-config-managementdescription: Use when configuring, maintaining, troubleshooting, or optimizing Claude Code extensions including skills, commands, hooks, MCP servers, or agents. Provides best practices and prevents common mistakes.--- # Claude Code Configuration Management ## Critical Constraints **Context Budget**: MCP servers consume tokens before you work. A single server with 20 tools can use 14,000+ tokens. Keep active servers under 10. **Precedence Rule**: Deny rules always win over allow rules at any level. More specific settings override broader ones. **Performance Threshold**: If startup exceeds 30 seconds, clean ~/.claude.json of old project metadata. ## Quick Decision Framework | I need to... | Use | Not | | ------------------------------- | ---------- | ---------------------- | | Enforce rules deterministically | Hook | Skill (probabilistic) | | Provide domain expertise | Skill | Command (user-invoked) | | Create user-triggered action | Command | Skill (auto-triggered) | | Connect external service | MCP Server | Hook | | Orchestrate multi-step tasks | Agent | Single command | ## File Locations | Content | Location | | ------------------ | ------------------------------ | | Project overview | CLAUDE.md (root) | | Team settings | .claude/settings.json | | Personal overrides | .claude/settings.local.json | | MCP servers (team) | .mcp.json | | Skills | .claude/skills/[name]/SKILL.md | | Commands | .claude/commands/[name].md | | Reference docs | .claude/docs/ | ## Anti-Patterns to Avoid **Skills**: Vague descriptions → Claude can't determine when to activate. Fix: Include trigger conditions. **Commands**: Complex multi-step workflows → Belongs in skill. Fix: Keep commands simple (3-5 max). **Hooks**: Complex inline commands → Hard to debug. Fix: Use script files. **MCP**: Too many servers → Context exhaustion. Fix: Use McPick for selective enabling. **CLAUDE.md**: Code style rules → Expensive enforcement. Fix: Use linters instead. ## Verification Commands ```bash /mcp # MCP server status /doctor # Full diagnostics /context # Context usage breakdown claude mcp list # List configured servers ``` ## Maintenance Schedule - **Weekly**: Review `/context`, clear accumulated sessions - **Monthly**: Audit CLAUDE.md, check extension updates, clean ~/.claude.json - **Quarterly**: Full audit, remove unused extensions, update team docs ## Detailed Reference For complete procedures, checklists, and troubleshooting: → Read `.claude/docs/config-management-reference.md` For finding and evaluating new extensions: → Read `.claude/docs/resource-discovery-reference.md` or use `/discover`

Frequently asked questions