CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

electron-ipc

Safe Electron IPC patterns for renderer-main communication with preload bridges, channel design, replies, and serialization limits.

Quality

81%

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

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.

The content is an actionable, well-structured IPC reference with executable code for every common pattern and clear selection guidance. Its main weaknesses are minor over-explanation of basics and a single-file layout that is slightly heavier than the ideal progressive-disclosure split.

DimensionReasoningScore

Conciseness

The body is mostly lean with tight code examples and rule lists, though a few lines restate basics Claude already knows (e.g. 'IPC is how Electron processes exchange messages.').

4 / 5

Actionability

Each pattern ships complete, copy-paste-ready code for main/preload/renderer, and the decision table maps concrete needs to specific APIs covering the common cases.

5 / 5

Workflow Clarity

The 'Pick the Right Pattern' table and 'Quick Guidance' give a clear selection flow with a security checklist, but there are no explicit validation checkpoints — acceptable here since no destructive/batch workflow is involved.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections with a single one-level external reference; at ~165 lines it exceeds the under-50-line auto-5 exception, and a couple of pattern sections could arguably live in separate files.

4 / 5

Total

17

/

20

Passed

Description

70%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, distinctive, and uses natural trigger terms, but it omits any explicit 'when to use' guidance, which the rubric caps at completeness 3. Adding a 'Use when...' clause would lift the strongest remaining weakness.

Suggestions

Append an explicit trigger clause, e.g. 'Use when designing or debugging communication between Electron main and renderer processes, or when wiring up a contextBridge preload API.'

Consider adding 'contextBridge' or 'main/renderer process' as additional natural keywords users are likely to say.

Keep the existing concrete capability list; it already distinguishes the skill well from generic Electron helpers.

DimensionReasoningScore

Specificity

Names the Electron IPC domain plus several concrete capability areas — 'preload bridges, channel design, replies, and serialization limits' — giving specific rather than generic coverage, with only minor gaps.

4 / 5

Completeness

The 'what' is clear and concrete, but there is no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric completeness is capped at 3.

3 / 5

Trigger Term Quality

Includes natural terms a user would say ('Electron IPC', 'renderer-main communication', 'preload bridges') with good coverage, though a few common phrasings like 'main/renderer process' or 'contextBridge' are absent.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Electron renderer-main IPC with preload bridges) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

16

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

tympanix/Electorrent

Path

.agents/skills/electron-ipc/SKILL.md

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.