p2p-conference

Implement serverless WebRTC mesh audio conferencing with decentralized signaling and RNNoise.

Updated Jan 22, 2026
One-click install
npx skills add https://github.com/bgscr/p2p_conference --skill p2p-conference
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: p2p-conference
Source: https://github.com/bgscr/p2p_conference/tree/main/.agent/skills/p2p-conference
Command: npx skills add https://github.com/bgscr/p2p_conference --skill p2p-conference

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Serverless, peer-to-peer audio conferencing is challenging due to signaling complexity, NAT traversal, and audio processing requirements. This skill provides patterns and architecture to implement WebRTC mesh topology, decentralized signaling, and client-side RNNoise noise suppression for cross-platform desktop apps.

Core Features & Use Cases

  • Full Mesh P2P audio with N-1 connections and no central media server
  • Decentralized signaling using Trystero, BitTorrent DHT, MQTT, or Nostr
  • Client-side RNNoise-based noise suppression integrated into the audio pipeline
  • Electron + React + TypeScript desktop scaffolding with cross-platform considerations
  • Platform-specific configuration guidance (macOS, Linux, Windows) and device management

Quick Start

Follow this guide to scaffold a P2P conference app and begin implementing decentralized signaling, WebRTC mesh, and RNNoise noise suppression.

Frequently Asked Questions about p2p-conference

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

FAQPage Schema
How do I build a serverless P2P audio conferencing app with WebRTC?▼

Build serverless P2P audio conferencing using a WebRTC full mesh topology with decentralized signaling via Trystero, MQTT, or Nostr, eliminating the need for a central media server.

What is decentralized signaling and how does it work for WebRTC mesh networks?▼

Decentralized signaling connects peers using BitTorrent DHT, MQTT, or Nostr protocols instead of a dedicated server, enabling full mesh WebRTC topology establishment for direct peer-to-peer audio streams.

Can I integrate RNNoise noise suppression into an Electron WebRTC audio pipeline?▼

Yes, you can integrate WASM-based RNNoise noise suppression directly into the client-side audio processing pipeline of an Electron, React, and TypeScript desktop application before audio transmission.

Does WebRTC full mesh topology scale for small decentralized audio chats?▼

WebRTC full mesh topology scales effectively for decentralized audio chats supporting 2 to 15 participants by maintaining N-1 direct peer connections per client without requiring a central media server.

What are the limitations of using a full mesh topology for P2P audio conferencing?▼

Full mesh P2P audio conferencing requires each client to maintain N-1 direct connections, limiting scaling to 15 participants before bandwidth and client-side processing constraints degrade audio quality.

How do I handle platform-specific device management for WebRTC audio in Electron?▼

Handle platform-specific configuration for macOS, Linux, and Windows by applying Electron desktop scaffolding patterns that ensure secure signaling and proper audio device management across the WebRTC mesh.