Feishu File Renamer
Security checks across malware telemetry and agentic risk
Overview
The skill’s file-renaming purpose is coherent, but the artifacts show it can rename files in place without the advertised output-directory containment or batch confirmation.
Use this only on backed-up files and trusted file mappings. Before allowing a batch rename, ask the agent to show the exact old and new filenames and confirm manually. Do not rely on --output-dir or the rename log for rollback unless the implementation is fixed.
VirusTotal
VirusTotal findings are pending for this skill version.
Risk analysis
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A triggering message with file mappings could rename multiple local files immediately, which may be surprising or hard to undo if mappings are wrong.
After trigger matching and file-mapping extraction, the handler calls batchRename directly, and restoreFileName performs a real filesystem rename. The supplied code does not require confirmation before batch mutation.
// 执行批量重命名 const result = batchRename(mappings); ... renameSync(hashFile, finalPath);
Add an explicit confirmation step that previews every old and new path, supports dry-run mode, and limits operations to a user-selected directory.
Users may believe files will be written to a separate output folder or easily restored from the log, while the implementation renames originals in place and does not log enough information for reliable rollback.
The user-facing documentation suggests output-directory containment and log-based recovery, but src/index.ts does not use outputDir and the generated log records counts/errors rather than old-to-new rename mappings.
--message-id "om_x100b520xxx" \ --output-dir "/tmp/renamed" ... A: 会生成重命名日志，可根据日志手动恢复。
Either implement outputDir and full old/new-path logging, or clearly warn that renames happen in place and that users should back up files first.