wiki-research-academic
Skill0 starsChanged 4 months agoMITView on GitHub
Research academic papers from arXiv, DOI, or Semantic Scholar and ingest into raw/academic/. Invoked by wiki-research for paper requests.
In this repository36 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- wiki-extract-annasSkill
- wiki-extract-crunchbaseSkill
- wiki-extract-ebookSkill
- wiki-extract-ecommerceSkill
- wiki-extract-githubSkill
- wiki-extract-linkedinSkill
- wiki-extract-newsletterSkill
- wiki-extract-patentsSkill
- wiki-extract-paywallSkill
- wiki-extract-podcastSkill
- wiki-extractSkill
- wiki-extract-wikipediaSkill
- wiki-extract-youtubeSkill
- wiki-fetchSkill
- wiki-ingestSkill
- wiki-learnSkill
- wiki-lintSkill
- wiki-maintainerSkill
- wiki-onboardSkill
- wiki-pipelineSkill
- wiki-querySkill
- wiki-raw-prepareSkill
- wiki-research-deepSkill
- wiki-research-feedsSkill
- wiki-research-loopSkill
- wiki-research-newsSkill
- wiki-researchSkill
- wiki-research-socialSkill
- wiki-research-webSkill
- wiki-retroSkill
- wiki-session-memorySkill
- wiki-setupSkill
- wiki-statusSkill
- wiki-upgradeSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 104
Blog post explaining it: search <paper title> explained via wiki-research-web
- Very specific: line 112
Run each file through skills/wiki-research/references/source-eval.md.
- Very specific: line 147
CLI: Run llm-wiki integrations status and any llm-wiki line from Step 1 of this skill (from the vault root).
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Wiki research — academic
Fetches academic papers and metadata from arXiv, DOI resolvers, or Semantic Scholar into raw/academic/. Use this sub-skill when the input contains an arXiv ID, DOI, or phrases like "paper", "preprint", "study", "literature review".
Step 1 — Identify the source type
| Input signal | Action |
arXiv ID (e.g. 2301.12345 or https://arxiv.org/abs/2301.12345) | Fetch via arXiv API |
DOI (e.g. 10.1145/3442188.3445922) | Resolve via DOI → fetch landing page with wiki-research-web |
| Author + title search | Query arXiv API or Semantic Scholar search |
| Semantic Scholar URL | Fetch via Semantic Scholar API |
Step 2 — Fetch paper metadata and content
arXiv (primary for CS / ML / physics)
Fetch metadata:
curl "https://export.arxiv.org/api/query?id_list=<ARXIV_ID>&max_results=1" > /tmp/arxiv.xmlParse from XML: <title>, <author>, <published>, <summary> (abstract), <id> (canonical URL), <link> (PDF).
Fetch full paper (HTML version, preferred over PDF):
llm-wiki ingest firecrawl "https://arxiv.org/html/<ARXIV_ID>" \
--out academic/<year>/<arxiv-id>.md
# Fallback to abstract page if HTML not available:
llm-wiki ingest firecrawl "https://arxiv.org/abs/<ARXIV_ID>" \
--out academic/<year>/<arxiv-id>.mdSearch by keyword:
curl "https://export.arxiv.org/api/query?search_query=all:<QUERY>+AND+cat:cs.AI&max_results=10&sortBy=relevance" > /tmp/arxiv_search.xmlSee skills/wiki-research/references/query-design.md for query construction.
DOI resolver
# Resolve DOI to landing URL
curl -sI "https://doi.org/<DOI>" | grep -i location
# Then fetch the landing URL with wiki-research-webSemantic Scholar API
# Search
curl "https://api.semanticscholar.org/graph/v1/paper/search?query=<QUERY>&fields=title,authors,year,abstract,externalIds,openAccessPdf" > /tmp/s2.json
# Fetch by arXiv ID
curl "https://api.semanticscholar.org/graph/v1/paper/arXiv:<ARXIV_ID>?fields=title,authors,year,abstract,citationCount,references" > /tmp/s2_paper.jsonStep 3 — Write to raw/
Output path: raw/academic/<year>/<arxiv-id-or-slug>.md
For non-arXiv papers, use: raw/academic/<year>/<first-author-last-name>-<short-title>.md
Required frontmatter:
---
title: "<Paper Title>"
source_type: academic
source_url: https://arxiv.org/abs/<id>
fetched_date: YYYY-MM-DD
arxiv_id: "2301.12345" # omit if not arXiv
doi: "10.xxxx/..." # omit if not known
authors:
- "First Author"
- "Second Author"
year: YYYY
venue: "NeurIPS 2024" # conference/journal if known
abstract: |
<abstract text>
---
<full paper content or abstract + key sections>Step 4 — Check for related work
For important papers, optionally fetch:
- Cited-by papers (if high-impact): Semantic Scholar
citationsendpoint - HN discussion (if notable): search
site:news.ycombinator.com <paper title>via wiki-research-social - Blog post explaining it: search
<paper title> explainedvia wiki-research-web
Limit to 2–3 supplementary sources to avoid scope creep.
Step 5 — Evaluate and return to orchestrator
Run each file through skills/wiki-research/references/source-eval.md. Then return to wiki-research Step 3 (post-process).
Wiki citation format:
Chain-of-thought prompting improves multi-step reasoning (Wei et al., 2022 — `raw/academic/2022/wei-chain-of-thought.md`).Done looks like
- Papers or abstracts land under
raw/academic/with structured frontmatter; source-eval applied. - Control returned to wiki-research post-process (merge not done inside this skill alone).
Troubleshooting
| Symptom | Fix |
| arXiv HTML 404 | Paper predates HTML rendering; use /abs/ page or fetch PDF with marker adapter |
| arXiv API returns no results | Try broader query; remove category filter |
| DOI redirect loop | Try https://unpaywall.org/<DOI> for open-access version |
| Semantic Scholar rate limit (429) | Wait 60s; S2 public API allows ~100 req/5min |
| PDF only (no HTML) | Use llm-wiki ingest marker <PDF_PATH> if marker is installed |
Related skills
- wiki-research — orchestrator that invoked this skill
- wiki-research-web — for non-academic URLs
- wiki-research-social — for HN discussions of papers
- wiki-raw-prepare — for cleaning PDF/OCR output
Smoke check
- CLI: Run
llm-wiki integrations statusand anyllm-wikiline from Step 1 of this skill (from the vault root). - Prompt: Invoke this skill by name in Claude Code; complete Step 1 only and confirm expected CLI or file output.
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.

