create-tooluniverse-skill
Create ToolUniverse Skill
Systematic workflow for creating production-ready ToolUniverse skills.
Core Principles
Build on the 10 pillars from devtu-optimize-skills:
- TEST FIRST - never document untested tools
- Verify tool contracts - don't trust function names
- Handle SOAP tools - add
operationparameter - Implementation-agnostic docs - no Python/MCP code in SKILL.md
- Foundation first - query aggregators before specialized tools
- Disambiguate carefully - resolve IDs properly
- Implement fallbacks - Primary -> Fallback -> Default
- Grade evidence - T1-T4 tiers on claims
- Quantified completeness - numeric minimums per section
- Synthesize - models and hypotheses, not just lists
See OPTIMIZE_INTEGRATION.md for detailed application of each pillar.
7-Phase Workflow
| Phase | Duration | Description |
|---|---|---|
| 1. Domain Analysis | 15 min | Understand use cases, data types, analysis phases |
| 2. Tool Discovery | 30-45 min | Search, read configs, test tools (MANDATORY) |
| 3. Tool Creation | 0-60 min | Create missing tools via devtu-create-tool |
| 4. Implementation | 30-45 min | Write python_implementation.py with tested tools |
| 5. Documentation | 30-45 min | Write SKILL.md (agnostic) + QUICK_START.md |
| 6. Validation | 15-30 min | Run test suite, validate checklist, manual verify |
| 7. Packaging | 15 min | Create summary, update tracking |
Total: ~1.5-2 hours (without tool creation).
Phase 1: Domain Analysis
- Gather concrete use cases and expected outputs
- Identify inputs, outputs, and intermediate data types
- Break workflow into logical phases
- Review existing skills in
skills/for patterns
Phase 2: Tool Discovery and Testing
Search tools in /src/tooluniverse/data/*.json (186 tool files). For each tool, read its config to understand parameters and return schema. See PARAMETER_VERIFICATION.md for common pitfalls.
Create and run a test script using test_tools_template.py. For each tool: call with known-good params, verify response format, document corrections. See TESTING_GUIDE.md for the full test suite template and procedures.
Phase 3: Tool Creation (If Needed)
Invoke devtu-create-tool when required functionality is missing and analysis is blocked. Use devtu-fix-tool if new tools fail tests.
Phase 4: Implementation
Create skills/tooluniverse-[domain]/ with:
python_implementation.py- use only tested tools, try/except per phase, progressive report writingtest_skill.py- test each input type, combined inputs, error handling
Use templates from CODE_TEMPLATES.md.
Phase 5: Documentation
Write implementation-agnostic SKILL.md using SKILL_TEMPLATE.md. Write multi-implementation QUICK_START.md using QUICKSTART_TEMPLATE.md. Key rules: zero Python/MCP code in SKILL.md, equal treatment of both interfaces in QUICK_START.
See IMPLEMENTATION_AGNOSTIC.md for format guidelines with examples.
Phase 6: Validation
Run the comprehensive test suite (see TESTING_GUIDE.md). Validate against VALIDATION_CHECKLIST.md. Perform manual verification: load ToolUniverse fresh, copy-paste QUICK_START example, verify output works.
Phase 7: Packaging
Create summary document using PACKAGING_TEMPLATE.md. Update session tracking if creating multiple skills.
Skill Integration
| Skill | When to Use |
|---|---|
| devtu-create-tool | Critical functionality missing |
| devtu-fix-tool | Tool returns errors or unexpected format |
| devtu-optimize-skills | Evidence grading, report optimization |
Quality Indicators
High quality: 100% test coverage before docs, agnostic SKILL.md, multi-implementation QUICK_START, fallback strategies, parameter corrections table, response format docs.
Red flags: Docs before testing, Python in SKILL.md, assumed parameters, no fallbacks, SOAP tools missing operation, no test script.
Reference Files
| File | Content |
|---|---|
SKILL_TEMPLATE.md |
Template for writing SKILL.md |
QUICKSTART_TEMPLATE.md |
Template for writing QUICK_START.md |
TESTING_GUIDE.md |
Test suite template and procedures |
VALIDATION_CHECKLIST.md |
Pre-release quality checklist |
PACKAGING_TEMPLATE.md |
Summary document template |
PARAMETER_VERIFICATION.md |
Tool parameter verification guide |
OPTIMIZE_INTEGRATION.md |
devtu-optimize-skills 10-pillar integration |
IMPLEMENTATION_AGNOSTIC.md |
Implementation-agnostic format guide with examples |
CODE_TEMPLATES.md |
Python implementation and test templates |
test_tools_template.py |
Tool testing script template |
More from mims-harvard/tooluniverse
tooluniverse-sequence-retrieval
Retrieves biological sequences (DNA, RNA, protein) from NCBI and ENA with gene disambiguation, accession type handling, and comprehensive sequence profiles. Creates detailed reports with sequence metadata, cross-database references, and download options. Use when users need nucleotide sequences, protein sequences, genome data, or mention GenBank, RefSeq, EMBL accessions.
1.4Ktooluniverse-image-analysis
Production-ready microscopy image analysis and quantitative imaging data skill for colony morphometry, cell counting, fluorescence quantification, and statistical analysis of imaging-derived measurements. Processes ImageJ/CellProfiler output (area, circularity, intensity, cell counts), performs Dunnett's test, Cohen's d effect size, power analysis, Shapiro-Wilk normality tests, two-way ANOVA, polynomial regression, natural spline regression with confidence intervals, and comparative morphometry. Supports CSV/TSV measurement tables, multi-channel fluorescence data, colony swarming assays, and neuron counting datasets. Use when analyzing microscopy measurement data, colony area/circularity, cell count statistics, swarming assays, co-culture ratio optimization, or answering questions about imaging-derived quantitative data.
379tooluniverse-literature-deep-research
Comprehensive literature deep research across any academic domain using 120+ ToolUniverse tools. Conducts subject disambiguation, systematic literature search with citation network expansion, evidence grading (T1-T4), and structured theme extraction. Produces detailed reports with mandatory completeness checklists, integrated models, and testable hypotheses. Use when users need thorough literature reviews, target/drug/disease profiles, topic deep-dives, claim verification, or systematic evidence synthesis. Supports biomedical (genes, proteins, drugs, diseases), computer science, social science, and general academic topics. For single factoid questions, uses a fast verification mode with inline answer.
347tooluniverse
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.
257tooluniverse-drug-research
Generates comprehensive drug research reports with compound disambiguation, evidence grading, and mandatory completeness sections. Covers identity, chemistry, pharmacology, targets, clinical trials, safety, pharmacogenomics, and ADMET properties. Use when users ask about drugs, medications, therapeutics, or need drug profiling, safety assessment, or clinical development research.
253setup-tooluniverse
Install and configure ToolUniverse for any use case — MCP server (chat-based), CLI (command line with 9 subcommands), or Python SDK (Coding API with 3 calling patterns). Covers uv/uvx setup, MCP configuration for 12+ AI clients (Cursor, Claude Desktop, Windsurf, VS Code, Codex, Gemini CLI, Trae, Cline, etc.), full CLI reference (tu list/grep/find/info/run/test/status/build/serve), Coding API quickstart, agentic tools, code executor, API key walkthrough, skill installation, and upgrading. Use when user asks how to set up ToolUniverse, which access mode to use (MCP vs CLI vs SDK), configuring MCP servers, using the CLI, troubleshooting installation, upgrading, or mentions installing ToolUniverse or setting up scientific tools. Also triggers for "how do I use ToolUniverse", "what's the best way to access tools", "command line", "tu command", "coding API", "tu build".
251