create-tooluniverse-skill
Create high-quality ToolUniverse skills following test-driven, implementation-agnostic methodology. Integrates tools from ToolUniverse's 1,264+ tool library, creates missing tools when needed, tests thoroughly, and produces skills with Python SDK + MCP support.
- License 许可
- MIT
- 最近更新
- 2026-11-02
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- create-tooluniverse-skill
- description
- Create high-quality ToolUniverse skills following test-driven, implementation-agnostic methodology. Integrates tools from ToolUniverse's 1,264+ tool library, creates missing tools when needed, tests thoroughly, and produces skills with Python SDK + MCP support.
03 SKILL.md 正文
Create ToolUniverse Skill
Systematic workflow for creating production-ready ToolUniverse skills.
Core Principles
Build on the 10 pillars from devtu (optimize-skills mode):
- 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 mode) |
| 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
Phase 2: Tool Discovery and Testing
Phase 3: Tool Creation (If Needed)
Phase 4: Implementation
Phase 5: Documentation
Phase 6: Validation
Phase 7: Packaging
Skill Integration
Quality Indicators
Reference Files
04 同仓库更多 Skills
clarify-requirements
Resolve genuine pre-execution ambiguity by scanning repo context, generating 1-6 grounded options, and asking 1-3 focused questions via AskUserQuestion. NOT for mid-task use (injection risk); NOT when the goal is already unambiguous; use to disambiguate vague prompts before any file edits.
openmm-md
Run FREE, open-source, Windows-native GPU molecular dynamics via the openmm-md MCP (OpenMM + CUDA on the local NVIDIA GPU). Use for protein / protein-ligand MD when you want a free stack or are on Windows without a Schrodinger license. Covers the full workflow (prepare, solvate, minimize, equilibrate, production, analyze, mmgbsa) AND an honest decision guide vs Schrodinger Desmond, including how to run Desmond legitimately on Linux or a cloud GPU with a real license. This is a deliberately LESSER free alternative and does NOT replace the schrodinger MCP tools. Do NOT use it to pick a free tool when a validated FEP+, WaterMap, IFD-MD, or Prime MM-GBSA result is actually required.
visual-review
Take screenshots of web pages and UI using Playwright for visual review and iteration
status
Diagnostic status report — shows metaswarm installation state, project setup, and potential issues
start
Use when starting work on any task, when the user mentions metaswarm, or when the user wants to begin tracked development work
setup
Interactive project setup — detects your project, configures metaswarm, writes project-local files