Agent skill

Test Production

Runs bin/test-production.ps1 to acceptance-test a production (or prerelease) release of browser4-cli.

Apache-2.0Auto-check passedTesting & QA

Install Test Production

skills CLI

$ npx skills add platonai/Browser4 --skill test-production -a claude-code

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

GitHub CLI

$ gh skill install platonai/Browser4 test-production --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/platonai/Browser4.git skills-src && mkdir -p .claude/skills && cp -r skills-src/coworker/skills/test-production .claude/skills/test-production && 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/

Paste into Claude Code

Install the "test-production" agent skill from https://github.com/platonai/Browser4/tree/main/coworker/skills/test-production into .claude/skills/test-production/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-production", 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

$skill-installer install https://github.com/platonai/Browser4/tree/main/coworker/skills/test-production

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

skills CLI

$ npx skills add platonai/Browser4 --skill test-production -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install platonai/Browser4 test-production --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/platonai/Browser4.git skills-src && mkdir -p .agents/skills && cp -r skills-src/coworker/skills/test-production .agents/skills/test-production && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "test-production" agent skill from https://github.com/platonai/Browser4/tree/main/coworker/skills/test-production into .agents/skills/test-production/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-production", 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.

skills CLI

$ npx skills add platonai/Browser4 --skill test-production -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install platonai/Browser4 test-production --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/platonai/Browser4.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/coworker/skills/test-production .cursor/skills/test-production && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "test-production" agent skill from https://github.com/platonai/Browser4/tree/main/coworker/skills/test-production into .cursor/skills/test-production/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-production", 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

$ gemini skills install https://github.com/platonai/Browser4.git --path coworker/skills/test-production

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add platonai/Browser4 --skill test-production -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install platonai/Browser4 test-production --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/platonai/Browser4.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/coworker/skills/test-production .gemini/skills/test-production && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "test-production" agent skill from https://github.com/platonai/Browser4/tree/main/coworker/skills/test-production into .gemini/skills/test-production/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-production", 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.

GitHub CLI

$ gh skill install platonai/Browser4 test-production

Installs 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).

skills CLI

$ npx skills add platonai/Browser4 --skill test-production -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/platonai/Browser4.git skills-src && mkdir -p .github/skills && cp -r skills-src/coworker/skills/test-production .github/skills/test-production && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "test-production" agent skill from https://github.com/platonai/Browser4/tree/main/coworker/skills/test-production into .github/skills/test-production/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-production", 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.

skills CLI

$ npx skills add platonai/Browser4 --skill test-production -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install platonai/Browser4 test-production --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/platonai/Browser4.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/coworker/skills/test-production .opencode/skills/test-production && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "test-production" agent skill from https://github.com/platonai/Browser4/tree/main/coworker/skills/test-production into .opencode/skills/test-production/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-production", 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: test-production
GitHub stars: 1.2k
Token cost: ~1.3k tokens
SKILL.md length: 480 words
Files: 1
Skills in repo: 17
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Runs bin/test-production.ps1 to acceptance-test a production (or prerelease) release of browser4-cli.

Works in 5 steps: Release status report — queries GitHub… → Pre-clean — removes any existing global… → Cycle 1 — Clean-room install (no… → …
Asked to run production tests
SKILL.md covers When to Use, Safe Default, Options and What It Tests, plus 6 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Test Production is an agent skill from platonai/Browser4. Runs bin/test-production.ps1 to acceptance-test a production (or prerelease) release of browser4-cli. Use when asked to run production tests, acceptance-test a release, or verify the published CLI.

Its SKILL.md is about 1.3k 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. The repository describes itself as: Browser4 — an AI-native browser engine for autonomous agents, intelligent extraction, and large-scale web automation. The licence is Apache-2.0.

When your agent uses it

Asked to run production tests
Acceptance-test a release
Verify the published CLI

Example prompts

“/test-production”

Requirements

Pre-approved tools (allowed-tools): Bash(pwsh:*), Bash(./bin/test-production.ps1:*)

Workflow steps

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

Release status report — queries GitHub Releases, npm registry, Aliyun OSS
Pre-clean — removes any existing global browser4-cli installation.
Cycle 1 — Clean-room install (no pre-existing config)
Cycle 2 — Re-install with config + timing
(With -Stress) Multi-scenarios stress test — runs

What it can do on your machine

Read from SKILL.md and the folder at commit 0fdba82. 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(pwsh:*)
- Bash(./bin/test-production.ps1:*)
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 bash).
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

Test Production loads about 1.3k tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 480 words of instructions outside code blocks.

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

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 platonai/Browser4 at commit 0fdba82, republished under its Apache-2.0 licence (© platonai). 480 words, ~1,276 tokens.

