AI Agent Hub
Back to skills
AI File Naming Rules Card icon

AI File Naming Rules Card

Office Efficiency Updated 2026.08.30

Paste the following prompt into your AI chat to install this skill:

Install @user_15292d5a/yjkj-ai-file-naming-system-card into your AI assistant following https://skillhub.cn/install/skillhub.md.

About this skill

The problem

Project folders often accumulate files like final2.docx, copy.pdf, and new draft.docx, so searching, archiving, and shared review depend on memory. Bulk renaming is risky when files are in shared drives or when context is missing. This skill turns messy file names into a simple, searchable, manually reviewable naming convention.

How it works

It does not scan directories, execute renames, or generate automation scripts. From a user-provided file list, project purpose, search terms, and constraints, it:
- clarifies the goal, such as sorting by date, grouping by client, or distinguishing draft from final;
- audits examples for missing dates, vague words, version markers, and inconsistent separators;
- recommends 3 to 5 tokens such as YYYY-MM-DD, project, content-type, and v01;
- outputs a one-page rules card, a recommended pattern, examples, and a manual rename queue;
- flags unknown values as needs review or [date], and advises backing up first and testing 5 to 10 files.

Boundaries

It fits project files, client deliverables, documents, images, reports, and asset naming. It does not read local folders, infer missing metadata, perform bulk renames, or migrate shared drives. If the user asks to scan a Documents folder and rename everything, it declines and instead builds a naming card and review queue from a pasted sample list.

Use Cases

  • When organizing client deliverables, turn samples like `draft deck` and `invoice` into a date-client-status rule.
  • For files like `notes final.docx` and `article copy.pdf`, build a searchable pattern and a manual review queue.
  • When organizing project files, distinguish drafts, finals, and versions to avoid unsearchable names like `final` or `copy`.
  • When maintaining shared drives, create a one-page rules card from a pasted file list, then back up and test small.

Best For

  • Engineers who archive project files want consistent naming and a manually reviewable rename queue.
  • Product managers handling client deliverables need scattered samples turned into date, client, and status rules.
  • Operations staff organizing course or event assets want drafts, finals, and versions distinguished instead of `final`-style names.
  • Team members maintaining shared drives want a one-page rules card without filesystem scanning or automatic renames.