tooluniverse-[domain-name]
[Complete description of what the skill does, which databases it uses, and when to use it. Include specific trigger phrases like "analyze [domain]", "find [data type]", etc. This description is the primary way Claude determines when to use your skill.]
Best use case
tooluniverse-[domain-name] is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
[Complete description of what the skill does, which databases it uses, and when to use it. Include specific trigger phrases like "analyze [domain]", "find [data type]", etc. This description is the primary way Claude determines when to use your skill.]
Teams using tooluniverse-[domain-name] should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/skill_template/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How tooluniverse-[domain-name] Compares
| Feature / Agent | tooluniverse-[domain-name] | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
[Complete description of what the skill does, which databases it uses, and when to use it. Include specific trigger phrases like "analyze [domain]", "find [data type]", etc. This description is the primary way Claude determines when to use your skill.]
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# [Domain Name] Analysis
[One paragraph overview describing what this skill does, what problems it solves, and what outputs it provides.]
## When to Use This Skill
**Triggers**:
- "[Trigger phrase 1]"
- "[Trigger phrase 2]"
- "[Trigger phrase 3]"
**Use Cases**:
1. **[Use Case 1]**: [Description]
2. **[Use Case 2]**: [Description]
3. **[Use Case 3]**: [Description]
## Core Databases Integrated
| Database | Coverage | Strengths |
|----------|----------|-----------|
| **Database 1** | [What it covers] | [What it's best for] |
| **Database 2** | [What it covers] | [What it's best for] |
| **Database 3** | [What it covers] | [What it's best for] |
## Workflow Overview
```
Input → Phase 1: [Name] → Phase 2: [Name] → Phase 3: [Name] → Report
```
---
## Phase 1: [Phase Name]
**When**: [When this phase runs - e.g., "When input_param_1 provided"]
**Objective**: [What this phase achieves]
### Tools Used
**TOOL_NAME_1**:
- **Input**:
- `parameter1` (type, required/optional): Description
- `parameter2` (type, required/optional): Description
- **Output**: Description of what the tool returns
- **Use**: What this tool provides for the analysis
**TOOL_NAME_2** (Fallback):
- **Input**: [Parameters]
- **Output**: [Description]
- **Use**: [Purpose]
### Workflow
1. Query TOOL_NAME_1 with [input description]
2. Extract [specific data fields] from response
3. If no results → try TOOL_NAME_2 (fallback)
4. Process data and add to report
5. Continue with available data
### Decision Logic
- **Successful query**: Process and display top 10-15 results
- **Empty results**: Note "[Database] returned no results"
- **API error**: Fall back to TOOL_NAME_2
- **Both fail**: Document unavailability and continue
---
## Phase 2: [Phase Name]
**When**: [Conditions]
**Objective**: [Goal]
### Tools Used
[Similar structure to Phase 1]
### Workflow
[Step-by-step process]
### Decision Logic
[How to handle different scenarios]
---
## Phase 3: [Phase Name]
[Similar structure]
---
## Phase 4: [Summary/Context Phase]
**When**: Always included
**Objective**: Provide context even when specific phases empty
[Structure similar to above phases]
---
## Output Structure
### Report Format
**Progressive Markdown Report**:
- Create report file first
- Add sections progressively
- Each section self-contained
- Handles empty data gracefully
**Required Sections**:
1. **Header**: Analysis parameters and metadata
2. **Phase 1 Results**: [Description]
3. **Phase 2 Results**: [Description]
4. **Phase 3 Results**: [Description]
5. **Phase 4 Results**: [Description]
**Per-Database Subsections**:
- Database name and result count
- Table of results with key metadata
- Note if database returns no results
- Links or IDs for follow-up
### Data Tables
**Phase 1 Results**:
| Column 1 | Column 2 | Column 3 |
| ... | ... | ... |
**Phase 2 Results**:
| Column 1 | Column 2 | Column 3 |
| ... | ... | ... |
---
## Tool Parameter Reference
**Critical Parameter Notes** (from testing):
| Tool | Parameter | CORRECT Name | Common Mistake |
|------|-----------|--------------|----------------|
| TOOL_NAME_1 | `param` | ✅ `actual_param_name` | ❌ `assumed_param_name` |
| TOOL_NAME_2 | `param` | ✅ `correct_name` | ❌ `function_name_param` |
**Response Format Notes**:
- **TOOL_NAME_1**: Returns standard `{status: "success", data: [...]}` format
- **TOOL_NAME_2**: Returns list directly (not wrapped in status/data)
- **TOOL_NAME_3**: Returns dict with custom structure `{field1: ..., field2: ...}`
**SOAP Tools** (if applicable):
- **TOOL_NAME_4**: Requires `operation` parameter (e.g., `operation="method_name"`)
- See QUICK_START.md for side-by-side Python/MCP examples
---
## Fallback Strategies
### Phase 1: [Phase Name]
- **Primary**: TOOL_NAME_1 ([reason it's primary])
- **Fallback**: TOOL_NAME_2 ([what it provides instead])
- **Default**: Continue with noting data unavailable
### Phase 2: [Phase Name]
- **Primary**: TOOL_NAME_3
- **Fallback**: [Alternative approach]
- **Default**: [How to proceed]
---
## Common Use Patterns
### Pattern 1: [Use Case Name]
```
Input: [Description of typical input]
Workflow: Phase 1 → Phase 3 → Report
Output: [What user gets]
```
### Pattern 2: [Use Case Name]
```
Input: [Description]
Workflow: [Which phases run]
Output: [Result type]
```
### Pattern 3: [Comprehensive Analysis]
```
Input: [Multiple inputs]
Workflow: All phases
Output: [Complete analysis]
```
---
## Quality Checks
### Data Completeness
- [ ] At least one phase completed successfully
- [ ] Each database result includes source attribution
- [ ] Empty results explicitly noted (not silently omitted)
- [ ] All required fields documented in tables
- [ ] IDs provided for follow-up analysis
### Biological/Scientific Validity
- [ ] Results consistent with known [domain] knowledge
- [ ] Cross-database results show expected overlaps
- [ ] Anomalies flagged for review
- [ ] Data quality indicators included
### Report Quality
- [ ] All sections present even if "no data"
- [ ] Tables formatted consistently
- [ ] Source databases clearly attributed
- [ ] Follow-up recommendations if data sparse
---
## Limitations & Known Issues
### Database-Specific
- **Database 1**: [Known limitations, coverage gaps, update frequency]
- **Database 2**: [Limitations]
- **Database 3**: [Limitations]
### Technical
- **Response formats**: Different tools use different structures (handled in implementation)
- **Rate limits**: [Any rate limiting concerns]
- **Version differences**: [Database version considerations]
### Analysis
- **[Domain]-specific limitation 1**: [Description]
- **[Domain]-specific limitation 2**: [Description]
---
## Summary
**[Domain] Analysis Skill** provides:
1. ✅ [Capability 1 with database]
2. ✅ [Capability 2 with databases]
3. ✅ [Capability 3 with databases]
4. ✅ [Capability 4]
**Outputs**: Markdown report with [description of content]
**Best for**: [Primary use cases and target users]Related Skills
tooluniverse
Router skill for ToolUniverse tasks. First checks if specialized tooluniverse skills (105+ skills covering disease/drug/target research, gene-disease associations, clinical decision support, genomics, epigenomics, proteomics, comparative genomics, chemical safety, toxicology, systems biology, and more) can solve the problem, then falls back to general strategies for using 2300+ scientific tools. Covers tool discovery, multi-hop queries, comprehensive research workflows, disambiguation, evidence grading, and report generation. Use when users need to research any scientific topic, find biological data, or explore drug/target/disease relationships. ALSO USE for any biology, medicine, chemistry, pharmacology, or life science question — even simple factoid questions like "how many X in protein Y", "what drug interacts with Z", "what gene causes disease W", or "translate this sequence". These questions benefit from database lookups (UniProt, PubMed, ChEMBL, ClinVar, GWAS Catalog, etc.) rather than answering from memory alone. When in doubt about a scientific fact, USE THIS SKILL to verify against real databases.
tooluniverse-variant-to-mechanism
End-to-end variant-to-mechanism analysis: given a genetic variant (rsID or coordinates), trace its functional impact from regulatory context (GWAS, eQTL, RegulomeDB, ENCODE) through target gene identification (GTEx, OpenTargets L2G) to downstream pathway and disease biology (STRING, Reactome, GO enrichment, disease associations). Produces an evidence-graded mechanistic narrative linking genotype to phenotype. Use when asked "how does this variant cause disease?", "what is the mechanism of rs7903146?", "trace variant to pathway", or "connect this GWAS hit to biology".
tooluniverse-variant-interpretation
Systematic clinical variant interpretation from raw variant calls to ACMG-classified recommendations with structural impact analysis. Aggregates evidence from ClinVar, gnomAD, CIViC, UniProt, and PDB across ACMG criteria. Produces pathogenicity scores (0-100), clinical recommendations, and treatment implications. Use when interpreting genetic variants, classifying variants of uncertain significance (VUS), performing ACMG variant classification, or translating variant calls to clinical actionability.
tooluniverse-variant-functional-annotation
Comprehensive functional annotation of protein variants — pathogenicity, population frequency, structural context, and clinical significance. Integrates ProtVar (map_variant, get_function, get_population) for protein-level mapping and structural context, ClinVar for clinical classifications, gnomAD for population frequency with ancestry data, CADD for deleteriousness scores, and ClinGen for gene-disease validity. Produces a structured variant annotation report with evidence grading. Use when asked about protein variant impact, missense variant pathogenicity, ProtVar annotation, variant functional context, or combining population and structural evidence for a variant.
tooluniverse-variant-analysis
Production-ready VCF processing, variant annotation, mutation analysis, and structural variant (SV/CNV) interpretation for bioinformatics questions. Parses VCF files (streaming, large files), classifies mutation types (missense, nonsense, synonymous, frameshift, splice, intronic, intergenic) and structural variants (deletions, duplications, inversions, translocations), applies VAF/depth/quality/consequence filters, annotates with ClinVar/dbSNP/gnomAD/CADD via ToolUniverse, interprets SV/CNV clinical significance using ClinGen dosage sensitivity scores, computes variant statistics, and generates reports. Solves questions like "What fraction of variants with VAF < 0.3 are missense?", "How many non-reference variants remain after filtering intronic/intergenic?", "What is the pathogenicity of this deletion affecting BRCA1?", or "Which dosage-sensitive genes overlap this CNV?". Use when processing VCF files, annotating variants, filtering by VAF/depth/consequence, classifying mutations, interpreting structural variants, assessing CNV pathogenicity, comparing cohorts, or answering variant analysis questions.
tooluniverse-vaccine-design
Design and evaluate vaccine candidates using computational immunology tools. Covers epitope prediction (MHC-I/II binding via IEDB), population coverage analysis, antigen selection, adjuvant matching, and immunogenicity assessment. Integrates IEDB for epitope prediction, UniProt for antigen sequences, PDB/AlphaFold for structural epitopes, BVBRC for pathogen proteomes, and literature for clinical precedent. Use when asked about vaccine design, epitope prediction, immunogenicity, MHC binding, T-cell epitopes, B-cell epitopes, or population coverage for vaccine candidates.
tooluniverse-toxicology
Assess chemical and drug toxicity via adverse outcome pathways, real-world adverse event signals, and toxicogenomic evidence. Integrates AOPWiki (AOPWiki_list_aops, AOPWiki_get_aop) for mechanism- level pathway tracing, FAERS for post-market adverse event quantification, OpenFDA for label mining, and CTD for chemical-gene-disease evidence. Produces structured toxicity reports with evidence grading (T1-T4). Use when asked about toxicity mechanisms, adverse outcome pathways, AOP mapping, FAERS signal detection, or chemical-disease relationships for drugs or environmental chemicals.
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.
tooluniverse-systems-biology
Comprehensive systems biology and pathway analysis using multiple pathway databases (Reactome, KEGG, WikiPathways, Pathway Commons, BioModels). Performs pathway enrichment, protein-pathway mapping, keyword searches, and systems-level analysis. Use when analyzing gene sets, exploring biological pathways, or investigating systems-level biology.
tooluniverse-structural-variant-analysis
Comprehensive structural variant (SV) analysis skill for clinical genomics. Classifies SVs (deletions, duplications, inversions, translocations), assesses pathogenicity using ACMG-adapted criteria, evaluates gene disruption and dosage sensitivity, and provides clinical interpretation with evidence grading. Use when analyzing CNVs, large deletions/duplications, chromosomal rearrangements, or any structural variants requiring clinical interpretation.
tooluniverse-structural-proteomics
Integrate structural biology data with proteomics for drug target validation. Retrieves protein structures from PDB (RCSB, PDBe), AlphaFold predictions, antibody structures (SAbDab), GPCR data (GPCRdb), binding pocket analysis (ProteinsPlus), and ligand interactions (BindingDB). Use when asked to find structures for a drug target, identify binding site ligands, cross-validate drug binding with structural data, assess structural druggability, or compare experimental vs predicted structures.
tooluniverse-stem-cell-organoid
Research stem cells, iPSCs, organoids, and cell differentiation using ToolUniverse tools. Covers pluripotency marker identification, differentiation pathway analysis, organoid model characterization, cell type annotation, and disease modeling. Integrates CellxGene/HCA for single-cell atlas data, CellMarker for cell type markers, GEO for stem cell datasets, and pathway tools for differentiation signaling. Use when asked about stem cells, iPSCs, organoids, cell reprogramming, pluripotency, differentiation protocols, or 3D culture models.