electron-development

Master Electron desktop app development with secure IPC, contextIsolation, preload scripts, multi-process architecture, electron-builder packaging, code signing, and auto-update.

Quality

55%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/electron-development/SKILL.md

Quality

Content

53%Scale 1-5

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

The skill excels in actionability with comprehensive, executable code examples covering the full Electron development lifecycle. However, it is severely over-long and monolithic — at 600+ lines it explains many concepts Claude already knows (process models, what IPC is, basic security principles) and packs everything into a single file rather than using progressive disclosure. The workflow is present but lacks explicit validation checkpoints for the build/distribution pipeline.

Suggestions

Split the monolithic content into separate files: SECURITY.md (hardening checklist + navigation hijacking + CSP), IPC.md (preload patterns + handlers), BUILD.md (electron-builder config + signing + auto-update), and DEBUGGING.md (diagnostics + testing). Keep SKILL.md as a concise overview with references.

Remove explanatory content Claude already knows: the process model table, explanations of what contextIsolation/nodeIntegration do conceptually, the 'Electron runs multiple processes' paragraph, and the persona/routing sections. Focus on the specific patterns and code.

Add explicit validation steps to the build/distribution workflow: e.g., verify code signing succeeded, test the packaged app before publishing, validate auto-update works with a staging channel before production release.

Trim the 'Common Issue Diagnostics' section to a compact troubleshooting table rather than verbose symptom/cause/solution blocks — Claude can reason about these issues given the code patterns.

Dimension	Reasoning	Score
Conciseness	The skill is extremely verbose at ~600+ lines, extensively covering topics Claude already understands well (process models, what IPC is, basic Electron concepts). The table explaining what Main/Renderer/Preload processes do, the lengthy explanations of security concepts, and the 'Common Issue Diagnostics' section all explain things Claude already knows. The persona preamble and 'Use this skill when' / 'Do not use this skill when' sections add significant padding.	2 / 5
Actionability	The skill provides fully executable, copy-paste ready code examples throughout — BrowserWindow creation, preload scripts with contextBridge, IPC handlers, electron-builder YAML config, auto-updater setup, Playwright E2E tests, VS Code launch config, and more. Every major section includes concrete, runnable code covering common use cases.	5 / 5
Workflow Clarity	The Instructions section provides a 5-step high-level workflow ending with 'Validate against the Production Security Checklist,' which is a good checkpoint. However, the workflow is very high-level and the detailed sections don't follow a clear sequential process with validation checkpoints. For a skill involving packaging and distribution (potentially destructive batch operations), there are no explicit validate-then-proceed feedback loops in the build/sign/distribute workflow.	3 / 5
Progressive Disclosure	This is a monolithic ~600-line file with no references to supporting bundle files. The content covering project structure, IPC, security, state management, build/signing, debugging, testing, lifecycle management, and diagnostics should clearly be split across multiple files. There are no bundle files provided and no references to any, making this a wall of content that would benefit enormously from progressive disclosure.	2 / 5
	Total	12 / 20 Passed

Description

57%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.

The description effectively enumerates Electron-specific technical concepts, making it reasonably specific and distinctive. However, it uses imperative/instructional voice ('Master...') rather than third-person descriptive voice, lacks action verbs describing what the skill does, and critically omits any 'Use when...' clause to guide skill selection. The description reads more like a course title than a functional skill description.

Suggestions

Add an explicit 'Use when...' clause with trigger phrases like 'Use when building Electron desktop applications, packaging apps for distribution, or configuring IPC between main and renderer processes.'

Rewrite in third-person active voice with concrete actions, e.g., 'Guides Electron desktop app development including secure IPC setup, preload script configuration, and packaging with electron-builder.'

Include common synonyms and related terms users might say, such as 'cross-platform desktop app', 'native app', 'Electron Forge', or file references like 'main.js', 'renderer process'.

Dimension	Reasoning	Score
Specificity	Lists several specific concepts: secure IPC, contextIsolation, preload scripts, multi-process architecture, electron-builder packaging, code signing, and auto-update. These are concrete technical capabilities, though they read more like a feature list than concrete actions (verbs are mostly missing).	4 / 5
Completeness	Provides a reasonable 'what' (Electron development with specific features), but completely lacks a 'when' clause. There is no 'Use when...' or equivalent trigger guidance, which per the rubric should cap completeness at 3, and the 'what' is more of a topic list than a clear action description, pushing it toward 2.	2 / 5
Trigger Term Quality	Includes strong natural keywords like 'Electron', 'desktop app', 'IPC', 'preload scripts', 'electron-builder', 'code signing', 'auto-update'. Missing some common user phrases like '.exe', 'native app', 'cross-platform desktop', 'Electron Forge', or 'main process/renderer process'.	4 / 5
Distinctiveness Conflict Risk	The focus on Electron specifically, along with Electron-specific terms like 'contextIsolation', 'preload scripts', and 'electron-builder', makes it fairly distinct. Minor overlap risk with general Node.js or web development skills, but the Electron-specific terminology reduces conflict significantly.	4 / 5
	Total	14 / 20 Passed

Validation

81%

Warnings & errors only

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

Validation — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (857 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/electron-development/SKILL.md
Commit: 57c135b

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.