AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

File Naming

skill-nweii-agent-stuff-file-naming · by nweii

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.

↗ Repository
— No reviews yet
0 installs
9 views
0.0% view→install

Install

$ agentstack add skill-nweii-agent-stuff-file-naming

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-nweii-agent-stuff-file-naming)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of File Naming? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills