AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Lit Review

skill-dgilford-ai-science-toolkit-lit-review · by dgilford

Search and synthesize scientific literature from Zotero, arxiv, bioRxiv, Google Scholar, and Consensus. Use when framing a research question, designing methods, interpreting results, mapping the field landscape, or identifying future directions.

No reviews yet
0 installs
18 views
0.0% view→install

Install

$ agentstack add skill-dgilford-ai-science-toolkit-lit-review

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access Used
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets Used
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-dgilford-ai-science-toolkit-lit-review)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
23d ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Lit Review? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Conduct a literature search and deliver a structured scientific briefing. See [REFERENCE.md](REFERENCE.md) for mode-specific guidance.

On invocation, ask the user

  1. Topic — what are we searching for?
  2. Modeframe / methods / interpret / landscape / synthesize
  3. Starting point (optional) — any known papers, authors, or search terms to seed from?

Search order

  1. Zotero — existing library first; note what's already there
  2. Consensus — synthesized search for landscape and key claims
  3. Google Scholar — seminal works, citation counts, author networks
  4. arxiv / bioRxiv — recent and unpublished work

Stop adding sources once coverage is sufficient for the mode.

Output structure

1. High-level summary — 1–2 paragraphs: what the field looks like, what is settled, what is contested. Tag findings as established / debated / emerging throughout.

2. Topical review — key ideas, findings, and debates organized by theme. Apply mode-specific guidance from REFERENCE.md. Distinguish what is well-established, actively debated, and absent.

3. Papers — for each paper:

  • Full citation (authors, year, title, journal/venue)
  • Peer-reviewed or preprint — flag explicitly
  • Key contribution in 1–2 sentences
  • Relevance to the current topic and mode

4. Offers — always prompt:

  • Save to REFERENCES.md? — check if it exists and show existing entries first. Append using the template in REFERENCE.md. Never overwrite.
  • Add to Zotero? — list papers not already in the library, then ask. If yes, execute the steps below.

Adding papers to Zotero

Required env vars (set in ~/.claude/settings.jsonenv block):

  • ZOTERO_USER_ID — your numeric Zotero user ID (find it at zotero.org/settings/keys)
  • ZOTERO_API_KEY — a Zotero API key with write access (same page)
  • ZOTERO_INBOX_COLLECTION — name of the collection to file new papers into (e.g. Inbox)

If any required var is unset, skip the Zotero write step and tell the user what to configure.

Step 1 — resolve the collection key:

curl -s "https://api.zotero.org/users/$ZOTERO_USER_ID/collections?limit=100" \
  -H "Zotero-API-Key: $ZOTERO_API_KEY" \
  | python3 -c "
import sys, json, os
cols = json.load(sys.stdin)
target = os.environ.get('ZOTERO_INBOX_COLLECTION', 'Inbox')
for c in cols:
    if c['data']['name'] == target:
        print(c['key'])
"

Step 2 — POST items. Build a JSON array; one object per paper. Use itemType journalArticle for peer-reviewed, preprint for arxiv/bioRxiv. Include collections: [\"\"] from Step 1.

Minimum required fields per item:

  • itemType, title, date
  • creators: [{"creatorType": "author", "firstName": "...", "lastName": "..."}]
  • DOI or url (include both when available)
  • collections: [""]
  • tags: [{"tag": "lit-review"}]
curl -s -X POST "https://api.zotero.org/users/$ZOTERO_USER_ID/items" \
  -H "Zotero-API-Key: $ZOTERO_API_KEY" \
  -H "Content-Type: application/json" \
  -d ''

Step 3 — report results. Parse the response: list titles that succeeded (HTTP 200 success key) and any that failed (failed key). A paper already in the library does not need to be re-added.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.