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.