collaborative-deep-research/agent-papers-cli
4 skills565 installs176 starsGitHub
Install
npx skills add https://github.com/collaborative-deep-research/agent-papers-cliSkills in this repo
1Literature ReviewLiterature-review is an agent skill for solo builders and researchers who need a disciplined survey before betting on an AI, ML, or technical idea. It drives a systematic review using the paper and paper-search CLIs: clarify topic boundaries and year range, run several query variants on Semantic Scholar (and Google Scholar), deduplicate hits, skim to label relevance, then deeply outline and section-read the best papers while capturing structured notes. Default assumptions—roughly five years of literature and fifteen to twenty core papers—keep indie projects scoped. Use when someone asks for a literature review, survey, or systematic overview, not for quick blog citations. Bash-backed tooling is required, so the agent can execute searches and writes the synthesized output you approve.562installs2Deep ResearchDeep-research is an agent skill that walks a solo builder through systematic topic investigation using the paper and paper-search CLI tools. It starts with wide web and Semantics Scholar queries, then refines with year, citation, and domain filters (including PubMed when biomedical). For the strongest hits, the agent outlines, skims, and reads sections of papers, browses key URLs, and walks citations and references to build context. It fits indie builders who need evidence-backed answers before scoping a product, picking a stack, or writing a spec—not a quick single-query chat answer. The workflow is procedural and repeatable, so you can hand the same ritual to Claude Code, Cursor, or Codex whenever a question deserves primary sources and traceable citations rather than model recall alone.1installs3Fact CheckFact-check is an agent skill from the agent-papers-cli stack that turns a single bold statement into an evidence-backed assessment solo builders can trust before they write landing copy, pitch decks, or technical posts. When a user asks to verify, fact-check, or confirm something, the skill first decomposes the claim into verifiable sub-claims, then runs structured paper-search queries across the open web and Semantic Scholar, drills into arXiv sections or browsed URLs for primary material, assigns one of four verdicts per sub-claim, and finishes with an overall assessment plus cited URLs. It fits indie researchers who cannot afford a human fact desk but still need to avoid publishing hallucinated statistics or misquoted papers. The allowed-tools surface (Bash, Read, Glob, Grep, Write) implies network-backed CLI search rather than guesswork from model weights. Use it in early Idea research, during Validate when testing positioning claims, or in Launch/Grow when auditing public-facing statements. It is not a legal compliance review or real-time news wire—latency and coverage depend on what paper-search returns.1installs4Research CoordinatorResearch Coordinator is a meta-orchestration skill for solo builders and agent users who receive open-ended research questions too large for one prompt. It sits above specialized workflows—deep investigation, systematic literature review, and targeted fact checking—and chooses the right path after analyzing intent. When the ask is compound, it decomposes work and dispatches multiple general-purpose subagents, each seeded with the appropriate skill file content and tooling access for academic paper and search CLIs. The coordinator synthesizes outcomes rather than replacing domain depth in child skills. It matches indie founders validating markets, engineers surveying prior art, or operators verifying claims before shipping copy. Ambiguity triggers a clarify-first gate so you do not waste subagent runs on the wrong workflow. Treat it as the front door to a papers-aware research stack, not a single-shot summarizer.1installs