skills/create-tooluniverse-skill/SKILL.md
Create high-quality ToolUniverse skills following test-driven, implementation-agnostic methodology.
npx skillsauth add mims-harvard/tooluniverse create-tooluniverse-skillInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Systematic workflow for creating production-ready ToolUniverse skills.
Build on the 10 pillars from devtu-optimize-skills:
operation parameterSee OPTIMIZE_INTEGRATION.md for detailed application of each pillar.
| 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).
skills/ for patternsSearch 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.
Invoke devtu-create-tool when required functionality is missing and analysis is blocked. Use devtu-fix-tool if new tools fail tests.
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 handlingUse templates from CODE_TEMPLATES.md.
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.
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.
Create summary document using PACKAGING_TEMPLATE.md. Update session tracking if creating multiple skills.
| 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 |
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.
| 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 |
tools
PCR / qPCR primer and oligo design — design forward/reverse primers for a target region (SantaLucia nearest-neighbor thermodynamics), compute melting temperature (Tm) and annealing temperature (Ta), check GC content, and screen an oligo for hairpins and primer-dimers. Use when you need primers for a sequence, want to QC an existing primer pair, or need the Tm of an oligo. Covers the primer-design rules (Tm matching, GC clamp, 3'-end, length) and the tools' constraint quirks.
tools
Pharmacokinetic (PK) analysis of concentration-time data — non-compartmental analysis (NCA) for Cmax, Tmax, AUC (0-t and 0-∞), terminal half-life, clearance (CL), volume of distribution (Vd), MRT, and absolute bioavailability (F). Also one-compartment fitting. Use when you have plasma/serum drug concentrations over time after a dose and need PK parameters, or to compute bioavailability from IV + oral AUCs. NOT for ADMET property prediction from structure (use tooluniverse-admet-prediction).
tools
Molecular cloning assembly design — Gibson Assembly (overlap design for seamless multi-fragment joining) and Golden Gate Assembly (Type IIS / BsaI / BbsI design with unique 4-bp fusion overhangs). Use when you need to plan how to join DNA fragments into a construct, design assembly overlaps/overhangs, or decide between cloning methods. Covers the domestication (internal-site removal), overhang-uniqueness, and overlap-Tm rules. For PCR primers to generate the fragments, see tooluniverse-primer-design.
tools
Meta-analysis / evidence synthesis — pool effect sizes across studies (odds ratios, risk ratios, hazard ratios, mean differences, correlations, GWAS betas) with fixed- or random-effects models, quantify heterogeneity (Q, I², τ²), and build a forest plot. Use when you have results from MULTIPLE studies and need a single pooled estimate, or to synthesize evidence from a systematic review / multiple GWAS / replicated experiments. Handles the error-prone effect-size + standard-error preparation (converting OR/HR/CI, two-group means±SD, proportions, and correlations into the (effect, SE) the pooling step needs).