CtrlK
BlogDocsLog inGet started
Tessl Logo

electron-development

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

61

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/electron-development/SKILL.md

The canonical home for this skill is electron-development in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is highly actionable with comprehensive executable examples and a clear validation-gated workflow, but it is verbose (repeated security guidance) and monolithic — everything is inlined in SKILL.md with no progressive disclosure to reference files for a skill this large.

Suggestions

Move the full electron-builder.yml config, the diagnostics reference, and the per-area code templates into files under references/ and link to them from SKILL.md, keeping only a concise overview and quick-start inline.

Consolidate the security guidance so it appears once — keep the Production Security Checklist as the single source and remove the duplicated bullets from the inline warnings and Best Practices list.

Tighten the Instructions steps into command-level actions (e.g., name the exact tooling/commands for 'Implement, test, and build') to push workflow clarity toward 5.

DimensionReasoningScore

Conciseness

Mostly efficient, code-heavy reference material, but it restates security guidance three times (inline CRITICAL warnings, the Production Security Checklist, and the Best Practices list) and opens the process model with basics Claude already knows ('Electron runs multiple processes that are isolated by design').

3 / 5

Actionability

Provides extensive copy-paste-ready, executable code and config across every major area — BrowserWindow creation, contextBridge preload, IPC handlers, electron-builder.yml, signing env vars, the auto-updater, and Playwright E2E tests — covering the common cases fully.

5 / 5

Workflow Clarity

The Instructions section gives a clear 5-step sequence culminating in validation against the Production Security Checklist, plus a diagnostics section for error recovery, but the early steps ('Analyze', 'Enforce', 'Design') remain high-level rather than command-driven.

4 / 5

Progressive Disclosure

Sections are well-organized with clear headers, but the ~850-line body inlines all bulk reference material (full electron-builder.yml, complete IPC/store code, diagnostics) with no split into reference files, and no bundle files exist to offload it.

3 / 5

Total

15

/

20

Passed

Description

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

The description is specific and distinctive, naming seven concrete Electron capabilities, but it omits any explicit 'when to use' trigger guidance, which caps completeness. Adding a Use-when clause would raise the score materially.

Suggestions

Append an explicit 'Use when...' clause (e.g., 'Use when building, securing, packaging, or auto-updating Electron desktop apps') to satisfy the completeness 'when' requirement.

Add natural synonyms or variations users might say (e.g., 'desktop app distribution', '.asar packaging', 'notarization') to broaden trigger-term coverage toward a 5.

Keep the third-person capability framing ('Master Electron...') — it is correct voice; just pair it with the trigger clause rather than replacing it.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'secure IPC, contextIsolation, preload scripts, multi-process architecture, electron-builder packaging, code signing, and auto-update' — giving comprehensive coverage of the domain's specific actions.

5 / 5

Completeness

Clearly answers 'what' with a concrete capability list but contains no 'Use when...' or equivalent explicit trigger guidance, so per the rubric completeness is capped at 3.

3 / 5

Trigger Term Quality

Good natural keyword coverage ('Electron desktop app', 'IPC', 'contextIsolation', 'preload scripts', 'auto-update', 'code signing') that a developer would say, but missing synonyms and common variations like 'distribute' or file extensions.

4 / 5

Distinctiveness Conflict Risk

A clearly defined Electron-specific niche with distinct technical triggers, minimal overlap risk with web/Tauri/mobile skills.

5 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

14

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.