digest-writerlisted

Canonical formatter for digests and research reports. Enforces a 5-section structure (TL;DR → What Changed → Why You Care → Detailed Findings → Sources) with the regulated-org lens applied to "Why You Care" and credibility-tier badges on every source. Delegates the actual file write to vault-writer, landing the digest at `vault/digests/{cadence}/YYYY-MM-DD-{skill}.md` (for scheduled agents) or `vault/research/{topic}/YYYY-MM-DD-{slug}.md` (for on-demand research). Every Category 2 scheduled agent and every Category 1 research skill writes through this skill. Use whenever a scheduled agent or research skill is formatting its final output — after claims are extracted and verified, immediately before the vault-writer write.
themarmack/research-bot · ★ 0 · Data & Documents · score 68

Install: claude install-skill themarmack/research-bot

# digest-writer **Path convention**: `vault/` is shorthand for `~/Obsidian/Research-Brain/`; all skills use the `vault/` form. The canonical output formatter for everything that lands in `vault/digests/` or `vault/research/`. Skills hand it raw findings + metadata; it produces a markdown document with the standard 5-section structure and delegates the file write to `vault-writer`. ## Why a separate skill Three reasons it's not just inlined per-skill: 1. **One review surface** — when the user reviews any Monday-morning digest, the layout is identical, so attention goes to content. 2. **One place to audit citations** — every digest passes through the same source-tier badge + accessed-date discipline. Months later, every digest is auditable. 3. **One place to enforce the regulated-org lens** — "Why You Care" framing is centralized. ## When to use - Every Category 2 scheduled agent at end of run. - Every Category 1 on-demand research skill when finalizing output. - Any ad-hoc digest the user wants formatted to the standard. ## When NOT to use - Individual fact / event / decision writes — those go through `vault-writer.write_fact/event/decision` directly. - Quick captures via the `quick-capture` skill — different format, different surface. - `_inbox/` stages — those are pre-curation, no formatting needed. ## Input ```json { "skill": "weekly-intelligence-digest", "destination": "digests" | "research", "cadence": "daily | weekly | biweekly | monthly | quarterly", //