Agents should invoke this skill for academic or technical papers, arXiv/PubMed/IEEE/ACM links, PDFs, methodology review, limitations, practical implications, or extracting findings for engineering decisions.
SkillScore77Maintained
Automatic
◆Research pack
Last verified 8/19/2026
What it changes
Passed 17 of 22 test cases with the skill, and 12 of 22 without it.
Without skill55%
With skill77%
Checks it passed that the model alone missed
The TL;DR summary is constrained to one or two sentences focusing on the key contribution.
The table schema consists of claim index, single-line claim, location in paper, and evidence type.
Each numbered finding anchors its evidence using section symbols, page numbers, or figure references.
and 3 more in the full report
5 fixed12 passed either way5 still failing0 broke
Pass-rate lift
+23 pp
Tokens
+1%
Agent turns
0%
Response time
-35%
Model gemini-3.6-flashMeasured 8/19/2026v117 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 5
Prompt
At the end of a technical paper summary on distributed key-value store performance, I want a standard verdict block. What three key evaluation metrics should be highlighted in bold within this verdict section?
What was checked, without and with the skill
Checked
Without skill
With skill
The verdict section presents structured ratings for reliability, organizational relevance, and action choice.
Missed
Passed
case-13 · gemini-3.6-flash · 8/19/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md104 linessingle file
Paper Summarizer
Extract actionable insights from academic and technical papers.
Summary Format
# Paper Summary: <Paper Title>
**Authors:** [Author list]
**Published:** [Journal/Conference, Date]
**Link:** [URL]
**Quality:** Peer-reviewed / Preprint / Workshop paper
## TL;DR
[1-2 sentence summary of the key contribution]
## Problem
[What problem does this paper address? Why does it matter?]
## Approach
[Methodology in plain language — what did they do?]
## Key Findings
Anchor each finding to the paper so readers can verify. Use **§** for sections, **Fig.** / **Table** when the evidence is visual or tabular.
1. **[Finding 1]:** [Description with key metrics/numbers] — *Evidence:* §[N] [section name]; [Fig. X / Table Y if applicable]
2. **[Finding 2]:** [Description] — *Evidence:* §[N] …
3. **[Finding 3]:** [Description] — *Evidence:* §[N] …
## Claim–evidence map
| # | Claim (one line) | Where in paper | Type |
|---|------------------|----------------|------|
| 1 | [Claim] | §3.2 Results, Table 2 | Empirical |
| 2 | [Claim] | §1 Introduction | Stated goal |