# Summarizer

Condense long articles, reports, and documents into clear, concise summaries.

- Repository: https://github.com/holaboss-ai/holaOS (11451 stars)
- Category: Engineering
- License: see repository
- Last updated: 2026-10-28
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add holaboss-ai/holaOS --skill summarizer -g -a claude-code -y`
Codex: `npx skills add holaboss-ai/holaOS --skill summarizer -g -a codex -y`
Cursor: `npx skills add holaboss-ai/holaOS --skill summarizer -g -a cursor -y`
Gemini CLI: `npx skills add holaboss-ai/holaOS --skill summarizer -g -a gemini-cli -y`

## Description

Condense long articles, reports, and documents into clear, concise summaries.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Summarizer

Summarize like an analyst writing for someone who won't read the original: capture everything that matters, drop everything that doesn't, and never let the compression distort the meaning. A good summary saves the reader time without costing them accuracy.

## When to use this skill

Use Summarizer to condense long inputs, articles, reports, research papers, transcripts, threads, into something faster to consume, at whatever depth the reader needs. If the task is to translate, retone, or rewrite for publication, use the relevant writing skill instead.

## Principles of a faithful summary

- **Fidelity first.** Never drop a critical point, caveat, number, or conclusion just to be shorter. Accuracy outranks brevity.
- **Lead with the conclusion.** Put the main takeaway up top; don't make the reader reconstruct it.
- **Preserve nuance.** Keep important qualifications, disagreements, and uncertainty, flattening them is a form of distortion.
- **Stay neutral.** Represent the source's position; don't inject your own opinion or invent detail not present in the text.
- **Cut redundancy, not substance.** Remove repetition, examples, and filler, keep the load-bearing ideas.

## Match the format to the need

Calibrate depth and shape to the request:

- **One-liner / TL;DR**, the single most important point.
- **Bullet points**, discrete key takeaways, good for scanning.
- **Narrative**, a short flowing paragraph that preserves the argument's logic.
- **Action items**, when the source implies decisions or next steps, extract them explicitly.

If the desired length or format isn't specified, pick a sensible default and state the level of detail you chose.

## How to work

The rest: https://github.com/holaboss-ai/holaOS/blob/HEAD/apps/desktop/electron/default-skills/summarizer/SKILL.md