Skip to content
mcp/skillhub

Agent Skill

Electron skill

electronvercel-labs/agent-browserskill-data/electron/SKILL.md

Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.

44kApache-2.0

always on

112 tokname + description

once used

1,503 tokSKILL.md body

bundled files

0

repo stars

44kGitHub

Install the Electron skill

Skills CLI (Claude Code, Codex, Cursor and others)

npx skills add https://github.com/vercel-labs/agent-browser --skill electron

Claude Code, by hand (all projects)

git clone --depth 1 https://github.com/vercel-labs/agent-browser.git /tmp/agent-browser
mkdir -p ~/.claude/skills
cp -R /tmp/agent-browser/skill-data/electron ~/.claude/skills/electron

For one project only, copy the folder into .claude/skills/ in that project instead. The agent picks it up when a task matches its description.

What it costs your context

Agent Skills load in three steps. Tokens counted with the o200k tokenizer; your model's count will differ a little.

WhenWhat loadsCost
Every sessionName and description112 tok
When the agent uses itThe SKILL.md instructions1,503 tok
Only if openedNo bundled files—

Until it is used, electron costs about 12× less than the median MCP server we measured (1,362 tokens on every turn). Installing all 10 skills from vercel-labs/agent-browser would load 1,058 tokens of descriptions. Skills vs MCP study

Checks

Our checks found nothing to flag: it follows the Agent Skills specification's naming and size guidelines and doesn't pipe downloads into a shell.

Pre-approved tools (allowed-tools): Bash(agent-browser:*), Bash(npx agent-browser:*). The agent can use these without asking while the skill is active.

Checked 2026-10-22 · method

What's inside

The headings of its SKILL.md. Read the full file on GitHub.

  • Electron App Automation
  • Core Workflow
  • Launching Electron Apps with CDP
  • macOS
  • Linux
  • Windows
  • Connecting
  • Tab Management
  • Webview Support
  • Common Patterns
  • Inspect and Navigate an App
  • Take Screenshots of Desktop Apps
  • Extract Data from a Desktop App
  • Fill Forms in Desktop Apps
  • Run Multiple Apps Simultaneously
  • Color Scheme
  • Troubleshooting
  • "Connection refused" or "Cannot connect"
  • App launches but connect fails
  • Elements not appearing in snapshot
  • Cannot type in input fields
  • Supported Apps

More skills from vercel-labs/agent-browser

All skills in this repo
  1. agent-browservercel-labs/agent-browser

    Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.

    1.2M200 tok idle · 489 in use
  2. agentcorevercel-labs/agent-browser

    Run agent-browser on AWS Bedrock AgentCore cloud browsers. Use when the user wants to use AgentCore, run browser automation on AWS, use a cloud browser with AWS credentials, or needs a managed browser session backed by AWS infrastructure. Triggers include "use agentcore", "run on AWS", "cloud browser with AWS", "bedrock browser", "agentcore session", or any task requiring AWS-hosted browser automation.

    44k89 tok idle · 826 in use
  3. corevercel-labs/agent-browser

    Core agent-browser usage guide. Read this before running any agent-browser commands. Covers the snapshot-and-ref workflow, navigating pages, interacting with elements (click, fill, type, select), extracting text and data, taking screenshots, managing tabs, handling forms and auth, waiting for content, running multiple browser sessions in parallel, and troubleshooting common failures. Use when the user asks to interact with a website, fill a form, click something, extract data, take a screenshot, log into a site, test a web app, or automate any browser task.

    44k3112 tok idle · 8,258 in use
  4. derive-clientvercel-labs/agent-browser

    Reverse-engineer a website's internal API by recording browser traffic into a HAR file, then generate a standalone client or CLI that calls the endpoints directly, with no browser needed after the first recording. Use when asked to "derive a client", "build a CLI for <site>", "reverse engineer this site's API", "record network requests", "turn this site into an API", or when the same site will be automated repeatedly and direct HTTP calls would beat driving the browser every time.

    44k100 tok idle · 1,076 in use
  5. dogfoodvercel-labs/agent-browser

    Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.

    44k100 tok idle · 2,341 in use
  6. protected-vercel-deploymentsvercel-labs/agent-browser

    Access and test Vercel deployments protected by Vercel Authentication, SSO, or Deployment Protection with agent-browser. Use when a preview or production URL redirects to a Vercel login page, returns a protection 401 or 403, or needs short-lived Trusted Sources OIDC authentication instead of a static bypass secret or public exception.

    44k75 tok idle · 1,339 in use
  7. slackvercel-labs/agent-browser

    Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.

    44k89 tok idle · 1,870 in use
  8. vercel-sandboxvercel-labs/agent-browser

    Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.

    44k126 tok idle · 1,744 in use