ToolUniverse SDK — build and test agent tools

Prerequisites: a Python environment and the ToolUniverse repo checked out where the agent can add tool definitions — no key needed for local development; a ToolUniverse API key only for remote registration/release (save it in the secure vault, never paste a live key here) Install "ToolUniverse SDK — build and test agent tools" for me. It gives my agent @mims-harvard's ToolUniverse development workflow: add or update local tool definitions (run/register_tool/register_remote_tool APIs), generate test cases with TestCaseGenerator (from config docs or plain-text requirements), validate through the iterate_and_validate loop (server_mode API server, local tool sync, iterate the LLM agent through failures until the tool passes), then release via the ToolUniverse HTTP API (/tools/register_remote_tool, /release) — with reference docs on the tool data model, OpenAPI import, the HTTP API client and test-case generator config. Apache-2.0-licensed. Repository: https://github.com/mims-harvard/tooluniverse/blob/main/plugin/skills/tooluniverse-sdk/SKILL.md 1. Fetch the SKILL.md file from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code — the only credentials are TOOLUNIVERSE_API_KEY and optionally OPENAI_API_KEY as environment variables, never committed. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "tooluniverse-sdk". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. clone the ToolUniverse repo and point the agent at my Python environment; save a ToolUniverse API key in the secure vault if I want remote registration/release — that's on me). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.