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 Testing

by nodetool-ai in nodetool-ai/nodetool

Write, repair, or diagnose Playwright E2E tests for NodeTool web and workflow harnesses using existing suites and fixtures.

AGPL-3.0Auto-check passedTesting & QA

Install E2E Testing

skills CLI
$ npx skills add nodetool-ai/nodetool --skill e2e-testing -a claude-code

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

GitHub CLI
$ gh skill install nodetool-ai/nodetool e2e-testing --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/nodetool-ai/nodetool.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/yts806379-everything-claude-code-e2e-testing .claude/skills/e2e-testing && 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-testing
GitHub stars
556
Token cost
~592 tokens
SKILL.md length
292 words
Files
2
Skills in repo
127
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Write, repair, or diagnose Playwright E2E tests for NodeTool web and workflow harnesses using existing suites and fixtures.

  • Tasks that involve End-to-end testing
  • SKILL.md covers Choose the suite, Write or diagnose the test and Verify and report
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

E2E Testing is an agent skill from nodetool-ai/nodetool. Write, repair, or diagnose Playwright E2E tests for NodeTool web and workflow harnesses using existing suites and fixtures.

Its SKILL.md is about 590 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. The repository describes itself as: Agent-first Creative Workspace. The licence is AGPL-3.0.

When your agent uses it

  • Tasks that involve End-to-end testing

Example prompts

  • “/e2e-testing”

What it can do on your machine

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

    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

E2E Testing loads about 592 tokens when it runs. Until then it costs about 34 tokens; SKILL.md has 292 words of instructions outside code blocks.

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

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 nodetool-ai/nodetool at commit 515bd28, republished under its AGPL-3.0 licence (© nodetool-ai). 292 words, ~592 tokens.

Download SKILL.mdSave it as .claude/skills/e2e-testing/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
e2e-testing
description
Write, repair, or diagnose Playwright E2E tests for NodeTool web and workflow harnesses using existing suites and fixtures.
origin
ECC

E2E testing

Build or repair a Playwright test that detects the requested user-visible behavior. Use web/TESTING.md and the existing suite's fixtures, page objects, and configuration. Do not replace them with a generic scaffold. Electron main-process tests use Jest under electron/src/__tests__/, as described in Electron instructions.

Choose the suite

Inspect web/package.json and the relevant Playwright config for the exact command. Use the graph runner or debug harness for real-backend workflow scenarios. Read its entry in the harness reference before first use. Build backend packages and install the required Playwright browser as described in the testing guide before running web E2E.

Write or diagnose the test

Reuse the nearest scenario. Select controls by role and accessible name when available. Assert the specific visible result with retrying Playwright assertions. Keep tests independent and reset fixtures through the suite's existing mechanism.

Register a network wait before triggering the action that produces the request. Wait for a specific response or visible state, not arbitrary sleeps or global network idleness. Use page objects only where they simplify repeated interactions.

For a reported failure, reproduce it before changing the test or application. Inspect its trace, screenshot, console, and request evidence. Use bounded repeat runs when diagnosing an intermittent race. A retry reaching green does not prove the race is fixed. Do not hide failures with skip, fixme, or extra retries.

Verify and report

Run the affected scenario and confirm the assertion detects the intended failure and passes with the correction. Use the suite's configured trace, screenshot, and video capture rather than introducing a separate recording mechanism.

Complete mandatory post-change verification for code changes. Report the tested scenario, actual command result, and relevant failure artifacts. Do not run unrelated browser suites without a dependency or unresolved concern that warrants them.

© nodetool-ai, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .agents/skills/yts806379-everything-claude-code-e2e-testing of nodetool-ai/nodetool.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 515bd28

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.

E2E Testing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
E2E Testing this skillnodetool-ai/nodetool556—~592Automated safety check: PassAGPL-3.0
Web Application Testinganthropics/skills180k51 repos~966Automated safety check: PassApache-2.0
playwright-cli Browser Automationgithub/gh-aw5.4k24 repos~2.8kAutomated safety check: PassMIT
Write and Verify Playwright Testsappsmithorg/appsmith41k—~2.9kAutomated safety check: NotesApache-2.0
Cucumber and Playwright E2E Testslanggenius/dify158k—~682Automated safety check: PassCustom licence
E2E Testinglangflow-ai/langflow156k—~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

  • 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 24 repos~2.8k tokens
    Testing & QAAuto-check passed

  • 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

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

    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.

    156k GitHub stars~3.3k tokensUpdated today
    Testing & QAAuto-check passed

  • 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

More from nodetool-ai/nodetool

All 127 skills in this repo

  • Beat Sync Editing

    nodetool-ai/nodetool

    Cut a NodeTool timeline to music and shape its pacing — detect the beat grid, place cuts on phrases, pick a cut type, build speed ramps with time remap, and give the piece an arc.

    556 GitHub stars~2.6k tokensUpdated today
    Auto-check passed

  • Caption Titles

    nodetool-ai/nodetool

    Add and animate a consistent text layer on an existing NodeTool timeline.

    556 GitHub stars~1.9k tokensUpdated today
    Auto-check passed

  • Color Motion

    nodetool-ai/nodetool

    Choose and animate colour on a NodeTool timeline, including shape and text gradients, colour grades, 3D LUTs, and dither.

    556 GitHub stars~2.3k tokensUpdated today
    Auto-check passed

  • Commercial Beat Sheet

    nodetool-ai/nodetool

    Write a shootable, precisely timed commercial beat sheet and store it as a NodeTool storyboard, with a consistent entity roster behind every shot.

    556 GitHub stars~4.6k tokensUpdated today
    Auto-check passed

  • Elevenlabs Audio Prompting

    nodetool-ai/nodetool

    Direct ElevenLabs speech, dialogue, sound effects and music — the bracketed audio tags v3 acts on and why the voice decides whether a tag lands, stability as the delivery dial, punctuation instead…

    556 GitHub stars~1.9k tokensUpdated today
    Auto-check passed

  • Frame Composition

    nodetool-ai/nodetool

    Stage the frame on a NodeTool timeline — grids, focal placement, safe areas per aspect ratio, depth layers and parallax, camera moves, and where elements enter and leave.

    556 GitHub stars~3.5k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about E2E Testing

What does E2E Testing do?

Write, repair, or diagnose Playwright E2E tests for NodeTool web and workflow harnesses using existing suites and fixtures. E2E Testing is an agent skill from nodetool-ai/nodetool. Write, repair, or diagnose Playwright E2E tests for NodeTool web and workflow harnesses using existing suites and fixtures.

When should I use E2E Testing?

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

How do I install E2E Testing in Claude Code?

Run `npx skills add nodetool-ai/nodetool --skill e2e-testing -a claude-code`. Or copy the skill folder (.agents/skills/yts806379-everything-claude-code-e2e-testing in nodetool-ai/nodetool) 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 nodetool-ai/nodetool --skill e2e-testing -a codex`. Or copy the skill folder (.agents/skills/yts806379-everything-claude-code-e2e-testing in nodetool-ai/nodetool) 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 nodetool-ai/nodetool --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?

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

Does E2E Testing 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 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 is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does E2E Testing use?

About 592 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 Testing?

Skills that share tags, products or a category with E2E Testing: Web Application Testing (anthropics/skills, 180k stars), playwright-cli Browser Automation (github/gh-aw, 5.4k stars), Write and Verify Playwright Tests (appsmithorg/appsmith, 41k 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 E2E Testing?

nodetool-ai (a GitHub organization) maintains it in nodetool-ai/nodetool, which has 556 GitHub stars. The repository holds 127 skills in this directory. The repository was last updated on October 8, 2026.

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