학술 연구를 위한 클로드 코드 기술 모음입니다. 어떤 도구는 논문, 사전 분석 계획, 연구비 제안서, 또는 결과의 코드를 피드백으로 제공합니다. 다른 것은 논문을 정책 요약이나 슬라이드 덱으로 변환하여 결과를 전달하는 데 도움을 줍니다. 일부는 나머지 도구들을 더 쉽게 사용하는 유틸리티입니다. 이 도구들은 클라에스 벡만이 개발했습니다. 연구에서 AI를 활용하는 더 넓은 입문서와 이러한 기술들이 워크플로우에 어떻게 부합하는지에 대해서는 AI 워크숍 페이지를 참조하세요.

이 리포의 기술

각 스킬은 Skills/ 폴더에 SKILL.md 파일로 저장되어 있습니다. 일부 스킬은 템플릿과 보조 스크립트도 같은 폴더에 함께 제공합니다.

글쓰기에 대한 피드백. 문서를 읽고 결과를 바탕으로 구조화된 보고서를 작성하는 검토 기술 계열입니다. 이 기술들은 논문에 대한 전면 심사위원식 검토, 기여 및 식별 확인 빠른 확인, 맞춤법 및 내부 일관성 기계적 점검, 사전 분석 계획 검토, 보조금 제안서 검토 등을 포함합니다.

• review-paper, review-paper-light, review-paper-checks, review-pap, review-grant

**코드에 대한 피드백.

AI tools for research

A collection of Claude Code skills for academic research. Some give you feedback on a paper, a pre-analysis plan, a grant proposal, or the code behind a result. Others help you communicate your results, by turning a paper into a policy brief or a slide deck. A few are utilities that make the rest easier to use. The tools were developed by Claes Bäckman. For a broader introduction to using AI in research, including how these skills fit into a workflow, see the AI workshop page.

Skills in this repo

Each skill lives in its own folder under Skills/ with a SKILL.md file. Some skills also ship templates and helper scripts in the same folder.

Feedback on your writing. A family of review skills that read a document and write a structured report with findings you can act on. They cover a full referee-style review of a paper, a quick check of the contribution and identification, a mechanical check of spelling and internal consistency, a review of a pre-analysis plan, and a review of a grant proposal.

• review-paper, review-paper-light, review-paper-checks, review-pap, review-grant

Feedback on your code. Skills that check whether the analysis code does what the paper says it does, hunt for errors in a recent change, or explain a change well enough that a coauthor could defend it.

• review-paper-code: Paper–code reproducibility and alignment review.
• audit-analysis: Adversarial audit of changed analysis code, run by an isolated subagent.
• explain-diff: Explain a code change as an offline HTML page with a quiz.

Communicating your results. Skills that turn a finished paper into something for a different audience.

• paper-version: Policy brief, one-page, or five-page summary with a standalone HTML page.
• explorable-deck: A Quarto reveal.js slide deck built around a running example and live, presenter-driven figures.
• explorable-beamer: The same deck in LaTeX beamer, with TikZ stages the presenter steps through, a handout build, and a screenshot-and-log check of every page.
• explorable-pptx: The same deck as a PowerPoint file that coauthors can edit, with stages drawn as native shapes, a handout build, and screenshots taken through PowerPoint itself.

Utilities.

• pdf-to-markdown: Convert a PDF to readable markdown, trimmed at the references.

How the skills work

These are Claude Code skills. A skill is a folder containing a SKILL.md file, installed under ~/.claude/skills// and invoked by typing / (for example, /review-paper) inside Claude Code.

A global install (~/.claude/skills/) is available in every project. A project-local install (.claude/skills/) applies only to that repository. Skills are picked up the next time you start Claude Code in the target directory.