wow-digest
Purpose
Pull last 24h of newsletters (email) and Telegram channel posts, filter noise,
score survivors for genuine surprise against the user's focus and recent research,
and append 3-7 WOW items to today's daily note.
Workflow
- Run to pull and normalize candidates from all sources
- Run to fetch full content for link-only newsletters (LinkedIn, beehiiv, Substack)
- Run
scripts/salience_filter.py
to drop obvious noise (marketing, payments, greetings)
- Run on filtered candidates to score and select WOW items
- Append selected items to today's daily note under
- Save raw candidates to
.wow-eval/candidates/YYYYMMDD.jsonl
for replay
- Archive processed newsletter emails via GWS
- During eval phase: run to collect human verdicts
Manual run
bash
python3 scripts/ingest.py --days 1 --output /tmp/wow-candidates.jsonl
python3 scripts/enrich.py --input /tmp/wow-candidates.jsonl --output /tmp/wow-enriched.jsonl
python3 scripts/salience_filter.py --input /tmp/wow-enriched.jsonl --output /tmp/wow-filtered.jsonl
python3 scripts/wow_score.py --input /tmp/wow-filtered.jsonl --output /tmp/wow-selected.json
# Then the skill appends to daily note and archives emails
Dry-Run Mode
When the user says
or "preview the digest", run the full pipeline but:
- Do NOT append to daily note
- Do NOT archive emails
- Instead, print the selected items with scores and hooks directly in the conversation
This lets the user preview what would be appended without side effects.
Context Sourcing
The scoring prompt uses three context signals from the vault (
):
- — From , sections , , (stops at ). This tells the scorer what the user cares about right now.
- — From files (last 30 days), parsed from filenames () and frontmatter. Shows what the user has already investigated.
- — From headings (last 7 days), excluding and . Shows recent daily note themes.
If these files don't exist, scoring still works but with degraded personalization.
Dedup
Ingestion deduplicates against the last 7 days of
.wow-eval/candidates/*.jsonl
using SHA-256 hashes of
(case-insensitive). Same article shared to multiple channels or re-sent in a newsletter won't appear twice. Pass
to
to skip.
Config
Edit
to add/remove email patterns or Telegram channels.
Edit
to tune the scoring prompt.
Output Format
After scoring, append to today's daily note (
) ABOVE the
separator, below any existing content:
markdown
## Reading
- **[Title]** (Source) — hook explaining WHY it's surprising
- **[Title]** (Source) — hook
...
_WOW digest · N candidates → M selected · YYYY-MM-DD_
CRITICAL: Always run
to get today's date. Never assume.
If
already exists in the daily note, append items to it rather than creating a duplicate section.
Archive
After appending to daily note, archive processed newsletter emails:
- Collect all values from email candidates
- Run GWS batchModify to remove INBOX label
bash
gws gmail users messages batchModify \
--params '{"userId":"me"}' \
--json '{"ids":["ID1","ID2",...],"removeLabelIds":["INBOX"]}'
Eval Mode (first 2 weeks)
During eval phase, do NOT auto-archive. Instead:
- Run ingest + scoring as normal
- Present the selected items to the user with FULL CONTENT, not just titles. For each item show:
- Title + source
- The snippet (first 300-500 chars of actual content)
- The LLM's hook and challenged_assumption
- WOW score breakdown (relevance, surprise, bridge_value, predictability)
- Show all items in a single text block first so the user can read the content
- Then ask via AskUserQuestion: "Was this actually WOW?" with options: wow / meh / noise / already_knew
- Record feedback via
- Show current feedback stats
- Only archive after user confirms
CRITICAL: The user CANNOT judge WOW from titles alone. Always show the snippet content.
If the snippet is empty or too short, fetch the full email body via GWS before presenting.
To check if eval mode is active:
- If has fewer than 50 entries → eval mode
- If 50+ entries → auto mode (archive without asking)