output-development

Automate development and debugging of streaming output sinks for UDP, RTSP, WebRTC, and NDI.

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/FacundoDuranDev/Spatial-Iteration-Engine --skill output-development
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: output-development
Source: https://github.com/FacundoDuranDev/Spatial-Iteration-Engine/tree/main/.claude/skills/output-development
Command: npx skills add https://github.com/FacundoDuranDev/Spatial-Iteration-Engine --skill output-development

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlining the development, debugging, and integration of final-output sinks (UDP, RTSP, WebRTC, NDI, previews, notebooks, recorder, and composite) for the streaming engine, with clear patterns and guardrails.

Core Features & Use Cases

  • Provides structured guidance for adding or updating output sinks in adapters/outputs, including subprocess patterns, preview sinks, and composite fan-outs.
  • Documents required interfaces, capabilities, and lifecycle semantics to ensure safe open/close, per-frame write, and resource cleanup.
  • Use Case: when implementing a new UDP sink or RTSP pipeline, follow the patterns to maintain compatibility with the existing outputs/ports contracts.

Quick Start

Review the existing UDP sink pattern and reference implementations to scaffold your own output sink.

Frequently Asked Questions about output-development

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

FAQPage Schema
How do I implement a streaming output sink for UDP or RTSP in Python?▼

To implement a streaming output sink for UDP or RTSP, follow structured subprocess patterns that ensure safe open/close lifecycles, proper per-frame write behavior, and resource cleanup compatible with the existing outputs and ports contracts.

What is a composite fan-out pattern for streaming outputs?▼

A composite fan-out pattern for streaming outputs distributes video frames across multiple downstream sinks simultaneously, using structured guidance to manage safe open/close lifecycles, per-frame writes, and resource cleanup across the Python streaming engine.

How do I ensure safe open/close lifecycles when building Python streaming output sinks?▼

Safe open/close lifecycles for Python streaming output sinks are ensured by following required interface semantics and pattern-based subprocess implementations that guarantee proper resource cleanup and per-frame write behavior during adapter integration.

Does this approach support building WebRTC and NDI output sinks?▼

Yes, this approach supports building WebRTC and NDI output sinks, applying structured patterns and guardrails to maintain safe open/close lifecycles, exhaustive capability reporting, and per-frame write behavior across the streaming engine.

How do I report capabilities for a new preview or notebook sink?▼

To report capabilities for a new preview or notebook sink, follow the documented required interfaces and lifecycle semantics to ensure exhaustive capability reporting alongside safe per-frame write behavior and proper resource cleanup.

What are the limitations when using subprocess patterns for streaming output sinks?▼

Subprocess patterns for streaming output sinks require strict adherence to safe open/close lifecycle semantics and proper resource cleanup to avoid resource leaks, ensuring per-frame write behavior stays compatible with existing adapter contracts.