agentleFS
waybarrioswaybarrios/opencode-power-pack/skills/paper-summarizer/SKILL.md

paper-summarizer

Skill547 starsChanged 3 months agoMITView on GitHub

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.

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check arXiv, PubMed, Google Scholar for open-access versions

    line 78
  2. Distinctive:

    If behind a paywall, note this and work with the abstract and any available supplementary material

    line 79
  3. Distinctive:

    Check for author's personal page (often has preprints)

    line 80
  4. Distinctive:

    Before paraphrasing implications, list atomic claims the paper makes (results, bounds, contributions).

    line 92
  5. Distinctive:

    If the answer is "nothing" — still summarize, but note low actionability

    line 98
  6. Distinctive:

    If the answer is specific — tie each implication to a row in Claim–evidence map where possible

    line 99

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Process

Step 1 — Access the Paper

  • Check arXiv, PubMed, Google Scholar for open-access versions
  • If behind a paywall, note this and work with the abstract and any available supplementary material
  • Check for author's personal page (often has preprints)

Step 2 — Read Strategically

  1. Abstract — Get the overview
  2. Introduction (last paragraph) — Usually states the contribution
  3. Figures and tables — Often convey key results
  4. Conclusion — Summary of findings and limitations
  5. Methodology — If the findings are relevant enough to dig deeper

Step 3 — Extract claims with locations

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.

Step 4 — Extract Practical Value

The most important question: "What can we do differently because of this paper?"

  • If the answer is "nothing" — still summarize, but note low actionability
  • If the answer is specific — tie each implication to a row in Claim–evidence map where possible

Step 5 — Assess Reliability

FactorAssessment
Peer review statusPublished / Preprint / Workshop
ReplicationReplicated / Single study / Theoretical
Sample sizeAdequate / Small / N/A
Methodology rigorStrong / Moderate / Weak
Author credibilityEstablished / New / Anonymous
Conflicts of interestNone apparent / Funded by [X] / Vendor paper

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.