CtrlK
BlogDocsLog inGet started
Tessl Logo

uv

Checks whether the uv Python package manager is installed and installs it if missing. Ensures uv is on PATH. Use when another skill requires uv as a prerequisite.

75

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-3

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

The body is a tight, actionable setup procedure with platform-specific commands and clear validation branching at each step. Its only weakness is minor marketing-fluff phrasing in the install-pitch step that adds tokens without aiding execution.

Suggestions

Tighten step 3(a): drop the "tool for creating a consistent and reliable Python environment" framing and simply tell the user you need to install uv before continuing.

Trim the intro paragraph — Claude already knows what uv is; keep only the project-specific note that Science Skills depend on it being on PATH.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete commands, but includes unnecessary padding such as telling the user uv is "a tool for creating a consistent and reliable Python environment" (step 3a) and an intro sentence restating what uv is — could be tightened.

2 / 3

Actionability

Provides fully executable, copy-paste-ready commands for both Unix/macOS and Windows (curl install, PowerShell install, export PATH), with specific version-check commands.

3 / 3

Workflow Clarity

Clear numbered sequence with explicit validation gates — "If this succeeds... skip the remaining steps", "If either succeeds, skip to step 4", and a final verify via `uv --version` — giving feedback branches at each checkpoint.

3 / 3

Progressive Disclosure

A simple under-50-line skill with no external references needed; it is well-organized into a Setup section with clearly ordered steps, which satisfies the simple-skill allowance.

3 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

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

The description is concise, specific, and complete: it states concrete actions and an explicit use-trigger tied to uv being a prerequisite for other skills. It avoids vague language and over-claims.

DimensionReasoningScore

Specificity

Names multiple concrete actions — "Checks whether the uv Python package manager is installed and installs it if missing" and "Ensures uv is on PATH" — matching the anchor for listing several specific actions.

3 / 3

Completeness

Explicitly answers both what (checks/installs/ensures PATH) and when via the "Use when another skill requires uv as a prerequisite" trigger clause.

3 / 3

Trigger Term Quality

Uses natural terms a user would say — "uv Python package manager", "installed", "PATH", "prerequisite" — giving good coverage rather than jargon.

3 / 3

Distinctiveness Conflict Risk

Scoped to a single tool (uv) as a dependency prerequisite, giving it a clear niche unlikely to conflict with other skills.

3 / 3

Total

12

/

12

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
google-deepmind/science-skills
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.