New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

E2E

by vellum-ai in vellum-ai/vellum-assistant

Run end-to-end tests via the CI workflow. An agent skill from vellum-ai/vellum-assistant.

MITAuto-check passedTesting & QA

Install E2E

skills CLI
$ npx skills add vellum-ai/vellum-assistant --skill e2e -a claude-code

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

GitHub CLI
$ gh skill install vellum-ai/vellum-assistant e2e --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/vellum-ai/vellum-assistant.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/vellum-skills/e2e .claude/skills/e2e && 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
GitHub stars
1.4k
Token cost
~612 tokens
SKILL.md length
309 words
Files
1
Skills in repo
108
Repo updated
First seen
Licence
MIT

At a glance

Run end-to-end tests via the CI workflow. An agent skill from vellum-ai/vellum-assistant.

  • Works in 3 steps: Determine options → Trigger the CI run → Report
  • Tasks that involve End-to-end testing
  • Calls bun and git

What it does

E2E is an agent skill from vellum-ai/vellum-assistant. Run end-to-end tests via the CI workflow.

Its SKILL.md is about 610 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. It works with Xcode. The repository describes itself as: An AI Assistant that’s easy to setup, does your work 24/7, knows your preferences and gets better over time. The licence is MIT.

When your agent uses it

  • Tasks that involve End-to-end testing

Example prompts

  • “/e2e”

Workflow steps

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

  1. Determine options
  2. Trigger the CI run
  3. Report

What it can do on your machine

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

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • bun
    • git

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

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    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 loads about 612 tokens when it runs. Until then it costs about 11 tokens; SKILL.md has 309 words of instructions outside code blocks.

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

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 passed

The automated check found no risky patterns in SKILL.md.

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 vellum-ai/vellum-assistant at commit 844117a, republished under its MIT licence (© vellum-ai). 309 words, ~612 tokens.

