mcpbeat

Summarize

serhiikorniienko/summarize

Produce a structured summary of a video, article, tweet thread, or PDF — TLDR, key points with timestamps/locations, notable quotes, and who should read/watch it. Use when the user asks to summarize a link or file, wants a TLDR, or asks "what does this video/article say" / "is this worth watching".

424 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
101
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/SerhiiKorniienko/bullshit-detector --skill summarize

What it tells the agent to use

found in the instruction text
WebFetch fetches pages from the network

The instruction itself

3 sections, as written by the author

summarize

Give someone the content without the runtime.

Workflow

  • 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.
  • 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.

How to use it

Copy the folder

Take serhiikorniienko/summarize from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.