How do I install the Verify skill?

Run npx skillmds@latest add theopenco/verify 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 Verify 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 Verify?

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 Verify free to use?

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

Who published Verify?

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

Verify by theopenco — Agent Skill

Name: Verify
Author: theopenco

Verify

Build, launch, and drive the LLM Gateway stack in an isolated worktree environment to verify API, gateway, dashboard, playground, or screenshot changes. Use when locally reproducing a change, launching services on offset ports, taking seeded-data screenshots, or checking a workflow end to end.

theopenco 0110a07 2.6 KB Updated Sep 17, 2026

File contents

Verify a change

Use the repository's current implementation and AGENTS.md as the source of truth. Do not reuse ports, containers, credentials, or commands remembered from another worktree.

Isolate the workspace

Read Running an isolated stack per worktree in AGENTS.md.
Reuse the worktree's exported STACK_SUFFIX, database URLs, Redis ports, app ports, and service URLs only if they are complete. Otherwise choose an unused slot and export the full block from AGENTS.md.
Confirm the selected ports are free. Never start or reset the default shared Docker stack from a Conductor worktree.

Start only the isolated services needed by the change:

pnpm build:core
docker compose up -d
pnpm wait-for-services
pnpm push-test
pnpm push-dev
pnpm seed

Use pnpm setup only when a full reset is required and STACK_SUFFIX is set; it removes the selected stack's volumes.

Build and launch

Build affected apps through Turbo filters, including their workspace dependencies. Run the full pnpm build before handoff when required by AGENTS.md.

Turbo's strict environment mode may not pass the worktree isolation variables declared in .envrc. Launch an isolated stack with pnpm exec turbo run dev --env-mode=loose, then confirm the startup logs show the selected ports rather than the defaults.

Drive and capture

Use seeded accounts and identifiers from packages/db/src/seed.ts; passwords equal their seeded email addresses.
Verify the changed behavior through the same surface a user exercises. Pin a gateway provider and set x-no-fallback: true when provider-specific behavior matters.
Use an available browser automation tool for UI verification. If a local Playwright script is needed, run it from an app that declares @playwright/test (apps/ui, apps/playground, or apps/code).
Capture only seeded local data. Resolve screenshot output paths from the tool being used instead of assuming a tool-specific directory.

Record the exact commands, URLs, and observed result. Do not describe a check as passing unless it ran successfully.

Clean up

Stop processes started for the check. Run docker compose down -v only when this session started the worktree-specific STACK_SUFFIX stack. Never tear down the default shared stack or a stack that was already running.

---name: verifydescription: Build, launch, and drive the LLM Gateway stack in an isolated worktree environment to verify API, gateway, dashboard, playground, or screenshot changes. Use when locally reproducing a change, launching services on offset ports, taking seeded-data screenshots, or checking a workflow end to end.---# Verify a changeUse the repository's current implementation and `AGENTS.md` as the source oftruth. Do not reuse ports, containers, credentials, or commands remembered fromanother worktree.## Isolate the workspace1. Read **Running an isolated stack per worktree** in `AGENTS.md`.2. Reuse the worktree's exported `STACK_SUFFIX`, database URLs, Redis ports, app ports, and service URLs only if they are complete. Otherwise choose an unused slot and export the full block from `AGENTS.md`.3. Confirm the selected ports are free. Never start or reset the default shared Docker stack from a Conductor worktree.Start only the isolated services needed by the change:```bashpnpm build:coredocker compose up -dpnpm wait-for-servicespnpm push-testpnpm push-devpnpm seed```Use `pnpm setup` only when a full reset is required and `STACK_SUFFIX` is set;it removes the selected stack's volumes.## Build and launchBuild affected apps through Turbo filters, including their workspacedependencies. Run the full `pnpm build` before handoff when required by`AGENTS.md`.Turbo's strict environment mode may not pass the worktree isolation variablesdeclared in `.envrc`. Launch an isolated stack with`pnpm exec turbo run dev --env-mode=loose`, then confirm the startup logs showthe selected ports rather than the defaults.## Drive and capture- Use seeded accounts and identifiers from `packages/db/src/seed.ts`; passwords equal their seeded email addresses.- Verify the changed behavior through the same surface a user exercises. Pin a gateway provider and set `x-no-fallback: true` when provider-specific behavior matters.- Use an available browser automation tool for UI verification. If a local Playwright script is needed, run it from an app that declares `@playwright/test` (`apps/ui`, `apps/playground`, or `apps/code`).- Capture only seeded local data. Resolve screenshot output paths from the tool being used instead of assuming a tool-specific directory.Record the exact commands, URLs, and observed result. Do not describe a check aspassing unless it ran successfully.## Clean upStop processes started for the check. Run `docker compose down -v` only whenthis session started the worktree-specific `STACK_SUFFIX` stack. Never tear downthe default shared stack or a stack that was already running.

Frequently asked questions