executive-summary-writerlisted

Turn an existing research note into a 1-page executive summary personalized to a named audience (e.g. `ciso`, `vp-eng`, `ceo`, or `default`). **Invoke ONLY when the user explicitly asks for an exec summary** — never as a post-write step in a Category 1 researcher flow. Loads audience preferences — length, voice, format, emphasize/avoid lists, special interests, section toggles — from `~/Obsidian/Research-Brain/_config/exec-preferences.md`. Writes the summary to `vault/insights/YYYY-MM-DD-exec-summary-{audience}-{slug}.md` via `vault-writer.write_insight`, then composes with `email-sender.prompt_then_send` to optionally deliver via Gmail. The 8-section structure (BLUF, Why This Matters Now, Key Findings, Implications, Recommended Action, Risks, Next Decision Point, Sources) is the spine — three sections are mandatory; the other five are toggleable per audience. Stop-and-reports on missing source note, missing prefs file, missing `## Default` section, or unknown audience. Use when the user asks to summarize a r
themarmack/research-bot · ★ 0 · AI & Automation · score 68

Install: claude install-skill themarmack/research-bot

# executive-summary-writer The skill that produces 1-page executive summaries from research notes. Tunes length, voice, format, and section emphasis per named audience by reading a Markdown preferences doc the user maintains in Obsidian. First skill in the toolkit to do per-audience personalization — every exec read of a research finding can be calibrated to that exec's actual taste. ## When to use **Only on explicit user request.** Triggers include: - `"Summarize that research for the CISO."` - `"Give me an exec summary of the latest Copilot research."` - `"Produce a 1-page version of <note> for VP Eng."` - `"I need CISO + VP Eng + Default versions of this for sharing."` Research notes do NOT auto-convert into exec summaries when they're written. The Category 1 researchers (`copilot-deep-dive`, `sdlc-best-practice`, etc.) finish at the research-note write — they do NOT chain into this skill. The user decides which research findings warrant an exec pass. ## When NOT to use - **Auto-triggered after a `vault-writer.write_research` succeeds.** Even if the research seems exec-worthy, do not auto-invoke. Wait for the user's explicit ask. - Source content is a digest (`vault/digests/{cadence}/...`), not research — digests are already summarized; this skill doesn't second-summarize. If you really want an exec take on a digest, copy the digest body to a `research/` note first. - Decision memos, ADRs, RFCs — those have their own writer skills (`decision-memo-writer`, `adr-write