Agent skill

E2E Test

by ALT-F4-LLC in ALT-F4-LLC/vorpal

Run end-to-end tests that validate Vorpal services and client builds.

Apache-2.0Auto-check: notesTesting & QA

Install E2E Test

skills CLI
$ npx skills add ALT-F4-LLC/vorpal --skill e2e-test -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ALT-F4-LLC/vorpal e2e-test --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ALT-F4-LLC/vorpal.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/e2e-test .claude/skills/e2e-test && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
e2e-test
GitHub stars
124
Token cost
~1.3k tokens
SKILL.md length
506 words
Files
1
Skills in repo
2
Repo updated
First seen
Licence
Apache-2.0

At a glance

Run end-to-end tests that validate Vorpal services and client builds.

  • Works in 5 steps: Start services in background → Wait for services → Run artifact build → …
  • Testing the full system (services + build pipeline)
  • SKILL.md covers Test Flow, Execution Instructions, Arguments and vorpal prepare integration ACs…, plus 1 more section
  • Calls make

What it does

E2E Test is an agent skill from ALT-F4-LLC/vorpal. Run end-to-end tests that validate Vorpal services and client builds. Use when testing the full system (services + build pipeline), validating changes work end-to-end, or verifying services and clients communicate correctly.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering End-to-end testing and CI/CD. The repository describes itself as: Build system that works as code. The licence is Apache-2.0.

When your agent uses it

  • Testing the full system (services + build pipeline)
  • Validating changes work end-to-end
  • Verifying services and clients communicate correctly

Example prompts

  • “/e2e-test”

Requirements

  • Pre-approved tools (allowed-tools): Bash, Read, Glob, Grep

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Start services in background
  2. Wait for services
  3. Run artifact build
  4. Stop services
  5. Report results

What it can do on your machine

Read from SKILL.md and the folder at commit 77ac6ad. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash
    • Read
    • Glob
    • Grep

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • make

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

E2E Test loads about 1.3k tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 506 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~58
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Bash, Read, Glob, Grep

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from ALT-F4-LLC/vorpal at commit 77ac6ad, republished under its Apache-2.0 licence (© ALT-F4-LLC). 506 words, ~1,299 tokens.

