Batch Rename

v1.0.0

Rename image datasets and annotations with custom patterns, prefixes, suffixes, and sequential numbering, including preview and undo support.

0· 303·2 current·2 all-time
byMingo_318@mingo-318
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
Name/description match the provided code and SKILL.md: the Python script implements batch rename of images and (optionally) annotation files with preview and overwrite options. No unrelated binaries, env vars, or network access are requested.
!
Instruction Scope
SKILL.md advertises 'Undo Support' and a restore workflow. The script includes a restore command that reads .rename_backup.json, but the rename implementation never writes that backup file — so 'undo' is not actually implemented. Additionally, SKILL.md documents pattern placeholders like {original} and {date}, but the script first calls pattern.format(...) with a positional numeric argument then applies string replacements for {original}/{date}; patterns lacking a numeric placeholder (e.g., using only {original}) will raise a formatting error. These are functional inconsistencies between the instructions and code.
Install Mechanism
Instruction-only skill with an included Python script; no install spec or downloads. No files are fetched from external URLs and nothing is written to system locations by an installer.
Credentials
No environment variables, credentials, or config paths are requested. The script performs only local filesystem operations in the provided directories.
Persistence & Privilege
The skill does not request permanent presence (always is false) and does not modify other skills or global agent settings. It only operates on user-supplied directories when invoked.
What to consider before installing
This skill appears to implement local batch renaming and doesn't request secrets or network access, but there are important mismatches you should address before using it on real data: (1) The README promises undo support, but the rename command never creates the .rename_backup.json file the restore command would need — so you cannot rely on the built-in undo. (2) Patterns are applied with pattern.format(positional_number) then string replacement for {original}/{date}; if your pattern doesn't include the numeric placeholder (e.g., you use only {original}) the script will likely raise a formatting error. Practical steps: (a) run the script in --preview mode and test on a small copy of your dataset first; (b) keep manual backups (copy the directory) before applying changes; (c) if you need true undo, modify the rename command to write a .rename_backup.json mapping before renaming (or ask the author to fix it); (d) stick to patterns like 'img_{:04d}{original}' that include the numeric placeholder, or review/adjust the code to support named placeholders safely. If the author updates the code to reliably write backups and to clearly document supported pattern syntax, the inconsistencies would be resolved and my assessment would become benign.

Like a lobster shell, security has layers — review code before you run it.

latestvk9789epw5c03p25b22tj5tznh182bqt2

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments