file-organizer_skill

Overview

This skill organizes files in a target directory by grouping them into categorized folders (Images, Documents, Videos, Code, Archives, etc.). It scans the directory, proposes a clear move plan, asks for confirmation, then creates folders and moves files while avoiding overwrites. The skill preserves file integrity and reports exactly what it changed.

How this skill works

It first analyzes the directory: lists files, detects types and counts per category, and notes existing folders and edge cases (hidden files, symlinks). It then builds an organization strategy (default: by file type; alternatives: by date, size, project, or custom categories) and presents a detailed plan for user confirmation. After approval, it creates missing folders, moves files without overwriting (renames on conflict), preserves timestamps and permissions, and returns a concise summary and undo instructions.

When to use it

• When you want to "organize files" or "sort files by type" in a directory
• To clean up a Downloads, Desktop, or project folder
• When preparing files for backup or archiving
• To group media, documents, code, or archives into predictable folders
• When you need a reversible, non-destructive reorganization

Best practices

• Work on one directory at a time and back up important files first
• Review the proposed plan before confirming any moves
• Test on a small folder before running on large directories
• Choose a clear categorization strategy (by type, date, size, or custom) beforehand
• Skip symbolic links unless you intend to relocate targets; preserve hidden config files by default

Example use cases

• Clean the Downloads folder into Images/, Documents/, Videos/, Archives/, Others/
• Group all media (images + videos) into a single Media/ folder and separate documents into Documents/
• Organize a project directory into source/, tests/, docs/, configs/ based on file extensions
• Sort a large photo collection into date-based subfolders after initial type-based grouping
• Resolve naming conflicts by renaming duplicates (photo.jpg → photo-2.jpg) and report changes