Actualize
NeoLabHQ/context-engineering-kit
Reconcile the project's FPF state with recent repository changes
A skill your agent uses to actually verify a web change in a real browser instead of assuming it works — click through a flow, catch console errors, check a form submits, confirm a fix on the page.
$ npx skills add OneWave-AI/claude-skills --skill browser-test-loop -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install OneWave-AI/claude-skills browser-test-loop --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/OneWave-AI/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/browser-test-loop .claude/skills/browser-test-loop && 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 "browser-test-loop" agent skill from https://github.com/OneWave-AI/claude-skills/tree/main/browser-test-loop into .claude/skills/browser-test-loop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-test-loop", 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/OneWave-AI/claude-skills/tree/main/browser-test-loopType 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 OneWave-AI/claude-skills --skill browser-test-loop -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install OneWave-AI/claude-skills browser-test-loop --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OneWave-AI/claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/browser-test-loop .agents/skills/browser-test-loop && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "browser-test-loop" agent skill from https://github.com/OneWave-AI/claude-skills/tree/main/browser-test-loop into .agents/skills/browser-test-loop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-test-loop", 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 OneWave-AI/claude-skills --skill browser-test-loop -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install OneWave-AI/claude-skills browser-test-loop --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OneWave-AI/claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/browser-test-loop .cursor/skills/browser-test-loop && 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 "browser-test-loop" agent skill from https://github.com/OneWave-AI/claude-skills/tree/main/browser-test-loop into .cursor/skills/browser-test-loop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-test-loop", 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/OneWave-AI/claude-skills.git --path browser-test-loop--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 OneWave-AI/claude-skills --skill browser-test-loop -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install OneWave-AI/claude-skills browser-test-loop --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OneWave-AI/claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/browser-test-loop .gemini/skills/browser-test-loop && 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 "browser-test-loop" agent skill from https://github.com/OneWave-AI/claude-skills/tree/main/browser-test-loop into .gemini/skills/browser-test-loop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-test-loop", 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 OneWave-AI/claude-skills browser-test-loopInstalls 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 OneWave-AI/claude-skills --skill browser-test-loop -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/OneWave-AI/claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/browser-test-loop .github/skills/browser-test-loop && 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 "browser-test-loop" agent skill from https://github.com/OneWave-AI/claude-skills/tree/main/browser-test-loop into .github/skills/browser-test-loop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-test-loop", 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 OneWave-AI/claude-skills --skill browser-test-loop -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install OneWave-AI/claude-skills browser-test-loop --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OneWave-AI/claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/browser-test-loop .opencode/skills/browser-test-loop && 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 "browser-test-loop" agent skill from https://github.com/OneWave-AI/claude-skills/tree/main/browser-test-loop into .opencode/skills/browser-test-loop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-test-loop", 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.
browser-test-loopA skill your agent uses to actually verify a web change in a real browser instead of assuming it works — click through a flow, catch console errors, check a form submits, confirm a fix on the page.
Browser Test Loop is an agent skill from OneWave-AI/claude-skills. Use to actually verify a web change in a real browser instead of assuming it works — click through a flow, catch console errors, check a form submits, confirm a fix on the page. Trigger when a UI change needs proof, a bug only reproduces in the browser, or the user asks to test, check, or screenshot the running app.
Its SKILL.md is about 900 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: 200+ production-ready Claude Code skills for sales, marketing, design, engineering, and AI agent architecture. Built and maintained by OneWave AI. The licence is MIT.
5 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit fc5b785. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
npxnpmFrom the folder's file list and the shell code blocks in SKILL.md.
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.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Browser Test Loop loads about 897 tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 445 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.
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.
The full file from OneWave-AI/claude-skills at commit fc5b785, republished under its MIT licence (© OneWave-AI). 445 words, ~897 tokens.
.claude/skills/browser-test-loop/SKILL.md (or your agent's skills folder).Code that compiles is not code that works. This is the loop that closes the gap between "the diff looks right" and "the page does the thing".
Drive a real browser against the running app, assert on what actually rendered, and fix what fails. Never report a UI change as working on the strength of the diff alone.
Playwright is the default. It installs its own browsers and runs headless in CI.
npm i -D @playwright/test && npx playwright install chromiumStart the app first and hold the port — a test suite against a dead server produces a wall of timeouts that tells you nothing:
npm run dev > /tmp/dev.log 2>&1 &
npx wait-on http://localhost:3000const errors = []
page.on('console', m => m.type() === 'error' && errors.push(m.text()))
page.on('pageerror', e => errors.push(e.message))
// ... drive the flow ...
expect(errors).toEqual([])Query the way a person looks at a page: role, label, and visible text. getByRole('button', { name: 'Send' }) survives a restyle; .btn-primary > span:nth-child(2) does not. Add data-testid only where the visible text is genuinely ambiguous.
Take one on failure automatically, and one at the end of a flow when a human needs to eyeball the result. Full-page for layout questions, element-scoped for a component. Save under /tmp unless the user wants them kept.
npx playwright test --reporter=line 2>&1 | tail -30Pipe the output. A full Playwright HTML reporter dump is thousands of tokens of nothing.
| Symptom | Real cause |
|---|---|
| Every test times out | App never started, or wrong port |
| Passes locally, fails headless | Animation or viewport size, not logic |
| Flaky on CI only | Waiting on a timeout instead of a condition |
| Blank page, no error | Client-side exception swallowed by an error boundary |
| Works once, fails on re-run | Test wrote state it never cleaned up |
Never fix flake with waitForTimeout. Wait for the condition — a selector, a response, a URL.
Say what flow was driven, what was asserted, and the result. If something is still unverified, name it. Screenshots go with the answer when the question was visual.
© OneWave-AI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in browser-test-loop of OneWave-AI/claude-skills.
Open the folder on GitHubat commit fc5b785
Browser Test Loop 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 |
|---|---|---|---|---|---|---|
| Browser Test Loop this skillOneWave-AI/claude-skills | 323 | — | ~897 | Automated safety check: Pass | MIT | |
| ActualizeNeoLabHQ/context-engineering-kit | 1.7k | — | ~932 | Automated safety check: Pass | GPL-3.0 | |
| Is This Actually Goodmohitagw15856/pm-claude-skills | 1.4k | — | ~884 | Automated safety check: Pass | MIT | |
| Actual Budgetsundial-org/awesome-openclaw-skills | 663 | — | ~1.6k | Automated safety check: Pass | None | |
| Budget Cash Flowsickn33/agentic-awesome-skills | 47k | 1 repos | ~4.1k | Automated safety check: Pass | MIT | |
| Skill Compliance Checkeraffaan-m/ECC | 275k | 1 repos | ~623 | Automated safety check: Pass | MIT |
NeoLabHQ/context-engineering-kit
Reconcile the project's FPF state with recent repository changes
mohitagw15856/pm-claude-skills
Get an honest verdict on whether something you made is actually good — not the reflexive 'this is great!' but a real, criteria-based judgment.
sundial-org/awesome-openclaw-skills
Query and manage personal finances via the official Actual Budget Node.js API.
sickn33/agentic-awesome-skills
Budget against actual by department, category and period, with budget and actual amounts, variance, percentage used and linked expenses.
affaan-m/ECC
Measures whether agents actually follow a skill, rule or agent definition by generating scenarios at three strictness levels and scoring tool-call traces.
mvanhorn/last30days-skill
Research what people actually say about any topic in the last 30 days.
OneWave-AI/claude-skills
Finds duplicate and junk records in a CRM CSV export with fuzzy matching, normalizes fields and writes a reviewable merge plan plus import-ready files without touching the live CRM.
OneWave-AI/claude-skills
Repairs broken decks and PDFs exported from Claude Design or similar AI deck generators: clipped text, wrong fonts and corrupted .pptx package structure.
OneWave-AI/claude-skills
Writes, explains, debugs, and optimizes BI calculations - Power BI / Fabric DAX measures and calculated columns, Tableau calculated fields (FIXED/INCLUDE/EXCLUDE LOD expressions, table…
OneWave-AI/claude-skills
Categorizes transactions, reconciles bank and card statements to the ledger, works a month-end checklist and prepares a close package, without ever forcing a balance.
OneWave-AI/claude-skills
Combines CSV, TSV and Excel files into one verified table with pandas, by stacking or joining, mapping columns, normalizing keys and removing duplicates.
OneWave-AI/claude-skills
Pulls financial statement numbers for US public companies straight from SEC EDGAR's free official XBRL APIs (companyfacts, companyconcept, frames, submissions) into a cited table.
A skill your agent uses to actually verify a web change in a real browser instead of assuming it works — click through a flow, catch console errors, check a form submits, confirm a fix on the page. Browser Test Loop is an agent skill from OneWave-AI/claude-skills. Use to actually verify a web change in a real browser instead of assuming it works — click through a flow, catch console errors, check a form submits, confirm a fix on the page.
Browser Test Loop fits situations like: actually verify a web change in a real browser instead of assuming it works — click through a flow; catch console errors; check a form submits; confirm a fix on the page.
Run `npx skills add OneWave-AI/claude-skills --skill browser-test-loop -a claude-code`. Or copy the skill folder (browser-test-loop in OneWave-AI/claude-skills) into .claude/skills/browser-test-loop in your project. Claude Code loads it when a task matches its description.
Run `npx skills add OneWave-AI/claude-skills --skill browser-test-loop -a codex`. Or copy the skill folder (browser-test-loop in OneWave-AI/claude-skills) into .agents/skills/browser-test-loop in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add OneWave-AI/claude-skills --skill browser-test-loop -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/browser-test-loop, .gemini/skills/browser-test-loop, .github/skills/browser-test-loop and .opencode/skills/browser-test-loop in your project.
Going by SKILL.md and its folder, Browser Test Loop needs the command-line tools its instructions call (npx and npm). Our summary lists: Node.js.
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.
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.
Browser Test Loop is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 897 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Browser Test Loop: Actualize (NeoLabHQ/context-engineering-kit, 1.7k stars), Is This Actually Good (mohitagw15856/pm-claude-skills, 1.4k stars), Actual Budget (sundial-org/awesome-openclaw-skills, 663 stars) and Budget Cash Flow (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
OneWave-AI (a GitHub organization) maintains it in OneWave-AI/claude-skills, which has 323 GitHub stars. The repository holds 70 skills in this directory. The repository was last updated on October 2, 2026.
Source: OneWave-AI/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.