SKILLEMALL.ai

CB windows-vm

Create, manage, or connect to a headless Windows 11 VM running in Docker with SSH access. Use when the user wants to spin up, stop, restart, or SSH into a Windows VM.

obra/superpowers-lab Claude Code author: obra 1 file body ≈ 2 424 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Create, manage, or connect to a headless Windows 11 VM running in Docker with SSH access.

As a process B 76/100 · Nearly there — weak spots: result and completion, progress reporting

IntegrationDockerSoftware developmentInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
C
87/100
safety, quality, tests
Safety 60%
93
Quality 40%
78
Run on models
none yet
Process rating
B
76/100
Nearly there
Result and completion w 14
0
Progress reporting w 2
0
Failures and branches w 10
50
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Broad scope medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

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 · 3

    ✓ No critical or high findings

    Medium and low: 3
    • medium Broad scope meta-broad-allowed-tools SKILL.md:1
      Broad tool permissions pre-approved: Bash
      allowed-tools: Bash Read Write
    • low Dangerous commands cmd-execpolicy-bypass SKILL.md:125
      Runs PowerShell with execution policy bypassed (quoted — discussed, not commanded)
      cat << 'PS' | sshpass -p 'password' ssh -o StrictHostKeyChecking=no -p 2222 user@localhost "powershell -ExecutionPolicy Bypass -Command -"
      quoted
    • low Dangerous commands cmd-execpolicy-bypass SKILL.md:219
      Runs PowerShell with execution policy bypassed (quoted — discussed, not commanded)
      - **Escaping hell** — Running PowerShell commands over SSH with nested quotes is unreliable. Pipe scripts via stdin using `powershell -ExecutionPolicy Bypass -Command -` instead.
      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 76/100

    • 0Result and completion. Does not say what the result is
    • 0Progress reporting. Says nothing while it works
    • 50Failures and branches. 0 branches, has a failure section
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Tools and files. Tools declared in frontmatter
    • 100Steps. 34 steps
    • 100When it triggers. States when to use and when not to
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2424 tokens
    • 100Running it twice. Mutating operations check current state

    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)
    • +3Output format is not stated: the model decides each time
    • -4Absolute local paths (C:\Users, /home/…): not portable
    • -2localhost URLs: will not work for another user
    • +1No license
    • +2Single-language instructions
    • +3Description length 166: enough signal without eating the budget
    • +4Structure: 13 headings
    • +3Step-by-step instructions: 34 items
    • +4Has examples (16 code blocks)

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