Agent skill

E2E

Run a basic E2E behavioral probe — one primary scenario smoke test for the grooming step.

GPL-2.0Auto-check passedTesting & QA

Install E2E

skills CLI

$ npx skills add wp-media/wp-rocket --skill e2e -a claude-code

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

GitHub CLI

$ gh skill install wp-media/wp-rocket 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/wp-media/wp-rocket.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/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/

Paste into Claude Code

Install the "e2e" agent skill from https://github.com/wp-media/wp-rocket/tree/develop/.claude/skills/e2e into .claude/skills/e2e/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "e2e", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/wp-media/wp-rocket/tree/develop/.claude/skills/e2e

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add wp-media/wp-rocket --skill e2e -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install wp-media/wp-rocket e2e --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/wp-media/wp-rocket.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/e2e .agents/skills/e2e && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "e2e" agent skill from https://github.com/wp-media/wp-rocket/tree/develop/.claude/skills/e2e into .agents/skills/e2e/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "e2e", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add wp-media/wp-rocket --skill e2e -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install wp-media/wp-rocket e2e --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/wp-media/wp-rocket.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/e2e .cursor/skills/e2e && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "e2e" agent skill from https://github.com/wp-media/wp-rocket/tree/develop/.claude/skills/e2e into .cursor/skills/e2e/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "e2e", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/wp-media/wp-rocket.git --path .claude/skills/e2e

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add wp-media/wp-rocket --skill e2e -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install wp-media/wp-rocket e2e --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/wp-media/wp-rocket.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/e2e .gemini/skills/e2e && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "e2e" agent skill from https://github.com/wp-media/wp-rocket/tree/develop/.claude/skills/e2e into .gemini/skills/e2e/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "e2e", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install wp-media/wp-rocket e2e

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add wp-media/wp-rocket --skill e2e -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/wp-media/wp-rocket.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/e2e .github/skills/e2e && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "e2e" agent skill from https://github.com/wp-media/wp-rocket/tree/develop/.claude/skills/e2e into .github/skills/e2e/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "e2e", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add wp-media/wp-rocket --skill e2e -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install wp-media/wp-rocket e2e --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/wp-media/wp-rocket.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/e2e .opencode/skills/e2e && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "e2e" agent skill from https://github.com/wp-media/wp-rocket/tree/develop/.claude/skills/e2e into .opencode/skills/e2e/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "e2e", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: e2e
GitHub stars: 767
Token cost: ~1.2k tokens
SKILL.md length: 449 words
Files: 1
Skills in repo: 15
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: GPL-2.0

At a glance

Run a basic E2E behavioral probe — one primary scenario smoke test for the grooming step.

