菜单
Run headless browser smoke and E2E tests for scaffolded web services. Use when verifying rendered web UI, checking browser errors, creating Playwright-style scenarios, collecting screenshots, or testing a deployed/local service through Chromium.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | headless-browser-test |
| description | Run headless browser smoke and E2E tests for scaffolded web services. Use when verifying rendered web UI, checking browser errors, creating Playwright-style scenarios, collecting screenshots, or testing a deployed/local service through Chromium. |
Use scripts first. This skill is for the NDX agent running inside its Docker runtime to test a project created or managed by NDX. Keep prompts short; let the checked scripts enforce browser setup, URL handling, artifacts, trace capture, and report shape.
sh .ndx/skills/headless-browser-test/scripts/check-headless-browser-env.sh
node .ndx/skills/headless-browser-test/scripts/run-headless-browser-test.mjs --url <url>
curl -fsS <url> >/dev/null
--spec.sh .ndx/skills/headless-browser-test/scripts/write-playwright-e2e-template.sh test/e2e
references/environment.md: package/runtime checks, missing Chromium or Playwright handling, local vs container URL rules.references/scenario-authoring.md: scenario JSON format, stable locator contract, and fill-in templates for common tests.references/operation.md: deployed service testing, artifact paths, failure triage, and final-answer requirements.playwright install, change package dependencies, or edit yarn.lock until check-headless-browser-env.sh proves the runtime is missing.runtime: ndx-container. If it is running on the Codex host, use the .codex headless-browser-test skill instead.runtime: ndx-container is an agent image problem, not a generated-project dependency problem.localhost rewriting change the security model of the page. If browser APIs such as crypto.randomUUID require a secure local origin, use --preserve-localhost.test/YYYYMMDD/<HHMMSS>_headless-browser-test/.Explicit-only Docker deploy. Run this skill's bundled scripts/deploy.sh directly; do not search for skills, inspect trees, or use subagents.
Explicit-only Docker deploy. Run this skill's bundled scripts/deploy.sh directly; do not search for skills, inspect trees, or use subagents.
Use only when explicitly invoked as $web-service-scaffold to run the bundled web-service scaffold script.
Use when a goal should be split across multiple queued session turns with reflection turns between work turns.
Enforce the repository package documentation contract as a navigable dependency graph. Use when creating or updating package README, docs pages, navigation tables, architecture router, API docs, usage docs, constraints, blast-radius/consumer records, internals, decisions, or testing docs. Docs exist so a later model drills down from task to edit target with minimal context and sees blast radius before editing. Keep content terse; keep only repo-specific contracts, paths, edges, intent, and decisions.
Enforce the repository Docker contract: Docker-first runtime, one root docker-compose.yml, module-owned Docker assets, apps service-module to container mapping, isolated networking, Docker socket passthrough for container-spawning services, a standard npm deploy entrypoint, and runtime-only Dockerfiles that copy prebuilt local dist artifacts instead of building the project. Use when defining compose services, Dockerfiles, networks, volumes, env_file wiring, deploy scripts, Docker socket access, or container ownership.