Connor Rhodes
451b9459d2
Each skill is now a folder with a SKILL.md inside. Added skill-creator skill with full eval tooling. Updated skill index and cross-references. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
62 lines
2.3 KiB
Markdown
62 lines
2.3 KiB
Markdown
---
|
|
name: file-organizer
|
|
description: Scan a folder for files that don't match your naming conventions, propose renames and folder placement, and execute on approval.
|
|
triggers:
|
|
- organize these files
|
|
- sort this folder
|
|
- clean up my files
|
|
- rename these
|
|
- sort my downloads
|
|
---
|
|
|
|
# File Organizer
|
|
|
|
Rename and sort files to match your naming conventions and folder structure.
|
|
|
|
## When to Use
|
|
|
|
Run this when you have a folder full of inconsistently named files, after downloading a batch of files, or any time things look messy.
|
|
|
|
## Instructions
|
|
|
|
1. Read the CLAUDE.md in the current workspace for naming conventions and folder structure rules.
|
|
2. Scan the target folder for files that don't match the naming convention.
|
|
3. For each file:
|
|
- Read the file (or read the filename and metadata) to understand what it is
|
|
- Determine the correct name following the naming convention
|
|
- Determine the correct subfolder based on the folder structure rules
|
|
4. Present the full plan as a list: current name → proposed name and location.
|
|
5. Wait for approval before executing any renames or moves.
|
|
6. Execute the approved changes.
|
|
|
|
### Output Format
|
|
|
|
**File Organization Plan**
|
|
|
|
| Current Name | Proposed Name | Destination |
|
|
|-------------|--------------|-------------|
|
|
| [old name] | [new name following conventions] | [target folder] |
|
|
|
|
[After approval, execute and confirm each change.]
|
|
|
|
## Customization Ideas
|
|
|
|
This is a starter file organizer. As you use it, consider adding:
|
|
- Rules for specific file types (images go here, PDFs go there)
|
|
- Automatic date detection from file metadata
|
|
- Project-specific naming patterns
|
|
- An archive step for old files
|
|
|
|
Video 8 walks you through setting up naming conventions and folder structure. Customize this skill to match the conventions you establish there.
|
|
|
|
## Rules
|
|
|
|
- **Never rename or move files without showing the plan first.** Always present and wait for approval.
|
|
- If CLAUDE.md has no naming conventions documented, ask the user to describe their preferred pattern before proceeding.
|
|
- Skip system files, hidden files, and anything in a `.git` or `.obsidian` folder.
|
|
- If a proposed name would conflict with an existing file, flag it and ask for guidance.
|
|
- Keep a log of what was renamed and where it was moved.
|
|
|
|
---
|
|
|
|
*Started with the Robot Assistant Field Guide Starter Kit. Customize after watching Video 8.*
|