summarizer
GitHub将长篇文章、报告等压缩为清晰简练的摘要,强调准确性与保真度。支持TL;DR、要点、叙事及行动项等多种格式,适用于快速提取核心信息。
Trigger Scenarios
Install
npx skills add holaboss-ai/holaOS --skill summarizer -g -y
SKILL.md
Frontmatter
{
"name": "summarizer",
"description": "Condense long articles, reports, and documents into clear, concise summaries."
}
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
- Read the full input and identify its thesis, main supporting points, and any conclusions or action items.
- Decide the right length and format for the reader's need.
- Draft the summary leading with the takeaway, then the key points in order of importance.
- Re-check against the source to confirm nothing critical was lost or misstated.
Output format
Return the summary in the requested format, takeaway first. For longer or multi-topic sources, group points under brief headers. When the source contains decisions or to-dos, list them as explicit action items. Note the detail level you targeted if it wasn't specified.
Version History
- f6013b5 Current 2026-08-19 23:16


