Skip to content

IbrahimSobh/AISkills / high-fidelity-summarizer

high-fidelity-summarizer

Verified

Compress technical, legal, financial, or analytical text into a dense summary that keeps every named entity, number, claim, and the source's structural/chronological flow — but rewrites the prose. Wording is carried over literally by exception only (proper nouns, product names, acronyms, file names, terms of art), plus at most one verbatim quote under 15 words. No outside information, no simplification. Length targets 25% of the source word count. Use whenever the user asks to "summarize," "condense," "compress," or "shorten" a document, article, contract, report, paper, or transcript — especially where factual precision outranks readability and the summary must stand in as a proxy for the original. Do NOT use for making text easier to understand (that's the simplifier skill — it preserves length and reduces difficulty; this preserves difficulty and reduces length). Do NOT use when the user wants the original's shape and wording kept for study with no length target (that's content-highlighter).

FileKindSize
README.mdmarkdown2.7 KB
SKILL.mdskill md10.5 KB
scripts/check_summary.pyscript3.2 KB
# high-fidelity-summarizer

Compresses technical, legal, financial, or analytical text to about 25% of its length while keeping every named entity, number, claim, and the source's order and formatting. The prose is rewritten; names and figures are not. For readers who need a summary that can stand in for the original.

## When to use it

- You need a shorter version of a contract, report, paper, or transcript that still carries the exact terms and figures.
- Precision outranks readability, so loose paraphrase is not acceptable.
- You want a measured result: the skill ends with a script-verified word count and percentage.

## Example request

> Summarize this section with high fidelity: [pasted text]

<details>
<summary>Input text (204 words)</summary>

> ## Why there's no verification loop here
>
> `content-diagrams` spends most of its effort on geometry: an SVG line, box, or label is just numbers Claude computed, and computed numbers can be wrong — hence render, screenshot, crop, and check.
>
> Mermaid removes that failure mode entirely. Node width, text wrapping, arrow paths, and collision avoidance between elements are the *renderer's* job, not Claude's — the renderer will not place a label on top of a box or route a line through a shape. Re-deriving that verification loop here (screenshotting the rendered diagram, cropping, checking overlaps) would just burn tokens and latency confirming something the tool already guarantees.
>
> What can still go wrong is entirely different, and entirely textual:
> - Broken syntax (unclosed brackets, a reserved word used as a node ID, mismatched arrow types)
> - An edge referencing a node ID that's never defined
> - Poor color contrast (a fill and text color that don't actually read against each other)
> - The wrong diagram type for the content's actual structure
>
> So verification here means: read the syntax once for correctness, check every classDef pairs a fill with a genuinely contrasting text color, and confirm the diagram type matches what's being modeled. No image rendering required.

</details>

## Example output

> ## Why there's no verification loop here
>
> Unlike `content-diagrams`, Mermaid's renderer owns layout and collisions, so screenshot checks waste tokens.
>
> Remaining failures are textual:
> - Broken syntax
> - Undefined node IDs in edges
> - Poor color contrast
> - Wrong diagram type
>
> Verify: read syntax once, check classDef contrast, confirm diagram type. No rendering.
>
> ---
> Summary number of words: 53
> Summary size percentage of the original : 26.0%

_Last run: 2026-10-12 · Claude Sonnet 5.5_

## Install

```bash
cp -r high-fidelity-summarizer ~/.claude/skills/
```

Full instructions for the agent: [SKILL.md](SKILL.md)
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall