CtrlK
BlogDocsLog inGet started
Tessl Logo

electron

Electron patterns for building cross-platform desktop applications. Trigger: When building desktop apps, working with Electron main/renderer processes, IPC communication, or native integrations.

59

Quality

69%

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 ./community/electron/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 content is highly actionable with complete, executable code examples across the core Electron concerns. It is weaker on conciseness (long boilerplate) and progressive disclosure (monolithic single file with no bundle references).

Suggestions

Move the full native-menu template and other large boilerplate into reference files under references/ and link to them, keeping SKILL.md a lean overview.

Trim redundant re-statements of the safe IPC pattern in the Anti-Patterns section by referencing the pattern above instead of re-listing the full code.

Add a short sequenced "Setup workflow" with explicit validation checkpoints (e.g., verify contextIsolation is enabled, test IPC round-trip) to improve workflow clarity.

DimensionReasoningScore

Conciseness

The body is mostly concrete code rather than concept explanation, but it includes lengthy boilerplate (e.g., the full ~75-line native menu template) and re-shows the safe IPC version in anti-patterns, which could be tightened.

3 / 5

Actionability

Provides fully executable, copy-paste-ready TypeScript covering the common Electron cases — preload contextBridge, IPC handlers, React hooks, auto-updater, menus, and security configuration.

5 / 5

Workflow Clarity

Organized as a patterns/examples catalog with clear sections rather than a sequenced multi-step workflow, and lacks explicit validation checkpoints or feedback loops.

3 / 5

Progressive Disclosure

Section headers are clear, but all content is inlined into a single ~520-line SKILL.md with no bundle files (references/, scripts/, assets/ are absent); the under-50-line simple-skill exception does not apply.

3 / 5

Total

14

/

20

Passed

Description

73%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 clearly identifies the Electron domain and provides an explicit trigger clause with natural keywords, making it highly distinctive. Its main weakness is that the "what" is a single general action rather than a list of concrete capabilities.

DimensionReasoningScore

Specificity

Names the Electron domain and a couple of specific areas (main/renderer processes, IPC communication, native integrations), but these read as trigger contexts rather than comprehensive concrete actions the skill performs.

3 / 5

Completeness

Both a "what" ("Electron patterns for building cross-platform desktop applications") and an explicit "when" ("Trigger: When building desktop apps...") are present, but the "what" is a single general action rather than the multi-action coverage of a 5.

4 / 5

Trigger Term Quality

Includes natural terms a user would say — "building desktop apps", "Electron main/renderer processes", "IPC communication", "native integrations" — with only a few synonyms/extensions missing.

4 / 5

Distinctiveness Conflict Risk

Electron is a specific named framework with distinct triggers (main/renderer processes, IPC, native integrations), giving it a clear niche and minimal conflict risk with other skills.

5 / 5

Total

16

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (533 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository
Gentleman-Programming/Gentleman-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.