E2E Testing
OpenHands/OpenHands
This skill should be used when the user asks to "add an E2E test", "run live E2E", "run mock-LLM tests", "debug Playwright CI", "test the Docker image", or changes tests/e2e, Playwright configs, E2E…
Write, update, debug, or run Baserow end-to-end tests in e2e-tests using Playwright, the repo's e2e fixtures, page objects, Docker stack, and just e2e commands.
Install Write E2E Test
$ npx skills add baserow/baserow --skill write-e2e-test -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install baserow/baserow write-e2e-test --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/baserow/baserow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/write-e2e-test .claude/skills/write-e2e-test && 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 "write-e2e-test" agent skill from https://github.com/baserow/baserow/tree/develop/.agents/skills/write-e2e-test into .claude/skills/write-e2e-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-e2e-test", 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/baserow/baserow/tree/develop/.agents/skills/write-e2e-testType 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 baserow/baserow --skill write-e2e-test -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install baserow/baserow write-e2e-test --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/baserow/baserow.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/write-e2e-test .agents/skills/write-e2e-test && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "write-e2e-test" agent skill from https://github.com/baserow/baserow/tree/develop/.agents/skills/write-e2e-test into .agents/skills/write-e2e-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-e2e-test", 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 baserow/baserow --skill write-e2e-test -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install baserow/baserow write-e2e-test --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/baserow/baserow.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/write-e2e-test .cursor/skills/write-e2e-test && 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 "write-e2e-test" agent skill from https://github.com/baserow/baserow/tree/develop/.agents/skills/write-e2e-test into .cursor/skills/write-e2e-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-e2e-test", 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/baserow/baserow.git --path .agents/skills/write-e2e-test--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 baserow/baserow --skill write-e2e-test -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install baserow/baserow write-e2e-test --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/baserow/baserow.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/write-e2e-test .gemini/skills/write-e2e-test && 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 "write-e2e-test" agent skill from https://github.com/baserow/baserow/tree/develop/.agents/skills/write-e2e-test into .gemini/skills/write-e2e-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-e2e-test", 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 baserow/baserow write-e2e-testInstalls 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 baserow/baserow --skill write-e2e-test -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/baserow/baserow.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/write-e2e-test .github/skills/write-e2e-test && 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 "write-e2e-test" agent skill from https://github.com/baserow/baserow/tree/develop/.agents/skills/write-e2e-test into .github/skills/write-e2e-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-e2e-test", 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 baserow/baserow --skill write-e2e-test -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install baserow/baserow write-e2e-test --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/baserow/baserow.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/write-e2e-test .opencode/skills/write-e2e-test && 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 "write-e2e-test" agent skill from https://github.com/baserow/baserow/tree/develop/.agents/skills/write-e2e-test into .opencode/skills/write-e2e-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-e2e-test", 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
write-e2e-test- GitHub stars
- 6.1k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 568 words
- Files
- 2
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Write, update, debug, or run Baserow end-to-end tests in e2e-tests using Playwright, the repo's e2e fixtures, page objects, Docker stack, and just e2e commands.
- Works in 6 steps: Put the spec in the existing feature… → Use API fixtures for initial data and… → Use role, label, placeholder, and text… → …
- Tasks that involve End-to-end testing
- SKILL.md covers First Step, Local Test Architecture, Writing Tests and Running Tests, plus 1 more section
- Calls just, rg and yarn
What it does
Write E2E Test is an agent skill from baserow/baserow. Write, update, debug, or run Baserow end-to-end tests in e2e-tests using Playwright, the repo's e2e fixtures, page objects, Docker stack, and just e2e commands.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Testing & QA, covering End-to-end testing. It works with Playwright, Docker and Airtable. The repository describes itself as: Build databases, automations, apps & agents with AI — no code. Open source platform available on cloud and self-hosted. GDPR, HIPAA, SOC 2 compliant. Best Airtable alternative.
When your agent uses it
- Tasks that involve End-to-end testing
Example prompts
- “/write-e2e-test”
Requirements
- Docker
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Put the spec in the existing feature directory, for example
- Use API fixtures for initial data and reserve UI steps for the behavior being
- Use role, label, placeholder, and text locators when stable. Use CSS class
- Wait with Playwright assertions such as await expect(locator).toBeVisible(),
- If multiple tests share expensive setup, follow nearby specs that use
- For network-sensitive behavior, use page.waitForResponse,
What it can do on your machine
Read from SKILL.md and the folder at commit 68aec3c. 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:
justrgyarn
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use yarn, 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
Write E2E Test loads about 1.3k tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 568 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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteMentions a .env fileSKILL.md:121
in `e2e-tests/.env`.
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 568 words (~1,282 tokens).
“Use this skill when a task involves adding, fixing, reviewing, debugging, or executing end-to-end tests in e2e-tests.”
- name
- write-e2e-test
Files
SKILL.md and 1 other file in .agents/skills/write-e2e-test of baserow/baserow.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 68aec3c
Compare with similar skills
Write 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Write E2E Test this skillbaserow/baserow | 6.1k | — | ~1.3k | Automated safety check: Notes | Custom licence | |
| E2E TestingOpenHands/OpenHands | 90k | — | ~308 | Automated safety check: Pass | MIT | |
| E2Esendou-ink/sendou.ink | 297 | — | ~2.1k | Automated safety check: Notes | AGPL-3.0 | |
| Dev Webtestclassmethod/tsumiki | 974 | — | ~4.2k | Automated safety check: Pass | MIT | |
| E2Eopenathleteorg/openathlete | 100 | — | ~675 | Automated safety check: Pass | AGPL-3.0 | |
| Dokan Run Test Suitegetdokan/dokan | 288 | — | ~4.7k | Automated safety check: Notes | None |
Similar skills
E2E
sendou-ink/sendou.ink
Run, debug, and manage Playwright e2e tests. An agent skill from sendou-ink/sendou.ink.
Dev Webtest
classmethod/tsumiki
This skill should be used when the user asks to "dev-webtest", "Webテスト", "画面の動作確認", "E2Eテスト", "web test", "visual check", "モンキーテスト", "アクセシビリティチェック", "レスポンシブテスト", "フォームテスト".
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…
Dokan Run Test Suite
getdokan/dokan
Execute the Dokan Playwright test suite (E2E + API), locally or via GitHub Actions.
E2E Live
receptron/mulmoclaude
実 Claude API を叩く総合テスト（全カテゴリ）を実行する。リリース前ではなく、定期的に手動で回して回帰を検出するための skill。yarn dev が起動済みであることが前提。
More from baserow/baserow
All 11 skills in this repoReview PR
baserow/baserow
Review a Baserow pull request, branch, or diff against its actual base the way the maintainers do.
Add Config Env Var
baserow/baserow
Add a Baserow configuration environment variable for the backend, frontend, or both, and propagate it through settings, Nuxt runtime config, Docker Compose, documentation, consumers, and tests as…
Create Changelog
baserow/baserow
Generate a changelog entry for the current Git branch by inspecting changed files, classifying the domain and type, writing a short public-friendly message, and running just changelog add after the…
Silk Profiler
baserow/baserow
Investigate backend performance using Django Silk profiling data.
Baserow Registry
baserow/baserow
Explain, create, update, or use Baserow registries across backend and frontend code, including Instance/Registry patterns, registration points, model-backed type registries, serializer/API…
Core Graph
baserow/baserow
A skill your agent uses when working on code involving Element/Page relationships in the Application Builder (contrib/builder) or AutomationNode/AutomationWorkflow relationships in the Automation…
Related
Works with
Categories
Questions about Write E2E Test
What does Write E2E Test do?
Write, update, debug, or run Baserow end-to-end tests in e2e-tests using Playwright, the repo's e2e fixtures, page objects, Docker stack, and just e2e commands. Write E2E Test is an agent skill from baserow/baserow. Write, update, debug, or run Baserow end-to-end tests in e2e-tests using Playwright, the repo's e2e fixtures, page objects, Docker stack, and just e2e commands.
When should I use Write E2E Test?
Write E2E Test fits situations like: tasks that involve End-to-end testing.
How do I install Write E2E Test in Claude Code?
Run `npx skills add baserow/baserow --skill write-e2e-test -a claude-code`. Or copy the skill folder (.agents/skills/write-e2e-test in baserow/baserow) into .claude/skills/write-e2e-test in your project. Claude Code loads it when a task matches its description.
How do I install Write E2E Test in Codex?
Run `npx skills add baserow/baserow --skill write-e2e-test -a codex`. Or copy the skill folder (.agents/skills/write-e2e-test in baserow/baserow) into .agents/skills/write-e2e-test in your project. Codex loads it when a task matches its description.
Can I use Write 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 baserow/baserow --skill write-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/write-e2e-test, .gemini/skills/write-e2e-test, .github/skills/write-e2e-test and .opencode/skills/write-e2e-test in your project.
What does Write E2E Test need to run?
Going by SKILL.md and its folder, Write E2E Test needs the command-line tools its instructions call (just, rg and yarn). Our summary lists: Docker.
Does Write 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 Write E2E Test safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Write E2E Test use?
Write E2E Test 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 Write E2E Test use?
About 1.3k tokens (SKILL.md is roughly 5.1k 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 Write E2E Test?
Skills that share tags, products or a category with Write E2E Test: E2E Testing (OpenHands/OpenHands, 90k stars), E2E (sendou-ink/sendou.ink, 297 stars), Dev Webtest (classmethod/tsumiki, 974 stars) and E2E (openathleteorg/openathlete, 100 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Write E2E Test?
baserow (a GitHub organization) maintains it in baserow/baserow, which has 6,092 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 7, 2026.
Source: baserow/baserow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.