SKILLEMALL.ai

CD 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.

google-deepmind/science-skills Agent Skills author: google-deepmind 1 file body ≈ 370 tokens Open the sourcegithub.com↗ analyzed 2 h ago

Checks whether the uv Python package manager is installed and installs it if missing.

As a process D 48/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
C
89/100
safety, quality, tests
Safety 60%
98
Quality 40%
76
Run on models
none yet
Process rating
D
48/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 2

    ✓ No critical or high findings

    Medium and low: 2
    • low Dangerous commands cmd-pipe-to-shell-known-host SKILL.md:37
      Pipe-to-shell installer from a well-known host (still executes remote code) (quoted — discussed, not commanded)
      -   **Unix/macOS**: `curl -LsSf https://astral.sh/uv/install.sh | sh`
      quoted
    • low Dangerous commands cmd-execpolicy-bypass SKILL.md:38
      Runs PowerShell with execution policy bypassed (quoted — discussed, not commanded)
      -   **Windows (PowerShell)**: `powershell -ExecutionPolicy ByPass -c
      quoted

    Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 48/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 20When it triggers. No condition that starts the skill
    • 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
    • 100Steps. 4 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 370 tokens
    • 100Running it twice. No mutating operations
    • 100Progress reporting. Reports progress

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +4Structure: 2 headings, hard to scan
    • +3Output format is not stated: the model decides each time
    • +4No input/output examples
    • +1No license
    • +2Single-language instructions
    • +3Description length 162: enough signal without eating the budget
    • +3Step-by-step instructions: 4 items

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.