CtrlK
BlogDocsLog inGet started
Tessl Logo

setup-tooluniverse

Install and configure ToolUniverse for any use case — MCP server (chat-based), CLI (command line with 14 subcommands), or Python SDK (Coding API with 3 calling patterns). Covers uv/uvx setup, MCP configuration for 12+ AI clients (Cursor, Claude Desktop, Windsurf, VS Code, Codex, Gemini CLI, Trae, Cline, etc.), full CLI reference (tu list/grep/info/find/run/test/status/build/remote/doctor/serve/connect/connections/disconnect), Coding API quickstart, agentic tools, code executor, API key walkthrough, skill installation, and upgrading. Use when user asks how to set up ToolUniverse, which access mode to use (MCP vs CLI vs SDK), configuring MCP servers, using the CLI, troubleshooting installation, upgrading, or mentions installing ToolUniverse or setting up scientific tools. Also triggers for "how do I use ToolUniverse", "what's the best way to access tools", "command line", "tu command", "coding API", "tu build".

70

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is setup-tooluniverse in mims-harvard/ToolUniverse

SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-sequenced setup guide with strong validation checkpoints and troubleshooting. Its two real weaknesses are token bloat from inlined reference material and over-explanation, and a bundle-structure problem: one referenced file is missing and four provided diagnostic scripts are never surfaced.

Suggestions

Fix or remove the broken reference to API_KEYS_REFERENCE.md (the file is absent from the bundle) — either ship it under references/ or fold the key tiers inline deliberately.

Link the four scripts/ diagnostics (e.g. check_prerequisites.py, diagnose_setup.py) from the relevant sections (Common Issues / Step 4) so the bundled tooling is discoverable.

Move the inlined bulk — the full CLI subcommand table, the prompt cheat sheet, and the per-client config-location tables — into references/ files and keep one-line summaries in SKILL.md to cut token cost.

DimensionReasoningScore

Conciseness

Mostly efficient, but padded with explanation Claude doesn't need and bulk that belongs in references: 'Config files are plain text that store settings — like a preference list for the app', instructions for opening Terminal on Mac/Windows, and fully inlined CLI subcommand, API-key tier, and prompt-cheat-sheet tables. Fits the level-3 anchor ('could be tightened') better than 4, which allows only minor trimming.

3 / 5

Actionability

Fully executable throughout: copy-paste install commands ('curl -LsSf https://astral.sh/uv/install.sh | sh'), complete MCP JSON config blocks, per-client config file paths, exact CLI invocations with JSON arguments, and a validation one-liner ('python3 -m json.tool < <path-to-config> > /dev/null && echo "JSON OK"').

5 / 5

Workflow Clarity

Steps 1-5 are clearly sequenced with explicit checkpoints and feedback loops: 'Verify: uv --version', 'Then validate before restarting the app', a dedicated 'Step 4: Test Together' with concrete test calls, and an 'If issues' recovery path backed by an extensive Common Issues table — matching the level-5 anchor.

5 / 5

Progressive Disclosure

Against the actual bundle: references/mcp-configs.md exists and is clearly signaled, but the referenced 'API_KEYS_REFERENCE.md' does not exist in the bundle, and all four scripts/ files (check_prerequisites.py, diagnose_setup.py, verify_installation.py, list_tool_categories.py) are never linked from SKILL.md. Combined with reference-worthy content inlined (CLI table, key tiers, cheat sheet), this sits between the level-3 and level-4 anchors, closer to 3.

3 / 5

Total

16

/

20

Passed

Description

96%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An excellent description: concrete, comprehensive, and explicit about both capabilities and trigger conditions. The only weakness is a handful of generic trigger phrases ('command line', 'coding API') that are not ToolUniverse-specific and could cause occasional false triggers.

Suggestions

Qualify generic trigger phrases, e.g. 'command line' -> 'ToolUniverse command line (tu)' and 'coding API' -> 'ToolUniverse Coding API', to reduce false-trigger risk.

Trim the long client list ('Cursor, Claude Desktop, Windsurf, VS Code, Codex, Gemini CLI, Trae, Cline, etc.') — '12+ AI clients' plus two examples conveys the same information more concisely.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions with comprehensive coverage: 'Install and configure ToolUniverse... MCP server (chat-based), CLI (command line with 14 subcommands), or Python SDK (Coding API with 3 calling patterns)' and enumerates subcommands ('tu list/grep/info/find/run/test/status/build/...'), agentic tools, code executor, API key walkthrough, and upgrading.

5 / 5

Completeness

Explicitly answers both what ('Install and configure... Covers uv/uvx setup, MCP configuration for 12+ AI clients...') and when ('Use when user asks how to set up ToolUniverse... Also triggers for...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural terms including synonyms and user phrasings: 'how do I use ToolUniverse', 'tu command', 'command line', 'coding API', 'tu build', 'configuring MCP servers', 'setting up scientific tools'. Fits the level-5 anchor; level 4 would require natural terms actually missing.

5 / 5

Distinctiveness Conflict Risk

Anchored by a clear niche ('ToolUniverse', 'tu command', 'tu build') with minimal conflict risk, but generic trigger phrases like 'command line', 'coding API', and 'what's the best way to access tools' could fire on unrelated questions — minor overlap risk, matching the level-4 anchor rather than 5.

4 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
mims-harvard/ToolUniverse
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.