Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Batch File Renamer
v1.0.0Batch rename files with powerful patterns, regex support, and preview functionality. Use when organizing large numbers of files, standardizing naming convent...
⭐ 0· 290·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
The name and description (batch rename, regex, preview) match the SKILL.md content. All code examples and guidance relate directly to renaming, numbering, timestamps, and preview/dry-run behavior. No unrelated binaries, credentials, or config paths are requested.
Instruction Scope
The instructions contain concrete Python code that performs local filesystem operations (os.listdir, os.rename) — which is appropriate for a renamer. The SKILL.md explicitly recommends preview and backups and provides a dry-run example. Note: the examples do perform destructive local changes when dry_run=False and do not include collision checks, permission handling, or exception handling; that is a correctness/safety concern but not scope creep.
Install Mechanism
There is no install spec and no code files beyond SKILL.md, so nothing is written to disk by an installer. This low-install surface is proportionate for an instruction-only utility.
Credentials
The skill declares no required environment variables, credentials, or config paths and the instructions do not reference external secrets or unrelated environment state. This is proportionate to the stated functionality.
Persistence & Privilege
The skill is not always-enabled and does not request elevated or persistent system presence. It does not modify other skills or system-wide agent settings.
Assessment
This skill is coherent and contains useful local Python examples, but they perform destructive file operations: always run the preview/dry-run first, back up important data, and test patterns on a small sample. Be aware the examples lack collision detection, exception handling, checks for symlinks, and permission/error handling — consider adding safeguards (unique-name checks, try/except around os.rename, handling name collisions) before running on large directories. If you prefer an installable tool, look for a trusted source or packaged implementation rather than copy-pasting unvetted code from an unknown source.Like a lobster shell, security has layers — review code before you run it.
latestvk9736zwfafbxg0tqwmmpcbjc7n8268vg
License
MIT-0
Free to use, modify, and redistribute. No attribution required.