← Back to Skills Marketplace
terrycarter1985

GOG Cleanup

by terrycarter1985 · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ Security Clean
47
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install gog-cleanup
Description
Find GOG games installed but not played for 30+ days, email the list, and add Apple Reminders to consider uninstalling. One-command cleanup sweep for your ba...
README (SKILL.md)

GOG Cleanup

Automated stale-game cleanup sweep: finds installed GOG games you haven't played in 30+ days, emails you a digest, and creates Apple Reminders so you can decide whether to uninstall.

What It Does

  1. Reads your GOG library from config/gog_library.json
  2. Filters for installed games whose last_played is 30+ days ago (or never played)
  3. Sends a formatted digest email via himalaya
  4. Adds each stale game to the Gaming list in Apple Reminders via remindctl

Prerequisites

Tool Purpose Install
jq JSON parsing brew install jq
himalaya Send email brew install himalaya
remindctl Apple Reminders brew install steipete/tap/remindctl
  • Himalaya must be configured with a personal account (see config/himalaya.toml)
  • Apple Reminders must have a Gaming list (auto-created if missing)

Usage

Run the full sweep (email + reminders)

bash scripts/gog-cleanup.sh

Email only (skip reminders)

SKIP_REMINDERS=1 bash scripts/gog-cleanup.sh

Reminders only (skip email)

SKIP_EMAIL=1 bash scripts/gog-cleanup.sh

Custom stale threshold (default 30 days)

STALE_DAYS=60 bash scripts/gog-cleanup.sh

Custom recipient (defaults to himalaya personal account email)

EMAIL_TO="[email protected]" bash scripts/gog-cleanup.sh

Configuration

The script reads from workspace config/:

File Purpose
config/gog_library.json GOG game library with install status & last_played timestamps
config/himalaya.toml Himalaya email account config (uses personal account)
config/reminders_lists.json Reminders list structure (Gaming list)

Output

  • Email: HTML-formatted digest sent to your personal inbox
  • Reminders: One reminder per stale game in the Gaming list, prefixed with "🧹 Consider uninstalling:"
  • Console: Summary of games found and actions taken

Scheduling

To run weekly via cron:

# Add to crontab for Monday 9 AM
0 9 * * 1 /path/to/scripts/gog-cleanup.sh >> /tmp/gog-cleanup.log 2>&1

Or use OpenClaw's cron tool for agent-managed scheduling.

Notes

  • Games with last_played: null (never played) are always included
  • Uninstalled games are always skipped regardless of last_played
  • The script is idempotent — re-running won't duplicate reminders (existing reminders with the same title are skipped)
Usage Guidance
Before installing, make sure you are comfortable letting this skill read your GOG library config, use your Himalaya personal email account, and create Apple Reminders. Verify the email recipient and reminders list, use SKIP_EMAIL=1 or SKIP_REMINDERS=1 if needed, and treat the owner metadata mismatch as a reason to review the source before scheduling recurring runs.
Capability Analysis
Type: OpenClaw Skill Name: gog-cleanup Version: 1.0.0 The gog-cleanup skill is a utility for managing a GOG game library by identifying games not played within a specific timeframe. It reads from local configuration files (config/gog_library.json, config/himalaya.toml) and uses standard CLI tools (jq, himalaya, remindctl) to send email digests and create Apple Reminders. The script logic in scripts/gog-cleanup.sh is transparent, follows the stated purpose in SKILL.md, and contains no indicators of malicious intent, data exfiltration, or unauthorized execution.
Capability Assessment
Purpose & Capability
The implementation is coherent with the stated purpose: it reads a GOG library file, identifies stale installed games, sends a digest, and creates reminders rather than uninstalling anything. The noteworthy part is that it performs account-backed actions through email and Apple Reminders.
Instruction Scope
The run instructions are explicit and include skip flags for email and reminders. Optional cron scheduling is documented as user-directed, not automatic.
Install Mechanism
There is no install spec or remote installer, but the skill depends on user-installed CLI tools. The supplied package metadata also has a provenance inconsistency between the registry owner and _meta.json owner.
Credentials
The script reads workspace config/gog_library.json and config/himalaya.toml, then emails game names, last-played dates, and install paths. That is purpose-aligned but worth noticing because local paths can reveal personal filesystem details.
Persistence & Privilege
The skill creates persistent Apple Reminders and documents optional weekly scheduling. These are disclosed and scoped to the cleanup workflow.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install gog-cleanup
  3. After installation, invoke the skill by name or use /gog-cleanup
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release: stale game detection, email digest, Apple Reminders integration
Metadata
Slug gog-cleanup
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is GOG Cleanup?

Find GOG games installed but not played for 30+ days, email the list, and add Apple Reminders to consider uninstalling. One-command cleanup sweep for your ba... It is an AI Agent Skill for Claude Code / OpenClaw, with 47 downloads so far.

How do I install GOG Cleanup?

Run "/install gog-cleanup" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is GOG Cleanup free?

Yes, GOG Cleanup is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does GOG Cleanup support?

GOG Cleanup is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created GOG Cleanup?

It is built and maintained by terrycarter1985 (@terrycarter1985); the current version is v1.0.0.

💬 Comments