WorkBuddy Daily Check-in Assistant

Problem

WorkBuddy's "Buddy Fuel Station" daily check-in is easy to miss if done manually, while simulating the desktop UI is fragile and usually outside an agent's interface-clicking capabilities. The practical problem is narrower: when the local client is already logged in, read the login state, call the official check-in API to claim credits, and turn duplicate sign-ins, status checks, and network failures into a predictable automation flow.

How It Works

The skill breaks the flow into three API-level steps:
- Credential lookup: it reads workbuddy-desktop.info only to extract accessToken and domain; it does not modify, delete, or exfiltrate tokens.
- Status check: it calls checkin-activity-status first and skips claiming when today_checked_in is true, avoiding unnecessary duplicate requests.
- Credit claim: it calls daily-checkin and treats HTTP 400, code=10001, or "already checked in today" as an idempotent success rather than an error.

The script uses only the Python standard library, outputs sanitized JSON and an exit code, and makes it easy to trigger alerts. Optional notifications support WeCom bot, PushPlus, and Bark; keys remain in a local config file outside the script and skill directory. The default policy is conservative: failures can notify, while success broadcasts are off by default to reduce noise.

Boundaries: this flow targets PC client login state, not the web version; the API domain should come from auth.domain; and an expired token, missing client login, powered-off machine, or absent network must be fixed first.