wu-yc/labclaw/tooluniverse-literature-deep-research
Claude Code and agent skill by wu-yc/labclaw
- community
Checking that the SKILL.md file is still in the repository.
Conduct comprehensive literature research with target disambiguation, evidence grading, and structured theme extraction. Creates a detailed report with mandatory completeness checklist, biological model synthesis, and testable hypotheses. For biological targets, resolves official IDs (Ensembl/UniProt), synonyms, naming collisions, and gathers expression/pathway context before literature search. Default deliverable is a report file; for single factoid questions, uses a fast verification mode and may include an inline answer. Use when users need thorough literature reviews, target profiles, or to verify specific claims from the literature.
Install
npx vskill@latest install wu-yc/labclaw/tooluniverse-literature-deep-researchSKILL.md
Literature Deep Research Strategy (Enhanced)
A systematic approach to comprehensive literature research that starts with target disambiguation to prevent missing details, uses evidence grading to separate signal from noise, and produces a content-focused report with mandatory completeness sections.
KEY PRINCIPLES:
- Target disambiguation FIRST - Resolve IDs, synonyms, naming collisions before literature search
- Right-size the deliverable - Use Factoid / Verification Mode for single, answerable questions; use full report mode for “deep research”
- Report-first output - Default deliverable is a report file; an inline answer is allowed (and recommended) for Factoid / Verification Mode
- Evidence grading - Grade every claim by evidence strength (mechanistic paper vs screen hit vs review vs text-mined)
- Mandatory completeness - All checklist sections must exist, even if "unknown/limited evidence"
- Source attribution - Every piece of information traceable to database/tool
- English-first queries - Always use English terms for literature searches and tool calls, even if the user writes in another language. Only try original-language terms as a fallback if English returns no results. Respond in the user's language
Workflow Overview
Phase 0: Initial Clarification
Mandatory Questions
- Target type: Is this a biological target (gene/protein), a general topic, or a disease?
- Scope: Is this a single factoid to verify (“Which antibiotic?”, “Which strain?”, “Which year?”) or a comprehensive/deep review?
- Known aliases: Any specific gene symbols or protein names you use?
- Constraints: Open access only? Include preprints? Specific organisms?
- Methods appendix: Do you want methodology details in a separate file?
Mode Selection (CRITICAL)
Pick exactly one mode based on the user’s intent and the question structure:
- Factoid / Verification Mode (single concrete question; answer should be a short phrase/sentence)
- Mini-review Mode (narrow topic; 1–3 pages of synthesis)
- Full Deep-Research Mode (use the full template + completeness checklist)
Heuristic:
- If the user asks “X has been evolved to be resistant to which antibiotic?” → Factoid / Verification Mode
- If the user asks “What does the literature say about X?” → Full Deep-Research Mode
Factoid / Verification Mode (Fast Path)
Goal: Provide a correct, source-verified single answer, with minimal but explicit evidence attribution.
Deliverables (still file-backed):
[topic]_factcheck_report.md(≤ 1 page)[topic]_bibliography.json(+ CSV) containing the key paper(s)
Fact-check report template:
Required verification behavior:
- Prefer ToolUniverse literature tools (Europe PMC / PubMed / PMC / Semantic Scholar) over general web browsing.
- Use full-text snippet verification when possible (Europe PMC auto-snippet tier is ideal).
- Avoid adding extra claims (e.g., “not X”) unless the paper explicitly supports them.
Suggested tool pattern:
EuropePMC_search_articles(query=..., extract_terms_from_fulltext=[...])to pull OA full-text snippets for the key terms.- If OA snippets unavailable: fall back to
PMC_search_papers(if in PMC) orSemanticScholar_search_papers→SemanticScholar_get_pdf_snippets.
Evidence grading (factoid):
- If the statement is explicitly made in a primary experimental paper (Results/Methods/Abstract): label T1 (★★★).
- If it’s only in a review: label T4 (☆☆☆) and try to locate the primary source.
Detect Target Type
| Query Pattern | Type | Action | |
|---|---|---|---|
| Gene symbol (EGFR, TP53, ATP6V1A) | Biological target | Phase 1 required | |
| Protein name ("V-ATPase", "kinase") | Biological target | Phase 1 required | |
| UniProt ID (P00533, Q93050) | Biological target | Phase 1 required | |
| Disease, pathway, method | General topic | Phase 1 optional | |
| "Literature on X" | Depends on X | Assess X |
Phase 1: Target Disambiguation + Profile (Default ON)
CRITICAL: This phase prevents "missing target details" when literature is sparse or noisy.
1.1 Resolve Official Identifiers
Use these tools to establish canonical identity:
Output for report:
1.2 Identify Naming Collisions
CRITICAL: Many gene names have collisions. Examples:
- TRAG: T-cell regulatory gene vs bacterial TraG conjugation protein
- WDR7-7: Could match gene WDR7 vs lncRNA
- JAK: Janus kinase vs Just Another Kinase
- CAT: Catalase vs chloramphenicol acetyltransferase
Detection strategy:
- Search PubMed for
"[SYMBOL]"[Title]- review first 20 titles - If >20% off-topic, identify collision terms
- Build negative filter:
NOT [collision_term1] NOT [collision_term2]
Output for report:
1.3 Protein Architecture & Domains
Use annotation tools (not literature):
Output for report:
1.4 Subcellular Location
Output for report:
1.5 Baseline Expression
Output for report:
1.6 GO Terms & Pathway Placement
Output for report:
Phase 2: Literature Search (Internal Methodology)
NOTE: This methodology is kept internal. The report shows findings, not process.
2.1 Query Strategy: Collision-Aware Synonym Plan
Step 1: High-Precision Seed Queries (Build Mechanistic Core)
Purpose: Get 15-30 high-confidence, mechanistic papers that are definitely on-target.
Step 2: Citation Network Expansion (Especially for Sparse Targets)
Once you have 5-15 core PMIDs:
Citation-network first option: For older targets with deprecated terminology, citation expansion often outperforms keyword searching.
Step 3: Collision-Filtered Broader Queries
Example for bacterial TraG collision:
2.2 Database Tools
Literature Search (use all relevant):
PubMed_search_articles- Primary biomedicalPMC_search_papers- Full-textEuropePMC_search_articles- European coverageopenalex_literature_search- Broad academicCrossref_search_works- DOI registrySemanticScholar_search_papers- AI-rankedBioRxiv_search_preprints/MedRxiv_search_preprints- Preprints
This is the start of the file. Read the full SKILL.md on GitHub.
Security
- Security scanPassed, 90 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/literature/tooluniverse-literature-deep-research/SKILL.md
Popularity
- Repository stars
- 880
- Repository forks
- 123
- 7-day trend score
- 34
Stars and forks are for the whole GitHub repository, not this skill alone. Refreshed 26 Mar 2026, 7 months ago.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/wu-yc/labclaw/tooluniverse-literature-deep-research)