peoplegraph-daily-reconnect

name: peoplegraph-daily-reconnect description: Run the daily reconnect curation loop — push re-engage candidates (strong relationships gone dormant) to the swipe web app, write a daily-note link, and apply the human's swipe decisions back into the contact graph via `peoplegraph feedback`.

PeopleGraph Daily Reconnect

Use this skill when Botwick/OpenClaw is asked to surface who the owner should reconnect with, run the daily reconnect job, or apply reconnect swipes.

The human-in-the-loop surface is a names-only Tinder-style swipe web app (apps/reconnect-web, deployed on Cloudflare). Each day Botwick pushes the top re-engage candidates to it and drops a one-line link in the daily note; the owner swipes; Botwick pulls the decisions and feeds them back into scoring. This replaces the earlier Telegram-brief approach (see the bottom of this file).

Architecture

Botwick machine (source of truth)              Cloudflare                  owner's phone
  peoplegraph reconnect  ──push names + opaque ids──►  Worker + D1  ──►  swipe UI (names only)
  peoplegraph feedback   ◄──pull swipe decisions─────                ◄──  right / left / 🗑

Privacy: emails never leave the source-of-truth machine. The bridge assigns each candidate an opaque id and keeps the id → email map locally; D1 only ever stores names + display fields.

Requirements

peoplegraph CLI 0.3.4 or newer (has reconnect and feedback).
PEOPLEGRAPH_CACHE → the source-of-truth contact-index.json (the bridge needs local writes, so run it on this machine, not over --remote).
The reconnect web app deployed (see apps/reconnect-web/README.md). Current deployment: https://reconnect-web.kayarjones901.workers.dev.
Bridge env (default ~/.peoplegraph/reconnect-web.env):
- RECONNECT_WEB_URL / RECONNECT_PUBLIC_URL — the Worker URL
- RECONNECT_SYNC_TOKEN — matches the Worker's SYNC_TOKEN secret
- PEOPLEGRAPH_CACHE, PEOPLEGRAPH_BIN, RECONNECT_LIMIT (default 5), RECONNECT_STATE
- optional RECONNECT_DAILY_NOTE — today's daily note to append the link to

The daily job (preferred path: the bridge)

The bridge script scripts/peoplegraph-reconnect-web.mjs does the whole loop. Normally you just run it:

source ~/.peoplegraph/reconnect-web.env
node scripts/peoplegraph-reconnect-web.mjs run     # = pull (apply yesterday's swipes) then push (post today's)

push — runs peoplegraph reconnect --limit N, assigns opaque ids (kept in RECONNECT_STATE), POSTs names to /api/sync, and appends a single click-through line to the daily note.
pull — GETs /api/decisions, maps each opaque id back to its email locally, applies it with peoplegraph feedback, and acks.

Cron it once a day on the machine with the cache:

0 8 * * *  source ~/.peoplegraph/reconnect-web.env && node /path/to/obsidian-gmail-crm/scripts/peoplegraph-reconnect-web.mjs run

Swipe semantics → feedback

The web app records one of three actions; the bridge applies each via peoplegraph feedback:

Swipe	action	`peoplegraph feedback` effect
right / ♥	`boost`	keep + raise the contact's effective score
left / ✕	`suppress`	hide from future reconnect suggestions + lower score
🗑 (confirm)	`delete`	remove the contact from the cache + add to `reconnect-blocklist.json`

peoplegraph --cache "$PEOPLEGRAPH_CACHE" feedback --email <email> --action boost|suppress|delete

reconnect honors this overlay (reconnect-feedback.json) on its next run: suppressed/deleted are excluded, boosted rank higher. This is what makes the swipes shape future suggestions instead of being a one-time filter.

Core rules

Suggestions come only from the re-engage quadrant (strong + dormant). Don't invent candidates or pull from other quadrants.
Keep it small — default 5/day. This is a nudge, not a CRM dump.
The nudge string from reconnect is the human-facing reason; you may rephrase it warmly but never fabricate facts (last-contact timing, email counts, role) beyond what the CLI returns.
feedback is a local write — it only runs on the source-of-truth machine, never over --remote.
If nothing is in re-engage after filtering, push nothing and skip the daily-note line. Don't post an empty batch every morning.

Doing it by hand (no bridge)

If asked to run a step manually or the bridge isn't available:

# see today's candidates
peoplegraph --cache "$PEOPLEGRAPH_CACHE" reconnect --limit 5

# apply a decision the owner tells you in chat ("keep harper", "suppress sri", "delete dr goldberg")
peoplegraph --cache "$PEOPLEGRAPH_CACHE" feedback --email harper@2389.ai --action boost

The owner can also act conversationally: "who should I reconnect with?" → run reconnect; "keep / suppress / delete " → resolve the name to an email (peoplegraph find-person) then feedback.

Failure handling

If peoplegraph exits with ok: false, surface error.kind + error.message; don't retry blindly.
If PEOPLEGRAPH_CACHE is unset, ask the operator to configure it; don't guess a path.
If the Worker is unreachable on pull, leave decisions un-acked so they're retried next run; on push, just skip — no candidates is safe.

Deprecated: Telegram brief

An earlier version of this skill delivered the daily list as a Telegram message with inline buttons (modeled on skills/peoplegraph-telegram-merge-review). That's superseded by the web swipe app. If a Telegram-only delivery is ever needed again, the same reconnect + feedback commands back it — send the brief, map pgr:<email>:<action> callbacks to peoplegraph feedback, and skip the web push/pull.

name: peoplegraph-daily-reconnect description: Run the daily reconnect curation loop — push re-engage candidates (strong relationships gone dormant) to the swipe web app, write a daily-note link, and apply the human's swipe decisions back into the contact graph via peoplegraph feedback.