Download SKILL.mdSave it as .claude/skills/e2e/SKILL.md (or your agent's skills folder).
name
e2e
description
Run end-to-end tests via the CI workflow.

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
  • --no-experimental overrides the default and excludes experimental tests
2. Trigger the CI run
bash
cd playwright && bun run scripts/agent-ci.ts <options>

Map the resolved options:

  • Test case filter: -t <case-name>
  • Experimental (default on): --experimental
  • Branch: -b <branch-name>
  • Xcode runner: --xcode
  • Detach mode: -d

Examples:

  • /e2e (on main, no context) → bun run scripts/agent-ci.ts --experimental
  • /e2e (on branch feat/phone, after editing phone-setup.md) → bun run scripts/agent-ci.ts --experimental -b feat/phone -t phone-setup
  • /e2e hello-world (on main) → bun run scripts/agent-ci.ts --experimental -t hello-world
  • /e2e --detach (on branch fix/bug) → bun run scripts/agent-ci.ts --experimental -b fix/bug -d
  • /e2e --no-experimental → bun run scripts/agent-ci.ts
3. Report

Before running, briefly state the resolved options (branch, test case, experimental) so the user can see what was inferred.

Once the command finishes (or is dispatched in detach mode), summarize:

  • Whether the workflow was triggered successfully
  • The branch, test case filter, and flags used
  • A link to the running workflow

© vellum-ai, MIT. 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/vellum-skills/e2e of vellum-ai/vellum-assistant.

Open the folder on GitHubat commit 844117a

Compare with similar skills

E2E 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 compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
E2E this skillvellum-ai/vellum-assistant1.4k—~612Automated safety check: PassMIT
Codex Local CLI E2Erebornix/Agmente545—~625Automated safety check: PassMIT
iOS Audio E2Ehyochan/react-native-nitro-sound961—~907Automated safety check: PassMIT
Web Application Testinganthropics/skills180k51 repos~966Automated safety check: PassApache-2.0
OpenHarness End-to-End EvalsHKUDS/OpenHarness16k1 repos~2.1kAutomated safety check: NotesMIT
Write and Verify Playwright Testsappsmithorg/appsmith41k—~2.9kAutomated safety check: NotesApache-2.0

Similar skills

  • Codex Local CLI E2E

    rebornix/Agmente

    Run and debug Agmente iOS end-to-end tests against a real local Codex CLI app-server instance.

    545 GitHub stars~625 tokensUpdated 4 mo ago
    Testing & QAAuto-check passed

  • iOS Audio E2E

    hyochan/react-native-nitro-sound

    Build and run device-backed iOS end-to-end checks for react-native-nitro-sound recording, playback, listeners, pause/resume, seek, speed, interruption, audio-session behavior, and rapid switching.

    961 GitHub stars~907 tokensUpdated 9 days ago
    MobileAuto-check passed

  • Web Application Testing

    anthropics/skills

    Official

    Tests local web applications with Python Playwright scripts, checking frontend behavior, capturing screenshots and reading browser console logs.

    180k GitHub starsUsed in 51 repos~966 tokens
    Testing & QAAuto-check passed

  • OpenHarness End-to-End Evals

    HKUDS/OpenHarness

    Validates OpenHarness features by running real multi-turn agent loops with live LLM calls against an unfamiliar codebase, checking actual tool execution.

    16k GitHub starsUsed in 1 repo~2.1k tokens
    Testing & QAAuto-check: notes

  • Write and Verify Playwright Tests

    appsmithorg/appsmith

    Writes a Playwright end-to-end test from a prompt, runs it against a live Appsmith deployment and retries with fixes up to three times until it passes.

    41k GitHub stars~2.9k tokensUpdated today
    Testing & QAAuto-check: notes

  • playwright-cli Browser Automation

    github/gh-aw

    Official

    Drives a real browser from the command line with playwright-cli to open pages, interact, mock requests, save state and work with Playwright tests.

    5.4k GitHub starsUsed in 23 repos~2.8k tokens
    Testing & QAAuto-check passed

More from vellum-ai/vellum-assistant

All 108 skills in this repo

  • Vellum GitHub App Setup

    vellum-ai/vellum-assistant

    Create and configure a GitHub App so the assistant can push commits, open PRs, and comment under its own bot identity.

    1.4k GitHub stars~3.1k tokensUpdated today
    Auto-check passed

  • Discord App Setup

    vellum-ai/vellum-assistant

    Connect a Discord bot to the assistant via the Discord Gateway with guided application creation and intent configuration

    1.4k GitHub stars~4.2k tokensUpdated today
    Auto-check passed

  • Sentry App Setup

    vellum-ai/vellum-assistant

    Create and configure a Sentry internal integration so the assistant can manage issues, alerts, and releases under its own identity

    1.4k GitHub stars~1.3k tokensUpdated today
    Auto-check passed

  • Memory Corpus Ingest

    vellum-ai/vellum-assistant

    Ingest a large dataset into memory as a skimmed map. An agent skill from vellum-ai/vellum-assistant.

    1.4k GitHub stars~3k tokensUpdated today
    Auto-check: notes

  • Plugin Builder

    vellum-ai/vellum-assistant

    A skill your agent uses when the user wants to build, scaffold, ship, or edit a Vellum plugin that bundles multiple surfaces (hooks, tools, skills, and more) into one installable package.

    1.4k GitHub stars~3.1k tokensUpdated today
    Auto-check passed

  • Slack App Setup

    vellum-ai/vellum-assistant

    Connect a Slack app to the Vellum Assistant via Socket Mode.

    1.4k GitHub stars~2.5k tokensUpdated today
    Auto-check: warnings

Works with

Categories

Questions about E2E

What does E2E do?

Run end-to-end tests via the CI workflow. An agent skill from vellum-ai/vellum-assistant. E2E is an agent skill from vellum-ai/vellum-assistant. Run end-to-end tests via the CI workflow.

When should I use E2E?

E2E fits situations like: tasks that involve End-to-end testing.

How do I install E2E in Claude Code?

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

How do I install E2E in Codex?

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

Can I use E2E 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 vellum-ai/vellum-assistant --skill e2e -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, .gemini/skills/e2e, .github/skills/e2e and .opencode/skills/e2e in your project.

What does E2E need to run?

Going by SKILL.md and its folder, E2E needs the command-line tools its instructions call (bun and git).

Does E2E access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is E2E safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does E2E use?

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

How many tokens does E2E use?

About 612 tokens (SKILL.md is roughly 2.4k 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?

Skills that share tags, products or a category with E2E: Codex Local CLI E2E (rebornix/Agmente, 545 stars), iOS Audio E2E (hyochan/react-native-nitro-sound, 961 stars), Web Application Testing (anthropics/skills, 180k stars) and OpenHarness End-to-End Evals (HKUDS/OpenHarness, 16k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains E2E?

vellum-ai (a GitHub organization) maintains it in vellum-ai/vellum-assistant, which has 1,400 GitHub stars. The repository holds 108 skills in this directory. The repository was last updated on October 9, 2026.

Source: vellum-ai/vellum-assistant on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.