Agent skill

Erpc Communication

by MatrixAges in MatrixAges/polywise

Guides using eRPC (electron-tRPC) for inter-process communication (IPC) between Electron main and renderer processes.

MITAuto-check passedBackend & APIs

Install Erpc Communication

skills CLI
$ npx skills add MatrixAges/polywise --skill erpc-communication -a claude-code

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

GitHub CLI
$ gh skill install MatrixAges/polywise erpc-communication --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/MatrixAges/polywise.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.opencode/skills/erpc .claude/skills/erpc-communication && 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/

Facts

Skill name
erpc-communication
GitHub stars
662
Token cost
~618 tokens
SKILL.md length
195 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

Guides using eRPC (electron-tRPC) for inter-process communication (IPC) between Electron main and renderer processes.

  • Works in 4 steps: Main Process Implementation → Preload Script Configuration → Renderer Process Usage → …
  • Tasks that involve gRPC and Protobuf
  • SKILL.md covers 1. Main Process Implementation, 2. Preload Script Configuration, 3. Renderer Process Usage and 4. Routes and Endpoints Best…
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Erpc Communication is an agent skill from MatrixAges/polywise. Guides using eRPC (electron-tRPC) for inter-process communication (IPC) between Electron main and renderer processes. Triggered when handling Electron IPC or tRPC-based systems.

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

It sits in Backend & APIs, covering gRPC and Protobuf. It works with tRPC. The repository describes itself as: The open source agentic content system to make your contents alive. Self-hosted on any platform. ◑. The licence is MIT.

When your agent uses it

  • Tasks that involve gRPC and Protobuf

Example prompts

  • “Use the erpc-communication skill to guide using eRPC (electron-tRPC) for inter-process communication (IPC) between Electron main and renderer…”
  • “/erpc-communication”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Main Process Implementation
  2. Preload Script Configuration
  3. Renderer Process Usage
  4. Routes and Endpoints Best Practices

What it can do on your machine

Read from SKILL.md and the folder at commit f8d2320. 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 typescript).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    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

Erpc Communication loads about 618 tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 195 words of instructions outside code blocks.

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

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 MatrixAges/polywise at commit f8d2320, republished under its MIT licence (© MatrixAges). 195 words, ~618 tokens.

