Menu

Individual skill

tooluniverse-connect

0upvotes

How to use ToolUniverse Connect (connect.aiscientist.tools), the hosted ToolUniverse service, and when to use it instead of ToolUniverse installed on this computer. Use when the user asks how to use ToolUniverse or ToolUniverse Connect, how to connect Claude, Claude Code or Codex, whether to use the hosted service or a local install, why a tool says a login or API key is missing and where to add it, how to share a model or script with colleagues, how to use a colleague's computer or a TU-SHARE code, how to publish a tool, or when ToolUniverse tools are missing, signed out or not connecting.

plugin/skills/tooluniverse-connect/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

# ToolUniverse Connect: what each part is for and how to use it

The person you are helping is usually a scientist, not a programmer. Answer in plain words, one step at a time. When you can do a step yourself (run a command, call a tool), do it; ask the user only for what only they can do, such as signing in or clicking **Allow**.

**Never ask the user to paste a key, token or password into the chat, and never write one into a file or command yourself.**

## 1. Find out which ToolUniverse this user has

| What you see | The user is on |
|---|---|
| ToolUniverse tools such as `what_can_i_use`, `list_skills` or `get_skill`, from the server `https://mcp.aiscientist.tools` (earlier setups: `https://tooluniverse-backend.onrender.com/mcp`, which still works) | **ToolUniverse Connect** (hosted) |
| A ToolUniverse server started on this computer (`uvx tooluniverse`, `tu serve`), the `tu` command, or Python `from tooluniverse import ToolUniverse` | **Local ToolUniverse** |
| No ToolUniverse tools at all | **Not connected yet** |
Back to top