Download SKILL.mdSave it as .claude/skills/e2e-test/SKILL.md (or your agent's skills folder).
name
e2e-test
description
Run end-to-end tests that validate Vorpal services and client builds. Use when testing the full system (services + build pipeline), validating changes work end-to-end, or verifying services and clients communicate correctly.
allowed-tools
Bash, Read, Glob, Grep

End-to-End Test Skill

Run end-to-end tests to validate that Vorpal services start correctly and can successfully build artifacts.

Test Flow

  1. Build the project (if not already built)
  2. Start backend services in background using run_in_background: true
  3. Wait for services to be ready on port 23153
  4. Run artifact build against the services
  5. Stop all services on port 23153
  6. Report results

Execution Instructions

Step 1: Start services in background

Use the Bash tool with run_in_background: true to start services:

bash
make vorpal-start

The service logs will stream to the shell output for review.

Step 2: Wait for services

Wait for port 23153 to be available (up to 60 seconds):

bash
for i in {1..60}; do nc -z localhost 23153 2>/dev/null && echo "Services ready after ${i}s" && break; [ $i -eq 60 ] && echo "ERROR: Services failed to start" && exit 1; sleep 1; done
Step 3: Run artifact build

Build the artifact against the running services. Default artifact is vorpal-shell:

bash
make VORPAL_ARTIFACT="vorpal-shell" vorpal-build

To test with a different artifact:

bash
make VORPAL_ARTIFACT="<artifact-name>" vorpal-build
Step 4: Stop services

After the build completes (success or failure), stop all services on port 23153:

bash
lsof -ti:23153 | xargs kill 2>/dev/null || true
Step 5: Report results
  • If build succeeded, report "E2E TEST PASSED"
  • If build failed, review the service logs in the shell output and the build error messages

Arguments

The skill accepts an optional artifact name. Default is vorpal:

  • /e2e-test - Test with vorpal-shell artifact
  • /e2e-test vorpal - Test with vorpal artifact
  • /e2e-test <name> - Test with specified artifact

vorpal prepare integration ACs (DKT-71)

These cover the integration-level vorpal prepare acceptance criteria that cannot be unit-tested in isolation because they require a live agent/worker/registry (real gRPC round-trip), not a Rust integration harness. They extend — do not replace — the build flow above. Run each against live services started via make vorpal-start (Step 1) and stop them after (Step 4).

Makefile targets were split: vorpal-build (was vorpal) runs vorpal build, vorpal-prepare runs vorpal prepare.

Show full SKILL.md (230 more words)Show less
AC (a): prepare never invokes the worker build for the target graph

Runnable locally (single host + services).

bash
make vorpal-start &
# wait for port 23153 (see Step 2)
make VORPAL_ARTIFACT="<artifact-name>" vorpal-prepare

Expected: the command resolves/pins sources and prints the mint/update/verify summary plus the resolved digest, and the output contains no build-artifact RPC or worker build invocation (no building artifact ... / no worker step output). prepare mints and verifies; it does not build.

AC (b): two-host remote-tarball fetch produces a byte-identical lock entry

CI / manual only — requires two host arch/OS combinations (e.g. an aarch64-darwin host and an x86_64-linux runner) preparing the same source.

On each host (against that host's services):

bash
make VORPAL_ARTIFACT="<artifact-name>" vorpal-prepare

Then diff the resulting Vorpal.lock source entry across the two hosts. The pin (digest) MUST be byte-identical. (Cross-host determinism assumption: ADR 0002 — normalization-stable filenames within a source.)

AC (c): --unlock=false enforces fail-closed end-to-end

Runnable locally if an unpinned remote source is present; otherwise CI.

bash
make vorpal-start &
# wait for port 23153
VORPAL_SOCKET_PATH=$(VORPAL_SOCKET) cargo run --bin vorpal -- prepare \
    --config <config> --unlock=false <artifact>

Expected against an unpinned remote source: the command fails closed with source '...' is unpinned - use --unlock to pin (the agent gate fires through the full prepare path, not just the isolated clap parse).

AC (d): prepare (default unlock) and build --unlock produce identical lock entries

Runnable locally (single host + services).

bash
make vorpal-start &
# wait for port 23153
# snapshot the lock after prepare (default --unlock=true)
cp Vorpal.lock /tmp/lock.prepare
make VORPAL_ARTIFACT="<artifact-name>" vorpal-prepare
cp Vorpal.lock /tmp/lock.prepare

# then build with explicit --unlock and snapshot again
VORPAL_SOCKET_PATH=$(VORPAL_SOCKET) cargo run --bin vorpal -- build \
    --config <config> --unlock <artifact>
cp Vorpal.lock /tmp/lock.build

diff /tmp/lock.prepare /tmp/lock.build

Expected: the diff is empty — prepare (default --unlock true) and build --unlock write byte-identical Vorpal.lock entries for the same target.

Troubleshooting

  • Port in use: lsof -ti:23153 | xargs kill
  • Build fails: Run make build first
  • Services crash: Review shell output for error messages

© ALT-F4-LLC, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/e2e-test of ALT-F4-LLC/vorpal.

Open the folder on GitHubat commit 77ac6ad

Compare with similar skills

E2E Test next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

E2E Test compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
E2E Test this skillALT-F4-LLC/vorpal124—~1.3kAutomated safety check: NotesApache-2.0
Local CImodule-federation/core2.7k—~914Automated safety check: PassMIT
Debug Playwrightquay/quay2.8k—~1.2kAutomated safety check: PassApache-2.0
Promotion Branches E2E Testhardisgroupcom/sfdx-hardis403—~11kAutomated safety check: NotesAGPL-3.0
E2E Testingaffaan-m/ECC276k3 repos~1.9kAutomated safety check: PassMIT
Dokan Run Test Suitegetdokan/dokan288—~4.7kAutomated safety check: NotesNone

Similar skills

  • Local CI

    module-federation/core

    Run this repository's local CI parity commands and pnpm run ci:local jobs.

    2.7k GitHub stars~914 tokensUpdated today
    Testing & QAAuto-check passed
  • Debug Playwright E2E test failures from GitHub Actions CI runs.

    2.8k GitHub stars~1.2k tokensUpdated today
    Testing & QAAuto-check passed
  • Promotion Branches E2E Test

    hardisgroupcom/sfdx-hardis

    Runs a full end-to-end test of sfdx-hardis promotion branches and backpromote against real Salesforce orgs and a throwaway repository, then writes a report.

    403 GitHub stars~11k tokensUpdated today
    Testing & QAAuto-check: notes
  • E2E Testing

    affaan-m/ECC

    Playwright E2E 测试模式、页面对象模型、配置、CI/CD 集成、工件管理和不稳定测试策略. An agent skill from affaan-m/ECC.

    276k GitHub starsUsed in 3 repos~1.9k tokens
    Testing & QAAuto-check passed
  • Dokan Run Test Suite

    getdokan/dokan

    Execute the Dokan Playwright test suite (E2E + API), locally or via GitHub Actions.

    288 GitHub stars~4.7k tokensUpdated today
    Testing & QAAuto-check: notes
  • E2E Testing

    affaan-m/ECC

    Playwright E2E test kalıpları, Page Object Model, yapılandırma, CI/CD entegrasyonu, artifact yönetimi ve kararsız test stratejileri.

    276k GitHub starsUsed in 1 repo~2k tokens
    Testing & QAAuto-check passed

More from ALT-F4-LLC/vorpal

  • SDK Parity

    ALT-F4-LLC/vorpal

    Test parity between Rust, Go, and TypeScript SDK builds by comparing artifact digests

    124 GitHub stars~2.7k tokensUpdated today
    Auto-check passed

Categories

Questions about E2E Test

What does E2E Test do?

Run end-to-end tests that validate Vorpal services and client builds. E2E Test is an agent skill from ALT-F4-LLC/vorpal. Run end-to-end tests that validate Vorpal services and client builds.

When should I use E2E Test?

E2E Test fits situations like: testing the full system (services + build pipeline); validating changes work end-to-end; verifying services and clients communicate correctly.

How do I install E2E Test in Claude Code?

Run `npx skills add ALT-F4-LLC/vorpal --skill e2e-test -a claude-code`. Or copy the skill folder (.claude/skills/e2e-test in ALT-F4-LLC/vorpal) into .claude/skills/e2e-test in your project. Claude Code loads it when a task matches its description.

How do I install E2E Test in Codex?

Run `npx skills add ALT-F4-LLC/vorpal --skill e2e-test -a codex`. Or copy the skill folder (.claude/skills/e2e-test in ALT-F4-LLC/vorpal) into .agents/skills/e2e-test in your project. Codex loads it when a task matches its description.

Can I use E2E Test in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ALT-F4-LLC/vorpal --skill e2e-test -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/e2e-test, .gemini/skills/e2e-test, .github/skills/e2e-test and .opencode/skills/e2e-test in your project.

What does E2E Test need to run?

Going by SKILL.md and its folder, E2E Test needs the command-line tools its instructions call (make). Its frontmatter pre-approves these tools: Bash, Read, Glob, Grep.

Does E2E Test access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is E2E Test safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does E2E Test use?

E2E Test is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does E2E Test use?

About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to E2E Test?

Skills that share tags, products or a category with E2E Test: Local CI (module-federation/core, 2.7k stars), Debug Playwright (quay/quay, 2.8k stars), Promotion Branches E2E Test (hardisgroupcom/sfdx-hardis, 403 stars) and E2E Testing (affaan-m/ECC, 276k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains E2E Test?

ALT-F4-LLC (a GitHub organization) maintains it in ALT-F4-LLC/vorpal, which has 124 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 9, 2026.

Source: ALT-F4-LLC/vorpal on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.