Local File Processor

Process local files with batch rename, format conversion, organization by date/type/metadata, duplicate detection, and metadata read/write/removal.

This skill appears to do what it says (batch renames, conversions, metadata edits, duplicate detection) but there are important inconsistencies and risks to consider before installing or running it: - Inconsistency: The registry lists no required binaries or install steps, yet the SKILL.md requires exiftool, ImageMagick, ffmpeg and an executable at ~/.openclaw/workspace/skills/local-file-processor/local-file-processor. Confirm where that executable comes from before making anything executable. - Verify before running: Do not run chmod or execute any binary placed in the workspace unless you have inspected its source. If the local-file-processor binary is provided separately, review its contents (source or vendor-signed release) first. - Test safely: Use --dry-run and operate on a copy/test directory before running destructive actions. Avoid --force or --action delete without backups. - Platform note: The install instructions use brew (macOS/Homebrew); if you use Linux/Windows ensure you install equivalent trusted packages (exiftool, imagemagick, ffmpeg) from your distro or official sources. - If you need assurance: Ask the publisher for a provenance link (source repo or release URL) or a proper install spec that places the executable from a trusted host. Without that, treat the skill as untrusted code that will operate on your local files. If you want, I can: (a) check whether the workspace executable already exists on your system (tell me the path contents), (b) suggest safe test commands to run with --dry-run, or (c) draft questions to ask the skill owner requesting a signed release or source repository.

Type: OpenClaw Skill Name: openclaw-skill-local-file-processor Version: 1.0.0 The skill documentation (SKILL.md) describes a tool with high-risk capabilities, specifically broad file system access and destructive operations such as file deletion (via the 'duplicates' command). While these actions are aligned with the stated purpose of a file processor and include safety mechanisms like dry-run modes and path sanitization, the prompt's criteria classify such risky capabilities as suspicious even when plausibly needed. Furthermore, the actual implementation script ('local-file-processor') referenced in the installation instructions is missing from the bundle, making it impossible to verify the safety of the underlying code logic.