AB ssh-handoff
Create and reuse a secure shared terminal handoff when a human must authenticate first and the agent must resume work in the same shell session afterward. Use for SSH handoff, sudo handoff, browser-opened temporary terminal access, or LAN-restricted terminal sharing backed by tmux when direct agent authentication is blocked or undesirable.
As a process B 65/100 · Nearly there — weak spots: result and completion, progress reporting
How to improve
- 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-background-processscripts/start-local-web-terminal.sh:52Starts a background / autostarted processnohup "${CMD[@]}" >/tmp/ttyd-"$SESSION_NAME".log 2>&1 & -
low Exfiltration
exfil-secret-in-urlscripts/start-url-token-web-terminal.sh:331Credential passed in a URL query string (normal for some APIs — verify the host is the intended service) (placeholder value)URL="http://$HOST:$PROXY_PORT/?token=…"
placeholder
Files scanned: 10. 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 65/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Failures and branches. 7 branches
- 85Steps. 72 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2100 tokens
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +1No license
- +2Single-language instructions
- +3Description length 341: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 72 items
- +4Has examples (11 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
- +3All 4 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.