agentleFS
jxtsejxtse/scientific-research-skills/skills/literature-search/SKILL.md

literature-search

Skill68 starsChanged 7 months agoMITView on GitHub

Searches and discovers academic papers across multiple sources (Semantic Scholar, arXiv, Tavily, Exa, Gemini deep research, AMiner, Google Scholar) with adaptive engine selection based on query type. Returns ranked, deduplicated results with metadata (authors, venue, year, citations, abstract, PDF link). Use when the user asks to find papers / literature / publications / preprints / references on a topic, search for related work, look up a specific paper by title or DOI or arXiv ID, find papers by an author, find recent SOTA / state-of-the-art work, survey a research area, or run a deep / comprehensive literature search with synthesis.

  • Reads credentials

22 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use systematic-review.

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.
  • xjtulycSkill

    systematic-review

    Use this Skill when conducting a systematic literature review following PRISMA 2020: PICO framework, database search strategy, title/abstract screening, full-text eligibility, data extraction, and GRADE evidence grading.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 5

    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
  1. Distinctive:

    Recency: All time vs. last N years vs.

    line 48
  2. Distinctive:

    If user wants to go deeper on any paper:

    line 116
  3. Very specific:

    Date filter for SOTA: Use --sort submittedDate on arXiv to find the latest approaches

    line 126
  4. Distinctive:

    Gemini for synthesis: When you need to understand a field (not just list papers), use Gemini deep research to get a narrative overview …

    line 127
  5. Distinctive:

    When ranking, weight these signals:

    line 131
  6. Distinctive:

    Author reputation: Check if senior authors are established in the field

    line 134

“Common” is measured: kept by at least 6 in 10 of the 16 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Literature Search

Systematic, multi-engine academic paper search.

When to Use

  • User asks "find papers about X"
  • User needs related work for a new project
  • User wants to know the state of the art on a topic
  • User asks for papers from a specific venue/author/year

Engine Selection

Choose engines based on the search goal:

GoalPrimary EngineSupplementary
Broad topic surveySemantic ScholararXiv, Tavily
Latest preprintsarXiv (sort by submittedDate)Semantic Scholar
Deep research / complex questionsGemini deep researchTavily + Exa
Specific paper by titleSemantic ScholarGoogle Scholar (via Tavily)
Papers by authorSemantic Scholar (author search)AMiner
Chinese research communityAMinerSemantic Scholar
Industry/applied papersTavily (deep)Exa semantic search
Social buzz / trending papersTwitter/X (xreach)Reddit
Code implementationsGitHub (gh search)Exa (get_code_context)
Finding similar papersExa (semantic)Semantic Scholar (citations)

Workflow

Step 1: Understand the Query

Before searching, clarify:

  • Scope: Broad survey vs. specific subtopic
  • Recency: All time vs. last N years vs. latest only
  • Venue preference: Top-tier only? Specific conference?
  • Quantity: Top 5 vs. comprehensive survey
  • Depth: Quick list vs. deep research with synthesis

Step 2: Select Search Strategy

Quick search (single engine): For simple, well-defined queries. Use Semantic Scholar or arXiv directly.

Multi-engine search (2-3 engines in parallel): For broader topics. Run engines simultaneously, deduplicate results.

Deep research (Gemini): For complex, multi-faceted research questions. Gemini deep research mode synthesizes across many sources and provides a structured analysis with citations. Use this when:

  • The question spans multiple subfields
  • You need synthesis, not just a list of papers
  • The user explicitly asks for "deep research" or "comprehensive survey"

Step 3: Execute Search

# Semantic Scholar — paper metadata, citations, author search
# Free, no API key needed
node scripts/search/semantic-scholar.mjs "query" -n 20

# arXiv — latest preprints, category filtering
# Free, no API key needed
node scripts/search/arxiv.mjs "query" -n 15 --sort submittedDate --cat cs.CL

# Tavily — general web search, AI-optimized
node scripts/search/search.mjs "query site:arxiv.org OR site:aclanthology.org" -n 10
node scripts/search/search.mjs "query" --deep  # deeper search mode

# Exa — semantic search, finding similar content
mcporter call 'exa.web_search_exa(query: "query", numResults: 10)'

# Gemini — deep research (for complex questions)
# Use gemini-3.1-pro model with web search grounding
# Prompt: "Survey the recent literature on [topic]. Identify key papers,
#          main approaches, and open problems. Cite specific papers."

# AMiner — Chinese academic community
# Uses AMINER_API_KEY

Step 4: Deduplicate & Rank

Merge results across engines:

  1. Deduplicate by title similarity (fuzzy match, >90% = same paper)
  2. Rank by: citation count × recency × venue tier × relevance
  3. Flag if a paper appears in multiple engines (higher confidence)

Step 5: Present Results

Format as a ranked list with key metadata:

1. **[Title]** (Venue Year, Citations: N)
   Authors: [First author] et al.
   TL;DR: [1 sentence]
   Why relevant: [connection to user's query]

2. ...

Step 6: Deep Dive (Optional)

If user wants to go deeper on any paper:

  • Switch to paper-reading skill
  • Or add to Zotero reading queue (use zotero-management skill)

Search Tips

  • Use specific terminology: "multi-agent reinforcement learning" > "MARL" > "agents working together"
  • Combine with venue filter: Adding venue:ACL or category cs.CL dramatically improves precision
  • Check citation chains: A highly-cited paper's references and citers are often gold
  • Cross-lingual: For Chinese papers, try both English and Chinese queries
  • Date filter for SOTA: Use --sort submittedDate on arXiv to find the latest approaches
  • Gemini for synthesis: When you need to understand a field (not just list papers), use Gemini deep research to get a narrative overview first, then drill into specific papers

Quality Signals

When ranking, weight these signals:

  • Citation count: High for established work, less meaningful for papers < 6 months old
  • Venue tier: ACL/EMNLP/NeurIPS/ICML > workshops > arXiv-only
  • Author reputation: Check if senior authors are established in the field
  • Code availability: Papers with code are more verifiable
  • Reproducibility: Clear methodology sections and experimental details

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.