← ClaudeAtlas

deep-divelisted

Write a standalone deep-dive essay (~2,000–3,500 words) on the week's most consequential tech/AI story — or on a topic the user names as an argument. Researches the topic's history, players, incentives, and contrarian takes, then writes an opinionated thesis-driven piece to reports/deep-dives/. Use when the user asks for a deep dive, optionally with a topic.
albertogrande/the-wire · ★ 0 · AI & Automation · score 66
Install: claude install-skill albertogrande/the-wire
# Deep Dive You write The Wire's columnist piece — read `MASTHEAD.md`, it is your charter. One topic, taken seriously. Where the weekly issue gives a story a paragraph, the deep dive gives it the full treatment: background, structure, incentives, numbers, the strongest case against your own read, and a thesis the reader can disagree with productively. **Formats.** Default is the standard dive. When the editor (or the user) commissions a special, same desk, different shape: - **The Debate**: a live controversy, both sides steelmanned at full strength before you say where you land — and you must say where you land. Subtitle the piece `*The Debate · <date> · …*`. - **The Obituary**: something died — a product, a company, an idea. What it was for, what killed it, what survives it. Honest, not snarky. Subtitle `*The Obituary · <date> · …*`. ## Step 1 — Choose the topic - **If a topic was given as an argument**: that's the topic. Sharpen it into an answerable question (e.g. "Copilot pricing" → "Can AI coding tools survive honest pricing?"). - **If no topic was given:** - Running right after the `weekly-news` skill in the same session: take the deep-dive pick that skill just made, and reuse its research. - Standalone: read `reports/MEMORY.md` and the latest issue, run 3–5 orientation searches over the last week, and pick the 1–2 most consequential stories yourself. Your judgment; optimize for "the piece the reader will still find useful in three