E2E
openathleteorg/openathlete
Run, debug or extend the OpenAthlete Playwright end-to-end tests, which exercise the production Docker images (API, worker, web, PostgreSQL, Redis) through the API and a real browser on desktop and…
Playwright end-to-end testing standards for RedisInsight: page object models, test structure, fixtures, navigation patterns, and flaky-test prevention.
Install E2E Testing
$ npx skills add redis/RedisInsight --skill e2e-testing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install redis/RedisInsight e2e-testing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/redis/RedisInsight.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.ai/skills/e2e-testing .claude/skills/e2e-testing && rm -rf skills-srcUse ~/.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/
Install the "e2e-testing" agent skill from https://github.com/redis/RedisInsight/tree/main/.ai/skills/e2e-testing into .claude/skills/e2e-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "e2e-testing", 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 install https://github.com/redis/RedisInsight/tree/main/.ai/skills/e2e-testingType 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.
$ npx skills add redis/RedisInsight --skill e2e-testing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install redis/RedisInsight e2e-testing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/redis/RedisInsight.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.ai/skills/e2e-testing .agents/skills/e2e-testing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "e2e-testing" agent skill from https://github.com/redis/RedisInsight/tree/main/.ai/skills/e2e-testing into .agents/skills/e2e-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "e2e-testing", 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.
$ npx skills add redis/RedisInsight --skill e2e-testing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install redis/RedisInsight e2e-testing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/redis/RedisInsight.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.ai/skills/e2e-testing .cursor/skills/e2e-testing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "e2e-testing" agent skill from https://github.com/redis/RedisInsight/tree/main/.ai/skills/e2e-testing into .cursor/skills/e2e-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "e2e-testing", 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 https://github.com/redis/RedisInsight.git --path .ai/skills/e2e-testing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add redis/RedisInsight --skill e2e-testing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install redis/RedisInsight e2e-testing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/redis/RedisInsight.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.ai/skills/e2e-testing .gemini/skills/e2e-testing && rm -rf skills-srcUse ~/.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/
Install the "e2e-testing" agent skill from https://github.com/redis/RedisInsight/tree/main/.ai/skills/e2e-testing into .gemini/skills/e2e-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "e2e-testing", 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.
$ gh skill install redis/RedisInsight e2e-testingInstalls 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).
$ npx skills add redis/RedisInsight --skill e2e-testing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/redis/RedisInsight.git skills-src && mkdir -p .github/skills && cp -r skills-src/.ai/skills/e2e-testing .github/skills/e2e-testing && rm -rf skills-srcUse ~/.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/
Install the "e2e-testing" agent skill from https://github.com/redis/RedisInsight/tree/main/.ai/skills/e2e-testing into .github/skills/e2e-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "e2e-testing", 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.
$ npx skills add redis/RedisInsight --skill e2e-testing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install redis/RedisInsight e2e-testing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/redis/RedisInsight.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.ai/skills/e2e-testing .opencode/skills/e2e-testing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "e2e-testing" agent skill from https://github.com/redis/RedisInsight/tree/main/.ai/skills/e2e-testing into .opencode/skills/e2e-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "e2e-testing", 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-testing- GitHub stars
- 8.9k
- Token cost
- ~5.1k tokens
- SKILL.md length
- 1,144 words
- Files
- 1
- Skills in repo
- 15
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Playwright end-to-end testing standards for RedisInsight: page object models, test structure, fixtures, navigation patterns, and flaky-test prevention.
- Works in 3 steps: Shared Database with beforeAll/afterAll → Use Serial Only When Tests Truly Depend… → Unique Test Data Per Test (when needed)
- Editing files under tests/e2e-playwright/
- SKILL.md covers Location, Test Plan, Project Structure and Playwright Projects, plus 6 more sections
- Calls npx and npm
What it does
E2E Testing is an agent skill from redis/RedisInsight, published by the product's own GitHub organization. Playwright end-to-end testing standards for RedisInsight: page object models, test structure, fixtures, navigation patterns, and flaky-test prevention. Use when editing files under tests/e2e-playwright/, writing Playwright tests, adding page objects, or when the user mentions Playwright, E2E tests, page objects, or end-to-end testing.
Its SKILL.md is about 5.1k 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 Browser testing. It works with Playwright and Redis.
When your agent uses it
- Editing files under tests/e2e-playwright/
- Writing Playwright tests
- Adding page objects
- The user mentions Playwright
Example prompts
- “/e2e-testing”
Requirements
- Node.js
Workflow steps
3 steps, taken from the step headings in SKILL.md.
- Shared Database with beforeAll/afterAll
- Use Serial Only When Tests Truly Depend on Each Other
- Unique Test Data Per Test (when needed)
What it can do on your machine
Read from SKILL.md and the folder at commit 43bd288. 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:
npxnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
github.com
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 Testing loads about 5.1k tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 1,144 words of instructions outside code blocks.
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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,144 words (~5,069 tokens).
“All E2E tests are in tests/e2e-playwright/. This is a standalone package - no imports from redisinsight/ui/ or redisinsight/api/.”
- name
- e2e-testing
Files
Just SKILL.md in .ai/skills/e2e-testing of redis/RedisInsight.
Open the folder on GitHubat commit 43bd288
Compare with similar skills
E2E Testing 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| E2E Testing this skillredis/RedisInsight | 8.9k | — | ~5.1k | Automated safety check: Pass | Custom licence | |
| E2Eopenathleteorg/openathlete | 100 | — | ~675 | Automated safety check: Pass | AGPL-3.0 | |
| Web Application Testinganthropics/skills | 180k | 51 repos | ~966 | Automated safety check: Pass | Apache-2.0 | |
| playwright-cli Browser Automationgithub/gh-aw | 5.4k | 24 repos | ~2.8k | Automated safety check: Pass | MIT | |
| Write and Verify Playwright Testsappsmithorg/appsmith | 41k | — | ~2.9k | Automated safety check: Notes | Apache-2.0 | |
| Cucumber and Playwright E2E Testslanggenius/dify | 158k | — | ~682 | Automated safety check: Pass | Custom licence |
Similar skills
- Official
Web Application Testing
anthropics/skills
Tests local web applications with Python Playwright scripts, checking frontend behavior, capturing screenshots and reading browser console logs.
- Official
playwright-cli Browser Automation
github/gh-aw
Drives a real browser from the command line with playwright-cli to open pages, interact, mock requests, save state and work with Playwright tests.
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.
Cucumber and Playwright E2E Tests
langgenius/dify
Guides changes and reviews of the Cucumber and Playwright end-to-end suite under `e2e/`: feature files, step definitions, support code, tags, locators and assertions.
E2E Testing
langflow-ai/langflow
Write and review Playwright E2E tests for Langflow. An agent skill from langflow-ai/langflow.
More from redis/RedisInsight
All 15 skills in this repo- Official
Redis Insight Plugin
redis/RedisInsight
A skill your agent uses when creating, modifying, debugging, deploying, or testing Redis Insight Workbench visualization plugins, plugin manifests, package.json visualizations, activationMethod…
- Official
Backend
redis/RedisInsight
NestJS backend development patterns for the RedisInsight API: module structure, services, controllers, DTOs, dependency injection, and error handling.
- Official
Code Quality
redis/RedisInsight
Code-quality standards for RedisInsight: TypeScript strictness, naming conventions (camelCase, PascalCase, UPPERSNAKECASE), linting rules, no any without reason, no !important in styles, and…
- Official
Commits
redis/RedisInsight
Generate commit messages following Conventional Commits format.
- Official
Dead Dependencies
redis/RedisInsight
Find and safely remove unused ("dead") npm dependencies in RedisInsight using a grep + leaf-check + build-gate recipe.
- Official
Feature Flags
redis/RedisInsight
Create, modify, and remove feature flags in RedisInsight. An agent skill from redis/RedisInsight.
Related
Works with
Categories
Questions about E2E Testing
What does E2E Testing do?
Playwright end-to-end testing standards for RedisInsight: page object models, test structure, fixtures, navigation patterns, and flaky-test prevention. E2E Testing is an agent skill from redis/RedisInsight, published by the product's own GitHub organization. Playwright end-to-end testing standards for RedisInsight: page object models, test structure, fixtures, navigation patterns, and flaky-test prevention.
When should I use E2E Testing?
E2E Testing fits situations like: editing files under tests/e2e-playwright/; writing Playwright tests; adding page objects; the user mentions Playwright.
How do I install E2E Testing in Claude Code?
Run `npx skills add redis/RedisInsight --skill e2e-testing -a claude-code`. Or copy the skill folder (.ai/skills/e2e-testing in redis/RedisInsight) into .claude/skills/e2e-testing in your project. Claude Code loads it when a task matches its description.
How do I install E2E Testing in Codex?
Run `npx skills add redis/RedisInsight --skill e2e-testing -a codex`. Or copy the skill folder (.ai/skills/e2e-testing in redis/RedisInsight) into .agents/skills/e2e-testing in your project. Codex loads it when a task matches its description.
Can I use E2E Testing 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 redis/RedisInsight --skill e2e-testing -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-testing, .gemini/skills/e2e-testing, .github/skills/e2e-testing and .opencode/skills/e2e-testing in your project.
What does E2E Testing need to run?
Going by SKILL.md and its folder, E2E Testing needs the command-line tools its instructions call (npx and npm). Our summary lists: Node.js.
Does E2E Testing access the network?
SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.
Is E2E Testing 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 Testing use?
E2E Testing has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does E2E Testing use?
About 5.1k tokens (SKILL.md is roughly 20k 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 Testing?
Skills that share tags, products or a category with E2E Testing: E2E (openathleteorg/openathlete, 100 stars), Web Application Testing (anthropics/skills, 180k stars), playwright-cli Browser Automation (github/gh-aw, 5.4k stars) and Write and Verify Playwright Tests (appsmithorg/appsmith, 41k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains E2E Testing?
redis (a GitHub organization, an official publisher) maintains it in redis/RedisInsight, which has 8,882 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 4, 2026.
Source: redis/RedisInsight on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.