Agent skill

Electron Ipc

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

GPL-3.0Auto-check passed

Install Electron Ipc

skills CLI

$ npx skills add tympanix/Electorrent --skill electron-ipc -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install tympanix/Electorrent electron-ipc --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/tympanix/Electorrent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/electron-ipc .claude/skills/electron-ipc && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "electron-ipc" agent skill from https://github.com/tympanix/Electorrent/tree/master/.agents/skills/electron-ipc into .claude/skills/electron-ipc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "electron-ipc", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/tympanix/Electorrent/tree/master/.agents/skills/electron-ipc

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add tympanix/Electorrent --skill electron-ipc -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install tympanix/Electorrent electron-ipc --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/tympanix/Electorrent.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/electron-ipc .agents/skills/electron-ipc && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "electron-ipc" agent skill from https://github.com/tympanix/Electorrent/tree/master/.agents/skills/electron-ipc into .agents/skills/electron-ipc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "electron-ipc", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add tympanix/Electorrent --skill electron-ipc -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install tympanix/Electorrent electron-ipc --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/tympanix/Electorrent.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/electron-ipc .cursor/skills/electron-ipc && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "electron-ipc" agent skill from https://github.com/tympanix/Electorrent/tree/master/.agents/skills/electron-ipc into .cursor/skills/electron-ipc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "electron-ipc", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/tympanix/Electorrent.git --path .agents/skills/electron-ipc

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add tympanix/Electorrent --skill electron-ipc -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install tympanix/Electorrent electron-ipc --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/tympanix/Electorrent.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/electron-ipc .gemini/skills/electron-ipc && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "electron-ipc" agent skill from https://github.com/tympanix/Electorrent/tree/master/.agents/skills/electron-ipc into .gemini/skills/electron-ipc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "electron-ipc", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install tympanix/Electorrent electron-ipc

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add tympanix/Electorrent --skill electron-ipc -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/tympanix/Electorrent.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/electron-ipc .github/skills/electron-ipc && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "electron-ipc" agent skill from https://github.com/tympanix/Electorrent/tree/master/.agents/skills/electron-ipc into .github/skills/electron-ipc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "electron-ipc", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add tympanix/Electorrent --skill electron-ipc -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install tympanix/Electorrent electron-ipc --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/tympanix/Electorrent.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/electron-ipc .opencode/skills/electron-ipc && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "electron-ipc" agent skill from https://github.com/tympanix/Electorrent/tree/master/.agents/skills/electron-ipc into .opencode/skills/electron-ipc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "electron-ipc", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: electron-ipc
GitHub stars: 1.2k
Token cost: ~1.2k tokens
SKILL.md length: 475 words
Files: 1
Skills in repo: 6
Repo updated: Oct 3, 2026
First seen: Oct 7, 2026
Licence: GPL-3.0

At a glance

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

Works in 5 steps: Keep privileged work in the main process. → Expose small, task-specific preload APIs… → Do not expose ipcRenderer.send,… → …
SKILL.md covers Purpose, Core Model, Default Rules and Pick the Right Pattern, plus 8 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Electron Ipc is an agent skill from tympanix/Electorrent. Safe Electron IPC patterns for renderer-main communication with preload bridges, channel design, replies, and serialization limits.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: A remote control client for µTorrent, qBittorrent, rTorrent, Transmission, Synology & Deluge. The licence is GPL-3.0.

Example prompts

“/electron-ipc”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

Keep privileged work in the main process.
Expose small, task-specific preload APIs such as openFile() or
Do not expose ipcRenderer.send, ipcRenderer.invoke, or ipcRenderer.on
When forwarding events from preload, strip the Electron event object and pass
Prefer namespaced channel names such as dialog:openFile for readability.

What it can do on your machine

Read from SKILL.md and the folder at commit d45444f. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are javascript).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
- electronjs.org
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Electron Ipc loads about 1.2k tokens when it runs. Until then it costs about 36 tokens; SKILL.md has 475 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~36
When it runs · the whole SKILL.md, loaded when a task matches: ~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from tympanix/Electorrent at commit d45444f, republished under its GPL-3.0 licence (© tympanix). 475 words, ~1,208 tokens.

