Workbench capy vm lane
Skill Fearvox/multica-ultimate-workbench/skills/workbench-capy-vm-lane
Public multi-agent workbench skill pack for SDD, review gates, context discipline, VM lanes, Sanity context, and autonomous agent coordination.
npx -y skills add Fearvox/multica-ultimate-workbench --skill workbench-capy-vm-laneAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 23 stars23 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Controlled VM/Computer execution lane for GUI, browser, sandbox, and screenshot-backed tasks.
SKILL.md
1.4 KB, as published. Nobody here has run it
Workbench Capy VM Lane
Use this skill only when an issue declares EXECUTION_TARGET: capy-vm or asks for isolated GUI/browser/sandbox execution.
Required Checks
Before execution:
- Confirm the issue has
VM_LEASE. - Confirm
secrets_policy. - Confirm
network_policy. - Confirm
ARTIFACTS_REQUIRED. - Confirm
TEARDOWN.
If any field is missing, return BLOCKED with the smallest missing field list.
Default Policy
secrets_policy: nonenetwork_policy: localhost-onlyfor smoke testsTEARDOWN: destroy- artifact root: local temp by default; set
CAPY_VM_ARTIFACT_DIRexplicitly for durable review evidence
Computer API Pattern
The local smoke path uses a Scrapybara-compatible Computer API:
curl -fsS -X POST "http://127.0.0.1:${CAPY_API_PORT}/computer" \
-H "Content-Type: application/json" \
-d '{"action":"take_screenshot"}'
The response must be saved before summarizing.
Report Contract
Always report:
- issue id,
- owner agent,
- execution target,
- lease fields,
- commands and exit codes,
- artifact paths,
- whether raw artifacts were kept outside Git,
- teardown state,
- residual risks,
VERDICT: PASS / FLAG / BLOCK.
Never paste base64 screenshots, raw cookies, OAuth codes, private tokens, API keys, or unrelated screen content into comments.