Download SKILL.mdSave it as .claude/skills/erpc-communication/SKILL.md (or your agent's skills folder).
name
erpc-communication
description
Guides using eRPC (electron-tRPC) for inter-process communication (IPC) between Electron main and renderer processes. Triggered when handling Electron IPC or tRPC-based systems.

eRPC Communication Guide

This skill provides mandatory instructions for implementing type-safe IPC using eRPC in this project.

1. Main Process Implementation

  • Route Definition: Must use the project's provided router utility to define tRPC routes.
  • Handler Initialization: Must use createIPCHandler from erpc/main to bind the router to Electron windows.
  • Context Injection: Should provide necessary instances (e.g., BrowserWindow or Tray) through createContext.
typescript
// Always initialize createIPCHandler within the app ready lifecycle
import { createIPCHandler } from 'erpc/main'

import { routers } from './rpcs'

createIPCHandler({
	createContext: async () => ({ win: mainWindow, tray: appTray }),
	router: routers,
	windows: [mainWindow]
})

2. Preload Script Configuration

  • Expose Bridge Interface: Must call exposeElectronTRPC() provided by erpc/main in the preload script.
  • Lifecycle: Should be called inside process.once('loaded').
typescript
import { exposeElectronTRPC } from 'erpc/main'

process.once('loaded', () => {
	exposeElectronTRPC()
})

3. Renderer Process Usage

  • Client Creation: Create tRPC client using ipcLink from erpc/renderer.
  • Type Safety: Always import Router type from main process to ensure complete end-to-end type safety.
typescript
import { createTRPCClient } from '@trpc/client'
import { ipcLink } from 'erpc/renderer'

import type { Router } from '@desktop/rpcs' // Import Router type from main process

export const trpc = createTRPCClient<Router>({
	links: [ipcLink()]
})

4. Routes and Endpoints Best Practices

  • Single Responsibility: Each route should correspond to a specific service in the main process (e.g., window, file, dialog).
  • Parameter Validation: It is strictly prohibited to write complex business logic in Router. Router is only responsible for validating input and output parameters; business logic must be delegated to Service (e.g., calling WindowService.open()).
  • Type Reference: For complex object parameters, type definitions must be placed under the packages/erpc package and shared between both ends, avoiding direct cross-package imports of entity logic.

© MatrixAges, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .opencode/skills/erpc of MatrixAges/polywise.

Open the folder on GitHubat commit f8d2320

Compare with similar skills

Erpc Communication 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.

Erpc Communication compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Erpc Communication this skillMatrixAges/polywise662—~618Automated safety check: PassMIT
Nestjs Trpctrycompai/crm11k—~2.8kAutomated safety check: PassMIT
Backend Dev Guidelineslangfuse/langfuse35k—~1.9kAutomated safety check: PassCustom licence
Trpc PatternsFranciscoMoretti/chat-js1.2k—~288Automated safety check: PassApache-2.0
Backend Dev Guidelineslitefuse/litefuse1001 repos~5.8kAutomated safety check: PassCustom licence
TrpcPrairieLearn/PrairieLearn512—~2kAutomated safety check: PassCustom licence

Similar skills

  • Nestjs Trpc

    trycompai/crm

    Build end-to-end type-safe tRPC APIs inside NestJS using the nestjs-trpc adapter — @Router/@Query/@Mutation/@Subscription decorators, TRPCModule.forRoot, injectable middlewares and context, Zod…

    11k GitHub stars~2.8k tokensUpdated 26 days ago
    Backend & APIsAuto-check passed
  • Backend Dev Guidelines

    langfuse/langfuse

    Build or review Langfuse backend code. An agent skill from langfuse/langfuse.

    35k GitHub stars~1.9k tokensUpdated today
    Backend & APIsAuto-check passed
  • Trpc Patterns

    FranciscoMoretti/chat-js

    Implement ChatJS tRPC routers, TanStack Query hooks, mutations, and cache invalidation.

    1.2k GitHub stars~288 tokensUpdated today
    Backend & APIsAuto-check passed
  • Backend Dev Guidelines

    litefuse/litefuse

    Comprehensive backend development guide for Litefuse's Next.js 14/tRPC/Express/TypeScript monorepo.

    100 GitHub starsUsed in 1 repo~5.8k tokens
    Backend & APIsAuto-check passed
  • Trpc

    PrairieLearn/PrairieLearn

    Conventions for writing tRPC routers and procedures. An agent skill from PrairieLearn/PrairieLearn.

    512 GitHub stars~2k tokensUpdated today
    Backend & APIsAuto-check passed
  • Lazy Prefetch Pattern

    FranciscoMoretti/chat-js

    Use the ChatJS React Query v5 lazy-prefetch pattern without blocking server rendering.

    1.2k GitHub stars~217 tokensUpdated today
    Backend & APIsAuto-check passed

More from MatrixAges/polywise

All 11 skills in this repo
  • Chrome Cdp

    MatrixAges/polywise

    Interacts with local browser via Chrome DevTools Protocol (only triggered after user explicitly requests to inspect, debug, or interact with pages open in Chrome)

    662 GitHub stars~800 tokensUpdated 3 mo ago
    Auto-check passed
  • Skill Generator

    MatrixAges/polywise

    Called when users need to create new OpenCode skills. An agent skill from MatrixAges/polywise.

    662 GitHub stars~333 tokensUpdated 3 mo ago
    Auto-check passed
  • Agentmap Generator

    MatrixAges/polywise

    Guides the generation, reading, and updating of agentmap.md files.

    662 GitHub stars~489 tokensUpdated 3 mo ago
    Auto-check passed
  • CSS

    MatrixAges/polywise

    Guides styling implementation using TailwindCSS + CSS Modules.

    662 GitHub stars~1.3k tokensUpdated 3 mo ago
    Auto-check passed
  • I18n

    MatrixAges/polywise

    Guides internationalization (i18n) implementation using i18next with TypeScript.

    662 GitHub stars~898 tokensUpdated 3 mo ago
    Auto-check passed
  • Mobx

    MatrixAges/polywise

    Guides state management implementation using MobX + tsyringe.

    662 GitHub stars~1.3k tokensUpdated 3 mo ago
    Auto-check passed

Works with

Questions about Erpc Communication

What does Erpc Communication do?

Guides using eRPC (electron-tRPC) for inter-process communication (IPC) between Electron main and renderer processes. Erpc Communication is an agent skill from MatrixAges/polywise. Guides using eRPC (electron-tRPC) for inter-process communication (IPC) between Electron main and renderer processes.

When should I use Erpc Communication?

Erpc Communication fits situations like: tasks that involve gRPC and Protobuf.

How do I install Erpc Communication in Claude Code?

Run `npx skills add MatrixAges/polywise --skill erpc-communication -a claude-code`. Or copy the skill folder (.opencode/skills/erpc in MatrixAges/polywise) into .claude/skills/erpc-communication in your project. Claude Code loads it when a task matches its description.

How do I install Erpc Communication in Codex?

Run `npx skills add MatrixAges/polywise --skill erpc-communication -a codex`. Or copy the skill folder (.opencode/skills/erpc in MatrixAges/polywise) into .agents/skills/erpc-communication in your project. Codex loads it when a task matches its description.

Can I use Erpc Communication 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 MatrixAges/polywise --skill erpc-communication -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/erpc-communication, .gemini/skills/erpc-communication, .github/skills/erpc-communication and .opencode/skills/erpc-communication in your project.

What does Erpc Communication need to run?

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

Does Erpc Communication access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Erpc Communication 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 Erpc Communication use?

Erpc Communication is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Erpc Communication use?

About 618 tokens (SKILL.md is roughly 2.5k 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 Erpc Communication?

Skills that share tags, products or a category with Erpc Communication: Nestjs Trpc (trycompai/crm, 11k stars), Backend Dev Guidelines (langfuse/langfuse, 35k stars), Trpc Patterns (FranciscoMoretti/chat-js, 1.2k stars) and Backend Dev Guidelines (litefuse/litefuse, 100 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Erpc Communication?

MatrixAges (a GitHub organization) maintains it in MatrixAges/polywise, which has 662 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on June 11, 2026.

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