CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tooluniverse-antigravity-plugin

Install, set up, verify, update, pin, uninstall, or troubleshoot the ToolUniverse plugin on Google Antigravity (AGY / Antigravity IDE / Antigravity 2.0). ALWAYS consult this skill for any of those — don't answer from memory, because the exact CLI name (agy), the "agy plugin install <path>" flow, 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 2,700+ scientific tools" / "the harvard tools") working on Antigravity, says the Antigravity plugin or its tools/skills won't load, hits a uvx or MCP-server startup error, asks how Antigravity updates it, wants to pin or remove it, or finds it running an old tool version. Not for the Codex plugin (use tooluniverse-codex-plugin) or Claude Code plugin (use tooluniverse-claude-code-plugin), for running research with the tools, or for authoring new tools or skills.

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

78%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 tight, executable install/verify/troubleshoot guide with a strong verification checkpoint and error-recovery table. Its main weaknesses are coverage gaps: the description promises pin and uninstall flows the body never provides, and the update path lacks a version-verification step; minor redundancy with the description keeps conciseness just below lean.

Suggestions

Add Uninstall and Pin sections with concrete commands (e.g., the agy plugin removal command and a uvx version-pinning syntax) — the description explicitly promises both operations, but the body gives no guidance for either.

Add a version-check command to Update and Troubleshooting (e.g., `uvx tooluniverse --version`) so users can verify an update actually took effect before restarting.

Trim the 'What you get' table and the natural-language example prompts, which mostly restate the frontmatter description — this would lift conciseness to anchor 5.

DimensionReasoningScore

Conciseness

Mostly lean — commands with inline fix comments, expected-output JSON, and symptom→fix tables, with no concept padding Claude already knows. However, the natural-language example prompts ("What are the top mutated genes in breast cancer?") and the "What you get" table largely restate the frontmatter description and could be trimmed, matching anchor 4 ("minor instances of over-explanation that could be trimmed") rather than anchor 5's every-token-earns-its-place.

4 / 5

Actionability

Every command present is copy-paste ready and executable ("agy plugin install /path/to/ToolUniverse/plugin", "uv cache clean tooluniverse", "uv python install 3.12", the export lines). But "pin" and "uninstall" — explicitly promised in the description ("update, pin, uninstall") — have no commands anywhere in the body, a coverage gap that keeps it below anchor 5's "specific examples cover the common cases"; it stays above anchor 3 because nothing present is vague or pseudocode.

4 / 5

Workflow Clarity

The install flow is clearly sequenced with an explicit validation checkpoint ("Verify it worked" with the expected `agy plugin list` output) and the troubleshooting table provides symptom→fix error recovery. But the Update flow ("uv cache clean tooluniverse" + restart) has no way to verify the running version actually changed, and the promised pin/uninstall workflows are absent entirely — "clear sequence with most checkpoints present; minor validation gaps" (anchor 4) rather than anchor 5's fully gated validation loops.

4 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/ directories), and this ~100-line self-contained skill needs none: sections are well organized (Prerequisites → Install → Verify → What you get → API keys → Update → Troubleshooting) with all content appropriately inline and easy to navigate. Per the rubric's simple-skill note, a skill with no need for external references scores 5 with well-organized sections.

5 / 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 model description: concrete lifecycle actions, dense natural-language triggers including synonyms and user-voice failure phrasings, an explicit 'Use it whenever...' clause, and clear not-for disambiguation from sibling skills. It matches the anchor-5 example pattern on every dimension with no vague or padded language.

DimensionReasoningScore

Specificity

Opens with seven concrete lifecycle actions ("Install, set up, verify, update, pin, uninstall, or troubleshoot") and names exact artifacts ("agy plugin install <path>", "uvx tooluniverse MCP server", "API-key env vars"), matching anchor 5's comprehensive multi-action coverage; nothing is generic enough to sit at 4.

5 / 5

Completeness

Explicitly answers both questions: 'what' via the opening action list and 'when' via "Use it whenever someone wants to get ToolUniverse... working on Antigravity" with concrete trigger scenarios, plus negative scope ("Not for the Codex plugin (use tooluniverse-codex-plugin)..."). This mirrors the anchor-5 example's what + when + concrete-triggers pattern; a 4 would require a less explicit 'when' clause, which is not the case here.

5 / 5

Trigger Term Quality

Covers natural user phrasings and synonyms comprehensively: "the 2,700+ scientific tools" / "the harvard tools", "says the Antigravity plugin or its tools/skills won't load", "hits a uvx or MCP-server startup error", "running an old tool version", plus platform variants (AGY / Antigravity IDE / Antigravity 2.0). This matches anchor 5's comprehensive synonym coverage; no common way a user would phrase this need is obviously missing.

5 / 5

Distinctiveness Conflict Risk

Clear niche (ToolUniverse on Google Antigravity specifically, with platform synonyms) and explicit redirects to sibling skills ("use tooluniverse-codex-plugin", "use tooluniverse-claude-code-plugin") and non-goals ("not for... running research with the tools, or for authoring new tools or skills") — minimal conflict risk per anchor 5.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

mims-harvard/ToolUniverse

Path

plugin/skills/tooluniverse-antigravity-plugin/SKILL.md

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.