The explain-this skill: know what every file in your project does

Your project folder fills up with files you never asked for. package.json, a lock file, a config with a dot at the front of its name, a folder with 4,000 things in it. None of it was your decision and all of it looks important, so the folder starts feeling like somebody else's machine and you stop opening it.

The explain-this skill fixes that one thing. You paste whatever you're staring at, and it tells you what it is, what it does while your project runs, who put it there, what would actually happen if it disappeared, and which two or three lines in it you'd ever realistically change. Then it gives you permission to ignore the rest.

It's free, it's in our public freeskills repo, and it's built for someone who has Claude Code open and has never opened one of these files on purpose.

Paste these three lines into your terminal. The first grabs the repo, the second makes sure your skills folder exists, the third puts explain-this where Claude Code goes looking for it.

Start a new Claude Code session and the skill is live. No API keys, no config file.

Type /explain-this and paste the thing that's confusing you. It takes anything: a whole file, a folder listing, five lines of code, an error, one word you saw and didn't recognize. If you'd rather name a path than paste, it opens the file itself.

What comes back is short and headed rather than a wall of prose. You get five answers in order, then any flags that genuinely apply, like a warning that you just pasted a secret key or that the file gets rewritten automatically so editing it by hand is pointless. It closes with exactly two labeled lines: worth understanding, and safe to ignore. The whole thing saves to ~/claude-explained/ named after what you asked about.

There's no task at the end of this one. It's for reading, and it says so, so you don't sit there waiting for a next step.

This is the real question most of the time. You want to tidy up and you're scared the folder you're eyeing is holding the whole thing together.

This is a good first run. Instead of one file, hand it the whole listing and get a map of which things matter and which ones are machinery.

Something broke, the red text mentioned a filename, and you have no idea what that file even is. Point the skill at it before you try to fix anything.

If you'd rather say it than read it, here is what the skill does and why it matters.

1. 1Hook: there's a brand new free Claude skill that takes you from a folder full of files you're scared to touch to knowing exactly what every one of them does.
2. 2Mechanism: you paste whatever is confusing you, a whole file or a folder listing or five lines you don't recognize. It answers the same five questions every time: what this is, what it does, why it's there, what would happen if it vanished, and the two or three lines you'd ever actually change. Then it closes with one idea worth understanding and one thing you can stop looking at forever.
3. 3Transformation: you open your own project without that low-level dread, and you stop avoiding the parts you didn't build. Every explanation saves to a folder, so it becomes your glossary in your own words.
4. 4Close: it's free, and it's one of 55 in the repo. Knowing your own folder is one piece of it. If you want the whole path, that's Claude Code Club at $9 a month. Link below.

Tonight, open the project you've been building and paste the one file you've been quietly avoiding. That's the whole action. You'll be less scared of the folder in about ninety seconds.