New: 97,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

Appbuilder E2E Testing

by NeverSight in NeverSight/learn-skills.dev

A skill your agent uses whenever the user wants browser-based end-to-end tests for an Adobe App Builder application.

Apache-2.0Auto-check passedTesting & QA

Install Appbuilder E2E Testing

skills CLI
$ npx skills add NeverSight/learn-skills.dev --skill appbuilder-e2e-testing -a claude-code

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

GitHub CLI
$ gh skill install NeverSight/learn-skills.dev appbuilder-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/NeverSight/learn-skills.dev.git skills-src && mkdir -p .claude/skills && cp -r skills-src/data/skills-md/adobe/skills/appbuilder-e2e-testing .claude/skills/appbuilder-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
appbuilder-e2e-testing
GitHub stars
216
Used in
1 other repo
Token cost
~1.8k tokens
SKILL.md length
758 words
Files
13
Skills in repo
43
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses whenever the user wants browser-based end-to-end tests for an Adobe App Builder application.

  • Works in 7 steps: Scan project for web-src/ (SPA) or… → Install Playwright if not present: npm… → Generate playwright.config.ts from… → …
  • The user wants browser-based end-to-end tests for an Adobe App Builder application
  • SKILL.md covers Pattern Quick-Reference, Fast Path (for clear requests), Quick Reference and Full Workflow (for ambiguous…, plus 6 more sections
  • Calls npx and npm

What it does

Appbuilder E2E Testing is an agent skill from NeverSight/learn-skills.dev. Use this skill whenever the user wants browser-based end-to-end tests for an Adobe App Builder application. Covers Playwright E2E testing for ExC Shell SPAs, AEM extension UIs, and full-stack flows. Use when the user mentions: "E2E test", "end-to-end test", "Playwright", "browser test", "test my SPA in the browser", "test my AEM extension", "test the full flow", "integration test with UI", "headless browser test", "E2E in CI". This skill is for BROWSER-based testing only. For Jest unit tests of actions or React…

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files (for example `stats.json`). Compatibility notes: Requires Node.js 18+, Playwright

It sits in Testing & QA, covering End-to-end testing, Browser testing and Unit testing. It works with Playwright, Adobe Experience Manager and Jest. The repository describes itself as: Curated high-quality AI Agent Skills. Search, install, copy and share. Works with Claude Code, Cursor, OpenClaw, and other AI coding tools. The licence is Apache-2.0.

When your agent uses it

  • The user wants browser-based end-to-end tests for an Adobe App Builder application
  • The user mentions: E2E test
  • End-to-end test
  • Test my SPA in the browser

Example prompts

  • “E2E test”
  • “end-to-end test”
  • “Playwright”
  • “/appbuilder-e2e-testing”

Requirements

  • Node.js
  • Compatibility (from SKILL.md): Requires Node.js 18+, Playwright
  • Pre-approved tools (allowed-tools): Bash(npx:*), Bash(npm:*), Bash(node:*), Bash(aio:*), Read, Write, Edit

Workflow steps

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

  1. Scan project for web-src/ (SPA) or @adobe/uix-guest in dependencies (AEM extension)
  2. Install Playwright if not present: npm install -D @playwright/test && npx playwright install chromium
  3. Generate playwright.config.ts from assets/playwright.config.ts
  4. For ExC Shell SPA: read references/e2e-testing-patterns.md, generate test with iframe navigation, shell wait, Spectrum ARIA selectors
  5. For AEM extension: read references/aem-extension-testing.md, generate test with Extension Tester URL, nested iframe handling, modal flows
  6. Run tests: npx playwright test
  7. If CI requested: generate GitHub Actions workflow from assets/e2e-ci-workflow.yml

What it can do on your machine

Read from SKILL.md and the folder at commit 08f9d22. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash(npx:*)
    • Bash(npm:*)
    • Bash(node:*)
    • Bash(aio:*)
    • Read
    • Write
    • Edit

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npx
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx and npm, 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.

  • Compatibility

    Requires Node.js 18+, Playwright

    From compatibility in the SKILL.md frontmatter.

Context cost

Appbuilder E2E Testing loads about 1.8k tokens when it runs. Until then it costs about 146 tokens; SKILL.md has 758 words of instructions outside code blocks.

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

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 NeverSight/learn-skills.dev at commit 08f9d22, republished under its Apache-2.0 licence (© NeverSight). 758 words, ~1,844 tokens.

Download SKILL.mdSave it as .claude/skills/appbuilder-e2e-testing/SKILL.md (or your agent's skills folder). This skill also uses 12 other files; get the full folder from GitHub.
name
appbuilder-e2e-testing
description
Use this skill whenever the user wants browser-based end-to-end tests for an Adobe App Builder application. Covers Playwright E2E testing for ExC Shell SPAs, AEM extension UIs, and full-stack flows. Use when the user mentions: "E2E test", "end-to-end test", "Playwright", "browser test", "test my SPA in the browser", "test my AEM extension", "test the full flow", "integration test with UI", "headless browser test", "E2E in CI". This skill is for BROWSER-based testing only. For Jest unit tests of actions or React components, use appbuilder-testing instead.
allowed-tools
Bash(npx:*), Bash(npm:*), Bash(node:*), Bash(aio:*), Read, Write, Edit
compatibility
Requires Node.js 18+, Playwright
metadata.category
e2e-testing
license
Apache-2.0

App Builder E2E Testing

Playwright-based browser E2E testing for Adobe App Builder SPAs and AEM extensions. This skill generates Playwright configs, test files, and CI workflows for browser-level validation.

Pattern Quick-Reference

Identify the user's intent, then read the referenced sections to generate tailored tests.

User wantsReferenceAsset
E2E test for ExC Shell SPAreferences/e2e-testing-patterns.mdassets/playwright.config.ts, assets/e2e-test-template.spec.ts
Test AEM extension in browserreferences/aem-extension-testing.mdassets/playwright.config.ts
E2E tests in CI pipelinereferences/ci-integration.mdassets/e2e-ci-workflow.yml

Fast Path (for clear requests)

When the user says "add E2E tests" or "write Playwright tests" and intent is clear:

  1. Scan project for web-src/ (SPA) or @adobe/uix-guest in dependencies (AEM extension)
  2. Install Playwright if not present: npm install -D @playwright/test && npx playwright install chromium
  3. Generate playwright.config.ts from assets/playwright.config.ts
  4. For ExC Shell SPA: read references/e2e-testing-patterns.md, generate test with iframe navigation, shell wait, Spectrum ARIA selectors
  5. For AEM extension: read references/aem-extension-testing.md, generate test with Extension Tester URL, nested iframe handling, modal flows
  6. Run tests: npx playwright test
  7. If CI requested: generate GitHub Actions workflow from assets/e2e-ci-workflow.yml

Quick Reference

  • Test directory: e2e/ at project root (separate from Jest test/)
  • Config file: playwright.config.ts at project root
  • Install command: npm install -D @playwright/test && npx playwright install chromium (installs Playwright + Chromium browser)
  • Run command: npx playwright test (headless) or npx playwright test --headed (visible browser)
  • Debug command: npx playwright test --debug (step-through mode)
  • Report command: npx playwright show-report (open HTML report)
  • ExC Shell iframe: Access SPA inside shell via page.frameLocator('iframe') — exact selector varies, see references/e2e-testing-patterns.md
  • Spectrum selectors: Use ARIA roles, not CSS classes: getByRole('button', { name: 'Save' }), getByRole('grid'), getByRole('textbox')
  • Auth note: Full ExC Shell auth automation is complex — recommend testing against aio app dev (local) first. See references/e2e-testing-patterns.md § Authentication.
  • AEM extensions: Use Extension Tester URL with devMode=true. See references/aem-extension-testing.md.

Full Workflow (for ambiguous or complex requests)

  1. Scan project — Check for web-src/ (SPA), @adobe/uix-guest (AEM extension), existing test setup, app.config.yaml extension type
  2. Confirm scope — Which pages/flows to test? Local dev or deployed? CI needed?
  3. Install Playwright — npm install -D @playwright/test && npx playwright install chromium if not already installed
  4. Generate config — Copy and customize assets/playwright.config.ts for the project
  5. Generate test files — Read appropriate reference doc, generate tests matching project structure:
    • ExC Shell SPA → references/e2e-testing-patterns.md
    • AEM extension → references/aem-extension-testing.md
  6. Add action stubbing — If tests need deterministic backend responses, add page.route() intercepts
  7. Run and iterate — npx playwright test, fix selectors/timing as needed
  8. Add CI workflow — If requested, read references/ci-integration.md and generate workflow from assets/e2e-ci-workflow.yml
  9. Validate — All tests pass, use ARIA selectors, have assertions, no hardcoded waits

Inputs To Request

  • Current repository path and project type (SPA vs AEM extension)
  • Which pages or user flows need E2E coverage
  • Whether tests should run against local dev or deployed environment
  • Whether CI integration is needed
Show full SKILL.md (301 more words)Show less

Deliverables

  • playwright.config.ts configured for the project
  • E2E test files in e2e/ directory
  • GitHub Actions workflow (if CI requested)
  • Passing test run output

Quality Bar

  • All tests use ARIA selectors (getByRole, getByLabel) — no CSS class selectors
  • Iframe navigation uses frameLocator() — no frame() with index
  • All tests have await expect() assertions — no assertion-free tests
  • Action responses are stubbed with page.route() for deterministic results
  • No hardcoded page.waitForTimeout() — use waitForSelector, waitForResponse, or Playwright auto-waiting
  • Tests run in < 60s on local machine

References

  • Use references/e2e-testing-patterns.md for Playwright E2E patterns for ExC Shell SPAs (iframe nav, Spectrum selectors, auth, action stubbing).
  • Use references/aem-extension-testing.md for AEM extension testing patterns (Extension Tester, nested iframes, modal lifecycle, extension points).
  • Use references/ci-integration.md for running Playwright in GitHub Actions (browser install, artifact upload, headless config).
  • Use assets/playwright.config.ts as the base Playwright configuration template.
  • Use assets/e2e-ci-workflow.yml as the GitHub Actions workflow template for E2E tests.

Common Issues

  • Iframe not found: The ExC Shell iframe selector varies — use DevTools to inspect. Try page.frameLocator('iframe[src*="your-app"]') or discover with page.frames().
  • Shell spinner never dismissed: Ensure runtime.done() is called in the SPA. For E2E, wait for content inside the iframe rather than the shell itself.
  • Spectrum component not clickable: React Spectrum components render ARIA roles — use getByRole() instead of CSS selectors. Check references/e2e-testing-patterns.md § Spectrum Selectors.
  • Auth popup blocks test: Test against local dev (aio app dev) which skips shell auth. See auth section in references/e2e-testing-patterns.md.
  • AEM extension not loading: Extension Tester requires IMS login. Use generous timeouts (10s+) for extension load. Check references/aem-extension-testing.md § Common Gotchas.
  • Tests flaky in CI: Add retries (retries: 1), use waitForResponse() for action calls, and check references/ci-integration.md for headless configuration.

Chaining

  • Chains FROM appbuilder-ui-scaffolder (after UI components are generated, add E2E tests)
  • Chains FROM appbuilder-testing (when user wants browser-level validation beyond Jest unit tests)
  • Chains TO appbuilder-cicd-pipeline (add E2E test job to CI/CD pipeline)

© NeverSight, Apache-2.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 12 other files in data/skills-md/adobe/skills/appbuilder-e2e-testing of NeverSight/learn-skills.dev.

  • SKILL.md
  • description_ar.txt
  • description_cn.txt
  • description_de.txt
  • description_en.txt
  • description_es.txt
  • description_fr.txt
  • description_it.txt
  • description_ja.txt
  • description_ko.txt
  • description_ru.txt
  • description_tw.txt
  • stats.json

Open the folder on GitHubat commit 08f9d22

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in NeverSight/learn-skills.dev, which our catalogue first saw on October 7, 2026.

Compare with similar skills

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

Appbuilder E2E Testing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Appbuilder E2E Testing this skillNeverSight/learn-skills.dev2161 repos~1.8kAutomated safety check: PassApache-2.0
Playwright Testingchongdashu/vibejam-starter-pack149—~2.1kAutomated safety check: PassNone
Playwright Testingchongdashu/vibejam-starter-pack149—~2.2kAutomated safety check: PassNone
Walkontable Rendering Engine Testinghandsontable/handsontable22k—~875Automated safety check: PassCustom licence
React Testingaffaan-m/ECC274k1 repos~3.3kAutomated safety check: PassMIT
Senior QAalirezarezvani/claude-skills28k1 repos~2.1kAutomated safety check: PassMIT

Similar skills

  • Playwright Testing

    chongdashu/vibejam-starter-pack

    Plan, implement, and debug frontend tests: unit/integration/E2E/visual/a11y.

    149 GitHub stars~2.1k tokensUpdated 5 mo ago
    Testing & QAAuto-check passed

  • Playwright Testing

    chongdashu/vibejam-starter-pack

    Plan, implement, and debug frontend tests: unit/integration/E2E/visual/a11y.

    149 GitHub stars~2.2k tokensUpdated 5 mo ago
    Testing & QAAuto-check passed

  • Walkontable Rendering Engine Testing

    handsontable/handsontable

    Explains how to run and write tests for Handsontable's Walkontable rendering engine, which has its own Jasmine, Puppeteer and Jest pipelines apart from the main E2E tests.

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

  • React Testing

    affaan-m/ECC

    React component testing with React Testing Library, Vitest/Jest, MSW for network mocking, accessibility assertions with axe, and the decision boundary between component tests and Playwright/Cypress…

    274k GitHub starsUsed in 1 repo~3.3k tokens
    Testing & QAAuto-check passed

  • Senior QA

    alirezarezvani/claude-skills

    Generates unit tests, integration tests, and E2E tests for React/Next.js applications.

    28k GitHub starsUsed in 1 repo~2.1k tokens
    Testing & QAAuto-check passed

  • Test Commander

    EliasOulkadi/shokunin

    Generate unit, integration, E2E, and visual regression tests following the Testing Trophy methodology (80% integration).

    114 GitHub stars~3k tokensUpdated 2 days ago
    Testing & QAAuto-check: notes

More from NeverSight/learn-skills.dev

All 43 skills in this repo

  • AI Marketing Videos

    NeverSight/learn-skills.dev

    Create AI marketing videos for ads, promos, product launches, and brand content.

    216 GitHub starsUsed in 3 repos~2.1k tokens
    Auto-check passed

  • Google Calendar

    NeverSight/learn-skills.dev

    Interact with Google Calendar via the Google Calendar API – list upcoming events, create new events, update or delete them.

    216 GitHub starsUsed in 2 repos~826 tokens
    Auto-check passed

  • Agent Orchestrator

    NeverSight/learn-skills.dev

    Meta-agent skill for orchestrating complex tasks through autonomous sub-agents.

    216 GitHub starsUsed in 1 repo~1.4k tokens
    Auto-check passed

  • AI Automation Workflows

    NeverSight/learn-skills.dev

    Build automated AI workflows combining multiple models and services.

    216 GitHub starsUsed in 1 repo~2.6k tokens
    Auto-check passed

  • AI Content Pipeline

    NeverSight/learn-skills.dev

    Build multi-step AI content creation pipelines combining image, video, audio, and text.

    216 GitHub starsUsed in 1 repo~1.8k tokens
    Auto-check passed

  • AI Podcast Creation

    NeverSight/learn-skills.dev

    Create AI-powered podcasts with text-to-speech, music, and audio editing.

    216 GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed

Works with

Categories

Questions about Appbuilder E2E Testing

What does Appbuilder E2E Testing do?

A skill your agent uses whenever the user wants browser-based end-to-end tests for an Adobe App Builder application. dev. Use this skill whenever the user wants browser-based end-to-end tests for an Adobe App Builder application.

When should I use Appbuilder E2E Testing?

Appbuilder E2E Testing fits situations like: the user wants browser-based end-to-end tests for an Adobe App Builder application; the user mentions: E2E test; end-to-end test; test my SPA in the browser.

How do I install Appbuilder E2E Testing in Claude Code?

Run `npx skills add NeverSight/learn-skills.dev --skill appbuilder-e2e-testing -a claude-code`. Or copy the skill folder (data/skills-md/adobe/skills/appbuilder-e2e-testing in NeverSight/learn-skills.dev) into .claude/skills/appbuilder-e2e-testing in your project. Claude Code loads it when a task matches its description.

How do I install Appbuilder E2E Testing in Codex?

Run `npx skills add NeverSight/learn-skills.dev --skill appbuilder-e2e-testing -a codex`. Or copy the skill folder (data/skills-md/adobe/skills/appbuilder-e2e-testing in NeverSight/learn-skills.dev) into .agents/skills/appbuilder-e2e-testing in your project. Codex loads it when a task matches its description.

Can I use Appbuilder 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 NeverSight/learn-skills.dev --skill appbuilder-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/appbuilder-e2e-testing, .gemini/skills/appbuilder-e2e-testing, .github/skills/appbuilder-e2e-testing and .opencode/skills/appbuilder-e2e-testing in your project.

What does Appbuilder E2E Testing need to run?

Going by SKILL.md and its folder, Appbuilder E2E Testing needs the command-line tools its instructions call (npx and npm). Our summary lists: Node.js. Its frontmatter pre-approves these tools: Bash(npx:*), Bash(npm:*), Bash(node:*), Bash(aio:*), Read, Write, Edit. Compatibility (from SKILL.md): Requires Node.js 18+, Playwright.

Does Appbuilder E2E Testing access the network?

SKILL.md contains no URLs. Its commands use npx and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Appbuilder 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 Appbuilder E2E Testing use?

Appbuilder E2E Testing is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Appbuilder E2E Testing use?

About 1.8k tokens (SKILL.md is roughly 7.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 Appbuilder E2E Testing?

Skills that share tags, products or a category with Appbuilder E2E Testing: Playwright Testing (chongdashu/vibejam-starter-pack, 149 stars), Playwright Testing (chongdashu/vibejam-starter-pack, 149 stars), Walkontable Rendering Engine Testing (handsontable/handsontable, 22k stars) and React Testing (affaan-m/ECC, 274k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Appbuilder E2E Testing?

NeverSight (a GitHub organization) maintains it in NeverSight/learn-skills.dev, which has 216 GitHub stars. The repository holds 43 skills in this directory. The repository was last updated on October 6, 2026.

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