Download SKILL.mdSave it as .claude/skills/electron-ipc/SKILL.md (or your agent's skills folder).

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

Skill: Electron IPC

Purpose

Use this skill when you need to design or implement communication between Electron's main and renderer processes.

Core Model

IPC is how Electron processes exchange messages.
Define your own channel names with ipcMain and ipcRenderer.
Channels are arbitrary and bidirectional, but keep names explicit and scoped.
In context-isolated apps, expose narrow preload APIs with contextBridge instead of exposing raw Electron modules to the renderer.

Default Rules

Keep privileged work in the main process.
Expose small, task-specific preload APIs such as openFile() or setTitle(title).
Do not expose ipcRenderer.send, ipcRenderer.invoke, or ipcRenderer.on directly to renderer code.
When forwarding events from preload, strip the Electron event object and pass only the data the renderer needs.
Prefer namespaced channel names such as dialog:openFile for readability.

Pick the Right Pattern

Need	Renderer API	Main API	Notes
Fire-and-forget renderer -> main	`ipcRenderer.send`	`ipcMain.on`	Good for commands with no result
Request/response renderer -> main	`ipcRenderer.invoke`	`ipcMain.handle`	Preferred two-way pattern
Push main -> renderer	preload listener wrapper	`webContents.send`	Main must target a specific window/webContents
Renderer -> renderer	relay through main or `MessagePort`	main as broker if needed	No direct IPC channel between renderers

Pattern 1: Renderer to Main, One Way

Use this when the renderer triggers a main-process action and does not need a result.

Main

ipcMain.on('set-title', (event, title) => {
  const win = BrowserWindow.fromWebContents(event.sender)
  win?.setTitle(title)
})

Preload

contextBridge.exposeInMainWorld('electronAPI', {
  setTitle: (title) => ipcRenderer.send('set-title', title)
})

Renderer

window.electronAPI.setTitle('New title')

Pattern 2: Renderer to Main, Two Way

Use this when the renderer needs a result from the main process. Prefer this over older reply patterns.

Main

ipcMain.handle('dialog:openFile', async () => {
  const { canceled, filePaths } = await dialog.showOpenDialog()
  return canceled ? undefined : filePaths[0]
})

Preload

contextBridge.exposeInMainWorld('electronAPI', {
  openFile: () => ipcRenderer.invoke('dialog:openFile')
})

Renderer

const filePath = await window.electronAPI.openFile()

Notes

invoke/handle is the preferred async request-response model.
Errors from ipcMain.handle are serialized; the renderer does not receive the full original error object.

Pattern 3: Main to Renderer

Use this when the main process needs to push updates into a specific window.

Show full SKILL.md (190 more words)Show less

Main

mainWindow.webContents.send('update-counter', 1)

Preload

contextBridge.exposeInMainWorld('electronAPI', {
  onUpdateCounter: (callback) => {
    ipcRenderer.on('update-counter', (_event, value) => callback(value))
  }
})

Renderer

window.electronAPI.onUpdateCounter((value) => {
  // update UI
})

Replying Back

There is no invoke equivalent from main to renderer. If the renderer needs to reply, send a new message back to the main process on a separate channel.

Legacy Patterns

Avoid these unless you have a strong compatibility reason:

ipcRenderer.send plus event.reply for two-way communication: works, but forces manual reply-channel bookkeeping.
ipcRenderer.sendSync: blocks the renderer and hurts responsiveness.

Security Checklist

Never hand the renderer unrestricted Electron or Node access.
Do not expose raw ipcRenderer methods over contextBridge.
Wrap listeners so the callback never receives the Electron event object.
Keep preload APIs minimal and purpose-built.
Validate inputs in the main process before using privileged APIs.

Serialization Limits

Electron IPC uses the Structured Clone Algorithm.

Safe: plain objects, arrays, strings, numbers, booleans, and other structured clone compatible values.
Not safe: DOM objects, Electron objects like BrowserWindow or WebContents, and Node/Electron objects backed by native C++ classes.

Pass serializable data, not live framework objects.

Quick Guidance

Need a command without a return value: send + on
Need a result: invoke + handle
Need to notify a renderer from main: webContents.send
Need renderer-to-renderer: broker via main or use MessagePort

Reference

https://www.electronjs.org/docs/latest/tutorial/ipc

Files

Just SKILL.md in .agents/skills/electron-ipc of tympanix/Electorrent.

Open the folder on GitHubat commit d45444f

Compare with similar skills

Electron Ipc next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Electron Ipc compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Electron Ipc this skilltympanix/Electorrent	1.2k	—	~1.2k	Automated safety check: Pass	GPL-3.0	5 days ago
Electron Developmentdavila7/claude-code-templates	32k	3 repos	~7k	Automated safety check: Pass	MIT	today
Developing Electron DesktopTriliumNext/Trilium	38k	—	~5.7k	Automated safety check: Pass	AGPL-3.0	today
Desktop ElectronOpenHands/OpenHands	90k	—	~302	Automated safety check: Pass	MIT	today
Electron Drive Skillsickn33/agentic-awesome-skills	47k	1 repos	~2.5k	Automated safety check: Pass	MIT	today
Fantasia Electron Mainvishiri/fantasia-archive	409	—	~1.4k	Automated safety check: Pass	GPL-3.0	yesterday

Similar skills

Electron Development
davila7/claude-code-templates
Master Electron desktop app development with secure IPC, contextIsolation, preload scripts, multi-process architecture, electron-builder packaging, code signing, and auto-update.
32k GitHub starsUsed in 3 repos~7k tokens
MobileAuto-check passed
Developing Electron Desktop
TriliumNext/Trilium
A skill your agent uses when working on the Trilium Electron desktop app (apps/desktop) — adding or changing an electronApi method / IPC channel, touching preload.ts, main.ts, services/window.ts or…
38k GitHub stars~5.7k tokensUpdated today
Knowledge ManagementAuto-check passed
Desktop Electron
OpenHands/OpenHands
This skill should be used when the user asks to "change the desktop app", "package Electron", "build a universal macOS app", "bundle Node or uv", "fix Electron startup", or changes electron/…
90k GitHub stars~302 tokensUpdated today
Auto-check passed
Electron Drive Skill
sickn33/agentic-awesome-skills
Launch the project's Electron app on a scratch profile and drive it: click, type, screenshot, run renderer or main-process code, read logs.
47k GitHub starsUsed in 1 repo~2.5k tokens
Testing & QAAuto-check passed
Fantasia Electron Main
vishiri/fantasia-archive
Works on Fantasia Archive Electron main process: app lifecycle, window management, platform tweaks, native integrations, and ipcMain registration (registerIpc + electron-ipc-bridge channel names).
409 GitHub stars~1.4k tokensUpdated yesterday
Testing & QAAuto-check passed
Render Blocking
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing slow page loads, heavy assets, or rendering delays related to Eliminate render-blocking resources.
74k GitHub stars~430 tokensUpdated 3 days ago
Frontend & DesignAuto-check passed

Questions about Electron Ipc

What does Electron Ipc do?

Safe Electron IPC patterns for renderer-main communication with preload bridges, channel design, replies, and serialization limits. Electron Ipc is an agent skill from tympanix/Electorrent. Safe Electron IPC patterns for renderer-main communication with preload bridges, channel design, replies, and serialization limits.

How do I install Electron Ipc in Claude Code?

Run `npx skills add tympanix/Electorrent --skill electron-ipc -a claude-code`. Or copy the skill folder (.agents/skills/electron-ipc in tympanix/Electorrent) into .claude/skills/electron-ipc in your project. Claude Code loads it when a task matches its description.

How do I install Electron Ipc in Codex?

Run `npx skills add tympanix/Electorrent --skill electron-ipc -a codex`. Or copy the skill folder (.agents/skills/electron-ipc in tympanix/Electorrent) into .agents/skills/electron-ipc in your project. Codex loads it when a task matches its description.

Can I use Electron Ipc in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tympanix/Electorrent --skill electron-ipc -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/electron-ipc, .gemini/skills/electron-ipc, .github/skills/electron-ipc and .opencode/skills/electron-ipc in your project.

What does Electron Ipc need to run?

SKILL.md names no scripts, command-line tools or credentials: Electron Ipc is instructions for the agent only.

Does Electron Ipc access the network?

SKILL.md names 1 domain. As links in the text: electronjs.org. This is read from the text; nothing was executed.

Is Electron Ipc safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Electron Ipc use?

Electron Ipc is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Electron Ipc use?

About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Electron Ipc?

Skills that share tags, products or a category with Electron Ipc: Electron Development (davila7/claude-code-templates, 32k stars), Developing Electron Desktop (TriliumNext/Trilium, 38k stars), Desktop Electron (OpenHands/OpenHands, 90k stars) and Electron Drive Skill (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Electron Ipc?

tympanix (a GitHub user) maintains it in tympanix/Electorrent, which has 1,193 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 3, 2026.

Source: tympanix/Electorrent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Electron Ipc

Facts

At a glance

What it does

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Skill: Electron IPC

Purpose

Core Model

Default Rules

Pick the Right Pattern

Pattern 1: Renderer to Main, One Way

Main

Preload

Renderer

Pattern 2: Renderer to Main, Two Way

Main

Preload

Renderer

Notes

Pattern 3: Main to Renderer

Main

Preload

Renderer

Replying Back

Legacy Patterns

Security Checklist

Serialization Limits

Quick Guidance

Reference

Files

Compare with similar skills

Similar skills

More from tympanix/Electorrent

Questions about Electron Ipc