Individual skill

create-tooluniverse-skill

Create high-quality ToolUniverse skills following test-driven, implementation-agnostic methodology.

skills/create-tooluniverse-skill/SKILL.md

Read pinned source

Source commit 5598a9fc97e32964fe9b703818e7d0747142f179

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,780
Repository last updated
Nov 8, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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](https://github.com/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
Back to top