DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to produce a literature review on a topic in one command with Academic Research Skills

Run /ars-lit-review on a topic to get a single-shot literature review draft from the Deep Research skills.

  • Research
  • Intermediate
  • 30 minutes
  • From the README
  • Claude Code

Who it is forA researcher starting work in a new area who needs an initial survey of sources before deciding on a research question.

The problemGathering and checking relevant sources for a new topic takes many hours of searching and reading before any writing starts.

The outcomeA literature review draft on your topic, with citations the Deep Research skills verify against the Semantic Scholar API, which you then check yourself.

What you need first

  • Claude Code CLI, VS Code, or JetBrains with the plugin marketplace available (plugin install needs v3.7.0+ of this repo)
  • An Anthropic API key set up as described in docs/SETUP.md
  • Optional: Pandoc or tectonic for DOCX or PDF output, per docs/SETUP.md
  • For the Claude Science path: a Claude Science account and this repo at v3.14.0+

Steps

  1. Run /plugin marketplace add Imbad0202/academic-research-skills
  2. Run /plugin install academic-research-skills
  3. Run /ars-lit-review "your topic" and replace the topic text with your own.
  4. Read the draft and check each cited source against the original paper before reuse.

Prompt for your agent

Using the repo Imbad0202/academic-research-skills in Claude Code, run /ars-lit-review on the topic <topic>. Expected output: a literature review draft with citations. Verify that every citation resolves to a real paper that supports the sentence it is attached to.

Caveat. The README says bibliographic resolvers receive data from your machine, and the README ties citation checking to Semantic Scholar, so review the data flows in docs/DATA_FLOWS.md before using private material.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page