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.
- Installs
- 377
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/veris-ai/plugins --skill veris-reference- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads veris-reference automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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, a 401/404 from /veris/* or a sandboxed agent's doctor lines mean |
evidence.md | writing a concise result with existing evidence and material limitations |
proof.md | interpreting test evidence, investigating retry/identity behavior, or using optional audit helpers |
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. Every twin operation has a
verb, including file upload (sandbox files import), a per-twin reset
(sandbox reset <twin>) and the operations list (sandbox services operations); never
curl a twin's control URL. The CLI sends the Veris API key itself, so the key is never
exported or printed. The control URL is not the address the app calls, and a vendor
hostname's /veris/* is the vendor's own 404; details in state.md,
The control URL and its key.
scripts/ holds optional record.sh and ledger.sh audit helpers; setup step 9
explains staging when an investigation needs them. Ordinary development does not
require a task ledger or a separate proof phase.
FAQ
What does the veris-reference skill do?
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.
How do I install veris-reference?
Run npx skills add https://github.com/veris-ai/plugins --skill veris-reference in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/veris-reference/ (personal) or .claude/skills/veris-reference/ (project).
Which AI agents can use veris-reference?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is veris-reference safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains veris-reference?
It is published by veris-ai in veris-ai/plugins. It has 377 recorded installs.
More from veris-ai/plugins
setup
veris-ai/plugins
Wire or repair this repository's Veris execution path, verify an application run, and save the working command for later development. Use for initial setup or changed wiring when the engineer names this command.
fix
veris-ai/plugins
Fix a defect using Veris to answer relevant service questions and test the changed application. Reuse normal development tests and report their results. Takes an issue link or a prompt. Run when the engineer names this command.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.