Agent skill

Browser E2E Tests

by dxos in dxos/dxos

Authoring browser end-to-end tests for the Composer app with Playwright.

Custom licenceAuto-check passedTesting & QA

Install Browser E2E Tests

skills CLI
$ npx skills add dxos/dxos --skill browser-e2e-tests -a claude-code

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

GitHub CLI
$ gh skill install dxos/dxos browser-e2e-tests --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/dxos/dxos.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/browser-e2e-tests .claude/skills/browser-e2e-tests && 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
browser-e2e-tests
GitHub stars
525
Token cost
~2k tokens
SKILL.md length
766 words
Files
1
Skills in repo
41
Repo updated
First seen
Licence
Custom licence

At a glance

Authoring browser end-to-end tests for the Composer app with Playwright.

  • Works in 3 steps: data-testid — the default; add it if… → Framework/ARIA state that encodes… → Role — only scoped inside a testid'd…
  • Reviewing .spec.ts under packages/apps/composer-app/src/playwright
  • SKILL.md covers Every test binds to an .mdl QA…, Golden rule: target by…, Selector priority (only when a… and Spec structure, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Browser E2E Tests is an agent skill from dxos/dxos. Authoring browser end-to-end tests for the Composer app with Playwright. Use when writing, editing, or reviewing .spec.ts under packages/apps/composer-app/src/playwright, adding page-object helpers, or deciding how to target elements (always data-testid, never labels/roles).

Its SKILL.md is about 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 Browser testing. It works with Playwright. The repository describes itself as: TypeScript implementation of the DXOS protocols, SDK, toolchain and Composer.

When your agent uses it

  • Reviewing .spec.ts under packages/apps/composer-app/src/playwright
  • Adding page-object helpers
  • Deciding how to target elements (always data-testid
  • Never labels/roles)

Example prompts

  • “/browser-e2e-tests”

Workflow steps

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

  1. data-testid — the default; add it if missing.
  2. Framework/ARIA state that encodes behavior, not copy: aria-selected, aria-current, ids/
  3. Role — only scoped inside a testid'd container, never role + translated name as the primary hook.

What it can do on your machine

Read from SKILL.md and the folder at commit 2e6b92a. 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

    No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript and mdl).

    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

Browser E2E Tests loads about 2k tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 766 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~74
When it runs · the whole SKILL.md, loaded when a task matches
~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

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 766 words (~1,979 tokens).

“Browser e2e drives the real Composer app in a browser — the only tier that verifies perceived behavior: interactivity during async work, no false empty states, and full click→render flows. Distinct from agent-eval-tests (the LLM agent harness) and storybook interaction…”

— opening of SKILL.md by dxos, Custom licence
name
browser-e2e-tests

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .agents/skills/browser-e2e-tests of dxos/dxos.

Open the folder on GitHubat commit 2e6b92a

Compare with similar skills

Browser E2E Tests 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.

Browser E2E Tests compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Browser E2E Tests this skilldxos/dxos525—~2kAutomated safety check: PassCustom licence
Web Application Testinganthropics/skills180k51 repos~966Automated safety check: PassApache-2.0
Write and Verify Playwright Testsappsmithorg/appsmith41k—~2.9kAutomated safety check: NotesApache-2.0
playwright-cli Browser Automationgithub/gh-aw5.4k23 repos~2.8kAutomated safety check: PassMIT
Cucumber and Playwright E2E Testslanggenius/dify158k—~682Automated safety check: PassCustom licence
E2E Testinglangflow-ai/langflow155k—~3.3kAutomated safety check: PassMIT

Similar skills

  • 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
  • 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
  • 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
  • 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.

    158k GitHub stars~682 tokensUpdated today
    Testing & QAAuto-check passed
  • E2E Testing

    langflow-ai/langflow

    Write and review Playwright E2E tests for Langflow. An agent skill from langflow-ai/langflow.

    155k GitHub stars~3.3k tokensUpdated today
    Testing & QAAuto-check passed
  • Handsontable Playwright E2E Tests

    handsontable/handsontable

    Guides writing and changing Playwright end-to-end tests for Handsontable using page objects, data-testid hooks and deterministic waits.

    22k GitHub stars~1.8k tokensUpdated today
    Testing & QAAuto-check passed

More from dxos/dxos

All 41 skills in this repo
  • Run the rule-driven agentic code review — discover rule blocks in the repo's .mdl files, prepare per-rule review groups (full project by default; diff-only with --pr-only), spawn one focused Sonnet…

    525 GitHub stars~4.4k tokensUpdated today
    Auto-check passed
  • Forensically inspect and repair Composer browser profiles — offline (Chrome OPFS / SQLite extract) or live via /recovery.html debug port.

    525 GitHub stars~3.1k tokensUpdated today
    Auto-check passed
  • Migrate Oxfmt

    dxos/dxos

    Guide for migrating a project from Prettier or Biome to Oxfmt.

    525 GitHub starsUsed in 3 repos~2.2k tokens
    Auto-check passed
  • Moon

    dxos/dxos

    This skill should be used when the user asks to "configure moon", "set up moonrepo", "create moon tasks", "run moon commands", "configure moon workspace", "add moon project", "moon ci setup", "moon…

    525 GitHub stars~2.1k tokensUpdated today
    Auto-check passed
  • Reference for SubductionPolicy (the four hooks authorizeConnect, authorizeFetch, authorizePut, filterAuthorizedFetch passed via Subduction.hydrate(..., policy) or new Repo({ subductionPolicy })).

    525 GitHub stars~3.4k tokensUpdated today
    Auto-check passed
  • Autocue

    dxos/dxos

    Record a demo of the running app that the agent drives itself — a .mdl QA test or an ad-hoc walkthrough — as a captioned .webm (or a screenshot), trimmed of dead air and ready to attach.

    525 GitHub stars~12k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Browser E2E Tests

What does Browser E2E Tests do?

Authoring browser end-to-end tests for the Composer app with Playwright. Browser E2E Tests is an agent skill from dxos/dxos. Authoring browser end-to-end tests for the Composer app with Playwright.

When should I use Browser E2E Tests?

Browser E2E Tests fits situations like: reviewing .spec.ts under packages/apps/composer-app/src/playwright; adding page-object helpers; deciding how to target elements (always data-testid; never labels/roles).

How do I install Browser E2E Tests in Claude Code?

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

How do I install Browser E2E Tests in Codex?

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

Can I use Browser E2E Tests 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 dxos/dxos --skill browser-e2e-tests -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/browser-e2e-tests, .gemini/skills/browser-e2e-tests, .github/skills/browser-e2e-tests and .opencode/skills/browser-e2e-tests in your project.

What does Browser E2E Tests need to run?

SKILL.md names no scripts, command-line tools or credentials: Browser E2E Tests is instructions for the agent only.

Does Browser E2E Tests 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 Browser E2E Tests 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 Browser E2E Tests use?

Browser E2E Tests 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 Browser E2E Tests use?

About 2k tokens (SKILL.md is roughly 7.9k 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 Browser E2E Tests?

Skills that share tags, products or a category with Browser E2E Tests: Web Application Testing (anthropics/skills, 180k stars), Write and Verify Playwright Tests (appsmithorg/appsmith, 41k stars), playwright-cli Browser Automation (github/gh-aw, 5.4k stars) and Cucumber and Playwright E2E Tests (langgenius/dify, 158k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Browser E2E Tests?

dxos (a GitHub organization) maintains it in dxos/dxos, which has 525 GitHub stars. The repository holds 41 skills in this directory. The repository was last updated on October 9, 2026.

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