bluesky-engagement

# Bluesky Engagement Automation for Bluesky reply tracking. The monitor reads; a human (or a queue consumer with explicit approval) writes. ## Why this exists Bluesky is a Zernio-connected channel for publishing, but Zernio does not expose an inbound/comments API. Engagement has to run directly against the open AT Protocol. This skill owns that path so future sessions don't re-ask for credentials or re-derive the PDS routing. ## Credentials Both are set in `.env` at repo root (git-ignored): | Var | Source | Notes | |---|---|---| | `BLUESKY_HANDLE` | bsky profile URL | e.g. `iganapolsky.bsky.social` | | `BLUESKY_APP_PASSWORD` | <https://bsky.app/settings/app-passwords> | Scoped, revocable. Never use the account login password. | **Rotation**: revoke the old app password at the settings URL above, generate a new one named `thumbgate-replies`, and replace the value on the `BLUESKY_APP_PASSWORD=` line of `.env`. No other files need updating. ## Architecture ``` launchd (com.thumbgate.bluesky-reply-monitor) └─ every 900s ─> node scripts/social-reply-monitor-bluesky.js ├─ com.atproto.server.createSession (bsky.social) │ └─ reads didDoc to find user's real PDS ├─ app.bsky.notification.listNotifications (user's PDS) ├─ filter reason in {reply, mention, quote} ├─ dedupe against .thumbgate/reply-monitor-state.json ├─ generateReply() — shared with Reddit/X ...