Control UI E2E
openclaw/openclaw
A skill your agent uses when designing, testing, fixing, or extending the OpenClaw Control UI GUI, including UI stress-test galleries with feedback inputs, Vitest + Playwright end-to-end checks…
A skill your agent uses when adding or updating BuildReactor Vitest or Playwright tests, especially extension page, service-worker, options, popup, dashboard, or CI-service coverage.
Install Testing
$ npx skills add AdamNowotny/BuildReactor --skill testing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install AdamNowotny/BuildReactor testing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/AdamNowotny/BuildReactor.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/testing .claude/skills/testing && rm -rf skills-srcUse ~/.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/
Install the "testing" agent skill from https://github.com/AdamNowotny/BuildReactor/tree/main/.agents/skills/testing into .claude/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing", 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 install https://github.com/AdamNowotny/BuildReactor/tree/main/.agents/skills/testingType 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.
$ npx skills add AdamNowotny/BuildReactor --skill testing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install AdamNowotny/BuildReactor testing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AdamNowotny/BuildReactor.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/testing .agents/skills/testing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "testing" agent skill from https://github.com/AdamNowotny/BuildReactor/tree/main/.agents/skills/testing into .agents/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing", 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.
$ npx skills add AdamNowotny/BuildReactor --skill testing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install AdamNowotny/BuildReactor testing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AdamNowotny/BuildReactor.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/testing .cursor/skills/testing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "testing" agent skill from https://github.com/AdamNowotny/BuildReactor/tree/main/.agents/skills/testing into .cursor/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing", 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 https://github.com/AdamNowotny/BuildReactor.git --path .agents/skills/testing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add AdamNowotny/BuildReactor --skill testing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install AdamNowotny/BuildReactor testing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AdamNowotny/BuildReactor.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/testing .gemini/skills/testing && rm -rf skills-srcUse ~/.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/
Install the "testing" agent skill from https://github.com/AdamNowotny/BuildReactor/tree/main/.agents/skills/testing into .gemini/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing", 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.
$ gh skill install AdamNowotny/BuildReactor testingInstalls 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).
$ npx skills add AdamNowotny/BuildReactor --skill testing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/AdamNowotny/BuildReactor.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/testing .github/skills/testing && rm -rf skills-srcUse ~/.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/
Install the "testing" agent skill from https://github.com/AdamNowotny/BuildReactor/tree/main/.agents/skills/testing into .github/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing", 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.
$ npx skills add AdamNowotny/BuildReactor --skill testing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install AdamNowotny/BuildReactor testing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AdamNowotny/BuildReactor.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/testing .opencode/skills/testing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "testing" agent skill from https://github.com/AdamNowotny/BuildReactor/tree/main/.agents/skills/testing into .opencode/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing", 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
testing- GitHub stars
- 138
- Token cost
- ~1.3k tokens
- SKILL.md length
- 666 words
- Files
- 1
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
A skill your agent uses when adding or updating BuildReactor Vitest or Playwright tests, especially extension page, service-worker, options, popup, dashboard, or CI-service coverage.
- Updating BuildReactor Vitest
- SKILL.md covers Choose The Layer, Structure, Extension Constraints and What To Test, plus 3 more sections
- Calls npx, npm and git
- Playwright tests
What it does
Testing is an agent skill from AdamNowotny/BuildReactor. Use when adding or updating BuildReactor Vitest or Playwright tests, especially extension page, service-worker, options, popup, dashboard, or CI-service coverage.
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 Unit testing and Browser testing. It works with Playwright and Vitest. The repository describes itself as: Developer notifications and dashboard (Google Chrome extension).
When your agent uses it
- Updating BuildReactor Vitest
- Playwright tests
- Especially extension page
- CI-service coverage
Example prompts
- “/testing”
Requirements
- Node.js
What it can do on your machine
Read from SKILL.md and the folder at commit 5ccb151. 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
Shell commands in SKILL.md call:
npxnpmgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npx, npm and git, 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.
Context cost
Testing loads about 1.3k tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 666 words of instructions outside code blocks.
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 666 words (~1,346 tokens).
“Use the smallest layer that proves the behavior:”
- name
- testing
Files
Just SKILL.md in .agents/skills/testing of AdamNowotny/BuildReactor.
Open the folder on GitHubat commit 5ccb151
Compare with similar skills
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Testing this skillAdamNowotny/BuildReactor | 138 | — | ~1.3k | Automated safety check: Pass | Custom licence | |
| Control UI E2Eopenclaw/openclaw | 392k | — | ~2.9k | Automated safety check: Pass | MIT | |
| Ckeditor5 TestingTriliumNext/Trilium | 38k | — | ~3.3k | Automated safety check: Pass | AGPL-3.0 | |
| Check Visual Changesigrlk/storybook-addon-test-codegen | 154 | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Svelte Testingspences10/sveltest | 113 | — | ~579 | Automated safety check: Pass | MIT | |
| Playwright Testingchongdashu/vibejam-starter-pack | 149 | — | ~2.1k | Automated safety check: Pass | None |
Similar skills
Ckeditor5 Testing
TriliumNext/Trilium
Testing CKEditor 5 plugins in the Trilium monorepo. An agent skill from TriliumNext/Trilium.
Check Visual Changes
igrlk/storybook-addon-test-codegen
Check the visual impact of an edit mid-task with uiverify check — render just the components you're touching on the UI Verify fleet and diff them against the real CI baseline, without opening a PR…
Svelte Testing
spences10/sveltest
Fix and create Svelte 5 tests with vitest-browser-svelte and Playwright.
Playwright Testing
chongdashu/vibejam-starter-pack
Plan, implement, and debug frontend tests: unit/integration/E2E/visual/a11y.
Ha Frontend Testing
home-assistant/frontend
Home Assistant frontend testing and validation workflow. An agent skill from home-assistant/frontend.
More from AdamNowotny/BuildReactor
CI Services
AdamNowotny/BuildReactor
A skill your agent uses when adding or updating BuildReactor CI service adapters, response parsing, provider fields, service fixtures, or service-specific tests.
Releases
AdamNowotny/BuildReactor
A skill your agent uses when preparing, reviewing, or publishing a BuildReactor versioned GitHub release and extension artifacts.
Related
Works with
Categories
Questions about Testing
What does Testing do?
A skill your agent uses when adding or updating BuildReactor Vitest or Playwright tests, especially extension page, service-worker, options, popup, dashboard, or CI-service coverage. Testing is an agent skill from AdamNowotny/BuildReactor. Use when adding or updating BuildReactor Vitest or Playwright tests, especially extension page, service-worker, options, popup, dashboard, or CI-service coverage.
When should I use Testing?
Testing fits situations like: updating BuildReactor Vitest; playwright tests; especially extension page; CI-service coverage.
How do I install Testing in Claude Code?
Run `npx skills add AdamNowotny/BuildReactor --skill testing -a claude-code`. Or copy the skill folder (.agents/skills/testing in AdamNowotny/BuildReactor) into .claude/skills/testing in your project. Claude Code loads it when a task matches its description.
How do I install Testing in Codex?
Run `npx skills add AdamNowotny/BuildReactor --skill testing -a codex`. Or copy the skill folder (.agents/skills/testing in AdamNowotny/BuildReactor) into .agents/skills/testing in your project. Codex loads it when a task matches its description.
Can I use 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 AdamNowotny/BuildReactor --skill 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/testing, .gemini/skills/testing, .github/skills/testing and .opencode/skills/testing in your project.
What does Testing need to run?
Going by SKILL.md and its folder, Testing needs the command-line tools its instructions call (npx, npm and git). Our summary lists: Node.js.
Does Testing access the network?
SKILL.md contains no URLs. Its commands use npx, npm and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is 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 Testing use?
Testing 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 Testing use?
About 1.3k tokens (SKILL.md is roughly 5.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 Testing?
Skills that share tags, products or a category with Testing: Control UI E2E (openclaw/openclaw, 392k stars), Ckeditor5 Testing (TriliumNext/Trilium, 38k stars), Check Visual Changes (igrlk/storybook-addon-test-codegen, 154 stars) and Svelte Testing (spences10/sveltest, 113 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Testing?
AdamNowotny (a GitHub user) maintains it in AdamNowotny/BuildReactor, which has 138 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on August 12, 2026.
Source: AdamNowotny/BuildReactor on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.