Test Electron App
PostHog/code
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser.
Attaches OpenCode browser tools to the OpenWork Electron dev app through CDP to explore its UI, send a composer task and debug, not to give test verdicts.
Install OpenWork Electron Browser Automation
$ npx skills add different-ai/openwork --skill browser-automation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install different-ai/openwork browser-automation --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/different-ai/openwork.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.opencode/skills/browser-automation .claude/skills/browser-automation && 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-automation" agent skill from https://github.com/different-ai/openwork/tree/dev/.opencode/skills/browser-automation into .claude/skills/browser-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-automation", 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/different-ai/openwork/tree/dev/.opencode/skills/browser-automationType 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 different-ai/openwork --skill browser-automation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install different-ai/openwork browser-automation --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/different-ai/openwork.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.opencode/skills/browser-automation .agents/skills/browser-automation && 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-automation" agent skill from https://github.com/different-ai/openwork/tree/dev/.opencode/skills/browser-automation into .agents/skills/browser-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-automation", 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 different-ai/openwork --skill browser-automation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install different-ai/openwork browser-automation --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/different-ai/openwork.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.opencode/skills/browser-automation .cursor/skills/browser-automation && 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-automation" agent skill from https://github.com/different-ai/openwork/tree/dev/.opencode/skills/browser-automation into .cursor/skills/browser-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-automation", 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/different-ai/openwork.git --path .opencode/skills/browser-automation--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 different-ai/openwork --skill browser-automation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install different-ai/openwork browser-automation --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/different-ai/openwork.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.opencode/skills/browser-automation .gemini/skills/browser-automation && 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-automation" agent skill from https://github.com/different-ai/openwork/tree/dev/.opencode/skills/browser-automation into .gemini/skills/browser-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-automation", 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 different-ai/openwork browser-automationInstalls 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 different-ai/openwork --skill browser-automation -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/different-ai/openwork.git skills-src && mkdir -p .github/skills && cp -r skills-src/.opencode/skills/browser-automation .github/skills/browser-automation && 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-automation" agent skill from https://github.com/different-ai/openwork/tree/dev/.opencode/skills/browser-automation into .github/skills/browser-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-automation", 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 different-ai/openwork --skill browser-automation -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install different-ai/openwork browser-automation --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/different-ai/openwork.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.opencode/skills/browser-automation .opencode/skills/browser-automation && 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-automation" agent skill from https://github.com/different-ai/openwork/tree/dev/.opencode/skills/browser-automation into .opencode/skills/browser-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-automation", 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
browser-automation- GitHub stars
- 24k
- Token cost
- ~780 tokens
- SKILL.md length
- 243 words
- Files
- 1
- Skills in repo
- 33
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Attaches OpenCode browser tools to the OpenWork Electron dev app through CDP to explore its UI, send a composer task and debug, not to give test verdicts.
- Works in 6 steps: List targets with browser_list using… → Select the OpenWork target ID. → Read state with browser_eval or… → …
- Driving the local OpenWork Electron dev app through CDP
- SKILL.md covers What I Do, Local Dev Setup, Background Launch and Browser Tool Flow, plus 2 more sections
- Calls pnpm
What it does
This skill is for exploration and debugging of the OpenWork Electron app during local development. For pass or fail verdicts it points to writing or running an evals/specs test instead. Running pnpm dev enables the Electron CDP endpoint by default on port 9823, which an environment variable can change or turn off, and the app UI normally loads on localhost port 5173.
The browser tool flow is: list targets with browser_list against the local CDP URL, select the OpenWork target, read state with browser_eval or browser_snapshot, fill the Lexical composer, click Run task and confirm the response from the page text or URL. A background launch with nohup and a port check with lsof are shown, along with a known-good smoke prompt and its expected reply. User browser tasks should use the built-in OpenWork Browser target, not this development tooling.
When your agent uses it
- Driving the local OpenWork Electron dev app through CDP
- Sending a task from the composer and confirming the response in the UI
- Running a quick local UI smoke test while developing
Example prompts
- “Start pnpm dev in the background and attach the browser tools to the OpenWork target.”
- “Send the smoke prompt from the composer and confirm the reply appears.”
- “Switch the Electron debug port to 9830 for this run and list the browser targets.”
Requirements
- pnpm and a local OpenWork checkout
- OpenCode browser tools
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- List targets with browser_list using browser_url: "http://127.0.0.1:9823".
- Select the OpenWork target ID.
- Read state with browser_eval or browser_snapshot.
- Fill the Lexical composer by targeting contenteditable="true".
- Click the Run task button.
- Confirm the session response by checking document.body.innerText or the current URL.
What it can do on your machine
Read from SKILL.md and the folder at commit 4ccc9e9. 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:
pnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm, 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
OpenWork Electron Browser Automation loads about 780 tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 243 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 243 words (~780 tokens).
“For verdicts, do not drive CDP by hand — write or run an evals/specs test (write-a-spec, run-tests). This skill is for exploration and debugging only.”
- name
- browser-automation
Files
Just SKILL.md in .opencode/skills/browser-automation of different-ai/openwork.
Open the folder on GitHubat commit 4ccc9e9
Compare with similar skills
OpenWork Electron Browser Automation 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 |
|---|---|---|---|---|---|---|
| OpenWork Electron Browser Automation this skilldifferent-ai/openwork | 24k | — | ~780 | Automated safety check: Pass | Custom licence | |
| Test Electron AppPostHog/code | 179 | — | ~2.9k | Automated safety check: Pass | MIT | |
| Test Electron AppPostHog/posthog | 40k | — | ~3k | Automated safety check: Pass | Custom licence | |
| Electron App Automationvercel-labs/agent-browser | 44k | 5 repos | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Electron Devtools Testingankitvgupta/exo | 496 | — | ~2.4k | Automated safety check: Pass | Custom licence | |
| Interactive TestingPorabuild/Poracode | 115 | — | ~4.5k | Automated safety check: Notes | Apache-2.0 |
Similar skills
- Official
- Official
Test Electron App
PostHog/posthog
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser.
- Official
Electron App Automation
vercel-labs/agent-browser
Automates Electron desktop apps such as VS Code, Slack or Discord by connecting agent-browser to their Chrome DevTools Protocol port.
Electron Devtools Testing
ankitvgupta/exo
Test the Electron app interactively using Chrome DevTools Protocol.
Interactive Testing
Porabuild/Poracode
Run repeatable integration and smoke testing against the real Poracode Electron app through Chrome DevTools Protocol.
Tracecat QA
TracecatHQ/tracecat
QA Tracecat product features in a real local cluster. An agent skill from TracecatHQ/tracecat.
More from different-ai/openwork
All 33 skills in this repoOpenWork Desktop CDP Driver
different-ai/openwork
Drives a running OpenWork desktop window over CDP from the shell to evaluate JS, take screenshots, start sessions and send prompts for hand checks.
Fake Model Provider Faults
different-ai/openwork
Makes the desktop app's model provider fail on demand, with refused connections, resets, stalls and HTTP 4xx and 5xx errors, so error and retry states can be reproduced.
OpenWork Model Alias Manager
different-ai/openwork
Manages OpenWork's inference model aliases, discounts and overlays over the upstream OpenRouter catalog, and triggers the GitHub workflow that refreshes base models.
Reproduce Chat States
different-ai/openwork
Fires known chat states in the running OpenWork desktop app, such as provider errors, retries and tool steps, so you can check how each renders.
Daytona Sandbox Operations
different-ai/openwork
Covers Daytona CLI setup, sandbox debugging, keeping a sandbox alive and which credentials the CLI uses, for when Daytona itself is the problem rather than the tests.
Daytona Seeded Cloud Demo
different-ai/openwork
Spins up a persistent OpenWork Cloud Den demo on a Daytona sandbox, seeds it with Acme Robotics data and returns shareable URLs and login details.
Related
Works with
Categories
Questions about OpenWork Electron Browser Automation
What does OpenWork Electron Browser Automation do?
Attaches OpenCode browser tools to the OpenWork Electron dev app through CDP to explore its UI, send a composer task and debug, not to give test verdicts. This skill is for exploration and debugging of the OpenWork Electron app during local development. For pass or fail verdicts it points to writing or running an evals/specs test instead.
When should I use OpenWork Electron Browser Automation?
OpenWork Electron Browser Automation fits situations like: driving the local OpenWork Electron dev app through CDP; sending a task from the composer and confirming the response in the UI; running a quick local UI smoke test while developing.
How do I install OpenWork Electron Browser Automation in Claude Code?
Run `npx skills add different-ai/openwork --skill browser-automation -a claude-code`. Or copy the skill folder (.opencode/skills/browser-automation in different-ai/openwork) into .claude/skills/browser-automation in your project. Claude Code loads it when a task matches its description.
How do I install OpenWork Electron Browser Automation in Codex?
Run `npx skills add different-ai/openwork --skill browser-automation -a codex`. Or copy the skill folder (.opencode/skills/browser-automation in different-ai/openwork) into .agents/skills/browser-automation in your project. Codex loads it when a task matches its description.
Can I use OpenWork Electron Browser Automation 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 different-ai/openwork --skill browser-automation -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-automation, .gemini/skills/browser-automation, .github/skills/browser-automation and .opencode/skills/browser-automation in your project.
What does OpenWork Electron Browser Automation need to run?
Going by SKILL.md and its folder, OpenWork Electron Browser Automation needs the command-line tools its instructions call (pnpm). Our summary lists: pnpm and a local OpenWork checkout; OpenCode browser tools.
Does OpenWork Electron Browser Automation 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 OpenWork Electron Browser Automation 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 OpenWork Electron Browser Automation use?
OpenWork Electron Browser Automation 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 OpenWork Electron Browser Automation use?
About 780 tokens (SKILL.md is roughly 3.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 OpenWork Electron Browser Automation?
Skills that share tags, products or a category with OpenWork Electron Browser Automation: Test Electron App (PostHog/code, 179 stars), Test Electron App (PostHog/posthog, 40k stars), Electron App Automation (vercel-labs/agent-browser, 44k stars) and Electron Devtools Testing (ankitvgupta/exo, 496 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains OpenWork Electron Browser Automation?
different-ai (a GitHub organization) maintains it in different-ai/openwork, which has 23,967 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 9, 2026.
Source: different-ai/openwork on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.