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.
Overall
score
95%
Does it follow best practices?
Validation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that hits all the key criteria. It provides specific capabilities with named apps and technical details, includes comprehensive natural trigger terms users would actually say, explicitly states both what it does and when to use it, and carves out a distinct niche for Electron/desktop app automation that won't conflict with general browser automation skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: 'Automate Electron desktop apps', 'interact with', 'connect to a running app', 'control', 'test'. Also names specific apps (VS Code, Slack, Discord, Figma, Notion, Spotify) and the technical mechanism (Chrome DevTools Protocol). | 3 / 3 |
Completeness | Clearly answers both what ('Automate Electron desktop apps using agent-browser via Chrome DevTools Protocol') and when (explicit 'Use when...' clause with multiple trigger scenarios, plus specific example phrases in 'Triggers include'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'automate Slack app', 'control VS Code', 'interact with Discord app', 'test this Electron app', 'connect to desktop app', 'native app', 'Electron application'. Includes both app-specific and generic variations. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on Electron apps and desktop automation via CDP. The combination of 'Electron', 'desktop app', and specific app names creates distinct triggers unlikely to conflict with web browser automation or other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill document that provides comprehensive, actionable guidance for automating Electron apps. The content is well-structured with clear workflows, executable examples across platforms, and practical troubleshooting guidance. The only weakness is that the document is somewhat long and could benefit from splitting some reference material (platform-specific commands, app lists) into separate files.
Suggestions
Consider moving platform-specific launch commands to a separate PLATFORMS.md reference file to reduce main document length
The 'Supported Apps' section could be moved to a separate APPS.md file or removed entirely since the principle 'any Electron app works' is sufficient
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only necessary information without explaining what Electron or CDP is beyond what's needed. Every section serves a purpose with no padding or redundant explanations. | 3 / 3 |
Actionability | Fully executable commands throughout with copy-paste ready examples for all major platforms (macOS, Linux, Windows). Concrete examples for every workflow pattern including launching, connecting, interacting, and troubleshooting. | 3 / 3 |
Workflow Clarity | Clear 5-step core workflow at the top, with explicit sequencing in all examples. Includes validation-like steps (sleep for app startup, re-snapshot after navigation) and troubleshooting section addresses common failure points with specific remediation steps. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's a fairly long monolithic document. Some content like the full list of supported apps or platform-specific launch commands could be split into separate reference files for better navigation. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
91%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
- 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.