paper-summarizer
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.
git clone --depth 1 https://github.com/waybarrios/opencode-power-pack /tmp/paper-summarizer && cp -r /tmp/paper-summarizer/skills/paper-summarizer ~/.claude/skills/paper-summarizerSKILL.md
# Paper Summarizer Extract actionable insights from academic and technical papers. ## Summary Format ```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 ``` ## 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 | 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 |
Audit and improve project-rules files (AGENTS.md, CLAUDE.md, .agents/instructions, local overrides) so the agent keeps accurate project context. Use when the user asks to check, audit, review, update, improve, or fix their AGENTS.md or CLAUDE.md, mentions "project rules maintenance" or "agent context optimization", or when the codebase has changed enough that the rules file may be stale. Scans the repository for every rules file, grades each against a quality rubric, outputs a quality report, and applies targeted edits only after user approval.
Capture learnings from the current session into the project-rules file (AGENTS.md, CLAUDE.md, or local override) so future sessions benefit. Use when the user says "revise the rules", "update AGENTS.md / CLAUDE.md with what we just learned", "save this to project memory", "remember this for next time", or at the end of a productive session when valuable context has emerged that is not yet documented. This complements agents-md-improver — improver audits, while this one captures.
Design a feature architecture by analyzing existing codebase patterns and conventions, then provide a comprehensive implementation blueprint with specific files to create or modify, component designs, data flows, and a build sequence. Use this skill when the user asks for an architecture design, an implementation plan for a non-trivial feature, or when dispatched as a sub-task during feature-dev architecture phase.
Deeply analyze an existing codebase feature by tracing execution paths, mapping architecture layers, understanding patterns and abstractions, and documenting dependencies. Use this skill when you need to understand how a feature works before modifying or extending it, when dispatched as a sub-task during feature-dev exploration, or when the user asks "how does X work in this codebase".
Review a pull request or a set of code changes for bugs, logic errors, and project-convention violations using a confidence-filtered, multi-agent process. Use this skill when the user asks to review a PR, audit pending changes, or inspect a diff for problems before merging.
Review code for bugs, logic errors, security vulnerabilities, code quality issues, and adherence to project conventions, using confidence-based filtering to report only high-priority issues that truly matter. Use this skill when reviewing a small set of changes locally (such as unstaged diff), when dispatched as a sub-task during feature-dev quality review, or when the user wants a critique of a specific file or function.
Guide a feature implementation through a structured seven-phase workflow with deep codebase understanding, clarifying questions, parallel architecture design, and quality review. Use this skill when the user asks to build a new feature, add functionality, or wants a methodical approach to implementation rather than diving straight to code.
Create distinctive, production-grade frontend interfaces with high design quality and accessible markup. Use this skill when the user asks to build or beautify web components, pages, applications, landing pages, dashboards, artifacts, or React/HTML/CSS UI. Generates creative, polished code that avoids generic AI aesthetics, then self-checks it against an objective accessibility and quality rubric.