How do I install the Veris Reference skill?

Run npx skillmds@latest add veris-ai/veris-reference in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Veris Reference safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Veris Reference?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Veris Reference free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Veris Reference?

veris-ai (@veris-ai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Veris Reference by veris-ai — Agent Skill

Name: Veris Reference
Author: veris-ai

Veris Reference

Knowledge the veris plugin commands read on demand - asking the twin, seeding and keeping state, faults and the clock, webhooks, troubleshooting, the PR evidence shape. Not a command; setup, build and fix name the file to read.

veris-ai d993ae5 19 files · 165.0 KB Updated Sep 17, 2026

File contents

Not a command. setup, build and fix link to the file a step needs:

file	read it when
`twin.md`	a design rests on a claim about the vendor, or you need to see what the vendor did: manual, schema, operations, data, trace
`state.md`	seeding rows and files, isolation inside a sandbox, reset, snapshots and the baseline
`run.md`	exercising the change with `veris run`: the two tiers, the image, what the run hands the workload, the flags that change the verdict, exit codes, what a green proves
`direct.md`	the app reads every vendor base URL from the environment and needs no proxy
`session.md`	current tools/context indicate an existing plugin-managed sandbox: verify identity, reuse interception, attribute receipts and sync changes
`opencode.md`	the existing session is OpenCode: provider tools, credentials, trust, control access and lifecycle differences
`hosted.md`	the engineer requests remote tests, or code needs redirection and Docker is unavailable: provider recipes, remote workload preparation, trace evidence, project notes and cleanup
`daytona.md`	the hosted tier selects Daytona: published SDK, existing-twin attachment, images, upload, trust, egress, callbacks and deletion
e2b.md	the hosted tier selects E2B: published SDK, existing-twin attachment, templates, upload, trust, network policy, callbacks and deletion
`faults.md`	the task is about a failure, or a case needs a condition the vendor will not produce on demand: fault rows, credentials, the clock
`webhooks.md`	the application receives callbacks
`troubleshooting.md`	what the receipt, an exit code, a trace tier, a certificate error, a vendor-shaped error or a sandboxed agent's `doctor` lines mean
`evidence.md`	writing the PR's verification section
`proof.md`	what closes a claim: the three layers, the ledger's four dispositions, the identity a fix rests on

In a verified plugin session, session.md replaces CLI operations and lifecycle with the discovered session interfaces. Otherwise twin operations use veris; veris <command> --help documents its flags. Hosted runner commands are documented in their provider recipe. Three twin operations have no verb of their own: file upload, a per-twin reset, the operations list. Each of those is a curl to the twin's control URL, which veris sandbox services get <twin> prints, and the file that covers it shows the call. scripts/ holds record.sh and ledger.sh, the measurement ledger fix uses; setup step 9 copies them into the repository's .veris/bin/.

---name: veris-referencedescription: Knowledge the veris plugin commands read on demand - asking the twin, seeding and keeping state, faults and the clock, webhooks, troubleshooting, the PR evidence shape. Not a command; setup, build and fix name the file to read.---Not a command. `setup`, `build` and `fix` link to the file a step needs:| file | read it when ||---|---|| `twin.md` | a design rests on a claim about the vendor, or you need to see what the vendor did: manual, schema, operations, data, trace || `state.md` | seeding rows and files, isolation inside a sandbox, reset, snapshots and the baseline || `run.md` | exercising the change with `veris run`: the two tiers, the image, what the run hands the workload, the flags that change the verdict, exit codes, what a green proves || `direct.md` | the app reads every vendor base URL from the environment and needs no proxy || `session.md` | current tools/context indicate an existing plugin-managed sandbox: verify identity, reuse interception, attribute receipts and sync changes || `opencode.md` | the existing session is OpenCode: provider tools, credentials, trust, control access and lifecycle differences || `hosted.md` | the engineer requests remote tests, or code needs redirection and Docker is unavailable: provider recipes, remote workload preparation, trace evidence, project notes and cleanup || `daytona.md` | the hosted tier selects Daytona: published SDK, existing-twin attachment, images, upload, trust, egress, callbacks and deletion || [e2b.md](e2b.md) | the hosted tier selects E2B: published SDK, existing-twin attachment, templates, upload, trust, network policy, callbacks and deletion || `faults.md` | the task is about a failure, or a case needs a condition the vendor will not produce on demand: fault rows, credentials, the clock || `webhooks.md` | the application receives callbacks || `troubleshooting.md` | what the receipt, an exit code, a trace tier, a certificate error, a vendor-shaped error or a sandboxed agent's `doctor` lines mean || `evidence.md` | writing the PR's verification section || `proof.md` | what closes a claim: the three layers, the ledger's four dispositions, the identity a fix rests on |In a verified plugin session, [session.md](session.md) replaces CLI operationsand lifecycle with the discovered session interfaces. Otherwise twin operations use `veris`; `veris <command> --help` documents its flags. Hostedrunner commands are documented in their provider recipe. Three twin operations haveno verb of their own: file upload, a per-twin reset, the operations list. Each of thoseis a `curl` to the twin's control URL, which`veris sandbox services get <twin>` prints, and the file that covers it shows the call.`scripts/` holds `record.sh` and `ledger.sh`, the measurement ledger `fix` uses;`setup` step 9 copies them into the repository's `.veris/bin/`.

Frequently asked questions