kkrpc

Expose and consume typed APIs over stdio, WebSocket, or HTTP transports.

Updated Jan 8, 2026
One-click install
npx skills add https://github.com/joeblew999/plat-trunk --skill kkrpc-joeblew999
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kkrpc
Source: https://github.com/joeblew999/plat-trunk/tree/main/.claude/skills/kkrpc
Command: npx skills add https://github.com/joeblew999/plat-trunk --skill kkrpc-joeblew999

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enable seamless bidirectional RPC between Node.js, Deno, Bun, and browsers by exposing typed APIs and consuming remote APIs over multiple transports.

Core Features & Use Cases

  • Type-safe RPC channels across diverse runtimes (Node, Deno, Bun, browsers)
  • Support for multiple transports: stdio, WebSocket, HTTP, Worker, and more
  • Flexible API exposure, cross-runtime compatibility, and optional validators

Quick Start

Expose a simple API on a server and call it from a client using an RPCChannel over a chosen IO transport.

Frequently Asked Questions about kkrpc

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I expose and consume typed APIs for bidirectional RPC across Node.js and browsers?

You can achieve bidirectional RPC by exposing and consuming typed APIs over multiple transports. Using an RPCChannel over stdio, WebSocket, or HTTP enables type-safe communication and cross-runtime compatibility between Node.js and browsers.

Can I use TypeScript RPC over WebSocket for cross-runtime communication between Deno and Bun?

Yes, TypeScript RPC over WebSocket supports cross-runtime communication between Deno and Bun. The system applies transport adapters to bridge diverse runtimes, allowing modular services to communicate seamlessly via bidirectional RPC channels.

What is the best way to handle bidirectional RPC orchestration with callbacks and property access?

The best way to handle bidirectional RPC orchestration is using a type-safe RPC channel that supports callbacks and property access. This allows flexible API exposure and consumption over stdio, WebSocket, or HTTP transports across runtimes.

Does bidirectional TypeScript RPC support optional validators and serialization strategies?

Yes, bidirectional TypeScript RPC supports optional validators and serialization strategies. This allows you to enforce type-safe API exposure while customizing data serialization across different transport adapters like WebSocket and HTTP.

When should I not use bidirectional RPC channels for cross-runtime service communication?

You should avoid bidirectional RPC channels when your cross-runtime communication requires simple one-way messaging rather than typed API exposure. If callbacks, property access, and strict type safety are unnecessary, simpler transport methods may suffice.