Download SKILL.mdSave it as .claude/skills/test-production/SKILL.md (or your agent's skills folder).

name: test-production
description: Runs bin/test-production.ps1 to acceptance-test a production (or prerelease) release of browser4-cli. Use when asked to run production tests, acceptance-test a release, or verify the published CLI.
allowed-tools: Bash(pwsh:*), Bash(./bin/test-production.ps1:*)
title: Test Production — Acceptance-test the latest published browser4-cli release

Test Production

Runs bin/test-production.ps1 — an acceptance test that simulates a real end user's journey with the published browser4-cli release. It downloads, installs, exercises, uninstalls, and re-installs the global CLI from the public OSS distribution channel.

This is a separate entrypoint from bin/test.ps1 (covered by the run-tests skill). test-production.ps1 tests the released artifact — not the in-repo source — and is designed to be run in CI or locally before tagging a release.

When to Use

"run production tests"
"run the production acceptance test"
"acceptance-test the latest release"
"test the published CLI"
"verify the release before tagging"
"test a prerelease candidate"
"run production acceptance with stress"

Safe Default

Running with no arguments shows help (safe default):

bash

./bin/test-production.ps1

Options

Flag	Description
`-WorkingDir <path>`	Working directory for temporary artifacts (default: random subdir under system temp)
`-Stress`	Enable the multi-scenario stress suite (opt-in)
`-MultiScenariosIterations <n>`	Iterations for the multi-scenario suite (default: 1, only with `-Stress`)
`-RemoveWorkingDir`	Delete the working directory on exit (default: preserved for review)
`-Version <tag>`	Test a specific release version (e.g. `v4.12.0-rc.1`, `v4.11.0`). Default: latest stable
`-Help`	Show help message

What It Tests

Release status report — queries GitHub Releases, npm registry, Aliyun OSS CDN, and custom mirrors to verify all distribution channels are reachable.
Pre-clean — removes any existing global browser4-cli installation.
Cycle 1 — Clean-room install (no pre-existing config):
- Installs the CLI via the remote bootstrap script (unmodified — no patches).
- Verifies the CLI is on PATH after install.
- Smoke-tests: --help, --version, config --help, agent-run --help, invalid command.
- Cold-starts the browser server (open), verifies health endpoint responds.
- Shuts down the server (close-all, kill-all), verifies it's unreachable.
- Uninstalls and verifies runtime data is removed.
Cycle 2 — Re-install with config + timing:
- Copies config (LLM keys, etc.) from the user's real ~/.browser4 into the test sandbox.
- Repeats the install→exercise→uninstall cycle.
- Measures warm-start latency vs cold-start.
(With -Stress) Multi-scenarios stress test — runs browser4-tests/tests-production/multi-scenarios.ps1 against the global CLI.

Show full SKILL.md (168 more words)Show less

Key Principle

The script acts like a real end user — it does not patch install scripts, create missing symlinks, or manually clean up after uninstall. If any of those are needed, the test fails because a real user would hit the same broken behavior.

Isolation

The test uses environment variables (BROWSER4_CLI_STATE_DIR, BROWSER4_RUNTIME_DIR) to route all state and runtime data into an isolated working directory. The user's real ~/.browser4 is never modified — it is only read to copy config into the test sandbox during Cycle 2.

Usage

Examples

bash

# Show help (no arguments = safe default)
./bin/test-production.ps1

# Run the full acceptance test (no stress)
./bin/test-production.ps1

# Run with stress suite
./bin/test-production.ps1 -Stress

# Production CI: stress test with multiple iterations, clean up afterward
./bin/test-production.ps1 -Stress -MultiScenariosIterations 3 -RemoveWorkingDir

# Test a specific prerelease candidate
./bin/test-production.ps1 -Version v4.12.0-rc.1 -Stress

# Test a specific stable release
./bin/test-production.ps1 -Version v4.11.0

# Use a specific working directory (kept for review by default)
./bin/test-production.ps1 -WorkingDir /tmp/my-acceptance-test

Typical CI invocation

bash

# Full acceptance gate for a release
./bin/test-production.ps1 -Stress -MultiScenariosIterations 3 -RemoveWorkingDir

Exit Codes

Code	Meaning
0	All steps passed
1	One or more steps failed

Working Directory

By default, a random subdirectory is created under the system temp directory (e.g. /tmp/.browser4-acceptance/20260720-143052-a3f2). The directory is preserved after the test for review unless -RemoveWorkingDir is passed.

Relationship to Other Skills

run-tests — covers bin/test.ps1 for in-repo unit, integration, E2E, CLI, and PowerShell tests. Use that skill for development-time testing.
test-production (this skill) — covers bin/test-production.ps1 for release-time acceptance testing of the published artifact.

Files

Just SKILL.md in coworker/skills/test-production of platonai/Browser4.

Open the folder on GitHubat commit 0fdba82

Compare with similar skills

Test Production 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.

Test Production compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Test Production this skillplatonai/Browser4	1.2k	—	~1.3k	Automated safety check: Pass	Apache-2.0	yesterday
Web Application Testinganthropics/skills	180k	51 repos	~966	Automated safety check: Pass	Apache-2.0	today
TDD WorkflowhellangleZ/burn-in-cceverywhere-ralph	112	11 repos	~2.4k	Automated safety check: Pass	None	8 mo ago
Uloop Replay Inputkurotu/VRCQuestTools	373	3 repos	~615	Automated safety check: Pass	MIT	8 days ago
Ui4 Convert Testspayloadcms/payload	45k	—	~3.5k	Automated safety check: Pass	MIT	today
E2Estackia/rtp2httpd	2.2k	—	~517	Automated safety check: Pass	GPL-2.0	6 days ago

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
TDD Workflow
hellangleZ/burn-in-cceverywhere-ralph
A skill your agent uses when writing new features, fixing bugs, or refactoring code.
112 GitHub starsUsed in 11 repos~2.4k tokens
Testing & QAAuto-check passed
Uloop Replay Input
kurotu/VRCQuestTools
Replay recorded PlayMode keyboard and mouse input. An agent skill from kurotu/VRCQuestTools.
373 GitHub starsUsed in 3 repos~615 tokens
Testing & QAAuto-check passed
Ui4 Convert Tests
payloadcms/payload
A skill your agent uses when UI changes are complete and e2e tests need updating.
45k GitHub stars~3.5k tokensUpdated today
Testing & QAAuto-check passed
E2E
stackia/rtp2httpd
Write, run, review, or debug rtp2httpd E2E tests and their harness in e2e/ and scripts/run-e2e.sh.
2.2k GitHub stars~517 tokensUpdated 6 days ago
Testing & QAAuto-check passed
Moav E2E
MotherofallVPNs/MoaV
Run and debug MoaV's end-to-end tests — real protocol connectivity (client-test.sh) and the moav CLI smoke test — against a LIVE server, via the self-hosted e2e workflow or a local test VPS.
448 GitHub stars~1.9k tokensUpdated yesterday
Testing & QAAuto-check: notes

Questions about Test Production

What does Test Production do?

Runs bin/test-production.ps1 to acceptance-test a production (or prerelease) release of browser4-cli. Test Production is an agent skill from platonai/Browser4.ps1 to acceptance-test a production (or prerelease) release of browser4-cli.

When should I use Test Production?

Test Production fits situations like: asked to run production tests; acceptance-test a release; verify the published CLI.

How do I install Test Production in Claude Code?

Run `npx skills add platonai/Browser4 --skill test-production -a claude-code`. Or copy the skill folder (coworker/skills/test-production in platonai/Browser4) into .claude/skills/test-production in your project. Claude Code loads it when a task matches its description.

How do I install Test Production in Codex?

Run `npx skills add platonai/Browser4 --skill test-production -a codex`. Or copy the skill folder (coworker/skills/test-production in platonai/Browser4) into .agents/skills/test-production in your project. Codex loads it when a task matches its description.

Can I use Test Production 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 platonai/Browser4 --skill test-production -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/test-production, .gemini/skills/test-production, .github/skills/test-production and .opencode/skills/test-production in your project.

What does Test Production need to run?

SKILL.md names no scripts, command-line tools or credentials: Test Production is instructions for the agent only. Its frontmatter pre-approves these tools: Bash(pwsh:*), Bash(./bin/test-production.ps1:*).

Does Test Production 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 Test Production 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 Test Production use?

Test Production is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Test Production 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 Test Production?

Skills that share tags, products or a category with Test Production: Web Application Testing (anthropics/skills, 180k stars), TDD Workflow (hellangleZ/burn-in-cceverywhere-ralph, 112 stars), Uloop Replay Input (kurotu/VRCQuestTools, 373 stars) and Ui4 Convert Tests (payloadcms/payload, 45k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Test Production?

platonai (a GitHub user) maintains it in platonai/Browser4, which has 1,152 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 7, 2026.

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

Install Test Production

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Test Production

When to Use

Safe Default

Options

What It Tests

Key Principle

Isolation

Usage

Examples

Typical CI invocation

Exit Codes

Working Directory

Relationship to Other Skills

Files

Compare with similar skills

Similar skills

More from platonai/Browser4

Related

Questions about Test Production