Skreenshot
ReviewAudited by ClawScan on May 1, 2026.
Overview
This looks like a coherent screenshot-management skill, but using its workflows can move or rename local screenshots, store OCR text, and optionally automate or upload screenshots if the user enables those features.
Before installing or using it, be aware that the main risks are normal for this kind of tool: it can bulk move or rename screenshot files, create a searchable text index of screenshot contents, and optionally set up recurring cleanup or cloud sharing. Use dry-run mode first, keep backups of important screenshots, avoid cloud upload for sensitive captures, and review any missing or separately downloaded helper script before running it.
Findings (5)
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.
Screenshots may be renamed or moved from their original locations, which could break references or make files harder to find.
The archive script moves screenshot files from the Desktop into dated archive folders when run; this is purpose-aligned but modifies local user files by default unless `--dry-run` is used.
shutil.move(filepath, dest_path)
Use `--dry-run` first, confirm the source and destination folders, and back up important screenshots before bulk operations.
Sensitive text that was only visible inside images can become searchable plain text on disk.
The OCR indexing workflow persists extracted text from screenshots into a local index file; screenshots can contain receipts, account details, error messages, or other private text.
textsnip -i "$f" >> ~/Pictures/Screenshots/ocr-index.txt
Store the OCR index in a protected location, exclude sensitive screenshots, and delete or regenerate the index when it is no longer needed.
If enabled, screenshots may be uploaded to a cloud service and accessible through generated links.
The CleanShot X workflow documents optional external cloud upload and shareable links for screenshots, which can move screenshot data outside the local machine.
Auto-upload to cloud (optional, generates shareable links)
Only enable auto-upload for screenshots you are comfortable sharing, review the cloud provider and link permissions, and avoid it for sensitive captures.
After setup, screenshots may be moved automatically without a fresh confirmation each time.
The reference suggests an optional cron job that would run the archive script weekly; it is disclosed and user-installed, but it creates ongoing file-moving automation.
0 9 * * 0 cd ~/Documents/Skreenshot && python scripts/archive_old_screenshots.py --days 30
Install persistent automation only if desired, document it, and remove the cron/Hazel rule if you no longer want automatic cleanup.
A user may look for or run an unreviewed script to complete the documented OCR workflow.
SKILL.md references an OCR search helper that is not included in the provided file manifest, so any separately obtained replacement would be outside the reviewed artifacts.
### `scripts/ocr_search.py` Search all screenshots by text content.
Use only included files unless you separately review any missing helper script before running it.