
Literature Search
- 20 installs
- 869 repo stars
- Updated June 8, 2026
- beita6969/scienceclaw
Literature-search is a Claude meta skill that orchestrates scientific paper search across Semantic Scholar, OpenAlex, arXiv, PubMed, and CrossRef with deduplication, ranking, and a zero-hallucination citation rule.
About
Literature-search is a meta skill that orchestrates comprehensive scientific paper searches across Semantic Scholar, OpenAlex, arXiv, PubMed, and CrossRef. It defines a mandatory protocol that starts with Semantic Scholar, adds OpenAlex and discipline-specific databases, then deduplicates, ranks, and chains citations. A strict zero-hallucination rule requires every citation detail to come from a real API call in the conversation.
- Orchestrates Semantic Scholar, OpenAlex, arXiv, PubMed, and CrossRef searches
- Enforces a mandatory search protocol with dedup, ranking, and citation chaining
- Applies a zero-hallucination rule requiring real API results for every citation
Literature Search by the numbers
- 20 all-time installs (skills.sh)
- Ranked #999 of 1,879 Documentation skills by installs in the Skillselion catalog
- Data as of Aug 2, 2026 (Skillselion catalog sync)
literature-search capabilities & compatibility
Free; uses open scientific database APIs
- Capabilities
- literature review · lit synthesizer · linguistics analysis
- Use cases
- research · web search
- Pricing
- Free
What literature-search says it does
Comprehensive multi-database scientific literature search orchestrating Semantic Scholar, OpenAlex, arXiv, PubMed, and CrossRef.
Every citation detail must come from a tool result in this conversation.
npx skills add https://github.com/beita6969/scienceclaw --skill literature-searchAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 20 |
|---|---|
| repo stars | ★ 869 |
| Last updated | June 8, 2026 |
| Repository | beita6969/scienceclaw ↗ |
What it does
Find and rank all relevant papers on a topic across multiple scientific databases with real API calls.
Who is it for?
Comprehensive multi-database paper discovery and building bibliographies for a topic.
Skip if: Single-database queries or data analysis.
When should I use this skill?
You need to find all relevant papers on a topic across multiple scientific databases.
What you get
A deduplicated, relevance-ranked list of real papers with verifiable identifiers pulled from live database APIs.
- A ranked, deduplicated list of papers with verifiable identifiers
By the numbers
- Orchestrates 5 databases
- 6-step mandatory search protocol
- OpenAlex covers 250M+ works
Files
Literature Search (Meta Skill)
Orchestrate comprehensive literature searches across multiple databases. Always execute real API calls — never fabricate results or rely on training data.
Priority Order of Databases
1. Semantic Scholar (PRIMARY) — best relevance ranking, AI TLDR summaries, citation graph 2. OpenAlex (PRIMARY) — 250M+ works, powerful filtering, open access URLs 3. arXiv — preprints in physics, math, CS, biology, finance, statistics 4. PubMed — biomedical and life sciences (NCBI may be unreachable from some networks) 5. CrossRef — DOI resolution and metadata only (NOT for search — poor relevance ranking)
IMPORTANT: CrossRef search results are poorly ranked by relevance. Never use CrossRef as the primary search engine. Use it only for DOI-based lookups and metadata enrichment.
Mandatory Search Protocol
Every literature search MUST follow this protocol:
Step 1: Semantic Scholar Search (always do this first)
# Primary search — returns papers ranked by relevance with AI summaries
curl -s "https://api.semanticscholar.org/graph/v1/paper/search?\
query=YOUR+SEARCH+TERMS&limit=10&\
fields=title,authors,year,abstract,citationCount,influentialCitationCount,\
isOpenAccess,openAccessPdf,url,externalIds,tldr,venue,publicationDate"Parse results with:
| python3 -c "
import sys, json
data = json.load(sys.stdin)
print(f'Total: {data[\"total\"]} papers')
for i, p in enumerate(data['data']):
authors = ', '.join(a['name'] for a in (p.get('authors') or [])[:3])
if len(p.get('authors') or []) > 3: authors += ' et al.'
tldr = p.get('tldr', {})
tldr_text = tldr['text'][:150] if tldr else 'N/A'
oa = '🔓' if p.get('isOpenAccess') else '🔒'
doi = (p.get('externalIds') or {}).get('DOI', '')
print(f'[{i+1}] {p[\"title\"]}')
print(f' {authors} ({p.get(\"year\",\"?\")}) — {p.get(\"venue\",\"?\")}')
print(f' Cited: {p.get(\"citationCount\",0)} (influential: {p.get(\"influentialCitationCount\",0)}) {oa}')
print(f' TLDR: {tldr_text}')
print(f' DOI: {doi}')
print()
"Useful filters:
year=2022-2025— restrict by year rangefieldsOfStudy=Computer Science— filter by disciplineminCitationCount=10— only cited papers
Step 2: OpenAlex Search (for broader coverage + OA links)
# Complementary search with powerful filtering
curl -s "https://api.openalex.org/works?\
search=YOUR+SEARCH+TERMS&per_page=10&\
sort=relevance_score:desc&\
select=title,publication_year,cited_by_count,doi,authorships,open_access,\
primary_location,abstract_inverted_index&\
mailto=scienceclaw@openclaw.ai"Useful filters (append to URL as &filter=):
publication_year:2023-2025— year rangecited_by_count:>50— minimum citationsopen_access.is_oa:true— only open accessauthorships.author.id:A5023888391— by author OpenAlex IDconcepts.id:C41008148— by concept (e.g., Computer Science)
Step 3: Discipline-Specific Database (if relevant)
| Discipline | Additional Database | Skill |
|---|---|---|
| Biomedicine / Clinical | PubMed | pubmed-search |
| Physics / CS / Math | arXiv | arxiv-search |
| Computer Science | DBLP | dblp-search |
| Economics / Social Sci | SSRN/RePEc | ssrn-econpapers |
Step 4: Deduplication and Ranking
Match across databases by DOI (most reliable), then normalized title. Rank by: Semantic Scholar relevance > citation count > influential citations > recency.
Step 5: Citation Chaining (for thorough searches)
For top 3-5 seed papers, retrieve their references and citations:
# Forward citations (who cites this paper)
curl -s "https://api.semanticscholar.org/graph/v1/paper/{paperId}/citations?\
fields=title,year,citationCount,venue&limit=20"
# Backward references (what this paper cites)
curl -s "https://api.semanticscholar.org/graph/v1/paper/{paperId}/references?\
fields=title,year,citationCount,venue&limit=20"Step 6: Paper Recommendations (for discovery)
# Find similar papers
curl -s "https://api.semanticscholar.org/recommendations/v1/papers/\
forpaper/{paperId}?fields=title,year,citationCount,tldr&limit=10"Search Quality Checklist
Before presenting results, verify:
- [ ] At least Semantic Scholar was searched with a real API call
- [ ] Results contain real DOIs/paper IDs (not fabricated)
- [ ] Citation counts are from the API (not estimated)
- [ ] Each paper has a verifiable identifier (DOI, arXiv ID, PMID, or S2 URL)
- [ ] TLDR summaries are from Semantic Scholar (not self-generated)
Output Format
[1] Title
Authors (Year) — Venue
Cited: N (influential: M) 🔓/🔒
TLDR: AI-generated summary from Semantic Scholar
DOI: 10.xxxx/xxxxx | arXiv: xxxx.xxxxx | PMID: xxxxxxxx
URL: https://...Zero-Hallucination Rule (ABSOLUTE)
Every citation detail must come from a tool result in this conversation.
- NEVER fabricate or "fill in" paper titles, authors, DOIs, PMIDs, citation counts, or journal names from training data
- NEVER say "a well-known study by X et al." without having searched for it first
- If a search returns 0 results, report that honestly — do not substitute training knowledge
- If a tool returns partial metadata (title but no DOI), report only what the tool returned
- Before presenting any paper, verify: Did a tool in THIS conversation return this information?
Common Pitfalls to Avoid
1. DO NOT use CrossRef /works?query= for discovery — its relevance ranking is poor 2. DO NOT fabricate paper titles, authors, or DOIs from training knowledge 3. DO NOT skip API calls and rely on what you "know" about the literature 4. DO NOT present Semantic Scholar TLDRs as your own analysis 5. ALWAYS run the actual curl commands and parse real responses 6. ALWAYS include at least one verifiable identifier per paper 7. ALWAYS self-check: every detail in your response must trace back to a tool result
Rate Limits
| Database | Without Key | With Key |
|---|---|---|
| Semantic Scholar | 100 req/5 min | 1/sec sustained |
| OpenAlex | 10 req/sec (polite pool with mailto) | Same |
| arXiv | ~1 req/3 sec | Same |
| CrossRef | 1 req/sec | 50 req/sec (with mailto) |
Related skills
FAQ
Which database does it search first?
Semantic Scholar always goes first for its relevance ranking and AI TLDR summaries, followed by OpenAlex.
Does it ever use training data for citations?
No. Its zero-hallucination rule requires every citation detail to come from a real API result in the conversation.