Article Lens Quick — 2-Minute Read Skill
Produce the sharpest possible digest of any article. Hard ceiling: 2 minutes of reading
(~480 words at average adult reading speed). Every word earns its place or gets cut.
Step 0 — Acquire the Content
If a URL is provided:
- Call
web_fetch immediately. Do not ask the user to paste the text.
- If fetch fails (paywall, bot-block): say "Couldn't fetch the page — paste the article text and I'll run the digest." Stop.
If raw text is pasted:
- Use it directly. No
web_fetch.
If both exist: use the pasted text.
Step 1 — Pre-flight (internal, silent)
Before writing, silently note:
- Content type — opinion/essay, tutorial, announcement, research summary, case study, listicle
- Author expertise — practitioner, academic, journalist, enthusiast
- Target audience — beginner, intermediate, senior practitioner
Do not output this. Do not ask anything. Proceed directly to output.
Step 2 — Output Structure
Three sections, in order, separated by ---. No preamble, no closing.
Before the first section, one metadata line:
📖 2 min read · Article title or inferred topic
Do not calculate — always show "2 min read" as the fixed label. This is the quick variant.
🧭 Summary
3 sentences maximum. No exceptions.
Sentence 1: the core thesis — what the article argues or shows.
Sentence 2: why it matters or what problem it addresses.
Sentence 3: the key caveat or constraint the author acknowledges (skip if none).
Pure prose. No bullets.
🔑 Key Points
3–5 bullets. One sentence each — no second sentences.
- Highest-signal points only. If a point could be inferred from another, cut it.
- Order by importance, not article order.
- No qualifications unless they change the meaning materially.
- Strictly from the article. No external context.
⚡ Actions & Suggestions
1–2 bullets. One sentence each.
- The single most actionable takeaway from the article for a senior reader.
- A second only if it's genuinely distinct and high-value. If in doubt, cut it.
- Grounded in something the article explicitly says or demonstrates.
Hard Limits
- 480 words total maximum — count ruthlessly, cut from Key Points first if over.
- No nested bullets at any level.
- No bold except for named concepts or terms.
- No headers beyond the three section headers.
- No editorializing — every claim traces back to the article.
- Thin article (< 400 words): note it in one line before Summary, reduce Key Points to 2–3.
Edge Cases
- Non-article URL (repo, docs, landing page): adapt, note content type beside the title in the metadata line.
- Multi-language content: respond in the user's message language.
1---2name: article-summarizer-2mins3description: Fast 2-minute read of any article, blog post, or web page: a tight summary, the most critical key points, and 1–2 sharp actions — all strictly from the content, delivered instantly with no back-and-forth. Use this skill when the user wants a rapid digest and says things like "quick summary", "TL;DR", "2 min version", "give me the gist", "what's the takeaway", "brief breakdown", or drops a URL and wants fast signal. Also triggers when the user just shares a URL or article text with no instruction and speed or brevity is implied. Works for any domain.4---56# Article Lens Quick — 2-Minute Read Skill78Produce the sharpest possible digest of any article. Hard ceiling: **2 minutes of reading**9(~480 words at average adult reading speed). Every word earns its place or gets cut.1011---1213## Step 0 — Acquire the Content1415**If a URL is provided:**16- Call `web_fetch` immediately. Do not ask the user to paste the text.17- If fetch fails (paywall, bot-block): say "Couldn't fetch the page — paste the article text and I'll run the digest." Stop.1819**If raw text is pasted:**20- Use it directly. No `web_fetch`.2122**If both exist:** use the pasted text.2324---2526## Step 1 — Pre-flight (internal, silent)2728Before writing, silently note:29- **Content type** — opinion/essay, tutorial, announcement, research summary, case study, listicle30- **Author expertise** — practitioner, academic, journalist, enthusiast31- **Target audience** — beginner, intermediate, senior practitioner3233Do not output this. Do not ask anything. Proceed directly to output.3435---3637## Step 2 — Output Structure3839Three sections, in order, separated by `---`. No preamble, no closing.4041**Before the first section**, one metadata line:4243> 📖 **2 min read** · *Article title or inferred topic*4445Do not calculate — always show "2 min read" as the fixed label. This is the quick variant.4647---4849### 🧭 Summary50*3 sentences maximum. No exceptions.*5152Sentence 1: the core thesis — what the article argues or shows.53Sentence 2: why it matters or what problem it addresses.54Sentence 3: the key caveat or constraint the author acknowledges (skip if none).5556Pure prose. No bullets.5758---5960### 🔑 Key Points61*3–5 bullets. One sentence each — no second sentences.*6263- Highest-signal points only. If a point could be inferred from another, cut it.64- Order by importance, not article order.65- No qualifications unless they change the meaning materially.66- Strictly from the article. No external context.6768---6970### ⚡ Actions & Suggestions71*1–2 bullets. One sentence each.*7273- The single most actionable takeaway from the article for a senior reader.74- A second only if it's genuinely distinct and high-value. If in doubt, cut it.75- Grounded in something the article explicitly says or demonstrates.7677---7879## Hard Limits8081- **480 words total maximum** — count ruthlessly, cut from Key Points first if over.82- **No nested bullets** at any level.83- **No bold** except for named concepts or terms.84- **No headers** beyond the three section headers.85- **No editorializing** — every claim traces back to the article.86- Thin article (< 400 words): note it in one line before Summary, reduce Key Points to 2–3.8788---8990## Edge Cases9192- **Non-article URL** (repo, docs, landing page): adapt, note content type beside the title in the metadata line.93- **Multi-language content**: respond in the user's message language.
anarefin