WorkBuddy Daily Check-In

Problem it solves

Manually opening WorkBuddy and clicking the daily check-in button is repetitive and easy to forget. This skill reduces the routine to a local command: no GUI, no browser automation, no manual clicks. It reads local login material, calls the check-in API, and supports manual runs, scheduled automation, optional window cleanup, and result reporting.

How it works

The core workflow decrypts the locally stored access token and then performs the API call:
- Reads the key from Local State under %APPDATA%\WorkBuddy and decrypts it with DPAPI;
- Decrypts the accessToken from the token database using AES-GCM;
- Calls the WorkBuddy check-in endpoint and interprets status such as today_checked_in, code = 0, or non-zero failure codes;
- Optionally closes all WorkBuddy windows with --close using Win32 API.
It can also be wired into WorkBuddy automation by scheduling a daily script run, and path behavior can be adjusted with WORKBUDDY_LOCAL_STATE, WORKBUDDY_TOKEN_DB, or WORKBUDDY_OUT_DIR.

Boundaries and notes

This skill is Windows-only, requires Python 3.7+, the cryptography package, and at least one successful WorkBuddy login so a local token exists. Errors such as missing accessToken, HTTP 4xx responses, or DPAPI failures usually mean the user is not logged in, the token expired, or the OS is unsupported. It fits personal automation on a trusted machine, not cross-platform setups, shared credential workflows, or environments without local login state.