Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
Run end-to-end tests via the CI workflow.
The user may pass `$ARGUMENTS` to filter to a specific test case by name (e.g., `hello-world`, `phone-setup`). If not provided, infer options from context (see below).
## Steps
### 1. Determine options
**Experimental tests:** Always include `--experimental` by default. The user can pass `--no-experimental` to exclude them.
**Branch detection:** Check what branch you're on via `git branch --show-current`. If you're on a branch other than `main`, automatically pass `-b <branch-name>` so the CI run tests against that branch. The user can override with `-b <other-branch>` explicitly.
**Test case filter:** Determine which test case to target:
1. If the user passes a bare word argument (e.g., `phone-setup`), use that as the filter.
2. Otherwise, look at the conversational context - if you've been working on or discussing a specific e2e test case (e.g., editing `playwright/cases/phone-setup.md`), automatically target that test case.
3. If neither applies, run all tests.
**Additional flags from `$ARGUMENTS`:**
- `--xcode` uses the agent-xcode (AXUIElement) runner
- `-d` or `--detach` triggers the run and exits without polling
…
The line at the top of this page pins the label git:20260317.23378c6, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_5tu5x6wpb4tciyvy
GET https://markdownregistry.com/api/v1/resolve?ref=vellum-ai/vellum-assistant/e2e
GET https://markdownregistry.com/api/v1/blob/019129eff285ec5aa36dbe262d1b2ec899ce9c6eadb57c49498dfe1849377831
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
vellum-ai/vellum-assistant · .claude/skills/add-mcp-integration/SKILL.md · Add a vendor's remote MCP server to the bundled integrations catalog (plugins/mcp-catalog/<name>/ +…
vellum-ai/vellum-assistant · .claude/skills/cli-testing/SKILL.md · Manually test a running Vellum assistant end-to-end purely from the CLI — no desktop app or web UI. Hatch an instance…
vellum-ai/vellum-assistant · .claude/skills/release/SKILL.md · Cut a new release: create the release branch (staging bake), then dispatch the production Release run on that branch.
vellum-ai/vellum-assistant · .claude/skills/update/SKILL.md · Restart the Vellum assistant and gateway services. Smart branch handling: pulls from main by default, restarts in-place…
vellum-ai/vellum-assistant · .cursor/skills/vellum-feature-flag-rollout/SKILL.md · Guide Vellum Assistant feature flag changes and rollout hygiene. Use when adding, editing, reviewing, or documenting…
vellum-ai/vellum-assistant · .cursor/skills/vellum-migration-checklist/SKILL.md · Validate Vellum Assistant database and workspace migrations. Use when adding, editing, reviewing, or testing…
vellum-ai/vellum-assistant · .cursor/skills/vellum-skill-authoring/SKILL.md · Author and review first-party Vellum skills in the repository. Use when editing files under skills/, assistant bundled…
vellum-ai/vellum-assistant · .cursor/skills/vellum-test-selection/SKILL.md · Select focused verification commands for Vellum Assistant changes. Use when deciding what tests, typechecks, lints, or…
sgaabdu4/building-flutter-apps · .agents/skills/e2e/SKILL.md · Prove real user journeys across browser, mobile, desktop, API and CLI surfaces using the project's existing test tools…
p2p2sp/p2p2.claude · viber/skills/e2e/SKILL.md · Generates and locally verifies Playwright tests for the QA scenarios of one viber run, then commits them. Use it after…
p2p2sp/p2p2.claude · docs/archive/superdev/skills/e2e/SKILL.md · Generate and locally verify Playwright tests for the scenarios of one docs/qa handoff file, then commit them for CI.
p2p2sp/viber · docs/archive/superdev/skills/e2e/SKILL.md · Generate and locally verify Playwright tests for the scenarios of one docs/qa handoff file, then commit them for CI.
p2p2sp/viber · viber/skills/e2e/SKILL.md · Generates and locally verifies Playwright tests for the QA scenarios of one viber run, then commits them. Use it after…
compforge/devloop · quality/skills/e2e/SKILL.md · Discover, operate, and incrementally extend a project's existing end-to-end test capability. Use when the user asks to…
