GOG Stale Games Cleanup
PassAudited by ClawScan on May 11, 2026.
Overview
The skill appears to do what it says, but running it will use your configured email and Apple Reminders accounts and can be scheduled to repeat.
Before installing or running, review scripts/sweep.sh, run it once with --dry-run, confirm the GOG library path, himalaya email account, recipient, and Reminders list, and only enable the cron example if you want recurring automated reports.
Findings (4)
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.
Running the script normally can add multiple reminders to the selected Reminders list.
The script creates an Apple Reminders list if needed and adds one reminder per stale game. This is disclosed and purpose-aligned, but it mutates user data.
remindctl list "$REMINDERS_LIST" --create ... remindctl add --title "$TITLE" --list "$REMINDERS_LIST"
Run with --dry-run first, confirm the target reminders list, and only run normally when you are comfortable with the reminders it will create.
The skill can use your configured email account to send a report and your Reminders authorization to create tasks.
The skill relies on existing email-sending and Apple Reminders authorization. These privileges are expected for the workflow, but they are account-level capabilities.
- himalaya configured for SMTP ... - remindctl installed and authorized (macOS)
Verify the himalaya account selected by --email and ensure remindctl is authorized only for the account/list you intend to use.
Your stale game list, last-played dates, and install paths may leave the local machine in an email message.
The email report includes local game metadata such as install paths and is sent through the configured himalaya email provider.
PATH_=$(echo "$line" | jq -r '.install_path // "N/A"') ... cat <<HEREDOC | himalaya --account "$EMAIL_ACCOUNT" template send
Confirm the recipient and email account before sending, and avoid using a library file containing paths or metadata you do not want emailed.
If you add the cron job, the skill may keep sending reports and adding reminders on schedule.
The documentation includes optional cron integration for recurring monthly runs. This is disclosed, but it creates ongoing automated email/reminder activity if enabled.
openclaw cron add --name "gog-stale-sweep" ... --command "bash /path/to/scripts/sweep.sh --library /path/to/gog_library.json"
Only enable cron if you want recurring sweeps, and remember to remove or disable the scheduled job when it is no longer needed.