stream-capture

Transition Response harness capture from blocking to stream-based processing.

Updated May 11, 2026
One-click install
npx skills add https://github.com/AesopScott/mojo --skill stream-capture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stream-capture
Source: https://github.com/AesopScott/mojo/tree/main/harnesses/skills/stream-capture
Command: npx skills add https://github.com/AesopScott/mojo --skill stream-capture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses performance bottlenecks in the Response harness by enabling stream-based capture, which prevents blocking and allows downstream processes to initiate work significantly faster.

Core Features & Use Cases

  • Performance Tuning: Switch between blocking and streaming capture modes to reduce latency and friction.
  • Harness Inspection: Provides a structured runbook to identify slow paths, repeated work, or over-synchronized bottlenecks.
  • Use Case: When a long-running API response is causing UI stalls, use this Skill to implement a streaming capture strategy that processes data chunks as they arrive rather than waiting for the full payload.

Quick Start

Execute the stream-capture command to analyze the current Response harness and propose a streaming configuration change to reduce latency.

Frequently Asked Questions about stream-capture

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

FAQPage Schema
How do I reduce API response latency when long-running processes cause UI stalls?

Stream-based data processing prevents blocking by capturing data chunks as they arrive instead of waiting for the full payload. This allows downstream processes to initiate work significantly faster, directly reducing operational latency and eliminating UI stalls.

What is the difference between blocking capture and streaming capture for performance optimization?

Blocking capture waits for the entire payload before processing, causing friction and UI stalls. Streaming capture processes data chunks as they arrive, significantly reducing latency and allowing downstream processes to initiate work much faster.

How do I identify performance bottlenecks in a Response harness?

Identify performance bottlenecks in the Response harness by using a structured runbook to inspect slow paths, repeated work, or over-synchronized processes. This requires precise identification of the boundary and lever selection for optimization.

When do I need to switch from blocking to streaming data processing?

You need to switch to streaming data processing when long-running API responses are causing UI stalls or when you need to improve system throughput. This transition targets bottlenecks within the Response harness to reduce operational latency.

How do I verify a streaming capture configuration change?

Verify a streaming capture configuration change through positive and boundary testing. This ensures the transition from blocking capture to stream-based processing effectively targets bottlenecks and improves overall throughput.

Can I use stream-capture for performance tuning without specific dependencies?

Yes, stream-capture operates without specific dependencies or components. It provides a structured runbook to analyze your current Response harness and propose streaming configuration changes to reduce latency.