본문으로 건너뛰기
cccskills
무료GitHub에 공개

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(1)

  • SKILL.md3.8 KB

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

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Audit GitHub Actions that run AI agents for prompt injection, unsafe interpolation, sandbox gaps, and permissive actor rules. Use for agentic CI workflows, not general application code review.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

waybarrios/opencode-power-pack5412026년 10월 19일 업데이트

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

waybarrios/opencode-power-pack5412026년 10월 19일 업데이트

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

waybarrios/opencode-power-pack5412026년 10월 19일 업데이트

ai-slop

무료

Operational rubric that turns "don't make AI slop" into observable properties, severity levels, evidence requirements, and repair actions for interface design. Use as the reference rubric when building or reviewing marketing sites, product interfaces, dashboards, portfolios, or e-commerce pages, especially alongside frontend-design.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

waybarrios/opencode-power-pack5412026년 10월 19일 업데이트

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

waybarrios/opencode-power-pack5412026년 10월 19일 업데이트

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

waybarrios/opencode-power-pack5412026년 10월 19일 업데이트

waybarrios의 스킬 모두 보기

이 스킬의 문제 신고