x-bookmark-triage

Turns X/Twitter bookmarks into searchable, tiered knowledge cards posted to a Discord channel. Captures, scores, and optionally unbookmarks — so your bookmark list stays clean and your knowledge base grows automatically.

Works standalone — no OpenClaw required for core triage. OpenClaw integration is optional (adds scheduled polling via cron and bus events). See references/adapting.md for standalone setup.

Architecture

CODEBLOCK0

Prerequisites

Quick Start (8-step MVP)

1. 1. Get credentials:

1. 2. Run auth flow: node scripts/x-oauth2-authorize.js → saves refresh token to INLINECODE9

1. 3. Set env vars: Export X_OAUTH2_CLIENT_ID, X_OAUTH2_CLIENT_SECRET, X_OAUTH2_REFRESH_TOKEN, DISCORD_BOT_TOKEN, INLINECODE14

1. 4. Set your Discord channel: Set env var KNOWLEDGE_INTAKE_CHANNEL_ID=<your-channel-id> (preferred), OR edit scripts/triage-url.js line 19 to hardcode it.

1. 5. Test triage: INLINECODE17

1. 6. Check Discord: You should see a formatted card in your channel

1. 7. Verify dedup: Run the command again — should skip (already seen)

1. 8. Done: Your first card is live. Next: set up scheduling (see Steps 3–4 below)

Setup

1. OAuth 2.0 Authorization

CODEBLOCK1

Store credentials in your gateway plist (or env):
CODEBLOCK2

The scripts also fall back to reading refresh_token from a secrets JSON file at runtime. See references/oauth-setup.md for full details.

2. Configure Target Channel

Set CHANNEL_ID at the top of scripts/triage-url.js to your Discord channel ID.

3. Register the Scheduled Poll (Optional — for automated polling)

CODEBLOCK3

Alternatively, drain all bookmarks one-time:
CODEBLOCK4

4. Register the launchd Poller (Optional — for automated polling)

Note: scripts/ai.watson.knowledge-intake-poll.plist is a template. Customize it first:

1. 1. Edit the file to replace /PATH/TO/skills/x-bookmark-triage/scripts/poll-channel.js with the actual path
2. Replace YOUR_BOT_TOKEN, YOUR_ANTHROPIC_KEY, YOUR_CHANNEL_ID, /PATH/TO/workspace with real values
3. Copy to LaunchAgents and load:

CODEBLOCK5

Or use OpenClaw to manage it — see references/cron-setup.md.

Scripts

triage-url.js — Core triage engine

CODEBLOCK6

• - Fetches content (fxtwitter for tweets, markdown.new for web pages)
• Triages with Claude Haiku → produces tier, freshness, topic, tags, proposed action
• Posts formatted card to Discord
• Marks URL as seen in INLINECODE30
• Exits 0 on success or "already seen"; exits 1 on hard failure

bookmark-poll.js — Scheduled sweep (latest 20)

CODEBLOCK7

• - Refreshes OAuth token, fetches 20 most recent bookmarks
• Calls triage-url.js for each unseen URL
• Unbookmarks after successful triage (+ already-seen items)
• Emits bookmark_sweep_complete to bus

backlog-sweep.js — One-time full drain

CODEBLOCK8

• - Pages through ALL bookmarks (up to API limit)
• INLINECODE35: list URLs without triaging or unbookmarking
• INLINECODE36: stop after N bookmarks
• INLINECODE37: seconds between triage calls (default: 3)
• Emits backlog_sweep_complete to bus

poll-channel.js — Discord drop handler

CODEBLOCK9

• - Polls a Discord channel every 2 min for new messages
• Extracts URLs from message content
• Calls triage-url.js for each unseen URL
• Intended to run as a persistent launchd service

Card Format

Tier 3–10 (work-relevant):
CODEBLOCK10

Tier 1–2 (off-topic/personal):
CODEBLOCK11

Tier Guide

Freshness Values

• - evergreen 🌿 — timeless, still valid in 2 years
• INLINECODE42 📅 — relevant but will age (benchmarks, roadmaps)
• INLINECODE43 ⏰ — time-sensitive, likely already stale

Topic Values (one per card)

INLINECODE44 · #veefriends · #product · #revenue · #openclaw · #personal · INLINECODE50

Token / Cost Estimate

Each triage call: ~3.5K avg input + 300 output tokens (claude-haiku-4-5)

• - Per URL: ~$0.003
• 20 new bookmarks/run: ~$0.06
• 2 runs/day at typical throughput: ~$3.60/month
• Full 1000-bookmark backlog: ~$3.50

Seen-URL Deduplication

URLs are tracked in data/knowledge-intake-seen.json. Cap: 2,000 entries (FIFO). Bookmarks already in the seen cache are still unbookmarked — they were captured in a prior run.

Refresh Token Rotation

X rotates refresh tokens on each use. The scripts:

1. 1. Detect rotation (new token in response)
2. Save new token to INLINECODE52
3. Log a warning to update the plist env var

Watson auto-detects and updates the secrets file. For non-Watson deployments, monitor for this warning and update X_OAUTH2_REFRESH_TOKEN in your env.

References

• - references/oauth-setup.md — Full OAuth 2.0 setup walkthrough
• INLINECODE55 — OpenClaw cron registration for scheduled polls
• INLINECODE56 — How to adapt channel IDs, topics, triage prompt for your workspace