plugin/skills/tooluniverse-install-skills/SKILL.md
Detect and auto-install missing ToolUniverse research skills. Checks common Claude Code/Cursor/Codex skill directories for the canary file, and installs any missing skills if none found. Use when the plugin's research skills aren't loading, when migrating between clients, or when verifying a skill installation.
npx skillsauth add mims-harvard/tooluniverse tooluniverse-install-skillsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Checks whether the ToolUniverse specialized skills are installed and installs them automatically if not.
Use the Shell tool to check for the canary file across all common client locations:
ls .cursor/skills/tooluniverse-drug-research/SKILL.md 2>/dev/null \
|| ls .agents/skills/tooluniverse-drug-research/SKILL.md 2>/dev/null \
|| ls .windsurf/skills/tooluniverse-drug-research/SKILL.md 2>/dev/null \
|| ls .gemini/skills/tooluniverse-drug-research/SKILL.md 2>/dev/null \
|| ls .claude/skills/tooluniverse-drug-research/SKILL.md 2>/dev/null \
|| ls .opencode/skills/tooluniverse-drug-research/SKILL.md 2>/dev/null \
|| ls .trae/skills/tooluniverse-drug-research/SKILL.md 2>/dev/null \
|| ls .skills/tooluniverse-drug-research/SKILL.md 2>/dev/null \
|| echo "NOT_INSTALLED"
NOT_INSTALLED → proceed to installation.# 1. Download skills from GitHub (shallow, sparse — only skills/ folder)
git clone --depth 1 --filter=blob:none --sparse \
https://github.com/mims-harvard/ToolUniverse.git /tmp/tu-skills
cd /tmp/tu-skills && git sparse-checkout set skills
# 2. Copy to the correct directory for the detected client:
mkdir -p .cursor/skills && cp -r /tmp/tu-skills/skills/* .cursor/skills/ # Cursor
# mkdir -p .agents/skills && cp -r /tmp/tu-skills/skills/* .agents/skills/ # Codex/OpenAI
# mkdir -p .windsurf/skills && cp -r /tmp/tu-skills/skills/* .windsurf/skills/ # Windsurf
# mkdir -p .gemini/skills && cp -r /tmp/tu-skills/skills/* .gemini/skills/ # Gemini CLI
# mkdir -p .claude/skills && cp -r /tmp/tu-skills/skills/* .claude/skills/ # Claude Code
# mkdir -p .opencode/skills && cp -r /tmp/tu-skills/skills/* .opencode/skills/ # OpenCode
# mkdir -p .trae/skills && cp -r /tmp/tu-skills/skills/* .trae/skills/ # Trae
# mkdir -p .skills && cp -r /tmp/tu-skills/skills/* .skills/ # Cline/VS Code
# 3. Clean up
rm -rf /tmp/tu-skills
If the client cannot be detected automatically, ask the user which one they use before running step 2.
Detect the client from the presence of config files:
| Config file present | Client |
|---|---|
| .cursor/ | Cursor |
| .agents/ | Codex / OpenAI |
| .windsurf/ | Windsurf |
| .gemini/ | Gemini CLI |
| .claude/ | Claude Code |
| .opencode/ | OpenCode |
| .trae/ | Trae |
| None of the above | Ask the user |
Confirm success:
ls .cursor/skills/tooluniverse-drug-research/SKILL.md
Tell the user: "ToolUniverse skills installed successfully. You now have access to 50+ specialized research workflows."
tools
Generate the success criteria for a task or question, then review work against them. Given a task, goal, or open-ended question, decompose it into scenarios, evaluation perspectives, and fine-grained weighted YES/NO criteria using the Recursive Expansion Tree (RET) method; if work is supplied, score it criterion-by-criterion and surface what is missing or could be better. Use when asked to self-review or check your own work, judge whether a task is done well or completely, build a definition-of-done or completeness checklist, create an evaluation rubric or grading criteria, score or grade answers to a question, set up an LLM-as-judge rubric, or when the user mentions self-review, completeness check, success criteria, evaluation criteria, scoring rubric, Qworld, or the RET algorithm.
tools
Find the real protein target(s) of a peptide from its sequence — peptide target deorphanization / off-target identification, for ANY target class (GPCR, ion channel, protease, cytokine/growth-factor receptor, enzyme, integrin), not only GPCRs. Use when a peptide has a phenotype but does not bind its hypothesized target, when a peptide binds a target in one species or assay but not another, or to screen candidate targets for an orphan peptide. A target-class router steers a multi-route keyless pipeline (PROSITE/ELM motif, BLAST homology, HGNC/InterPro/GPCRdb/GtoPdb target-family enumeration, OpenTargets phenotype anchor, EnsemblCompara/Alliance cross-species reconciliation) plus optional NVIDIA-NIM co-folding (Boltz2, AlphaFold2-Multimer, OpenFold3) for structural confirmation.
tools
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.
tools
Install, set up, verify, update, pin, uninstall, or troubleshoot the ToolUniverse plugin on OpenAI Codex. ALWAYS consult this skill for any of those — don't answer from memory, because the exact marketplace name (mims-harvard/ToolUniverse), the "codex plugin marketplace add" then "codex plugin add -m tooluniverse" flow, Codex's startup auto-upgrade behavior, the uvx tooluniverse MCP server, and the API-key env vars are easy to get wrong. Use it whenever someone wants to get ToolUniverse (or "the 1000+ scientific tools" / "the harvard tools") working on Codex, says the Codex plugin or its tools/skills won't load, hits a uvx or MCP-server startup error, asks how Codex updates it, wants to pin or remove it, or finds it running an old tool version — even if they never say the word "plugin". Not for the Claude Code plugin (use tooluniverse-claude-code-plugin), for running research with the tools, or for authoring new tools or skills.