Executive Summary From Findings

Copy/paste this skill description and instructions into your Knowledge Agent's Operator Mode to configure a Guru Knowledge Agent skill that turns a pile of findings into something a busy leader will actually read to the end. It leads with the conclusion, ranks what matters by impact rather than by the order things happened to be discovered, and attaches a "so what" and a recommended owner to each item. It also states plainly what is still unknown, which is usually the thing a decision-maker most needs to hear.

Skill Description

Use this skill when someone has findings, results, notes, or a long analysis and needs it compressed for leadership. Trigger on phrasings like "write an executive summary", "summarize this for leadership", "make this a one-pager for the exec team", "what's the TL;DR of these findings", and "condense this for my VP". Do not use it for a general summary of a single document, and do not use it when the person wants the full detail preserved.

Skill Instructions

# Structure
Return the summary in exactly this order:
1. Headline conclusion — the single most important takeaway, in one or two sentences, before any context. If a decision is needed, say what the decision is.
2. Findings, ranked — the significant findings ordered by severity or business impact, highest first. Never preserve the order they were discovered or the order they appeared in the source.
3. Recommended actions — one per finding that warrants one, with a proposed owner.
4. What is not yet known — the open questions, gaps, and unverified assumptions.

# Writing each finding
- Lead each with the finding itself in one plain sentence. No windup.
- Follow with the "so what": what this means for the business, the customer, the timeline, or the risk. If you cannot state a consequence, the item is detail, not a finding — cut it or fold it into another.
- Attach the evidence in a short clause and name the card or source it came from.

# Proposing an owner
- Name the team or role documented as owning the area, as recorded in the knowledge base — not a guess at who is probably responsible.
- If no owner is documented, write that the owner is not documented and that assignment is needed. Do not leave the line blank and do not invent a name.

# Naming what is unknown
- List the specific unknowns, not a generic caveat. Say which question the material does not answer and what it would take to answer it.
- Flag any finding that rests on a single unverified source, and say so in that finding's line.

# Length and restraint
- Aim for one page or less. Three sharp findings beat nine thin ones.
- If the source material supports only one real finding, return one. Do not manufacture a second for symmetry.

# Boundaries
- Do not introduce a conclusion the source material does not support. Every claim in the summary must trace to something in the findings.
- Do not pad to look thorough: no filler recommendations, no restating the obvious, no "further analysis is recommended" unless you name the specific analysis.
- Do not soften a severe finding to make the summary easier to deliver, and do not sharpen a mild one to make it more interesting.
- Do not assign an action to a named individual as though the assignment were already agreed. Label it a proposal.