Not selling anything — it’s free and open source (MIT). Just sharing something I made for myself in case it’s useful, and I’d genuinely like feedback. The problem: my Claude Code config had turned into a mess. Skills, agents, hooks, MCP servers spread across a bunch of files. I’d write a skill, it wouldn’t trigger, and there was no obvious way to see why. Hooks that weren’t wired to an event just silently did nothing. Editing the raw files by hand was tedious and error-prone. So I built Claude Manager — a local web app (Node + Express, one dependency, runs entirely on your machine) that: Shows everything in one place, including the stuff that’s normally invisible — e.g. hooks that exist but aren’t actually wired to anything. Generates skills/agents/hooks from a plain-English description, then mechanically checks them — the most common bug I hit was a skill using a tool its allowed-tools never granted, so it now catches and one-click-fixes exactly that. Lets you copy the exact terminal command instead, if you’d rather run it yourself. A few design choices I’d be curious to hear opinions on: Correctness is enforced in code , not asked for in the prompt — a linter + auto-repair, not “please remember to grant tools.” There’s an optional self-eval loop for generated skills, but it’s hard-capped (max 3 model calls) because unbounded self-correction just oscillates and burns tokens. One-shot runs use –dangerously-skip-permissions , which is genuinely risky — so destructive commands like rm -rf are blocked via deny rules that hold even in that mode, and the default copy command is the interactive one that asks before each action. Repo: https://github.com/neeraj1892/claude-manager Roast it, break it, tell me what’s dumb. ~250 tests but I’m sure there are holes. submitted by /u/Loan-Sad
Originally posted by u/Loan-Sad on r/ClaudeCode