tooluniverse-literature-deep-research▌
mims-harvard/tooluniverse · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Systematic literature research: disambiguate, search with collision-aware queries, grade evidence, produce structured reports.
Literature Deep Research
Systematic literature research: disambiguate, search with collision-aware queries, grade evidence, produce structured reports.
KEY PRINCIPLES: (1) Disambiguate first (2) Right-size deliverable (3) Grade every claim T1-T4 (4) All sections mandatory even if "limited evidence" (5) Source attribution for every claim (6) English-first queries, respond in user's language (7) Report = deliverable, not search log
LOOK UP, DON'T GUESS
Search PubMed/EuropePMC FIRST before reasoning. A published paper beats memory.
Factoid search strategy:
- Extract KEY TERMS (most specific nouns/verbs)
EuropePMC_search_articles(query="term1 term2 term3", limit=5)- No results -> BROADEN (remove most restrictive term)
- Too many -> NARROW (add specific terms)
- Answer usually in abstract of top results
- Failed query -> try DIFFERENT TERMS/synonyms, don't repeat
COMPUTE, DON'T DESCRIBE
When analysis requires computation (statistics, data processing, scoring, enrichment), write and run Python code via Bash. Don't describe what you would do — execute it and report actual results. Use ToolUniverse tools to retrieve data, then Python (pandas, scipy, statsmodels, matplotlib) to analyze it.
Workflow
Phase 0: Clarify + Mode Select → Phase 1: Disambiguate + Profile → Phase 2: Literature Search → Phase 3: Report
Phase 0: Mode Selection
| Mode | When | Deliverable |
|---|---|---|
| Factoid | Single concrete question | 1-page fact-check report + bibliography |
| Mini-review | Narrow topic | 1-3 page narrative |
| Full Deep-Research | Comprehensive overview | 15-section report + bibliography |
Factoid Mode (Fast Path)
# [TOPIC]: Fact-check Report
## Question / ## Answer (with evidence rating) / ## Source(s) / ## Verification Notes / ## Limitations
Domain Detection
| Pattern | Domain | Action |
|---|---|---|
| Gene/protein symbol | Biological target | Full bio disambiguation |
| Drug name | Drug | Drug disambiguation (1.5) |
| Disease name | Disease | Disease disambiguation (1.6) |
| CS/ML topic | General academic | Skip bio tools, literature-only |
| Cross-domain | Interdisciplinary | Resolve each entity in its domain |
Cross-Skill Delegation
- Gene/protein deep-dive:
tooluniverse-target-research - Drug profile:
tooluniverse-drug-research - Disease profile:
tooluniverse-disease-research
Use this skill for literature synthesis. Use specialized skills for entity profiling. For max depth, run both.
Phase 1: Subject Disambiguation + Profile
1.1 Biological Target Resolution
UniProt_search → UniProt_get_entry_by_accession → UniProt_id_mapping
ensembl_lookup_gene → MyGene_get_gene_annotation
1.2 Naming Collision Detection
Check first 20 results. If >20% off-topic, build negative filter: NOT [collision1] NOT [collision2].
Gene family: "ADAR" NOT "ADAR2" NOT "ADARB1". Cross-domain: add context terms.
1.3 Baseline Profile (Bio Targets)
InterPro_get_protein_domains, UniProt_get_ptm_processing_by_accession, HPA_get_subcellular_location,
GTEx_get_median_gene_expression, GO_get_annotations_for_gene, Reactome_map_uniprot_to_pathways,
STRING_get_protein_interactions, intact_get_interactions, OpenTargets_get_target_tractability_by_ensemblID
GPCR targets: delegate to tooluniverse-target-research.
1.5 Drug Disambiguation
Identity: OpenTargets_get_drug_chembId_by_generic_name, ChEMBL_get_drug, PubChem_get_CID_by_compound_name, drugbank_get_drug_basic_info_by_drug_name_or_id
Targets: ChEMBL_get_drug_mechanisms, OpenTargets_get_associated_targets_by_drug_chemblId, DGIdb_get_drug_gene_interactions
Safety: OpenTargets_get_drug_adverse_events_by_chemblId, OpenTargets_get_drug_indications_by_chemblId, search_clinical_trials
1.6 Disease Disambiguation
OpenTargets disease search → EFO/MONDO IDs
DisGeNET_get_disease_genes, DisGeNET_search_disease
CTD_get_disease_chemicals
1.7 Compound Queries (e.g., "metformin in breast cancer")
Resolve both entities, then cross-reference via CTD_get_chemical_gene_interactions, CTD_get_chemical_diseases, OpenTargets drug-target/drug-disease tools. Intersect shared targets/pathways.
1.8 General Academic / 1.9 Interdisciplinary
Non-bio: skip bio tools, use ArXiv/DBLP/OSF. Cross-domain: resolve bio entities with 1.1-1.3, search CS/general in parallel, merge and cross-reference.
Phase 2: Literature Search
Methodology stays internal. Report shows findings, not process.
2.1 Query Strategy
Step 1: Seeds (15-30 core papers): domain-specific title searches with date/sort filters.
Step 2: Citation expansion: PubMed_get_cited_by, EuropePMC_get_citations/references, PubMed_get_related, SemanticScholar_get_recommendations, OpenCitations_get_citations
Step 3: Collision-filtered broader queries: "[TERM]" AND ([context]) NOT [collision]
2.2 Literature Tools
Biomedical: PubMed_search_articles, PMC_search_papers, EuropePMC_search_articles, PubTator3_LiteratureSearch
Biology (ecology/evolution/plant): EuropePMC as PRIMARY (PubMed returns 0-1 for non-clinical biology). Also openalex_literature_search.
CS/ML: ArXiv_search_papers, DBLP_search_publications, SemanticScholar_search_papers
General: openalex_literature_search, Crossref_search_works, CORE_search_papers, DOAJ_search_articles
Preprints: BioRxiv_get_preprint, MedRxiv_get_preprint, OSF_search_preprints, EuropePMC_search_articles(source='PPR')
Multi-source: advanced_literature_search_agent (12+ DBs; needs Azure key -- fallback: query PubMed+ArXiv+SemanticScholar+OpenAlex individually)
Citation impact: iCite_search_publications (RCR/APT), iCite_get_publications (by PMID), scite_get_tallies (support/contradict). PubMed-only; for CS use SemanticScholar.
2.3-2.4 Full-Text & PubMed Zero-Result Fallback
Full-text: see FULLTEXT_STRATEGY.md for three-tier strategy.
CRITICAL: PubMed returns 0 for ~30% of valid queries. Always retry with EuropePMC when PubMed returns empty. This is not optional.
2.5 Tool Failure / OA Handling
Retry once -> fallback tool. Key fallbacks: PubMed_get_cited_by -> EuropePMC_get_citations -> OpenCitations. OA: Unpaywall if configured, else Europe PMC/PMC/OpenAlex flags.
Phase 3: Evidence Grading
| Tier | Label | Bio Example | CS/ML Example |
|---|---|---|---|
| T1 | Mechanistic | CRISPR KO + rescue, RCT | Formal proof, controlled ablation |
| T2 | Functional | siRNA knockdown phenotype | Benchmark with baselines |
| T3 | Association | GWAS, screen hit | Observational, case study |
| T4 | Mention | Review article | Survey, workshop abstract |
Inline: Target X regulates Y [T1: PMID:12345678]. Per theme: summarize evidence distribution.
Report Output
| File | Mode |
|---|---|
[topic]_report.md |
Full |
[topic]_factcheck_report.md |
Factoid |
[topic]_bibliography.json + .csv |
All |
Progressive update: create report with all section headers immediately. Fill after each phase. Write Executive Summary LAST.
Use 15-section template from REPORT_TEMPLATE.md. Domain adaptations: bio (architecture/expression/GO/disease), drug (properties/MOA/PK/safety), disease (epi/patho/genes/treatments), general (history/theories/evidence/applications).
Communication
Brief progress updates only: "Resolving identifiers...", "Building paper set...", "Grading evidence..." Do NOT expose: raw tool outputs, dedup counts, search round details.
References
TOOL_NAMES_REFERENCE.md-- 123 tools with parametersREPORT_TEMPLATE.md-- template, domain adaptations, bibliography, completeness checklistFULLTEXT_STRATEGY.md-- three-tier full-text verificationWORKFLOW.md-- compact cheat-sheetEXAMPLES.md-- worked examples
How to use tooluniverse-literature-deep-research on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add tooluniverse-literature-deep-research
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches tooluniverse-literature-deep-research from GitHub repository mims-harvard/tooluniverse and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate tooluniverse-literature-deep-research. Access the skill through slash commands (e.g., /tooluniverse-literature-deep-research) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.7★★★★★73 reviews- ★★★★★Omar Mensah· Dec 28, 2024
I recommend tooluniverse-literature-deep-research for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Ishan Tandon· Dec 28, 2024
tooluniverse-literature-deep-research fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Noor Malhotra· Dec 16, 2024
Solid pick for teams standardizing on skills: tooluniverse-literature-deep-research is focused, and the summary matches what you get after install.
- ★★★★★Lucas Martinez· Dec 12, 2024
Registry listing for tooluniverse-literature-deep-research matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Noor Kapoor· Dec 12, 2024
tooluniverse-literature-deep-research has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Min Flores· Nov 23, 2024
We added tooluniverse-literature-deep-research from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Zaid Yang· Nov 19, 2024
tooluniverse-literature-deep-research fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Min Zhang· Nov 19, 2024
I recommend tooluniverse-literature-deep-research for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Rahul Santra· Nov 15, 2024
Keeps context tight: tooluniverse-literature-deep-research is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Noor Chawla· Nov 7, 2024
tooluniverse-literature-deep-research has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 73