Synthèse automatique
Ce skill aide à réorganiser les fichiers et dossiers d'un ordinateur en analysant leur contenu, en repérant les doublons et en proposant une arborescence plus logique, avec des commandes shell concrètes.
Points forts
- Fournit des commandes d'inspection prêtes à l'emploi (ls, find, du, comptage par extension) pour dresser un état des lieux
- Couvre plusieurs axes de rangement : par type, par usage, par date
- Intègre une recherche de doublons par hash MD5 et par nom de fichier
- Prévoit une étape de clarification du périmètre et du niveau d'agressivité avant toute action
Limites
- Le contenu du SKILL.md est tronqué : les commandes de détection de doublons et la suite des instructions sont incomplètes
- Aucune procédure de sauvegarde, de journal des déplacements ou d'annulation n'est décrite
- Les exemples sont pensés pour macOS/Linux uniquement, rien n'est prévu pour Windows
À utiliser lorsque le dossier Téléchargements ou Documents est encombré et qu'on veut une arborescence plus claire sans trier à la main.
À éviter sur des répertoires système, sensibles ou versionnés, faute de garde-fous documentés pour les déplacements de fichiers.
Analyse de sécurité
PrudenceThe skill is benign in intent—it provides shell commands for scanning, moving, renaming, and de-duplicating files, plus guidance to confirm deletions and log moves. There is no exfiltration, obfuscation, curl|sh, or safety-disabling. However, it does drive destructive, irreversible file operations (mv/delete) across potentially wide scopes like the whole home folder, so it warrants a caution rating rather than safe.
- •Instructs use of powerful shell operations (find, mv, rm-adjacent deletion of duplicates) with broad scope potentially over the entire home directory.
- •No enforced exclusions: although it asks users about sensitive folders, the workflow could reorganize or delete files in sensitive directories if the user is not careful.
- •Deletion safety relies entirely on the model following 'confirm before deleting' guidance; no technical safeguard exists.
- •Uses md5 for duplicate detection, which is collision-prone and could lead to incorrect duplicate identification if the model deletes based on it.
- •The skill instructs the agent to run shell commands (find, du, md5, mkdir, mv) despite declaring no allowed-tools.
- •It supports moving, renaming, archiving, and deleting user files; although it asks for confirmation before deletion and recommends logging moves, incorrect execution could still cause data loss.
Exemples
Help me organize my Downloads folder — there are hundreds of unsorted files and I can't find anything.Find duplicate files in my Documents folder and help me decide which copies to keep.Review my project directories under ~/work and suggest a better folder structure.name: file-organizer description: Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort. author: Joseph OBrien status: unpublished updated: '2025-12-23' version: 1.0.1 tag: skill type: skill
File Organizer
This skill acts as your personal organization assistant, helping you maintain a clean, logical file structure across your computer without the mental overhead of constant manual organization.
When to Use This Skill
- Your Downloads folder is a chaotic mess
- You can't find files because they're scattered everywhere
- You have duplicate files taking up space
- Your folder structure doesn't make sense anymore
- You want to establish better organization habits
- You're starting a new project and need a good structure
- You're cleaning up before archiving old projects
What This Skill Does
- Analyzes Current Structure: Reviews your folders and files to understand what you have
- Finds Duplicates: Identifies duplicate files across your system
- Suggests Organization: Proposes logical folder structures based on your content
- Automates Cleanup: Moves, renames, and organizes files with your approval
- Maintains Context: Makes smart decisions based on file types, dates, and content
- Reduces Clutter: Identifies old files you probably don't need anymore
How to Use
From Your Home Directory
cd ~
Then run Claude Code and ask for help:
Help me organize my Downloads folder
Find duplicate files in my Documents folder
Review my project directories and suggest improvements
Specific Organization Tasks
Organize these downloads into proper folders based on what they are
Find duplicate files and help me decide which to keep
Clean up old files I haven't touched in 6+ months
Create a better folder structure for my [work/projects/photos/etc]
Instructions
When a user requests file organization help:
-
Understand the Scope
Ask clarifying questions:
- Which directory needs organization? (Downloads, Documents, entire home folder?)
- What's the main problem? (Can't find things, duplicates, too messy, no structure?)
- Any files or folders to avoid? (Current projects, sensitive data?)
- How aggressively to organize? (Conservative vs. comprehensive cleanup)
-
Analyze Current State
Review the target directory:
# Get overview of current structure ls -la [target_directory] # Check file types and sizes find [target_directory] -type f -exec file {} \; | head -20 # Identify largest files du -sh [target_directory]/* | sort -rh | head -20 # Count file types find [target_directory] -type f | sed 's/.*\.//' | sort | uniq -c | sort -rnSummarize findings:
- Total files and folders
- File type breakdown
- Size distribution
- Date ranges
- Obvious organization issues
-
Identify Organization Patterns
Based on the files, determine logical groupings:
By Type:
- Documents (PDFs, DOCX, TXT)
- Images (JPG, PNG, SVG)
- Videos (MP4, MOV)
- Archives (ZIP, TAR, DMG)
- Code/Projects (directories with code)
- Spreadsheets (XLSX, CSV)
- Presentations (PPTX, KEY)
By Purpose:
- Work vs. Personal
- Active vs. Archive
- Project-specific
- Reference materials
- Temporary/scratch files
By Date:
- Current year/month
- Previous years
- Very old (archive candidates)
-
Find Duplicates
When requested, search for duplicates:
# Find exact duplicates by hash find [directory] -type f -exec md5 {} \; | sort | uniq -d # Find files with same name find [directory] -type f -printf '%f\n' | sort | uniq -d # Find similar-sized files find [directory] -type f -printf '%s %p\n' | sort -nFor each set of duplicates:
- Show all file paths
- Display sizes and modification dates
- Recommend which to keep (usually newest or best-named)
- Important: Always ask for confirmation before deleting
-
Propose Organization Plan
Present a clear plan before making changes:
# Organization Plan for [Directory] ## Current State - X files across Y folders - [Size] total - File types: [breakdown] - Issues: [list problems] ## Proposed Structure[Directory]/ ├── Work/ │ ├── Projects/ │ ├── Documents/ │ └── Archive/ ├── Personal/ │ ├── Photos/ │ ├── Documents/ │ └── Media/ └── Downloads/ ├── To-Sort/ └── Archive/
## Changes I'll Make 1. **Create new folders**: [list] 2. **Move files**: - X PDFs → Work/Documents/ - Y images → Personal/Photos/ - Z old files → Archive/ 3. **Rename files**: [any renaming patterns] 4. **Delete**: [duplicates or trash files] ## Files Needing Your Decision - [List any files you're unsure about] Ready to proceed? (yes/no/modify) -
Execute Organization
After approval, organize systematically:
# Create folder structure mkdir -p "path/to/new/folders" # Move files with clear logging mv "old/path/file.pdf" "new/path/file.pdf" # Rename files with consistent patterns # Example: "YYYY-MM-DD - Description.ext"Important Rules:
- Always confirm before deleting anything
- Log all moves for potential undo
- Preserve original modification dates
- Handle filename conflicts gracefully
- Stop and ask if you encounter unexpected situations
-
Provide Summary and Maintenance Tips
After organizing:
# Organization Complete! ✨ ## What Changed - Created [X] new folders - Organized [Y] files - Freed [Z] GB by removing duplicates - Archived [W] old files ## New Structure [Show the new folder tree] ## Maintenance Tips To keep this organized: 1. **Weekly**: Sort new downloads 2. **Monthly**: Review and archive completed projects 3. **Quarterly**: Check for new duplicates 4. **Yearly**: Archive old files ## Quick Commands for You ```bash # Find files modified this week find . -type f -mtime -7 # Sort downloads by type [custom command for their setup] # Find duplicates [custom command]Want to organize another folder?
Examples
Example 1: Organizing Downloads (From Justin Dielmann)
User: "My Downloads folder is a mess with 500+ files. Help me organize it."
Process:
- Analyzes Downloads folder
- Finds patterns: work docs, personal photos, installers, random PDFs
- Proposes structure:
- Downloads/
- Work/
- Personal/
- Installers/ (DMG, PKG files)
- Archive/
- ToSort/ (things needing decisions)
- Downloads/
- Asks for confirmation
- Moves files intelligently based on content and names
- Results: 500 files → 5 organized folders
Example 2: Finding and Removing Duplicates
User: "Find duplicate files in my Documents and help me decide which to keep."
Output:
# Found 23 Sets of Duplicates (156 MB total)
## Duplicate Set 1: "proposal.pdf"
- `/Documents/proposal.pdf` (2.3 MB, modified: 2024-03-15)
- `/Documents/old/proposal.pdf` (2.3 MB, modified: 2024-03-15)
- `/Desktop/proposal.pdf` (2.3 MB, modified: 2024-03-10)
**Recommendation**: Keep `/Documents/proposal.pdf` (most recent in correct location)
Delete the other 2 copies?
[Continue for all duplicates...]
Example 3: Restructuring Projects Folder
User: "Review my ~/Projects directory and suggest improvements."
Output:
# Analysis of ~/Projects
## Current Structure Issues
- Mix of active and archived projects (3+ years old)
- No consistent naming convention
- Some projects at root, others in random subfolders
- Duplicate folders (project-name, project-name-old, project-name-v2)
## Proposed Structure
Projects/ ├── Active/ │ ├── client-work/ │ ├── side-projects/ │ └── learning/ ├── Archive/ │ ├── 2022/ │ ├── 2023/ │ └── 2024/ └── Templates/
## Specific Changes
1. Move 12 projects not touched since 2022 → Archive/
2. Consolidate 4 duplicate project folders
3. Rename projects to consistent format: "client-name-project-name"
4. Create Archive for old work
Want me to implement this?
Example 4: Organizing Photos by Date
User: "Organize my photo folders by year and month."
Output: Creates structure like:
Photos/
├── 2023/
│ ├── 01-January/
│ ├── 02-February/
│ └── ...
├── 2024/
│ ├── 01-January/
│ └── ...
└── Unsorted/
Then moves photos based on EXIF data or file modification dates.
Common Organization Tasks
Downloads Cleanup
Organize my Downloads folder - move documents to Documents,
images to Pictures, keep installers separate, and archive files
older than 3 months.
Project Organization
Review my Projects folder structure and help me separate active
projects from old ones I should archive.
Duplicate Removal
Find all duplicate files in my Documents folder and help me
decide which ones to keep.
Desktop Cleanup
My Desktop is covered in files. Help me organize everything into
my Documents folder properly.
Photo Organization
Organize all photos in this folder by date (year/month) based
on when they were taken.
Work/Personal Separation
Help me separate my work files from personal files across my
Documents folder.
Pro Tips
- Start Small: Begin with one messy folder (like Downloads) to build trust
- Regular Maintenance: Run weekly cleanup on Downloads
- Consistent Naming: Use "YYYY-MM-DD - Description" format for important files
- Archive Aggressively: Move old projects to Archive instead of deleting
- Keep Active Separate: Maintain clear boundaries between active and archived work
- Trust the Process: Let Claude handle the cognitive load of where things go
Best Practices
Folder Naming
- Use clear, descriptive names
- Avoid spaces (use hyphens or underscores)
- Be specific: "client-proposals" not "docs"
- Use prefixes for ordering: "01-current", "02-archive"
File Naming
- Include dates: "2024-10-17-meeting-notes.md"
- Be descriptive: "q3-financial-report.xlsx"
- Avoid version numbers in names (use version control instead)
- Remove download artifacts: "document-final-v2 (1).pdf" → "document.pdf"
When to Archive
- Projects not touched in 6+ months
- Completed work that might be referenced later
- Old versions after migration to new systems
- Files you're hesitant to delete (archive first)
Related Use Cases
- Setting up organization for a new computer
- Preparing files for backup/archiving
- Cleaning up before storage cleanup
- Organizing shared team folders
- Structuring new project directories
Du fichier au premier essai
Le téléchargement contient exactement le contenu affiché sur cette fiche. Cette copie peut différer de la dernière version du dépôt source.
Consulter la source et ses fichiers annexesCe téléchargement contient uniquement SKILL.md. Les scripts, références, modèles et dépendances éventuels ne sont pas inclus. Récupérez les fichiers nécessaires depuis la source en conservant leur arborescence avant de poursuivre.
1. Télécharger le fichier
Télécharger SKILL.mdDepuis la racine d’un projet de test, enregistrez le fichier sous .skill-downloads/file-organizer-mmio7223/SKILL.md, ou utilisez la commande suivante. Ce dossier sert à examiner la skill avant son installation.
Commande pour macOS/Linux ou WSL : un shell POSIX et curl sont nécessaires. Sous Windows sans WSL, utilisez le bouton de téléchargement et créez le dossier manuellement.
mkdir -p '.skill-downloads/file-organizer-mmio7223' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/file-organizer-mmio7223/download' --output '.skill-downloads/file-organizer-mmio7223/SKILL.md.part' && mv '.skill-downloads/file-organizer-mmio7223/SKILL.md.part' '.skill-downloads/file-organizer-mmio7223/SKILL.md'2. Vérifier les prérequis
Lisez SKILL.md avant de l’utiliser. Si le fichier cite des scripts ou services externes, examinez-les et préparez les accès nécessaires dans votre environnement de test.
Aucune section de prérequis reconnue dans ce fichier. Cela ne signifie pas qu’il est autonome : les bibliothèques, outils et accès peuvent être cités ailleurs dans le contenu ou dans le dépôt source.
Les plateformes de la fiche sont des indications du catalogue. Les chemins ci-dessous suivent la documentation des outils ; ils ne prouvent pas que cette skill y a été exécutée. Aucune version minimale de ces outils n’est attestée pour cette fiche.
3. Charger la skill
Après vérification, copiez le dossier complet dans le projet avec l’une des commandes ci-dessous, puis ouvrez une nouvelle session de l’outil. La commande s’arrête si un dossier du même nom existe déjà : comparez les fichiers avant de le remplacer.
Claude Code
test -f '.skill-downloads/file-organizer-mmio7223/SKILL.md' && test -s '.skill-downloads/file-organizer-mmio7223/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/file-organizer' && cp -R '.skill-downloads/file-organizer-mmio7223' '.claude/skills/file-organizer'OpenSkills
OpenSkills doit déjà être installé. La procédure locale install/read est contrôlée avec OpenSkills 1.5.0, qui exige Node.js ≥ 20.6.0. Aucun slug du catalogue n’est résolu automatiquement.
Installation officielle d’OpenSkillsopenskills install './.skill-downloads/file-organizer-mmio7223'openskills read 'file-organizer-mmio7223'La lecture doit afficher le contenu du fichier installé et son dossier de base. Elle ne lance ni la skill ni ses dépendances.
Pour un agent qui lit AGENTS.md, synchronisez ensuite l’index. Cette commande modifie AGENTS.md : relisez le diff avant de l’utiliser.
openskills syncMode manuel ou autre outil : joignez SKILL.md à une conversation, ou ouvrez-le dans un agent capable de lire les fichiers. Ajoutez les ressources annexes nécessaires. Il n’existe pas de dossier universel reconnu par tous les outils.
4. Faire un premier essai
Utilisez une entrée courte et fictive : un endpoint d’API, un petit document ou un brief d’interface. Dans une nouvelle conversation, joignez le fichier ou donnez son chemin à l’agent, puis adaptez cette demande :
Lis .skill-downloads/file-organizer-mmio7223/SKILL.md et applique ses instructions à cet exemple : [décrire une entrée de test]. Indique les fichiers, dépendances ou accès qui manquent. Produis le résultat demandé par la skill sans inventer de données ni exécuter de script non examiné.Résultat attendu : une sortie correspondant aux instructions de la skill, ou une liste précise des prérequis manquants. Une simple confirmation de lecture ne valide pas le premier usage. Si une ressource externe est indisponible, ce parcours reste à tester.
Lecteur PDF
Productivite
Lit et extrait le texte de fichiers PDF (rapports, contrats, tableurs). Gère les fichiers locaux, les URL et les pièces jointes WhatsApp. Utilisez-le dès qu'un contenu PDF est nécessaire, même sans demande explicite.
Workflows de messagerie Discord
Productivite
Utilisez l'outil message pour envoyer, modifier et modérer des messages Discord avec des composants interactifs.
Aperçu interactif des verdicts
Productivite
Générer un aperçu HTML interactif des verdicts (garder/supprimer) pour la revue par le mainteneur, puis traiter le JSON de retour.