Back to skills
writingv1.0.0Free

Summarize Link

Give it a URL, get a tight 3-paragraph summary. Use for articles, blog posts, papers, and docs pages when the user asks for the gist or "what is this about?". Output is exactly three paragraphs: what it says, why it matters, what is missing.

Activate this skill on your agent
Adds summarize-link to your agent’s instructions. The skill takes effect on your next provision or refresh.
Sign up to activate →
SKILL.md
# Summarize Link

Take a single URL and produce a tight, lossless 3-paragraph summary that a
busy reader can absorb in under 60 seconds.

## When to use

Use this skill when the user gives you a URL — an article, blog post,
research paper, docs page, or news story — and asks for a summary, the
gist, or "what's this about?". Default to this format unless the user
asks for bullets, a TL;DR-only, or a longer treatment.

## Inputs

- A single URL (required). HTTPS only.
- Optional: `audience` — e.g. "engineer", "marketer", "five-year-old".
  If absent, write for a smart generalist.
- Optional: `focus` — a specific question to answer from the page.

## Process

1. Fetch the URL. If fetching fails, say so and stop. Do not guess.
2. Strip nav, footer, comments, and other chrome. Keep the body.
3. Identify the thesis and the 2–4 strongest supporting claims.
4. Write three paragraphs in the format below.
5. If the page is a video transcript or interview, attribute quotes to
   the actual speaker, not "the article".

## Output format

Exactly three paragraphs. No headings, no bullets, no preamble.

- **Paragraph 1 — What it says.** State the thesis in plain English.
  One or two sentences setting the scene, then the core claim.
- **Paragraph 2 — Why it matters / how it argues it.** The strongest
  evidence, the mechanism, or the surprising data point. This is where
  most of the substance lives.
- **Paragraph 3 — What's missing or worth pushing back on.** The
  honest limitation, counter-argument, or open question. End on
  something the reader can do or check next.

End the summary with one line: `Source: <url>`

## Example

> Source: https://example.com/why-static-sites-won.html

Static-site generators have quietly displaced most CMS-driven blogs
because the cost of a CDN-served HTML file is now indistinguishable
from zero. The author argues that the win isn't speed — it's that
"infinite scale at zero cost" reframes what counts as a viable
publishing project: a hobbyist blog now costs the same as a Fortune 500
microsite.

The strongest evidence is a year-long survey of 4,200 personal sites
that migrated off WordPress: median monthly hosting bill dropped from
$11 to $0.04, and median Core Web Vitals score moved from 62 to 91.
Crucially, the author shows the migration takes <2 hours for a typical
500-post archive — the cost barrier wasn't the platform, it was the
perceived difficulty.

What's missing is a serious treatment of dynamic features — comments,
search, member-only content — where static sites still need a SaaS
crutch. The piece also doesn't grapple with content velocity: WordPress
is bad at performance but excellent at "publish a thought in 30
seconds". For a high-frequency publisher, that may still tip the
balance.

Source: https://example.com/why-static-sites-won.html

## Hard rules

- Three paragraphs. Not two, not four. Not a list pretending to be paragraphs.
- Never invent a fact, statistic, or quote. If it isn't on the page, it doesn't go in.
- Never editorialize beyond what the source supports.
- If the page is paywalled or blocked, say so explicitly: "Could not access content".