One-click install
npx skills add https://github.com/Ryno-Crypto-Mining-Services/ryno-assets --skill file-renamer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: file-renamer
Source: https://github.com/Ryno-Crypto-Mining-Services/ryno-assets/tree/main/.claude/skills/file-renamer
Command: npx skills add https://github.com/Ryno-Crypto-Mining-Services/ryno-assets --skill file-renamer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the tedious and error-prone process of manually renaming files to comply with strict repository naming conventions, saving time and preventing inconsistencies.

Core Features & Use Cases

  • Intelligent Renaming: Automatically converts filenames to lowercase, replaces spaces with hyphens, adds versioning, and structures names based on file type (images, documents, markdown).
  • Interactive Guidance: Prompts for missing information (e.g., organization, product, descriptor) when automated content analysis is insufficient.
  • Use Case: After a large data import, use this skill to automatically standardize all image and document filenames to match your company's CLAUDE.md guidelines, ensuring consistency and discoverability.

Quick Start

Use the file-renamer skill to rename 'My_Old_Report_v1.pdf' to comply with the document naming conventions.

Frequently Asked Questions about file-renamer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically rename files to match naming conventions?

File renaming converts filenames to lowercase, replaces spaces with hyphens, removes special characters, and adds versioning to comply with CLAUDE.md standards. The skill handles images, documents, and markdown files automatically, prompting for missing metadata like organization or product descriptor when needed.

Can I rename bulk files across a repository at once?

Yes, the skill applies file-type-specific naming templates across your entire repository. It standardizes images, documents, and markdown simultaneously, making it ideal for post-import cleanup, legacy directory organization, and pre-commit hook integration without manual per-file intervention.

What happens to file metadata like resolution or categories during renaming?

The skill extracts or prompts for organization, product, and descriptor information. For images, it infers and includes resolution in the renamed filename. For documents and markdown, it extracts or requests category information, embedding these details into the file-type-specific structural template.

When should I use automated file renaming instead of manual organization?

Automated renaming prevents human error and inconsistency when handling large datasets, imports, or legacy files. Use it before committing code to ensure repository hygiene, during document imports to enforce compliance, or when reorganizing directories—tasks where manual renaming becomes tedious and error-prone.

Does the skill work with images, documents, and markdown files?

The skill supports images, documents, and markdown files with file-type-specific handling. Images receive resolution inference, documents and markdown receive category extraction or prompting, and all file types receive lowercase normalization, hyphenation, special character removal, and version suffixes.

What if automated content analysis can't extract required metadata?

The skill provides interactive guidance, prompting you for missing information like organization, product descriptor, or category when automated analysis is insufficient, ensuring complete compliance without skipping files or requiring manual cleanup afterward.