Configure a repository's Veris sandbox wiring and verify one application run against service twins.
npx skills add https://github.com/veris-ai/plugins --skill setup-veris-ai
Please help me install this Agent Skill. Skill: setup Source: https://github.com/veris-ai/plugins/tree/main/veris/skills/setup Command: npx skills add https://github.com/veris-ai/plugins --skill setup-veris-ai
veris doctor, and resolves login, Docker, and sandboxing issues before wiring anything. - Tier selection and environment creation: Chooses between direct, container, and hosted execution tiers based on how the code calls vendors, then creates or adopts a Veris environment with the required services. - Proving run and handoff: Runs the smallest vendor-calling test through veris run, validates the receipt ledgers, and writes .veris/twin.yaml, .veris/NOTES.md, and .veris/setup.json for later tasks. - Use Case: An engineer adds Veris to a repository that calls Stripe and Google Calendar; the Skill identifies the vendor hostnames, creates the environment, proves a test run reaches both twins, and saves the verified command. ## Quick Start Ask the assistant to run the Veris setup command to wire this repository and verify one application test run against the service twins.High-intent search queries and answers about installing and using this skill.
Run the setup command, which checks the session and machine with `veris doctor`, identifies vendor hostnames from the code, creates an environment with the required services, and proves one test run reaches the twins. It saves the working command in `.veris/NOTES.md` for later build and fix runs.
Use the direct tier when every vendor URL comes from an environment variable the app already reads. Use the container tier (`veris run --image`) when hostnames are hardcoded and Docker is available. Use the hosted tier when remote execution is requested or Docker cannot run.
Docker is required only for the container tier. The direct tier needs no proxy at all, and the hosted tier runs tests in a remote box, so setup can proceed without a local Docker daemon in those paths.
Exit 3 means a requirement was unmet, usually because the test never calls the vendor, the hostname has no matching twin, the SDK refused the proxy certificate, or the twin is a non-proxied data plane. The Skill checks each cause in order without changing the test's vendor call.
Yes, but only when the existing environment belongs to this project, meaning its services exactly match your list or its server name is the project's. Adopt it with `veris env create <name> --from <full id>`; otherwise create a new environment to avoid sharing state with another project.
truefoundryInstrument Python and TypeScript apps with OpenTelemetry tracing via Traceloop SDK.
JhabbigVerify work completion against fresh command output and execution evidence.
spyqsDiagnose NanoClaw container agent failures via logs and mounts.
HKUDSManage WireMock server stubs, requests, and scenarios via command-line tools.