mcpField
S
summarize

summarize

github.com/serhiikorniienkoProductivity16278 installsUpdated 4w ago
Repository

About summarize

A productivity skill for turning source material into structured summaries with traceable key points. It emphasizes fidelity to the source and adjusts length to the content.

Key features

  1. 01Summarize text with a thesis-focused TLDR
  2. 02Add key points with timestamps or page references
  3. 03Preserve source structure and complete lists
  4. 04Keep names, numbers, and claims source-faithful

Use cases

  1. 01Summarizing an article or transcript
  2. 02Creating notes that link back to source passages

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/serhiikorniienko/bullshit-detector --skill summarize

After installing, type/summarizein Claude Code to confirm it loaded.

Bundled filesVERSION

Details

From the project README

summarize

Give someone the content without the runtime.

Workflow

  1. Get the text. If the input is a URL and the fetch-content skill is installed, use its script; otherwise use your web fetch tool or ask for a paste. Keep the metadata.
  2. Read fully, then write:
# <title>
**<author> · <platform> · <date> · <duration/length> · <views if notable>**

**TLDR:** one paragraph, ≤3 sentences — the actual thesis, not the topic.

## Key points
Bulleted. Each point = one idea, with [timestamp] or [p.N] so the
reader can jump to it. Preserve the content's own structure (if it
promises "14 ways", list all 14 — compressed, not truncated).

## Notable quotes
1–3 verbatim quotes that carry the content's voice, with locations.

## Worth your time?
One honest sentence per audience: who gains from the full version,
who is fine with this summary.

Rules

  • Summarize what the content says, not what you think of it (that's the bullshit-detector skill — mention it if the content smells hyped, don't perform its job here).
  • Numbers, names, and claims must come from the content verbatim — no rounding, no "improving".
  • If the content is listicle-shaped, the summary must contain the complete list. Never "...and 9 more ways".
  • Scale length to source: a tweet gets 3 lines, a 3-hour podcast gets a full page.

Comments

Markdown supported