batch-rename
v1.0.0This skill should be used when the user wants to batch rename multiple files at once. It handles various rename patterns including sequential numbering, find...
⭐ 0· 80·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the delivered code: the Python script implements sequential numbering, find/replace, prefix/suffix, regex, extension filtering, and recursion as advertised. Minor mismatch: SKILL.md demonstrates wildcard ext values like "*.txt", but the script expects either '*' or a bare extension (e.g., 'txt' or '.txt'), so some example usages in the docs are misleading.
Instruction Scope
SKILL.md instructs the agent to 'report what will be renamed before executing' and to confirm scope for recursive operations, but the script provides no explicit dry-run/preview mode or interactive confirmation: it prints counts and then performs renames, printing each change as it happens. This increases the risk of unintended mass changes if the agent runs the script without a manual review step.
Install Mechanism
No install spec and no external packages or network fetches. The script is pure Python using stdlib modules; nothing is written to disk beyond normal file renames performed by the script itself.
Credentials
The skill requests no environment variables, credentials, or config paths — requirements are proportionate to its stated purpose.
Persistence & Privilege
always is false and the skill does not modify other skills or require permanent presence. It performs local filesystem operations only when invoked.
Assessment
This skill appears to implement a legitimate batch-rename tool and does not request credentials or network access. However: 1) Make a backup before running this on important files — the script uses os.rename() and will change files in place. 2) The SKILL.md suggests preview/confirmation but the script has no --dry-run or interactive confirm; ask the author to add a dry-run flag (or manually check file lists) before executing. 3) Use the --ext argument as a bare extension (e.g., --ext jpg or --ext .txt) rather than wildcard patterns like "*.txt" (the examples in the docs are misleading). 4) Test on a small sample directory first to verify the pattern, recursion, and collision behavior. 5) If you want autonomous invocation by an agent, ensure the agent will request explicit user confirmation before running the rename to avoid accidental mass edits.Like a lobster shell, security has layers — review code before you run it.
latestvk97eab1b4n13m86v2f2yyf1fm184jazg
License
MIT-0
Free to use, modify, and redistribute. No attribution required.