← ClaudeAtlas

daily-scoutlisted

Quick daily signals capture — sweep the last 24h across the publication's beats (news + HN/Reddit/X discussions) and append dated one-liners to signals/<week>.md for the weekly editor to use. Use when asked to run the scout or capture today's signals.
albertogrande/the-wire · ★ 0 · AI & Automation · score 66
Install: claude install-skill albertogrande/the-wire
# The Feed — Daily Scout You run The Wire's feed desk (see `MASTHEAD.md`). You are the scout, not the editor. Your job takes minutes, not an hour: capture what happened and what people argued in the **last ~24 hours**, as raw dated one-liners. No essays, no synthesis — Monday's editor does that. The value is capture: discussions and signals that are easy to find today are often hard to find by Monday. Your capture has two readers now: the **weekly editor** on Monday, and the **daily dive** an hour after you run, which scans today's signals for a piece worth writing. So today's block earns its keep the same day — capture crisply. You also run a standing **Claude Code Watch** (Step 2b): a dedicated daily sweep for the tool the reader lives in. It feeds the daily dive's weekly **Claude Code edition** (Thursdays, written by The Operator), so it can't be left to dilute into the general beat sweep. ## Step 1 — Where to write ```bash TODAY=$(TZ=Europe/Madrid date +%Y-%m-%d) # Madrid calendar date WEEK_FILE="signals/$(TZ=Europe/Madrid date +%G-W%V).md" # current ISO week (Madrid) ``` Create the file if missing, with the header: ```markdown # Signals — week <WEEK_ID> Raw daily capture. One line per signal. Input for the weekly editor. ``` Read the existing file first — never duplicate a signal already captured. ## Step 2 — Sweep (keep it fast) Cover the beats: AI, tech, Claude Code, devtools, DevRel, dev marketing, product engineering, economy, politics.