What problem does it solve? Engineers testing applications against Veris sandbox twins need detailed operational knowledge—seeding state, arming faults, intercepting traffic, reading receipts—without loading every reference document into context at once. This Skill supplies the exact reference file a setup, build, or fix command needs for the step it is on. ## Core Features & Use Cases - On-demand reference routing: Maps each workflow situation (twin inspection, state seeding, faults, webhooks, hosted runners, troubleshooting) to the specific Markdown file to read. - Execution tier guidance: Documents the container, host, direct, and hosted (Daytona/E2B) tiers for running unmodified application code against a twin with production hostnames. - Evidence and fault discipline: Explains receipts, trace watermarks, fault rows, credential modes, and the sandbox clock so test results are attributable to the current run. - Use Case: While fixing a bug where a lost Stripe response duplicates an invoice, the fix command reads faults.md to arm a hang fault with phase: after, then run.md to execute the application's own test through veris run and interpret the receipt. ## Quick Start Ask the veris setup, build, or fix command to handle your task, and it will read the appropriate reference file from this Skill for each step.