Works in 3 steps: Boot the environment (idempotent — safe… → Run the primary happy path scenario from… → Report
Tasks that involve End-to-end testing
SKILL.md covers Config, Basic tier — behavioral probe and Project-specific notes
Calls bash and curl

What it does

E2E is an agent skill from wp-media/wp-rocket. Run a basic E2E behavioral probe — one primary scenario smoke test for the grooming step.

Its SKILL.md is about 1.2k 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 QA and bug reports. It works with WordPress, Bash and Playwright. The repository describes itself as: Performance optimization plugin for WordPress. The licence is GPL-2.0.

When your agent uses it

Tasks that involve End-to-end testing
Tasks that involve QA and bug reports

Example prompts

“/e2e”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

Boot the environment (idempotent — safe to run if already up)
Run the primary happy path scenario from the spec or grooming plan.
Report

What it can do on your machine

Read from SKILL.md and the folder at commit 3a96b66. 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:
- bash
- curl
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use curl, 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 1.2k tokens when it runs. Until then it costs about 23 tokens; SKILL.md has 449 words of instructions outside code blocks.

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

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 wp-media/wp-rocket at commit 3a96b66, republished under its GPL-2.0 licence (© wp-media). 449 words, ~1,169 tokens.

Download SKILL.mdSave it as .claude/skills/e2e/SKILL.md (or your agent's skills folder).

name: e2e
description: Run a basic E2E behavioral probe — one primary scenario smoke test for the grooming step.

E2E SKILL — Basic tier

Config

This skill targets wp-media/wp-rocket:

E2E_URL = http://localhost:8888
E2E_BOOT = bash bin/dev-up.sh
E2E_SETTINGS = http://localhost:8888/wp-admin/options-general.php?page=wprocket

The local WordPress environment is at http://localhost:8888 (admin / password). Boot or restart it with bash bin/dev-up.sh.

This skill provides a single behavioral probe using the Playwright MCP and curl. WP Rocket does not commit Playwright specs — this skill never writes, commits, or publishes test artifacts. It exists only to verify one primary scenario quickly.

Basic tier — behavioral probe

Purpose: behavioral verification and smoke tests. Fast enough to fit inside a planning agent's execution window.

Invoker:

grooming-agent — verify behavioral assumptions about the current system before writing the spec. Use to confirm: does the current feature behave as described in the issue? What does the current API or AJAX endpoint return for the scenario being changed?

Anti-rationalization table

You'll be tempted to say	Why you can't
"The environment probably isn't up, I'll skip"	Run `bash bin/dev-up.sh`. It's idempotent. If it fails, log `SKIP` with the reason — do not silently omit the step.
"The change is backend-only, no need to smoke it"	The primary happy path must be verified. A backend change with no observable behavior change still needs a confirming assertion.
"I already read the code, I know it works"	"Seems right" never closes a task. Run the scenario.
"One scenario is too slow for this stage"	Basic tier is exactly one primary scenario. The cost is acceptable.

Process

Boot the environment (idempotent — safe to run if already up):
bash
```
bash bin/dev-up.sh
```
If the script exits non-zero, set status: "SKIP", note the reason, and do not block the pipeline.

Run the primary happy path scenario from the spec or grooming plan.

Backend / AJAX / REST:

bash

# Public REST or AJAX
curl -s -X POST http://localhost:8888/wp-admin/admin-ajax.php \
  -H "Cookie: $(cat .wp-session-cookie 2>/dev/null)" \
  -d 'action=<action>&nonce=...'

# Cache headers
curl -sI http://localhost:8888/ | grep -E '(x-cache|cf-cache)'

Browser (settings page, dashboard notices, interactive UI): Use the Playwright MCP directly for the basic-tier smoke:

mcp__playwright__navigate({ url: "http://localhost:8888/wp-login.php" })
# login
mcp__playwright__fill({ selector: "#user_login", value: "admin" })
mcp__playwright__fill({ selector: "#user_pass", value: "password" })
mcp__playwright__click({ selector: "#wp-submit" })
# primary scenario
mcp__playwright__navigate({ url: "http://localhost:8888/wp-admin/options-general.php?page=wprocket" })
mcp__playwright__snapshot({})
# Inspect snapshot output to confirm expected element/text is present

Take at most 1–2 screenshots if helpful, but do not publish them.

Report:

json

{
  "status": "PASS|FAIL|SKIP",
  "scenarios_tested": ["Settings page loads without errors after enabling X option"],
  "details": "Logged in as admin, navigated to the WP Rocket settings page, confirmed no JS console errors and X toggle present"
}

SKIP: bash bin/dev-up.sh failed or environment unreachable. Record reason. Do not block the pipeline.

Show full SKILL.md (133 more words)Show less

Boundaries

Do: verify the one primary scenario from the spec or grooming plan
Do: probe current-system behavior (grooming-agent only) when an assumption needs verification
Do not: cover all acceptance criteria — that belongs to the qa-engineer + e2e-qa-tester path
Do not: write, commit, or publish Playwright specs — WP Rocket does not commit Playwright specs
Do not: publish screenshots

Project-specific notes

The boot script bash bin/dev-up.sh is idempotent. Always run it before testing — don't pre-check whether the environment is up. Seed data with bash bin/dev-seed.sh if needed.
Admin credentials: admin / password.
Settings page URL: http://localhost:8888/wp-admin/options-general.php?page=wprocket.
Plugin activation check:
bash
```
wp plugin list --name=wp-rocket
```
The basic tier never writes Playwright spec files and is invoked by grooming-agent only. Implementation agents (backend-agent, frontend-agent) do not invoke the e2e skill — full E2E validation belongs to the qa-engineer + e2e-qa-tester tier.

Files

Just SKILL.md in .claude/skills/e2e of wp-media/wp-rocket.

Open the folder on GitHubat commit 3a96b66

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
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
E2E this skillwp-media/wp-rocket	767	—	~1.2k	Automated safety check: Pass	GPL-2.0	today
E2Ecallstack/react-native-pager-view	3.4k	1 repos	~2.1k	Automated safety check: Pass	MIT	today
Verify Omnigent End-to-Endomnigent-ai/omnigent	11k	—	~1.6k	Automated safety check: Pass	Apache-2.0	today
Glance TestDebugBase/glance	156	—	~827	Automated safety check: Pass	MIT	5 mo ago
QAKiln-AI/Kiln	5.2k	—	~3.6k	Automated safety check: Pass	Custom licence	today
Twenty QA Scouttwentyhq/twenty	58k	—	~2k	Automated safety check: Pass	Custom licence	today

Similar skills

E2E
callstack/react-native-pager-view
Agentic end-to-end tests with e2e, the e2e runner. An agent skill from callstack/react-native-pager-view.
3.4k GitHub starsUsed in 1 repo~2.1k tokens
Testing & QAAuto-check passed
Verify Omnigent End-to-End
omnigent-ai/omnigent
Spins up an isolated Omnigent server, runner and mock model to prove a user-facing behavior or bug fix with recorded evidence instead of reasoning from code.
11k GitHub stars~1.6k tokensUpdated today
Testing & QAAuto-check passed
Glance Test
DebugBase/glance
Run E2E browser tests on any web application using Glance MCP.
156 GitHub stars~827 tokensUpdated 5 mo ago
Testing & QAAuto-check passed
QA
Kiln-AI/Kiln
Multi-agent, browser-driven QA pass over a branch or PR — scope it, plan it, fan out one subagent per testing area in its own isolated sandbox, compile a severity-ranked markdown report.
5.2k GitHub stars~3.6k tokensUpdated today
Testing & QAAuto-check passed
Twenty QA Scout
twentyhq/twenty
Browser QA for a pull request against a running Twenty app: scenarios drawn from the diff, run in a real browser, checked in the database and logs, and closed with a verdict and report.
58k GitHub stars~2k tokensUpdated today
Testing & QAAuto-check passed
Agentic Browser Testing
petrkindlmann/qa-skills
Goal-driven E2E testing where a browser agent (Playwright MCP / computer-use) reads a natural-language goal and explores the app via the accessibility tree to assert outcomes — no pre-written script.
165 GitHub stars~4.5k tokensUpdated 3 mo ago
Testing & QAAuto-check passed

Questions about E2E

What does E2E do?

Run a basic E2E behavioral probe — one primary scenario smoke test for the grooming step. E2E is an agent skill from wp-media/wp-rocket. Run a basic E2E behavioral probe — one primary scenario smoke test for the grooming step.

When should I use E2E?

E2E fits situations like: tasks that involve End-to-end testing; tasks that involve QA and bug reports.

How do I install E2E in Claude Code?

Run `npx skills add wp-media/wp-rocket --skill e2e -a claude-code`. Or copy the skill folder (.claude/skills/e2e in wp-media/wp-rocket) 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 wp-media/wp-rocket --skill e2e -a codex`. Or copy the skill folder (.claude/skills/e2e in wp-media/wp-rocket) 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 wp-media/wp-rocket --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 (bash and curl).

Does E2E access the network?

SKILL.md contains no URLs. Its commands use curl, 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 GPL-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 use?

About 1.2k tokens (SKILL.md is roughly 4.7k 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: E2E (callstack/react-native-pager-view, 3.4k stars), Verify Omnigent End-to-End (omnigent-ai/omnigent, 11k stars), Glance Test (DebugBase/glance, 156 stars) and QA (Kiln-AI/Kiln, 5.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains E2E?

wp-media (a GitHub organization) maintains it in wp-media/wp-rocket, which has 767 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 7, 2026.

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

E2E

Install E2E

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

E2E SKILL — Basic tier

Config

Basic tier — behavioral probe

Anti-rationalization table

Process

Boundaries

Project-specific notes

Files

Compare with similar skills

Similar skills

E2E

Verify Omnigent End-to-End

Glance Test

QA

Twenty QA Scout

Agentic Browser Testing

More from wp-media/wp-rocket

Knowledge Graph

Wordpress Compliance

Issue Workflow

Wp Rocket Architecture

Challenge

Compliance

Questions about E2E

Install E2E

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

E2E SKILL — Basic tier

Config

Basic tier — behavioral probe

Anti-rationalization table

Process

Boundaries

Project-specific notes

Files

Compare with similar skills

Similar skills

More from wp-media/wp-rocket

Related

Questions about E2E