File Organizer

File organization and batch operations for workspace management. Use when organizing files for: (1) Moving files to correct directories, (2) Batch renaming (...

Security Scan

The skill is an instruction-only file-organization helper whose requirements and instructions align with its stated purpose; it contains potentially destructive shell recipes but includes safety guidance and requests no credentials or installs.

Purpose & Capability

The name/description (file organization and batch ops) matches the included instructions and templates. The SKILL.md assumes standard POSIX utilities (mv, find, xargs, mkdir, tar, git, stat, date) but the skill metadata does not declare required binaries — this is not necessarily malicious but users should be aware the skill expects a Unix-like shell environment.

Instruction Scope

Instructions stay within the file-organization domain (moving, renaming, scaffolding). Many commands are destructive (e.g., find . -type f -exec mv {} . \;, find . -type f -empty -delete, batch mv operations) and the docs correctly recommend dry runs, backups, and respecting workspace boundaries. No instructions reference unrelated files, external endpoints, or hidden data exfiltration. Because the skill is instruction-only, the agent following it could execute these shell commands — the risk is operational (data loss) rather than covert exfiltration.

Install Mechanism

No install spec or code files are present. As an instruction-only skill it writes nothing to disk and does not download external code, which minimizes supply-chain risk.

Credentials

The skill requests no environment variables, credentials, or config paths. That is proportionate to its stated purpose.

Persistence & Privilege

always is false and the skill does not request elevated persistence or modify other skills or system-wide agent settings.

Assessment

This skill is coherent and appears safe in intent, but it is instruction-only: if you let an agent execute these commands they will run shell utilities on your files. Before installing or running, (1) ensure you have backups (tar or git snapshot), (2) test on a small sample or a disposable directory, (3) run dry-runs (echo/find) and inspect outputs, (4) confirm you are in the intended working directory (the docs recommend limiting to ~/openclaw), and (5) be cautious with commands that delete or flatten directories (find ... -exec mv ... and -delete). Also note these recipes assume a Unix-like shell; adapt or avoid them on Windows. If you want stronger safety, require the agent to provide proposed commands for manual review rather than allowing automatic execution.

Manages file organization through safe, predictable batch operations.

Core Workflows

Directory Structure

Create standard project layouts:

project/
├── src/          - Source code
├── docs/         - Documentation
├── tests/        - Test files
├── assets/       - Images, fonts, media
├── scripts/      - Build scripts, utilities
└── config/       - Configuration files

Moving Files

• mv <source> <dest> - Single file
• find . -name "*.ext" -exec mv {} <dest>/ \; - Batch by extension
• Always confirm destination exists

Batch Renaming

Patterns:

• Sequential numbering: file_{001..100}.txt
• Date-based: YYYY-MM-DD_description
• Type-based: Group by extension

Safe approach:

1. echo commands first (dry run)
2. Review output
3. Remove echo, execute

Organizing by Type

Group files by extension into folders:

mkdir -p images docs code
find . -name "*.png" -o -name "*.jpg" | xargs -I {} mv {} images/
find . -name "*.md" -o -name "*.txt" | xargs -I {} mv {} docs/
find . -name "*.py" -o -name "*.js" | xargs -I {} mv {} code/

Finding Scattered Files

find . -type f -name "*.ext"    # Find by extension
find . -type f -mtime -7        # Modified in last 7 days
find . -type f -size +100M      # Large files

Dry Runs First

Always preview batch operations:

echo "Would move these files:"
find . -name "*.ext"
# Review, then execute

Safety Rules

1. Never delete without explicit permission (use trash if available)
2. Dry run first - Always echo/preview batch operations
3. Check destinations - Confirm target directories exist
4. Backup before restructure - Snapshot before major moves
5. Respect workspace boundaries - Only touch ~/openclaw

When to Read references/patterns.md

Load when:

• Complex rename patterns needed
• Project structure templates required
• Advanced find commands for filtering
• Edge cases (symlinks, special characters)