literature-review
Skill1 starsChanged 2 months agoMITView on GitHub
関連研究を体系的に調査するとき、「文献調査して」「サーベイして」と言われたときに必ず使う。
92 other projects use a version of this.
Adopted by
Most recently taken up by
- BraveDistribution/claude-skillstheir own version, first seen Nov 16, 2026
- KPISTOLAS/claude-skillstheir own version, first seen Nov 16, 2026
- Ivan-propio/claude-skillstheir own version, first seen Nov 16, 2026
- tatashbar/Economic-Modeling-Studiotheir own version, first seen Nov 16, 2026
- lengrufeng2008/dsh-skill-librarytheir own version, first seen Nov 15, 2026
- PerryLink/dsh-research-skillstheir own version, first seen Nov 15, 2026
Used with
Projects with it also use pdf-explore, paper-narrative and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
JimLiuSkillpdf-explore
Use this skill when the user has attached a PDF, paper, report, or other document and the answer needs content from more than one place in it: summarize the methods or any other section, compare sections, find where a topic is discussed, read a value or label off a figure or chart, or find/list/extract every instance of something across the whole document (datasets, benchmarks, citations, figures, table rows, accession numbers — including appendices). Skip it only for a single lookup of 1–4 pages quoted in your very next response — `read_file(pages=[...])` attaches pages as images that are dropped from context after one turn, so multi-section answers end up re-reading the same ranges repeatedly. Parses the PDF once in the Python kernel: `pdf_pages` (pages as persistent text), `pdf_outline` (TOC), `pdf_scan` (rank pages by relevance), `pdf_map`/`pdf_extract` (per-page summary / structured fields via parallel haiku calls). For PDF creation/manipulation, use reportlab/pypdf directly.
Also in 9 projects that use this
JimLiuSkillpaper-narrative
Judge and reshape the STORY a paper's figures tell. Input is the work itself — manuscript (or abstract) + figure deck — no hand-written brief. `derive_paper_brief(abstract, captions)` extracts pitch/vision/per-figure-claims; a handling-editor reviewer on the full deck returns hook_verdict (would Fig 1 make me send this for review?), arc (hook→mechanism→evidence→application), figure_moves (panels in the wrong figure), missing_panels (concrete analyses to RUN), kill_list, and boldest_defensible_fig1. Hands per-figure claims to `figure-composer`. Load when writing or revising a paper.
Also in 5 projects that use this
Norman-burySkillbrainstorming-research
Use before writing any paper - clarifies paper type, discipline, topic, methodology, and chapter structure through natural dialogue
Also in 4 projects that use this
lingzhi227Skilllatex-formatting
Handle LaTeX formatting, templates, and styling for academic papers. Set up conference templates (ICML, ICLR, NeurIPS, AAAI, ACL), fix formatting issues, manage packages, and ensure venue-specific compliance. Use when the user needs to set up a paper template, fix LaTeX formatting, or prepare for submission.
Also in 4 projects that use this
lingzhi227Skillnovelty-assessment
Assess research idea novelty through systematic literature search. Multi-round search-evaluate loops with harsh critic persona. Binary novel/not-novel decision with justification. Use before committing to a research direction.
Also in 4 projects that use this
- +6 more from JimLiu
- +1 more from lingzhi227
Other versions92 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 92
- advaitpaliwal/feynman★ 10ksame name
- companion-inc/feynman★ 10ksame name
- getcompanion-ai/feynman★ 10ksame name
- Norman-bury/research-writing-skill★ 3.4ksame name
- Norman-bury/articlewriting-skill★ 3.4ksame name
- HughYau/AcademicForge★ 2.6ksame name
- K-Dense-AI/claude-scientific-writer★ 2.6ksame name
- xuzhougeng/wisp-science★ 1.1ksame name
- wu-yc/LabClaw★ 1.1ksame name
- LeonChaoX/qinyan-academic-skills★ 910same name
82 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository27 other files it gives its agents.
- AGENTS.mdAGENTS.md
- adrSkill
- architecture-checkSkill
- brainstormSkill
- branch-namingSkill
- codex-delegateSkill
- config-explainSkill
- config-setSkill
- cross-reviewSkill
- design-interviewSkill
- diagnosing-bugsSkill
- fix-ciSkill
- handoffSkill
- leakage-checkSkill
- mlflow-logSkill
- multi-seedSkill
- mutation-testSkill
- paper-writingSkill
- pre-mortemSkill
- property-testSkill
- python-standardsSkill
- refactor-scoutSkill
- regression-suiteSkill
- retrospectiveSkill
- security-reviewSkill
- spec-checklistSkill
- tddSkill
The file
Files
文献レビュー(構造化された調査)
場当たり的な検索ではなく、スコープを固定してから調査する。 調査の再現性(なぜこの文献群を選んだか)を担保する。
進め方
1. スコープの固定
調査を始める前に、以下をユーザーと確認して literature/<テーマ>/scope.md に保存する。
テーマ: <調査対象>
必須キーワード: [<キーワード1>, <キーワード2>]
除外条件: <対象外とする条件>
期間: <例: 2020年以降>
目的: <査読対応 / 関連研究セクション執筆 / 手法の比較検討>2. 検索
- arXiv MCP が接続されていれば優先的に使う(検索・アブストラクト取得)
- 無ければ web_search で "site:arxiv.org <キーワード>" 等の検索を行う
- 検索クエリと取得結果は literature/<テーマ>/search-log.md に記録する (後で「なぜこの文献を見つけた/見逃したか」を追えるようにするため)
3. スクリーニング
各文献をタイトル+アブストラクトで判定し、以下に分類する。
- 採用: スコープに合致。詳細を読む
- 保留: 関連はあるが目的から外れる。理由を1行記録
- 除外: スコープ外。理由を1行記録
4. 抽出
採用文献ごとに以下を literature/<テーマ>/notes/<文献ID>.md に記録する。
- 書誌情報(著者、年、会議/誌名、URL)
- 1行要約
- 手法の要点(3行以内)
- 本研究との関係(何が同じで何が違うか)
- 引用する可能性のある主張とその根拠箇所
5. 統合
literature/<テーマ>/summary.md に統合レポートを書く。
- 文献同士の関係(系譜、対立、補完)
- 本研究の位置づけ(既存研究との差分)
- 見つかった研究ギャップ
重要なルール
- 存在しない文献をでっち上げない。確認できた文献のみを扱う
- アブストラクトしか読んでいない文献を「詳細を確認した」ように書かない。 確認レベル(アブストのみ / 本文確認済み)を必ず記録する
- 本文に書かれていない結論を文献に帰属させない
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
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.

