file-organization
Skill0 starsChanged 4 months agoMITView on GitHub
Check the repository tree against ORGANIZATION.md and propose fixes for anything misfiled, orphaned, or undeclared. Use before a goal brief moves to review, when files have accumulated in unclear places, when deciding where a new deliverable should live, or when the user asks whether the repo is organized. Proposes moves for approval; never reorganizes on its own.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- neilghosh/skillstheir own version, first seen Nov 9, 2026
- nimadorostkar/Claude-Skills-collectiontheir own version, first seen Oct 13, 2026
- z-Zihan/Evirtheir own version, first seen Oct 13, 2026
- sherifican/Agent-FleetOpstheir own version, first seen Oct 7, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- nimadorostkar/Claude-Skills-collection★ 37same name
- sherifican/Agent-FleetOps★ 34same name
- z-Zihan/Evir★ 11same name
- neilghosh/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repositoryOne other file it gives its agents.
- CLAUDE.mdCLAUDE.md
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 3 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Keep the tree matching ORGANIZATION.md.
- Very specific: line 13
Read ORGANIZATION.md. If it doesn't exist, stop and say so — there is nothing to check against, and inventing a taxonomy on the spot is …
- Distinctive: line 32
If nothing diverges but the map has drifted from reality in spirit — a category that describes nothing, a folder holding something other …
- Distinctive: line 37
Never move files without approval.
- Very specific: line 40
When work genuinely needs a category the map doesn't have, propose amending ORGANIZATION.md — as part of the goal that needs it, not as a …
- Very specific: line 55
Before a brief moves to review — the tree should match the map before a human is asked to accept the work.
- Distinctive: line 57
When picking the deliverable paths for a new brief.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
File organization
Keep the tree matching ORGANIZATION.md. That file is the contract; this skill checks
against it and proposes fixes. It does not rearrange things on its own judgment.
Check
- Read
ORGANIZATION.md. If it doesn't exist, stop and say so — there is nothing to check against, and inventing a taxonomy on the spot is exactly what this skill is meant to prevent. - List the tree, skipping
.git/and anything gitignored. Compare, and collect four kinds of divergence:
- Unaccounted — files in paths the map doesn't describe.
- Misfiled — files that exist somewhere the map wouldn't put them.
- Undelivered — paths declared by a brief in
active/orreview/that don't exist yet. - Undeclared — files that appeared but no brief claims as a deliverable. Cross-check
against
deliverablesin every brief's frontmatter.
Report
Group by kind, most consequential first. For each item give the path, why it diverges, and the specific fix. Say "no divergence" when there is none rather than inventing something to report.
If nothing diverges but the map has drifted from reality in spirit — a category that describes nothing, a folder holding something other than what it claims — say that too.
Propose, don't move
Never move files without approval. Present the moves as a list the user can accept whole or
in part, then execute what's approved with git mv so history follows the file.
When work genuinely needs a category the map doesn't have, propose amending
ORGANIZATION.md — as part of the goal that needs it, not as a silent side effect.
Be conservative
Premature structure costs as much as none. Bias toward leaving things alone.
- One file with no clear reason to expect a second doesn't need a folder.
- Deep nesting for a handful of files makes things harder to find, not easier.
- Directory names should say what things are — not who made them, or when.
- A file that's genuinely temporary belongs in the scratchpad or
.gitignore, not in a newmisc/ortmp/directory.
When to run
- Before a brief moves to
review— the tree should match the map before a human is asked to accept the work. - When picking the deliverable paths for a new brief.
- On request.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

