Use when "organizing files", "cleaning up folders", "finding duplicates", "structuring directories", or asking about "Downloads cleanup", "folder structure", "file management"
Installation
Details
Usage
After installing, this skill will be available to your AI coding assistant.
Verify installation:
npx agent-skills-cli listSkill Instructions
name: file-organization description: Use when "organizing files", "cleaning up folders", "finding duplicates", "structuring directories", or asking about "Downloads cleanup", "folder structure", "file management" version: 1.0.0
<!-- 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
- Analyze - Review current structure
- Plan - Propose new structure
- Confirm - Get user approval
- Execute - Move files systematically
- 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).pdfβfile.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
| Frequency | Task |
|---|---|
| Weekly | Sort new downloads |
| Monthly | Review/archive projects |
| Quarterly | Check for duplicates |
| Yearly | Archive old files |
Important Rules
- Always confirm before deleting
- Log all moves for undo
- Preserve modification dates
- Stop and ask on unexpected situations
More by eyadsibai
View allUse when "data pipelines", "ETL", "data warehousing", "data lakes", or asking about "Airflow", "Spark", "dbt", "Snowflake", "BigQuery", "data modeling"
Use when "LangChain", "LLM chains", "ReAct agents", "tool calling", or asking about "RAG pipelines", "conversation memory", "document QA", "agent tools", "LangSmith"
This skill should be used when the user asks to "create a commit", "write commit message", "create a pull request", "generate changelog", "manage branches", "git workflow", "merge strategy", "PR description", or mentions git operations and version control workflows.
Use when implementing end-to-end tests, using Playwright or Cypress, testing user journeys, debugging flaky tests, or asking about "E2E testing", "Playwright", "Cypress", "browser testing", "visual regression", "test automation"
