CtrlK
BlogDocsLog inGet started
Tessl Logo

tooluniverse-cs-setup

Install or update ToolUniverse in Claude Science — create the conda env, install the tooluniverse pip package, and (re)build the tooluniverse-research skill by fetching the current workflow library from GitHub. Use for first-time setup, upgrading the ToolUniverse version, refreshing the bundled workflows after an upstream release, or reinstalling on a new machine.

74

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 well-structured, highly actionable skill body: numbered executable steps, a verification section, and concise operational notes. Main gaps are the absence of an explicit failure-recovery loop and minor over-explanation in the framing prose.

Suggestions

Add a short error-recovery note under Verify (e.g., 'if the sidecar gate rejects kernel.py, fix the errors and rerun step 4') to turn the validation checkpoint into a full feedback loop.

Trim the intro paragraph's restatement of how Claude Science differs from Claude Code to only the non-obvious delta, letting the steps speak for themselves.

Clarify in step 3 what to inspect in the returned dict (n_workflows, dropped) so the user can confirm the rebuild succeeded before publishing.

DimensionReasoningScore

Conciseness

Mostly lean and efficient — code blocks carry the load and the Notes explain non-obvious facts (cache redirect, dropped plugin entries). The intro paragraph and a few Notes lines edge toward over-explanation that could be trimmed slightly; not a 5 because some explanatory framing restates context Claude can infer.

4 / 5

Actionability

Fully executable, copy-paste-ready code for all four steps with exact function calls, parameters, a version-pinning example, and a Verify section showing real expected output — concrete guidance covering the common cases.

5 / 5

Workflow Clarity

A clearly sequenced four-step process with a dedicated Verify section and an explicit validation checkpoint (the sidecar-gate refusal on publish). Not a 5 because there is no explicit error-recovery/feedback loop describing what to do when verify or the gate fails.

4 / 5

Progressive Disclosure

Well-organized into Full install, Verify, and Notes sections with no nested references and a self-contained single file. Not a 5 because the body slightly exceeds the ~50-line simple-skill threshold and no progressive-disclosure mechanism (split references) is demonstrated or needed, keeping it just below the top anchor.

4 / 5

Total

17

/

20

Passed

Description

100%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.

A strong description: concrete actions, natural trigger terms, explicit what-and-when guidance, and a distinct niche. Uses third-person imperative voice throughout with no vague fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'create the conda env, install the tooluniverse pip package, and (re)build the tooluniverse-research skill by fetching the current workflow library from GitHub' — giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both 'what' (the enumerated install/rebuild actions) and 'when' via the 'Use for first-time setup, upgrading... or reinstalling on a new machine' clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases a user would say — 'first-time setup', 'upgrading the ToolUniverse version', 'refreshing the bundled workflows after an upstream release', 'reinstalling on a new machine' — covering the common invocation scenarios comprehensively.

5 / 5

Distinctiveness Conflict Risk

Targets a clearly named niche (ToolUniverse setup in Claude Science) with distinct triggers, making overlap with unrelated skills minimal.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.