From mims-harvard-tooluniverse
Creates production-ready ToolUniverse skills via 7-phase test-driven workflow: analyzes domain, discovers/tests tools from 1,264+ library, implements Python SDK + MCP, documents agnostically.
npx claudepluginhub joshuarweaver/cascade-data-analytics --plugin mims-harvard-tooluniverseThis skill uses the workspace's default tool permissions.
Systematic workflow for creating production-ready ToolUniverse skills.
CODE_TEMPLATES.mdOPTIMIZE_INTEGRATION.mdPACKAGING_TEMPLATE.mdPARAMETER_VERIFICATION.mdQUICKSTART_TEMPLATE.mdSKILL_TEMPLATE.mdTESTING_GUIDE.mdVALIDATION_CHECKLIST.mdassets/skill_template/QUICK_START.mdassets/skill_template/python_implementation.pyassets/skill_template/test_skill.pyreferences/devtu_optimize_integration.mdreferences/implementation_agnostic_format.mdreferences/skill_standards_checklist.mdreferences/tool_testing_workflow.mdscripts/test_tools_template.pytest_tools_template.pyConducts multi-round deep research on GitHub repos via API and web searches, generating markdown reports with executive summaries, timelines, metrics, and Mermaid diagrams.
Dynamically discovers and combines enabled skills into cohesive, unexpected delightful experiences like interactive HTML or themed artifacts. Activates on 'surprise me', inspiration, or boredom cues.
Generates images from structured JSON prompts via Python script execution. Supports reference images and aspect ratios for characters, scenes, products, visuals.
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 |