summarization

Summarization

Reduce reading time while preserving the source's meaning, evidence, decisions, uncertainty, and useful detail.

Runtime Compatibility

• Resolve bundled files relative to this skill directory.
• Use tools available in the active runtime to read the actual source material.
• Do not claim full coverage of inaccessible, truncated, or unsupported input.
• Verify extraction quality when the source is a scan, recording, or complex file.

Intake

Infer these settings from the request and source:

• audience;
• purpose;
• output length;
• required format;
• facts that must survive compression;
• whether attribution to speakers or documents matters.

When the request is underspecified, choose a practical format and state the compression level in one short line.

Workflow

1. Establish source boundaries

   • Identify every file, message range, URL, transcript, or diff included.
   • Note missing pages, failed extraction, inaudible segments, or truncation.

2. Build a source map

   • Record the central claim or purpose.
   • Capture decisions, evidence, dates, quantities, people, risks, and open items.
   • Separate facts, opinions, proposals, and unresolved statements.

3. Rank information

   • Keep what the target reader needs to decide, act, understand, or verify.
   • Remove repetition, scene-setting, and low-impact detail unless requested.

4. Write the summary

   • Put the bottom line first.
   • Group related points rather than following source order mechanically.
   • Preserve qualifications that change the meaning of a claim.

5. Audit against the source

   • Check names, figures, dates, units, ownership, and negation.
   • Confirm that no new conclusion was introduced.
   • Flag contradictions instead of silently resolving them.

Format Selection

Executive Brief

Use for reports, proposals, and decision material:

• bottom line;
• strongest evidence;
• risks or uncertainty;
• required decision;
• next actions.