AC proxima-vps-setup
Set up, repair, or document a Proxima deployment on a remote Ubuntu VPS with a non-root Electron runtime, virtual desktop GUI, loopback-only VNC/noVNC/REST exposure, and SSH-stdio MCP access for local IDEs like Antigravity, Windsurf, Zed, or Claude Desktop. Use when a user asks to install Proxima on a VPS, expose the GUI safely, make REST reachable through SSH tunnels, configure `proxima-mcp`, or troubleshoot remote MCP/GUI connectivity.
As a process C 53/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, consistency
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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Dangerous commands
cmd-background-processreferences/server-setup-runbook.md:227Starts a background / autostarted processsystemctl enable --now proxima-user-xvfb.service
-
low Dangerous commands
cmd-background-processreferences/server-setup-runbook.md:228Starts a background / autostarted processsystemctl enable --now proxima-user-xfce.service
-
low Dangerous commands
cmd-background-processreferences/server-setup-runbook.md:229Starts a background / autostarted processsystemctl enable --now prox…ice
-
low Dangerous commands
cmd-background-processreferences/server-setup-runbook.md:230Starts a background / autostarted processsystemctl enable --now proxima-user-novnc.service
-
low Dangerous commands
cmd-background-processreferences/server-setup-runbook.md:261Starts a background / autostarted processsystemctl enable --now proxima-app.service
Files scanned: 7. 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 53/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (proxima-vps-setup) differs from the folder (proxima-vps)
- 55Failures and branches. 1 branches
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 22 steps
- 100Execution cost. Instruction body is 548 tokens
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)
- +4No input/output examples
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +3Description length 441: enough signal without eating the budget
- +4Structure: 5 headings
- +3Step-by-step instructions: 22 items
- +3Output format is stated explicitly
- +4Reference files are cited in the instructions (4 of 4)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.