mcpField
F
file-naming

file-naming

github.com/nweiiProductivity1080 installsUpdated 1w ago
Repository

About file-naming

A file-naming skill for agents that analyzes file content and metadata, then proposes sortable, readable names. It previews and validates the full plan before making changes.

Key features

  1. 01Content- and metadata-based analysis
  2. 02Naming patterns for common document types
  3. 03Collision and destination validation
  4. 04Preview and confirmation before renaming
  5. 05No-clobber execution

Use cases

  1. 01Organizing receipts, invoices, and statements
  2. 02Standardizing names for photos and project files
  3. 03Renaming files after reviewing a proposed plan

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nweii/agent-stuff --skill file-naming

After installing, type/file-namingin Claude Code to confirm it loaded.

Bundled filesreferences/tv-episodes.md

Details

From the project README

Rename Files

Analyze files and propose intelligent renames based on content type and metadata. Provide: a single file path, list of file paths, or folder path.

Naming Conventions

Transactional/Periodic Documents

Repetitive transactions (orders, receipts, invoices, appointments):

  • Format: YYYY-MM-DD Category Type - Details.extension
  • Example: 2025-06-13 Amazon Order 123-456 - USB Cable.pdf
  • Include: dates, entity names, order/invoice numbers, item descriptions

Periodic documents (statements, bills, forms):

  • Format: YYYY-MM Type - Entity.extension
  • Example: 2025-06 Bank Statement - Chase Checking.pdf
  • Example: 2023-12 W2 - Acme Corp.pdf

Ongoing agreements (contracts, policies):

  • Format: YYYY-MM Type - Entity.extension
  • Example: 2025-01 Service Agreement - Internet Provider.pdf

Appointments/visits:

  • Format: YYYY-MM-DD Type - Provider/Location.extension
  • Example: 2025-06-13 Dental Visit - Dr Johnson.pdf
Creative/Project Files

Date as supplementary (photos, projects, creative work):

  • Format: Description - Date.extension or Description - Context Date.extension
  • Example: Vacation Photos - Hawaii 2025.jpg
  • Example: Website Redesign - Draft 2025-06.pdf
  • Example: Company Logo 2025.png

Evergreen content (manuals, references):

  • Format: Type - Name/Description.extension
  • Example: Product Manual - Widget Pro.pdf

Key Principles

  • ISO 8601 dates: YYYY-MM-DD (specific dates) or YYYY-MM (monthly/annual)
  • Date placement: Start for time-critical sorting; end for contextual info
  • Remove: Technical metadata (1080p, WEB-DL), problematic characters (:*?"<>|#%&)
  • Keep: Scannable and sortable filenames

Process

  1. Analyze files using OCR, text extraction, vision analysis, filename patterns
  2. Build the complete rename plan before taking any action
  3. Validate the plan: if any file cannot be mapped to a destination name, stop and report — do not proceed with partial results
  4. Validate the plan: confirm no two files share a destination name — if any collision exists, stop and report
  5. Present preview table: "Original Filename" | "New Filename" (show up to 15 files if many present; note any that couldn't be analyzed)
  6. Wait for confirmation before executing
  7. Execute using no-clobber semantics — never overwrite an existing file; if a collision occurs at execution time, halt immediately

If content unclear: make best guess from filename, clean up existing name, or leave unchanged with note.

For TV show files, see references/tv-episodes.md for Plex/media manager naming conventions.

Comments

Markdown supported