auto-review-loop
Adversarial iterative review loop with generator-evaluator separation. Up to 4 rounds of independent review, improvement, and…
Retrieves papers from local folder or ArXiv and Semantic Scholar using domain-aware keyword expansion, builds synthesis matrix, identifies gaps. Calls tools/arxiv_fetch.py and tools/semantic_scholar_fetch.py. Writes to output/paper-cache/ and output/LIT_REVIEW_REPORT.md.
$ npx -y skills add grind-lab-core/night_owl_research_agent --skill lit-review --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/lit-reviewContext preview
The summary Claude sees to decide when to auto-load this skill.
Retrieves papers from local folder or ArXiv and Semantic Scholar using domain-aware keyword expansion, builds synthesis matrix, identifies gaps. Calls tools/arxiv_fetch.py and tools/semantic_scholar_fetch.py. Writes to output/paper-cache/ and output/LIT_REVIEW_REPORT.md.
name: lit-review description: Retrieves papers from local folder or ArXiv and Semantic Scholar using domain-aware keyword expansion, builds synthesis matrix, identifies gaps. Calls tools/arxiv_fetch.py and tools/semantic_scholar_fetch.py. Writes to output/paper-cache/ and output/LIT_REVIEW_REPORT.md. argument-hint: [paper-topic-or-url] tools: Bash, Read, Write, WebFetch, WebSearch, Agent, Glob, Grep,
You perform a targeted literature review for $ARGUMENTS. Your outputs feed idea discovery and paper writing. This skill checks multiple sources **in priority order**. All are optional — if a source is not configured or not requested, skip it silently.
Research topic: $ARGUMENTS
---
1. `papers/` in the current project directory 2. Custom path specified by user in `CLAUDE.md` under `## Constants`
> 💡 Overrides: > - `/lit-review "topic" — paper library: ~/my_papers/` — custom local PDF path
Parse `$ARGUMENTS` for a `— sources:` directive:
Examples:
/lit-review "diffusion models" → all (default, no S2) /lit-review "diffusion models" — sources: all → all (default, no S2) /lit-review "diffusion models" — sources: zotero → Zotero only /lit-review "diffusion models" — sources: zotero, web → Zotero + web /lit-review "diffusion models" — sources: local → local PDFs only /lit-review "topic" — sources: obsidian, local, web → skip Zotero /lit-review "topic" — sources: web, semantic-scholar → web + S2 API (IEEE/ACM venue papers) /lit-review "topic" — sources: all, semantic-scholar → all + S2 API
| Priority | Source | ID | How to detect | What it provides | |----------|--------|----|---------------|-----------------| | 1 | **Zotero** (via MCP) | `zotero` | Try calling any `mcp__zotero__*` tool — if unavailable, skip | Collections, tags, annotations, PDF highlights, BibTeX, semantic search | | 2 | **Obsidian** (via MCP) | `obsidian` | Try calling any `mcp__obsidian-vault__*` tool — if unavailable, skip | Research notes, paper summaries, tagged references, wikilinks | | 3 | **Local PDFs** | `local` | `Glob: papers/**/*.pdf` | Raw PDF content (first 3 pages) | | 4 | **Web search** | `web` | Always available (WebSearch) | arXiv, Semantic Scholar, Google Scholar | | 5 | **Semantic Scholar API** | `semantic-scholar` | `tools/semantic_scholar_fetch.py` exists | Published venue papers (IEEE, ACM, Springer) with structured metadata: citation counts, venue info, TLDR. **Only runs when explicitly requested** via `— sources: semantic-scholar` or `— sources: web, semantic-scholar` |
> **Graceful degradation**: If no MCP servers are configured, the skill works exactly as before (local PDFs + web search). Zotero and Obsidian are pure additions.
**Skip this step entirely if Zotero MCP is not configured.**
Try calling a Zotero MCP tool (e.g., search). If it succeeds:
1. **Search by topic**: Use the Zotero search tool to find papers matching the research topic 2. **Read collections**: Check if the user has a relevant collection/folder for this topic 3. **Extract annotations**: For highly relevant papers, pull PDF highlights and notes — these represent what the user found important 4. **Export BibTeX**: Get citation data for relevant papers (useful for `/paper-draft` later) 5. **Compile results**: For each relevant Zotero entry, extract:
> 📚 Zotero annotations are gold — they show what the user personally highlighted as important, which is far more valuable than generic summaries.
**Skip this step entirely if Obsidian MCP is not configured.**
Try calling an Obsidian MCP tool (e.g., search). If it succeeds:
1. **Search vault**: Search for notes related to the research topic 2. **Check tags**: Look for notes tagged with relevant topics (e.g., `#diffusion-models`, `#paper-review`) 3. **Read research notes**: For relevant notes, extract the user's own summaries and insights 4. **Follow links**: If notes link to other relevant notes (wikilinks), follow them for additional context 5. **Compile results**: For each relevant note:
> 📝 Obsidian notes represent the user's **processed understanding** — more valuable than raw paper content for understanding their perspective.
Before searching online, check if the user already has relevant papers locally:
1. **Locate library**: Check **PAPER_LIBRARY** paths for PDF files
Glob: papers/**/*.pdf
2. **De-duplicate against Zotero**: If Step 0a found papers, skip any l
A fully automatic, domain-aware AI research agent for Geoscientists, Remote Sensing researchers, and GIScientists — powered entirely by Claude Code skills.
Adversarial iterative review loop with generator-evaluator separation. Up to 4 rounds of independent review, improvement, and…
Discover, evaluate, and download publicly available datasets from the internet. Infers data needs from a research question or…
Deploy and run experiments for ML/DL training (local, remote, or Modal GPU) AND spatial data science / GIScience experiments…
Run an end-to-end workflow that chains the skills `refine-research` and `experiment-design`. Use when the user wants a one-shot…
Turn a refined GIScience / remote sensing / spatial data science proposal into a detailed, claim-driven experiment roadmap. Use…
Complete 4-stage end-to-end research pipeline. Orchestrates idea-discovery-pipeline → deploy-experiment → auto-review-loop →…