File Organizer workflow skill. Use this skill when the user needs 6. Reduces Clutter: Identifies old files you probably don't need anymore and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
File Organizer workflow skill. Use this skill when the user needs 6. Reduces Clutter: Identifies old files you probably don't need anymore and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
This public intake copy packages plugins/antigravity-awesome-skills-claude/skills/file-organizer from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.
Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.
This intake keeps the copied upstream files intact and uses metadata.json plus ORIGIN.md as the provenance anchor for review.
File Organizer
Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: What This Skill Does, Limitations.
When to Use This Skill
Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.
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
Operating Table
Situation
Start here
Why it matters
First-time use
metadata.json
Confirms repository, branch, commit, and imported path before touching the copied workflow
Provenance review
ORIGIN.md
Gives reviewers a plain-language audit trail for the imported source
Workflow execution
SKILL.md
Starts with the smallest copied file that materially changes execution
Supporting context
SKILL.md
Adds the next most relevant copied source file without loading the entire package
Handoff decision
## Related Skills
Helps the operator switch to a stronger native skill when the task drifts
Workflow
This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.
Understand the Scope
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
Total files and folders
Imported Workflow Notes
Imported: 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 structurels -la [target_directory]
# Check file types and sizes
find [target_directory] -type f -exec file {} \; | head -20
# Identify largest filesdu -sh [target_directory]/* | sort -rh | head -20
# Count file types
find [target_directory] -type f | sed 's/.*\.//' | sort | uniq -c | sort -rn
Summarize 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 similar names
find [directory] -type f -printf'%f\n' | sort | uniq -d
# Find similar-sized files
find [directory] -type f -printf'%s %p\n' | sort -n
For 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 Make1.**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 structuremkdir -p "path/to/new/folders"# Move files with clear loggingmv"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# 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?
Imported: 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
Examples
Example 1: Ask for the upstream workflow directly
Use @file-organizer to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.
Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.
Example 2: Ask for a provenance-grounded review
Review @file-organizer against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.
Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.
Example 3: Narrow the copied support files before execution
Use @file-organizer for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.
Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.
Example 4: Build a reviewer packet
Review @file-organizer using the copied upstream files plus provenance, then summarize any gaps before merge.
Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.
Best Practices
Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.
Use clear, descriptive names
Avoid spaces (use hyphens or underscores)
Be specific: "client-proposals" not "docs"
Use prefixes for ordering: "01-current", "02-archive"
Include dates: "2024-10-17-meeting-notes.md"
Be descriptive: "q3-financial-report.xlsx"
Avoid version numbers in names (use version control instead)
Imported Operating Notes
Imported: 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)
Problem: The operator skipped the imported context and answered too generically
Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills-claude/skills/file-organizer, fails to mention provenance, or does not use any copied source files at all.
Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Load only the files that materially change the answer, then restate the provenance before continuing.
Problem: The imported workflow feels incomplete during review
Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task.
Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.
Problem: The task drifted into a different specialization
Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better.
Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.
Related Skills
@00-andruia-consultant-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
@10-andruia-skill-smith-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
@20-andruia-niche-intelligence-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
@2d-games - Use when the work is better handled by that native specialization after this imported skill establishes context.
Additional Resources
Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.
Resource family
What it gives the reviewer
Example path
references
copied reference notes, guides, or background material from upstream
references/n/a
examples
worked examples or reusable prompts copied from upstream
examples/n/a
scripts
upstream helper scripts that change execution or validation
scripts/n/a
agents
routing or delegation notes that are genuinely part of the imported package
agents/n/a
assets
supporting assets or schemas copied from the source package
assets/n/a
Imported Reference Notes
Imported: Limitations
Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
