Run the tests, run one spec, run e2e locally or on Daytona, investigate a skipped spec. Use for executing @openwork/testkit agent-first verification.
pnpm evals:e2e <slug>
pnpm evals:pr specs/<name>.test.tsThe CLI prints the placement and reason; copy that line into the report. Use
--local only when the user asks for local. --daytona requires Daytona. Never
switch lanes to turn a red Daytona run green.
pnpm --filter @openwork/types build
pnpm --filter @openwork-ee/den-db build
pnpm --filter @openwork/email build
pnpm dev:den:mysqlserver() requires MySQL at 127.0.0.1:3306.OPENWORK_EVAL_SURFACES_DIR to a
space-free path before E2E tests. node-gyp and electron-rebuild require it.pnpm evals:pr specs/<name>.test.tspnpm evals:e2e <name>placement: <daytona|local> (<reason>).Check what runtime the changed code ships on before trusting a green run.
apps/server tests run on Bun; Desktop runs that same code on Electron's
Node (undici). If the change touches fetch, streams, signals, GC, or timers,
run it on the shipping runtime too:
ELECTRON_RUN_AS_NODE=1 apps/desktop/node_modules/electron/dist/Electron.app/Contents/MacOS/Electron --expose-gc <script>A green run on the wrong runtime is not evidence.
skipped — needs: X; never call it passed. A green command
containing skips makes the overall verdict Incomplete.Passed, Incomplete, or Failed for the overall result.OPENWORK_EVAL_DEN_API_URL.Passed, remove the reuse override and cold-boot through
server() on the same commit.infisical run --silent --; never print or echo values.417244c
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.