Run the tests, run one spec, run e2e locally or on Daytona, investigate a skipped spec. Use for executing @openwork/testkit agent-first verification.
90%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
pnpm evals:e2e <slug>The 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.
Know what each placement runs before reading a verdict:
daytona CLI is logged in) builds
OPENWORK_EVAL_REF, which defaults to dev, not your working tree. To test a
branch, push it and export OPENWORK_EVAL_REF=$(git rev-parse HEAD); add
--strict-ref so a mismatch fails instead of warning.--local runs your working tree. A spec whose world uses appWeb stays in
headless Chrome. A spec whose world uses desktop (seed.desktop, app())
opens an Electron window that takes focus on this computer; run those on
Daytona unless the user asks for a local window.The test every PR runs. Its world is a Freestyle VM, so this needs only the evals install and the Freestyle key:
FREESTYLE_API_KEY="$(infisical secrets get FREESTYLE_API_KEY --env dev --path /openwork-ops --plain --silent)" \
node evals/bin/evals.mjs core/core-chat.e2e.test.ts --local --engine v1 --surface webIt runs against the pushed HEAD commit; push first. After changing the world
itself, run node evals/scripts/check-freestyle-world.ts --base <sha> instead.
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.electron.log inside them, are removed when
a journey ends. Set OPENWORK_EVAL_SURFACE_LOGS_DIR to a directory outside
the surfaces directory to keep a copy of each log; the packaged smoke does.pnpm evals:e2e <name>placement: <daytona|local> (<reason>).Check what runtime the changed code ships on before trusting a green run.
apps/server runs on Bun in evals; 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.different-ai/openwork
be86f8c
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.