Install any skill in seconds. Free to start, no credit card required.
Get Started Free →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.
.claude/skills/waybarrios-paper-summarizer/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-01 | ✗→✓ | ▲ Improved | -26% | 0% |
| case-02 | ✗→✓ | ▲ Improved | -15% | 0% |
| case-10 | ✗→✓ | ▲ Improved | -1% | 0% |
| case-13 | ✗→✓ | ▲ Improved | 22% | 0% |
| case-16 | ✗→✓ | ▲ Improved | 41% | 0% |
Extract actionable insights from academic and technical papers.
markdown# 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 | | 3 | [Claim] | Fig. 4 | Qualitative | Use this table for citation-audit alignment against the project's own research notes. If the PDF has no section numbers, use **page** or **heading text** instead of §. ## Practical Implications [What does this mean for practitioners? How can we use these findings?] - For the current stack: [Specific applicability to Rust/TS/Python work] - For current projects: [How this might inform current work] ## Limitations - [Limitation 1: e.g., small sample size, specific domain] - [Limitation 2: e.g., not replicated, theoretical only] ## Related Work - [Paper 1] — [How it relates] - [Paper 2] — [How it relates] ## Verdict **Reliability:** High / Medium / Low **Relevance to us:** High / Medium / Low **Action:** Apply directly / Consider for future / Interesting but not actionable
Before paraphrasing implications, list atomic claims the paper makes (results, bounds, contributions). For each: section / figure / table reference (or page). Prefer primary evidence (results section) over abstract-only restatement.
The most important question: "What can we do differently because of this paper?"
| Factor | Assessment | |---|---| | Peer review status | Published / Preprint / Workshop | | Replication | Replicated / Single study / Theoretical | | Sample size | Adequate / Small / N/A | | Methodology rigor | Strong / Moderate / Weak | | Author credibility | Established / New / Anonymous | | Conflicts of interest | None apparent / Funded by X] / Vendor paper |
Other measured skills in the registry, with their headline benchmark lift.