tooluniverse-target-research
Gather comprehensive biological target intelligence from 9 parallel research paths covering protein info, structure, interactions, pathways, expression, variants, drug interactions, and literature. Features collision-aware searches, evidence grading (T1-T4), explicit Open Targets coverage, and mandatory completeness auditing. Use when users ask about drug targets, proteins, genes, or need target validation, druggability assessment, or comprehensive target profiling.
Install
mkdir -p .claude/skills/tooluniverse-target-research && curl -L -o skill.zip "https://mcp.directory/api/skills/download/2774" && unzip -o skill.zip -d .claude/skills/tooluniverse-target-research && rm skill.zipInstalls to .claude/skills/tooluniverse-target-research
About this skill
Comprehensive Target Intelligence Gatherer
Gather complete target intelligence by exploring 9 parallel research paths. Supports targets identified by gene symbol, UniProt accession, Ensembl ID, or gene name.
KEY PRINCIPLES:
- Report-first approach - Create report file FIRST, then populate progressively
- Tool parameter verification - Verify params via
get_tool_infobefore calling unfamiliar tools - Evidence grading - Grade all claims by evidence strength (T1-T4). See EVIDENCE_GRADING.md
- Citation requirements - Every fact must have inline source attribution
- Mandatory completeness - All sections must exist with data minimums or explicit "No data" notes
- Disambiguation first - Resolve all identifiers before research
- Negative results documented - "No drugs found" is data; empty sections are failures
- Collision-aware literature search - Detect and filter naming collisions
- English-first queries - Always use English terms in tool calls, even if the user writes in another language. Translate gene names, disease names, and search terms to English. Only try original-language terms as a fallback if English returns no results. Respond in the user's language
When to Use This Skill
Apply when users:
- Ask about a drug target, protein, or gene
- Need target validation or assessment
- Request druggability analysis
- Want comprehensive target profiling
- Ask "what do we know about [target]?"
- Need target-disease associations
- Request safety profile for a target
When NOT to use: Simple protein lookup, drug-only queries, disease-centric queries, sequence retrieval, structure download -- use specialized skills instead.
Phase 0: Tool Parameter Verification (CRITICAL)
BEFORE calling ANY tool for the first time, verify its parameters:
tool_info = tu.tools.get_tool_info(tool_name="Reactome_map_uniprot_to_pathways")
# Reveals: takes `id` not `uniprot_id`
Known Parameter Corrections
| Tool | WRONG Parameter | CORRECT Parameter |
|---|---|---|
Reactome_map_uniprot_to_pathways | uniprot_id | id |
ensembl_get_xrefs | gene_id | id |
GTEx_get_median_gene_expression | gencode_id only | gencode_id + operation="median" |
OpenTargets_* | ensemblID | ensemblId (camelCase) |
STRING_get_protein_interactions | single ID | protein_ids (list), species |
intact_get_interactions | gene symbol | identifier (UniProt accession) |
GTEx Versioned ID Fallback (CRITICAL)
GTEx often requires versioned Ensembl IDs. If ENSG00000123456 returns empty, try ENSG00000123456.{version} from ensembl_lookup_gene.
Critical Workflow Requirements
1. Report-First Approach (MANDATORY)
DO NOT show the search process or tool outputs to the user. Instead:
- Create the report file FIRST (
[TARGET]_target_report.md) with all section headers and[Researching...]placeholders. See REPORT_FORMAT.md for template. - Progressively update each section as data is retrieved.
- Methodology in appendix only - create separate
[TARGET]_methods_appendix.mdif requested.
2. Evidence Grading (MANDATORY)
Grade every claim by evidence strength using T1-T4 tiers. See EVIDENCE_GRADING.md for tier definitions, required locations, and citation format.
Core Strategy: 9 Research Paths
Target Query (e.g., "EGFR" or "P00533")
|
+- IDENTIFIER RESOLUTION (always first)
| +- Check if GPCR -> GPCRdb_get_protein
|
+- PATH 0: Open Targets Foundation (ALWAYS FIRST - fills gaps in all other paths)
|
+- PATH 1: Core Identity (names, IDs, sequence, organism)
| +- InterProScan_scan_sequence for novel domain prediction
+- PATH 2: Structure & Domains (3D structure, domains, binding sites)
| +- If GPCR: GPCRdb_get_structures (active/inactive states)
+- PATH 3: Function & Pathways (GO terms, pathways, biological role)
+- PATH 4: Protein Interactions (PPI network, complexes)
+- PATH 5: Expression Profile (tissue expression, single-cell)
+- PATH 6: Variants & Disease (mutations, clinical significance)
| +- DisGeNET_search_gene for curated gene-disease associations
+- PATH 7: Drug Interactions (known drugs, druggability, safety)
| +- Pharos_get_target for TDL classification (Tclin/Tchem/Tbio/Tdark)
| +- BindingDB_get_ligands_by_uniprot for known ligands
| +- PubChem_search_assays_by_target_gene for HTS data
| +- If GPCR: GPCRdb_get_ligands (curated agonists/antagonists)
| +- DepMap_get_gene_dependencies for target essentiality
+- PATH 8: Literature & Research (publications, trends)
For detailed code implementations of each path, see IMPLEMENTATION.md.
Identifier Resolution (Phase 1)
Resolve ALL identifiers before any research path. Required IDs:
- UniProt accession (for protein data, structure, interactions)
- Ensembl gene ID + versioned ID (for Open Targets, GTEx)
- Gene symbol (for DGIdb, gnomAD, literature)
- Entrez gene ID (for KEGG, MyGene)
- ChEMBL target ID (for bioactivity)
- Synonyms/full name (for collision-aware literature search)
After resolution, check if target is a GPCR via GPCRdb_get_protein. See IMPLEMENTATION.md for resolution and GPCR detection code.
PATH 0: Open Targets Foundation (ALWAYS FIRST)
Populates baseline data for Sections 5, 6, 8, 9, 10, 11 before specialized queries.
| Endpoint | Report Section | Data Type |
|---|---|---|
OpenTargets_get_diseases_phenotypes_by_target_ensemblId | 8 | Diseases/phenotypes |
OpenTargets_get_target_tractability_by_ensemblId | 9 | Druggability assessment |
OpenTargets_get_target_safety_profile_by_ensemblId | 10 | Safety liabilities |
OpenTargets_get_target_interactions_by_ensemblId | 6 | PPI network |
OpenTargets_get_target_gene_ontology_by_ensemblId | 5 | GO annotations |
OpenTargets_get_publications_by_target_ensemblId | 11 | Literature |
OpenTargets_get_biological_mouse_models_by_ensemblId | 8/10 | Mouse KO phenotypes |
OpenTargets_get_chemical_probes_by_target_ensemblId | 9 | Chemical probes |
OpenTargets_get_associated_drugs_by_target_ensemblId | 9 | Known drugs |
PATH 1: Core Identity
Tools: UniProt_get_entry_by_accession, UniProt_get_function_by_accession, UniProt_get_recommended_name_by_accession, UniProt_get_alternative_names_by_accession, UniProt_get_subcellular_location_by_accession, MyGene_get_gene_annotation
Populates: Sections 2 (Identifiers), 3 (Basic Information)
PATH 2: Structure & Domains
Use 3-step structure search chain (do NOT rely solely on PDB text search):
- UniProt PDB cross-references (most reliable)
- Sequence-based PDB search (catches missing annotations)
- Domain-based search (for multi-domain proteins)
- AlphaFold (always check)
Tools: UniProt_get_entry_by_accession (PDB xrefs), get_protein_metadata_by_pdb_id, PDB_search_similar_structures, alphafold_get_prediction, InterPro_get_protein_domains, UniProt_get_ptm_processing_by_accession
GPCR targets: Also query GPCRdb_get_structures for active/inactive state data.
Populates: Section 4 (Structural Biology)
See IMPLEMENTATION.md for the 3-step chain code.
PATH 3: Function & Pathways
Tools: GO_get_annotations_for_gene, Reactome_map_uniprot_to_pathways, kegg_get_gene_info, WikiPathways_search, enrichr_gene_enrichment_analysis
Populates: Section 5 (Function & Pathways)
PATH 4: Protein Interactions
Tools: STRING_get_protein_interactions, intact_get_interactions, intact_get_complex_details, BioGRID_get_interactions, HPA_get_protein_interactions_by_gene
Minimum: 20 interactors OR documented explanation.
Populates: Section 6 (Protein-Protein Interactions)
PATH 5: Expression Profile
GTEx with versioned ID fallback + HPA as backup. For comprehensive HPA data, also query cell line expression comparison.
Tools: GTEx_get_median_gene_expression, HPA_get_rna_expression_by_source, HPA_get_comprehensive_gene_details_by_ensembl_id, HPA_get_subcellular_location, HPA_get_cancer_prognostics_by_gene, HPA_get_comparative_expression_by_gene_and_cellline, CELLxGENE_get_expression_data
Populates: Section 7 (Expression Profile)
See IMPLEMENTATION.md for GTEx fallback and HPA extended expression code.
PATH 6: Variants & Disease
Separate SNVs from CNVs in ClinVar results. Integrate DisGeNET for curated gene-disease association scores.
Tools: gnomad_get_gene_constraints, clinvar_search_variants, OpenTargets_get_diseases_phenotypes_by_target_ensembl, DisGeNET_search_gene, civic_get_variants_by_gene, cBioPortal_get_mutations
Required: All 4 constraint scores (pLI, LOEUF, missense Z, pRec).
Populates: Section 8 (Genetic Variation & Disease)
PATH 7: Druggability & Target Validation
Comprehensive druggability assessment including TDL classification, binding data, screening data, and essentiality.
Tools: OpenTargets_get_target_tractability_by_ensemblID, DGIdb_get_gene_druggability, DGIdb_get_drug_gene_interactions, ChEMBL_search_targets, ChEMBL_get_target_activities, Pharos_get_target, BindingDB_get_ligands_by_uniprot, PubChem_search_assays_by_target_gene, DepMap_get_gene_dependencies, OpenTargets_get_target_safety_profile_by_ensemblID, OpenTargets_get_biological_mouse_models_by_ensemblID
GPCR targets: Also query GPCRdb_get_ligands.
Populates: Sections 9 (Druggability), 10 (Safety), 12 (Competitive Landscape)
Key Data Sources for Druggability
| Source | What It Provides |
|---|---|
| Pharos TDL | Tclin/Tchem/Tbio/Tdark classification |
| BindingDB | Experimental Ki/IC50/Kd values |
| Pub |
Content truncated.
More by mims-harvard
View all skills by mims-harvard →You might also like
flutter-development
aj-geddes
Build beautiful cross-platform mobile apps with Flutter and Dart. Covers widgets, state management with Provider/BLoC, navigation, API integration, and material design.
drawio-diagrams-enhanced
jgtolentino
Create professional draw.io (diagrams.net) diagrams in XML format (.drawio files) with integrated PMP/PMBOK methodologies, extensive visual asset libraries, and industry-standard professional templates. Use this skill when users ask to create flowcharts, swimlane diagrams, cross-functional flowcharts, org charts, network diagrams, UML diagrams, BPMN, project management diagrams (WBS, Gantt, PERT, RACI), risk matrices, stakeholder maps, or any other visual diagram in draw.io format. This skill includes access to custom shape libraries for icons, clipart, and professional symbols.
ui-ux-pro-max
nextlevelbuilder
"UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient."
godot
bfollington
This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.
nano-banana-pro
garg-aayush
Generate and edit images using Google's Nano Banana Pro (Gemini 3 Pro Image) API. Use when the user asks to generate, create, edit, modify, change, alter, or update images. Also use when user references an existing image file and asks to modify it in any way (e.g., "modify this image", "change the background", "replace X with Y"). Supports both text-to-image generation and image-to-image editing with configurable resolution (1K default, 2K, or 4K for high resolution). DO NOT read the image file first - use this skill directly with the --input-image parameter.
fastapi-templates
wshobson
Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.
Related MCP Servers
Browse all serversBoost Postgres performance with Postgres MCP Pro—AI-driven index tuning, health checks, and safe, intelligent SQL optimi
Optimize Facebook ad campaigns with AI-driven insights, creative analysis, and campaign control in Meta Ads Manager for
Maigret OSINT offers open source intelligence tools to find user info across social networks. Boost your OSINT intellige
Anubis streamlines artificial intelligence development software with AI for software development, using role-based agent
Integrate RetellAI Voice Services for ai voice chat, call initiation, and customer service using artificial intelligence
Integrate with Prometheus for real-time performance analysis, process monitoring, and advanced Prometheus 2.0 metric dis
Stay ahead of the MCP ecosystem
Get weekly updates on new skills and servers.