Agent Browser Automation
withkynam/vibecode-pro-max-kit
Drives a browser through the agent-browser CLI, using compact snapshots with element refs to keep context small in long sessions, plus video recording and cloud browsers.
Test the Electron app interactively using Chrome DevTools Protocol.
Install Electron Devtools Testing
$ npx skills add ankitvgupta/exo --skill electron-devtools-testing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ankitvgupta/exo electron-devtools-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/ankitvgupta/exo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/electron-devtools-testing .claude/skills/electron-devtools-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 "electron-devtools-testing" agent skill from https://github.com/ankitvgupta/exo/tree/main/.claude/skills/electron-devtools-testing into .claude/skills/electron-devtools-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "electron-devtools-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/ankitvgupta/exo/tree/main/.claude/skills/electron-devtools-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 ankitvgupta/exo --skill electron-devtools-testing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ankitvgupta/exo electron-devtools-testing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ankitvgupta/exo.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/electron-devtools-testing .agents/skills/electron-devtools-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 "electron-devtools-testing" agent skill from https://github.com/ankitvgupta/exo/tree/main/.claude/skills/electron-devtools-testing into .agents/skills/electron-devtools-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "electron-devtools-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 ankitvgupta/exo --skill electron-devtools-testing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ankitvgupta/exo electron-devtools-testing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ankitvgupta/exo.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/electron-devtools-testing .cursor/skills/electron-devtools-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 "electron-devtools-testing" agent skill from https://github.com/ankitvgupta/exo/tree/main/.claude/skills/electron-devtools-testing into .cursor/skills/electron-devtools-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "electron-devtools-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/ankitvgupta/exo.git --path .claude/skills/electron-devtools-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 ankitvgupta/exo --skill electron-devtools-testing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ankitvgupta/exo electron-devtools-testing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ankitvgupta/exo.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/electron-devtools-testing .gemini/skills/electron-devtools-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 "electron-devtools-testing" agent skill from https://github.com/ankitvgupta/exo/tree/main/.claude/skills/electron-devtools-testing into .gemini/skills/electron-devtools-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "electron-devtools-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 ankitvgupta/exo electron-devtools-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 ankitvgupta/exo --skill electron-devtools-testing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ankitvgupta/exo.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/electron-devtools-testing .github/skills/electron-devtools-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 "electron-devtools-testing" agent skill from https://github.com/ankitvgupta/exo/tree/main/.claude/skills/electron-devtools-testing into .github/skills/electron-devtools-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "electron-devtools-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 ankitvgupta/exo --skill electron-devtools-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 ankitvgupta/exo electron-devtools-testing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ankitvgupta/exo.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/electron-devtools-testing .opencode/skills/electron-devtools-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 "electron-devtools-testing" agent skill from https://github.com/ankitvgupta/exo/tree/main/.claude/skills/electron-devtools-testing into .opencode/skills/electron-devtools-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "electron-devtools-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
electron-devtools-testing- GitHub stars
- 496
- Token cost
- ~2.4k tokens
- SKILL.md length
- 877 words
- Files
- 1
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Test the Electron app interactively using Chrome DevTools Protocol.
- Works in 2 steps: chrome-devtools MCP must be configured —… → Pick a free debug port, then launch the…
- The user asks to test
- SKILL.md covers Prerequisites, How It Works, Workflow and Key UI Navigation, plus 3 more sections
- Calls npm, npx and claude
What it does
Electron Devtools Testing is an agent skill from ankitvgupta/exo. Test the Electron app interactively using Chrome DevTools Protocol. Use when the user asks to test, verify, or interact with the running app via browser automation.
Its SKILL.md is about 2.4k 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 Productivity & Automation, covering Browser testing and Browser automation. It works with Chrome DevTools, Electron, Model Context Protocol and npm. The repository describes itself as: Claude Code for your Inbox.
When your agent uses it
- The user asks to test
- Interact with the running app via browser automation
Example prompts
- “/electron-devtools-testing”
Requirements
- Node.js
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- chrome-devtools MCP must be configured — add it to your MCP config
- Pick a free debug port, then launch the app headless on it
What it can do on your machine
Read from SKILL.md and the folder at commit 04da760. 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:
npmnpxclaude
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm and npx, 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
Electron Devtools Testing loads about 2.4k tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 877 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 877 words (~2,389 tokens).
“Test the Exo Electron app interactively using Chrome DevTools Protocol (CDP) via the chrome-devtools MCP.”
- name
- electron-devtools-testing
Files
Just SKILL.md in .claude/skills/electron-devtools-testing of ankitvgupta/exo.
Open the folder on GitHubat commit 04da760
Compare with similar skills
Electron Devtools 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 |
|---|---|---|---|---|---|---|
| Electron Devtools Testing this skillankitvgupta/exo | 496 | — | ~2.4k | Automated safety check: Pass | Custom licence | |
| Agent Browser Automationwithkynam/vibecode-pro-max-kit | 1.1k | — | ~2.6k | Automated safety check: Pass | Apache-2.0 | |
| Cdp Connectadobe/skills | 195 | — | ~847 | Automated safety check: Pass | Apache-2.0 | |
| Agent Browser Electronmoeru-ai/airi | 50k | — | ~3.1k | Automated safety check: Pass | MIT | |
| Browseragutinbaigo28/financial-agent-api | 128 | 1 repos | ~480 | Automated safety check: Pass | None | |
| Chrome Devtoolseinverne/dotfiles | 121 | 1 repos | ~1.6k | Automated safety check: Notes | Apache-2.0 |
Similar skills
Cdp Connect
adobe/skills
Connect Claude Code to an existing Chrome browser via CDP (Chrome DevTools Protocol).
Agent Browser Electron
moeru-ai/airi
A skill your agent uses when Codex needs to inspect, debug, or automate an Electron app through agent-browser and Chrome DevTools Protocol, especially when the app has multiple BrowserWindow…
Browser
agutinbaigo28/financial-agent-api
This skill should be used for browser automation tasks using Chrome DevTools Protocol (CDP).
Chrome Devtools
einverne/dotfiles
Browser automation, debugging, and performance analysis using Puppeteer CLI scripts.
Anti Detect Browser
antibrow/anti-detect-browser-skills
Drive Chromium from standard Playwright APIs with a real-device fingerprint applied in the kernel, one persistent isolated profile per identity, and a per-profile proxy whose exit IP sets timezone…
More from ankitvgupta/exo
Reviewloop
ankitvgupta/exo
Iteratively improves a PR until all review bots (Greptile, Devin, and others) are satisfied with zero unresolved comments, then fixes any CI failures.
Clear Caches
ankitvgupta/exo
Clear extension caches, analysis data, and drafts from the database.
Take Screenshots
ankitvgupta/exo
Capture screenshots of the Exo Electron app workflows using Playwright in demo mode.
Review Code
ankitvgupta/exo
Pre-commit code review for production-critical issues. An agent skill from ankitvgupta/exo.
Gh Local
ankitvgupta/exo
Run GitHub Actions CI workflows locally using nektos/act in Docker.
Related
Categories
Questions about Electron Devtools Testing
What does Electron Devtools Testing do?
Test the Electron app interactively using Chrome DevTools Protocol. Electron Devtools Testing is an agent skill from ankitvgupta/exo. Test the Electron app interactively using Chrome DevTools Protocol.
When should I use Electron Devtools Testing?
Electron Devtools Testing fits situations like: the user asks to test; interact with the running app via browser automation.
How do I install Electron Devtools Testing in Claude Code?
Run `npx skills add ankitvgupta/exo --skill electron-devtools-testing -a claude-code`. Or copy the skill folder (.claude/skills/electron-devtools-testing in ankitvgupta/exo) into .claude/skills/electron-devtools-testing in your project. Claude Code loads it when a task matches its description.
How do I install Electron Devtools Testing in Codex?
Run `npx skills add ankitvgupta/exo --skill electron-devtools-testing -a codex`. Or copy the skill folder (.claude/skills/electron-devtools-testing in ankitvgupta/exo) into .agents/skills/electron-devtools-testing in your project. Codex loads it when a task matches its description.
Can I use Electron Devtools 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 ankitvgupta/exo --skill electron-devtools-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/electron-devtools-testing, .gemini/skills/electron-devtools-testing, .github/skills/electron-devtools-testing and .opencode/skills/electron-devtools-testing in your project.
What does Electron Devtools Testing need to run?
Going by SKILL.md and its folder, Electron Devtools Testing needs the command-line tools its instructions call (npm, npx and claude). Our summary lists: Node.js.
Does Electron Devtools Testing access the network?
SKILL.md contains no URLs. Its commands use npm and npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Electron Devtools 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 Electron Devtools Testing use?
Electron Devtools 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 Electron Devtools Testing use?
About 2.4k tokens (SKILL.md is roughly 9.6k 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 Electron Devtools Testing?
Skills that share tags, products or a category with Electron Devtools Testing: Agent Browser Automation (withkynam/vibecode-pro-max-kit, 1.1k stars), Cdp Connect (adobe/skills, 195 stars), Agent Browser Electron (moeru-ai/airi, 50k stars) and Browser (agutinbaigo28/financial-agent-api, 128 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Electron Devtools Testing?
ankitvgupta (a GitHub user) maintains it in ankitvgupta/exo, which has 496 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on September 5, 2026.
Source: ankitvgupta/exo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.