academic-research
Skill0 starsChanged 3 months agoMITView on GitHub
Use when the user asks to find research papers, check what a study found, look up peer-reviewed literature, or verify a scientific/technical claim against published research. Triggers on "find papers on", "what does the research say", "peer-reviewed studies on", "academic research", "literature on X". Produces evidence records (DOI/URL + verbatim quote + peer-review status), never conclusions. Do NOT use for a blog's summary or interpretation of a paper (use blog-research, then cross-check against this skill when the claim is load-bearing), or for general web content (use web-research).
9 other projects use a version of this.
Adopted by
Most recently taken up by
- velonx/agent-skillstheir own version, first seen Sep 24, 2026
- ViewWay/academic-research-skilltheir own version, first seen May 19, 2026
- sergeeey/Claude-cod-top-2026their own version, first seen May 13, 2026
- fabioc-aloha/alex-cognitive-architecturetheir own version, first seen Apr 26, 2026
- hint-shu/deep-researchtheir own version, first seen Apr 17, 2026
- tdimino/claude-code-minoantheir own version, first seen Apr 16, 2026
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- voidful/academic-skills★ 126same name
- tdimino/claude-code-minoan★ 41same name
- sergeeey/Claude-cod-top-2026★ 9same name
- orhoncan/oneshot-academic-research-skill★ 8same name
- hint-shu/deep-research★ 4same name
- ViewWay/academic-research-skill★ 4same name
- velonx/agent-skills★ 1same name
- fabioc-aloha/alex-cognitive-architecture★ 0same name
- romanmesicek/agent-skills★ 0same name
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 repository10 other files it gives its agents.
- blog-researchSkill
- github-researchSkill
- news-researchSkill
- official-source-researchSkill
- reddit-researchSkill
- research-intelligenceSkill
- research-plannerSkill
- social-researchSkill
- source-verifySkill
- web-researchSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
Don't use for: a secondary summary/interpretation as if it were the paper itself (fetch the paper directly, or flag when only the summary …
- Distinctive: line 26
Check for retraction/correction status: before recording — a retracted paper is excluded outright, not just tiered down.
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Academic Research
Overview
Collects evidence from peer-reviewed papers and preprints. The defining risk here is exactly acceptance test 4 in this repo's test suite: a blog post misreading or overstating what a paper actually found. This skill's job includes resolving that conflict in the paper's favor when it arises — the root always outranks a derivative's misreading (engine/conflict-resolution.md's derivation check).
Layer rule: produces evidence, not results. Synthesis and confidence status are the orchestrator's job.
When to use
Direct use: "find studies on X", "what's the peer-reviewed evidence for Y". As a component: orchestrator dispatches this whenever a fact-type claim has a scientific/technical basis worth checking against the actual literature rather than someone's summary of it.
Don't use for: a secondary summary/interpretation as if it were the paper itself (fetch the paper directly, or flag when only the summary was accessible), general web content with no scholarly indexing (→ web-research).
Workflow
- Search the actual literature index, not general web search — arXiv, PubMed, DOI resolution, or whatever academic search surface is available. General web search will miss paywalled or properly-indexed papers a dedicated search catches, and will surface blog summaries instead of the source.
- Distinguish peer-reviewed from preprint from non-reviewed. A preprint (arXiv, bioRxiv, medRxiv) is real research not yet vetted — usable, but tier 2, not tier 1. Never present preprint findings with peer-reviewed confidence.
- Read past the abstract for load-bearing claims. Abstracts compress and sometimes overstate; a claim central to the finding (a specific number, a causal claim, a stated limitation) should be checked against the actual body text before being recorded as the paper's claim — this is the single most common source of subtly wrong numbers in literature synthesis. Skimming the abstract is acceptable only for context/orientation claims, not for anything a
factfinding will lean on. - If a search returns nothing: run references/query-relaxation.md, adapted to academic search syntax (drop field/date filters first, then reduce to core terms). Log full exhaustion as a gap — a thin-coverage area (e.g., non-arXiv CS venues, non-biomedical topics) is a real, reportable limitation, not a search failure to hide.
- Check for retraction/correction status before recording — a retracted paper is excluded outright, not just tiered down; a correction changes what the record should quote.
- Extract publication date — journal/preprint metadata is normally structured and reliable. Use
published_atfor the version you actually quoted, andmodified_atwhen a revised version exists (a preprint later published with different numbers is a revision worth recording, not a footnote). - A paper is its own root:
root_id: doi:<doi>. The preprint and the published version of the same work share it — quoting both is not corroboration. Independent corroboration means a different study, ideally by a different group. - Archive per references/citation-rules.md — for papers, a DOI is itself a durable identifier; still archive the specific page/PDF fetched, since DOI resolvers can change what they point to.
- Assign tier per references/source-tiers.md's academic table (1 = peer-reviewed; 2 = preprint; 3 = thesis/workshop paper without full review; 5 = predatory-journal/retracted) and purpose (usually
fact, sometimesimplementationfor methods papers with reproducible results). - Write the evidence record per engine/evidence-contract.md,
verification_status: pending. Do not self-verify.
Output
One evidence record per claim, appended to the run's evidence.jsonl.
Common mistakes
| Mistake | Fix |
| Recording a claim from a paper's abstract when it's load-bearing | Read the body text; abstracts overstate more often than expected |
| Tiering a preprint as peer-reviewed | Preprint is always tier 2 until publication is confirmed |
| Citing a paper without checking retraction status | Check retraction/correction databases before recording |
| Treating a blog's summary of a paper as the paper's own claim | Fetch the paper directly; if only the summary was reachable, say so in limitations |
| Assuming general web search covers the literature | Use the actual academic index — web search surfaces summaries, not sources |
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.

