CtrlK
BlogDocsLog inGet started
Tessl Logo

electron

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.

89

3.42x
Quality

88%

Does it follow best practices?

Impact

89%

3.42x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-organized automation guide built on concrete executable commands and a clear workflow with troubleshooting feedback. Minor gaps are redundant connect calls, a missing explicit connect-verification step, and a launch catalog that could be externalized.

Suggestions

Remove the repeated `agent-browser connect 9222` preamble from each 'Common Pattern' example by establishing the connection once and referencing it, to cut redundancy.

Add an explicit verification step after connecting (e.g. confirm the connection succeeded before running snapshot) to strengthen the workflow checkpoint.

Consider moving the full macOS/Linux/Windows per-app launch catalog into a references file and keeping only one representative example per OS inline.

DimensionReasoningScore

Conciseness

Mostly lean and command-driven, but each 'Common Pattern' redundantly repeats `agent-browser connect 9222` and the 6-app x 3-OS launch catalog could be tightened.

4 / 5

Actionability

Fully executable, copy-paste-ready commands across launching, connecting, snapshots, interaction, tabs, webviews, screenshots, and form filling cover the common cases.

5 / 5

Workflow Clarity

A clear 5-step core workflow (Launch, Connect, Snapshot, Interact, Re-snapshot) with a troubleshooting feedback section, but it lacks an explicit verify-connect checkpoint before snapshotting.

4 / 5

Progressive Disclosure

Single well-sectioned SKILL.md with no external bundle files; structure is good but at ~230 lines the per-app/per-OS launch reference could be split into a separate file.

4 / 5

Total

17

/

20

Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that explicitly states both capabilities and trigger conditions with natural, app-specific phrases. The only weakness is that several named actions overlap semantically, leaving specificity slightly below fully comprehensive.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Automate Electron desktop apps', 'connect to a running app', 'control a native app', 'test an Electron application'), but several are near-synonyms so coverage has minor gaps rather than being fully comprehensive.

4 / 5

Completeness

Clearly answers what ('Automate Electron desktop apps...using agent-browser via Chrome DevTools Protocol') and when ('Use when the user needs to interact with an Electron app...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Explicit natural triggers with named apps and synonyms ('automate Slack app', 'control VS Code', 'interact with Discord app', 'test this Electron app', 'connect to desktop app') give comprehensive coverage of phrases users would actually say.

5 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Electron desktop apps via CDP) with app-specific triggers, making conflict with other skills unlikely.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository
vercel-labs/agent-browser
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.