学術研究のためのClaude Codeスキルのコレクション。論文、事前分析計画、助成金提案書、結果の背後にあるコードに対するフィードバックを提供するものもあります。また、論文を政策ブリーフやスライドデッキに変換して結果を伝えるのに役立つものもあります。いくつかは、他のツールをより使いやすくするためのユーティリティです。これらのツールはClaes Bäckmanによって開発されました。研究における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.