Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
eyadsibai avatar

File Organization

  • 569 installs
  • 7 repo stars
  • Updated January 15, 2026
  • eyadsibai/ltk

file-organization is a Claude Code skill that guides developers through auditing directories, removing duplicates, and standardizing folder layouts so coding agents can reliably locate and edit the right files.

About

file-organization is a version 1.0.0 agent skill adapted from awesome-claude-skills/file-organizer for cleaning chaotic project trees, Downloads folders, and duplicate-heavy directories. The skill prescribes shell analysis commands such as ls -la over target paths, then applies repeatable folder-structure patterns before archiving or starting new work. Developers reach for file-organization when scattered assets block navigation, duplicate files waste disk space, or an agent keeps editing the wrong path because naming and hierarchy are inconsistent. The workflow emphasizes progressive cleanup: overview the tree, identify duplicates and misplaced files, restructure directories, and document the resulting layout so future edits stay predictable.

  • Enforces consistent folder structures across new and existing projects
  • Generates and maintains a clear project layout specification
  • Reduces agent context errors caused by scattered files
  • Produces a reusable organization checklist for every new repository
  • Works with any tech stack to create predictable navigation patterns

File Organization by the numbers

  • 569 all-time installs (skills.sh)
  • Ranked #701 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
  • Data as of Jul 30, 2026 (Skillselion catalog sync)
npx skills add https://github.com/eyadsibai/ltk --skill file-organization

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs569
repo stars7
Last updatedJanuary 15, 2026
Repositoryeyadsibai/ltk

How do you clean up chaotic project folders and duplicates?

Keep project files, folders, and documentation consistently organized so agents can reliably find and edit the right code.

Who is it for?

Developers whose repos or Downloads folders are scattered and who need agent-friendly directory conventions before further coding.

Skip if: Teams that only need greenfield scaffolding templates without auditing existing files or removing duplicates.

When should I use this skill?

The user mentions organizing files, cleaning folders, finding duplicates, Downloads cleanup, folder structure, or file management.

What you get

A deduplicated directory tree, documented folder layout, and shell audit notes agents can follow.

  • Restructured folder tree
  • Duplicate removal plan
  • Documented directory layout

By the numbers

  • Skill version 1.0.0
  • Adapted from awesome-claude-skills/file-organizer

Files

SKILL.mdMarkdownGitHub ↗

<!-- Adapted from: awesome-claude-skills/file-organizer -->

File Organization Guide

Organize files, find duplicates, and maintain clean folder structures.

When to Use

  • Downloads folder is chaotic
  • Can't find files (scattered everywhere)
  • Duplicate files taking up space
  • Folder structure doesn't make sense
  • Starting a new project structure
  • Cleaning up before archiving

Analysis Commands

# Overview of directory
ls -la [directory]

# Count file types
find [directory] -type f | sed 's/.*\.//' | sort | uniq -c | sort -rn

# Largest files
du -sh [directory]/* | sort -rh | head -20

# Files modified this week
find [directory] -type f -mtime -7

Finding Duplicates

# By hash (exact duplicates)
find [directory] -type f -exec md5sum {} \; | sort | uniq -d

# By name
find [directory] -type f -printf '%f\n' | sort | uniq -d

# By size
find [directory] -type f -printf '%s %p\n' | sort -n | uniq -D -w 10

Organization Patterns

By Type

Downloads/
├── Documents/     # PDF, DOCX, TXT
├── Images/        # JPG, PNG, SVG
├── Videos/        # MP4, MOV
├── Archives/      # ZIP, TAR, DMG
├── Code/          # Projects
└── ToSort/        # Needs decision

By Purpose

Documents/
├── Work/
│   ├── Projects/
│   ├── Reports/
│   └── Archive/
└── Personal/
    ├── Finance/
    ├── Medical/
    └── Archive/

By Date

Photos/
├── 2024/
│   ├── 01-January/
│   ├── 02-February/
│   └── ...
├── 2023/
└── Unsorted/

Organization Workflow

1. Analyze - Review current structure 2. Plan - Propose new structure 3. Confirm - Get user approval 4. Execute - Move files systematically 5. Summarize - Report changes

Execution Commands

# Create structure
mkdir -p "path/to/new/folders"

# Move files
mv "old/path/file.pdf" "new/path/file.pdf"

# Batch move by extension
find . -name "*.pdf" -exec mv {} Documents/ \;

Best Practices

Folder Naming

  • Clear, descriptive names
  • Avoid spaces (use hyphens)
  • Use prefixes for ordering: 01-current, 02-archive

File Naming

  • Include dates: 2024-10-17-meeting-notes.md
  • Be descriptive
  • Remove download artifacts: file (1).pdffile.pdf

When to Archive

  • Not touched in 6+ months
  • Completed work for reference
  • Old versions after migration
  • Files you're hesitant to delete

Maintenance Schedule

FrequencyTask
WeeklySort new downloads
MonthlyReview/archive projects
QuarterlyCheck for duplicates
YearlyArchive old files

Important Rules

  • Always confirm before deleting
  • Log all moves for undo
  • Preserve modification dates
  • Stop and ask on unexpected situations

Related skills

FAQ

When should file-organization run?

file-organization should run when Downloads or project folders are chaotic, duplicates consume space, or agents cannot reliably find files. The skill triggers on phrases like organizing files, cleaning folders, and folder structure.

What commands does file-organization use?

file-organization starts with shell directory overviews such as ls -la on the target path, then guides duplicate detection and restructuring before documenting the final layout for future agent edits.

Productivity & Planningintegrationsdocs

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.