Create Tooluniverse Skill

This is a structured workflow for building ToolUniverse skills with a test-first methodology across seven phases, from domain analysis through packaging. It enforces testing tools before writing any documentation, keeps SKILL.md files implementation-agnostic (no Python or MCP code), and includes fallback strategies for when tools fail. The 10-pillar foundation emphasizes verifying tool contracts rather than trusting function names, handling SOAP operations correctly, and grading evidence in tiers. Expect to spend 90 to 120 minutes per skill if you're not creating new tools. The approach is rigid by design, with validation checklists and mandatory test scripts, which makes sense if you're building a catalog where consistency matters more than speed.

skills.sh installs: 412
GitHub stars: 1.8K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add mims-harvard/tooluniverse --skill create-tooluniverse-skill --agent claude-code

Installs into .claude/skills of the current project.

Files

Create ToolUniverse Skill

Systematic workflow for creating production-ready ToolUniverse skills.

The devtu-* skills this one hands off to are no longer in this repository. devtu-optimize-skills, devtu-create-tool and devtu-fix-tool moved to the tu-harness plugin (tooluniverse/tooluniverse-harness), because they operate on this repository rather than being something a user of it calls. Install them with claude plugin install tu-harness@tooluniverse-harness; the references below name them by skill, so they resolve once that plugin is present. This skill is maintainer-facing too -- it is not in the user-facing plugin mirror -- and belongs beside them; it has not moved yet only because nothing forced the question.