config-hygiene-edho-ferdian

Audits and cleans stale skills, hooks, permissions, and caches in Claude Code environments.

2|Updated Sep 6, 2026
One-click install
npx skills add https://github.com/edhoferdian/EEF --skill config-hygiene-edho-ferdian-edhoferdian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: config-hygiene-edho-ferdian
Source: https://github.com/edhoferdian/EEF/tree/main/.agents/skills/config-hygiene-edho-ferdian
Command: npx skills add https://github.com/edhoferdian/EEF --skill config-hygiene-edho-ferdian-edhoferdian

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Claude Code environments accumulate dead weight over time: unused skills, orphaned hooks, duplicate permission entries, failing MCP servers, and bloated caches silently inflate context cost and slow sessions. This Skill performs periodic garbage collection across the entire ~/.claude configuration surface with human confirmation and an undo path for every change. ## Core Features & Use Cases - Nine scan channels: Detects redundant skills, stale memory files, orphaned hooks, duplicate permissions, broken MCP servers, expired automations, stale project history, oversized caches, and context-expensive components. - Safe removal workflow: Ranks findings by confidence, confirms each item individually, soft-deletes to a trash folder, and logs every action with undo instructions. - Config tamper detection: Flags lint and formatter config edits that weaken checks to make gates pass instead of fixing code. - Use Case: A user notices sessions starting slowly and context filling fast. Run this Skill to audit ~/.claude, identify a 40MB stale cache, three unused MCP servers, and an always-loaded skill that fires twice a year, then reclaim the budget with per-item confirmation. ## Quick Start Ask the assistant to audit your Claude Code configuration for stale skills, unused MCP servers, and context-heavy components, then review each finding one by one.

Frequently Asked Questions about config-hygiene-edho-ferdian

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

FAQPage Schema
How do I clean up unused Claude Code skills and configs?

Run a config hygiene scan that checks nine channels including skills, hooks, permissions, and MCP servers. Each candidate is presented with evidence and confirmed individually, then soft-deleted to a trash folder so every change is reversible.

How to reduce context usage in Claude Code sessions?

Audit always-loaded components like MCP server tool definitions, skill frontmatter, and memory files, then rank them by tokens-per-session against actual usage. Disable, narrow descriptions, or reclassify rarely used items as library-only instead of daily-loaded.

Can config cleanup delete files automatically without confirmation?

No. This workflow never deletes autonomously and offers no yes-to-all option. Every candidate gets individual confirmation, items are renamed to .disabled or moved to a trash folder first, and each run is logged with undo instructions.

What is config tampering in lint and formatter settings?

Config tampering is when a failing lint or format gate is fixed by loosening the config, such as disabling an eslint rule or widening a ruff ignore list, instead of fixing the code. Scans flag such edits as high-confidence findings rather than routine changes.

When should I run a Claude Code environment audit?

Run a review roughly every 30 days, or when sessions start slowly, context fills quickly, or the skill list feels bloated. Each run is capped at about 20 candidates to keep the review manageable.