How do I install the File Naming skill?

Run npx skillmds@latest add nweii/file-naming in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is File Naming safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with File Naming?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is File Naming free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published File Naming?

nweii (@nweii) published this skill. Their other Agent Skills are listed on their SkillMD profile.

File Naming by nweii — Agent Skill

Name: File Naming
Rating: 4.666666666666667 (3 reviews)
Author: nweii

File Naming

Analyze file content and propose intelligent renames using context-aware naming conventions. Date-prefixed for transactional/periodic documents, content-first for creative works. Use for organizing files, cleaning up downloads, or standardizing filenames.

nweii Updated Sep 9, 2026

File contents

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

Analyze files using OCR, text extraction, vision analysis, filename patterns
Build the complete rename plan before taking any action
Validate the plan: if any file cannot be mapped to a destination name, stop and report — do not proceed with partial results
Validate the plan: confirm no two files share a destination name — if any collision exists, stop and report
Present preview table: "Original Filename" | "New Filename" (show up to 15 files if many present; note any that couldn't be analyzed)
Wait for confirmation before executing
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.

--- name: file-naming description: "Analyze file content and propose intelligent renames using context-aware naming conventions. Date-prefixed for transactional/periodic documents, content-first for creative works. Use for organizing files, cleaning up downloads, or standardizing filenames." metadata: author: nweii version: "1.1.0" --- # 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](references/tv-episodes.md) for Plex/media manager naming conventions.

Frequently asked questions