effect-streams-pipelines

Construct streaming data pipelines with backpressure and concurrency control.

Updated Nov 20, 2025
One-click install
npx skills add https://github.com/mepuka/adjunct --skill effect-streams-pipelines
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: effect-streams-pipelines
Source: https://github.com/mepuka/adjunct/tree/main/.claude/skills/effect-streams-pipelines
Command: npx skills add https://github.com/mepuka/adjunct --skill effect-streams-pipelines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stream creation, transformation, sinks, batching, and resilience for building data pipelines with controlled concurrency and memory usage.

Core Features & Use Cases

  • Create/transform/consume streams
  • Resource-safe pipelines with acquireRelease
  • Resilient streaming with retry and backpressure

Quick Start

Build a stream from a list, map, group, and drain with a controlled concurrency.

Frequently Asked Questions about effect-streams-pipelines

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

FAQPage Schema
How do I build data pipelines with backpressure and concurrency control?

Backpressure in data pipelines prevents memory overflow by controlling consumption rate relative to production. This Skill automates pipeline construction with built-in concurrency tuning, batching, and backpressure-aware transformations (mapEffect, filter, grouped) across streams, networks, and storage backends.

Can I process large-scale streaming data without exhausting memory?

Yes. This Skill provides memory-sensitive streaming for large-scale processing through resource-safe patterns (acquireRelease), controlled concurrency per transformation, and batching—enabling safe I/O across networks and storage while maintaining backpressure.

How do I handle failures and retries in streaming data pipelines?

The Skill includes resilience patterns with retry logic and backpressure awareness, allowing you to recover from transient failures in stream transformations without losing data or control over concurrency.

What's the best way to structure streaming transformations with per-item concurrency?

Use pipe-based transformations with mapEffect to tune concurrency per operation, combined with grouped and filter stages. This lets you balance throughput and resource usage across individual items in the pipeline.

When should I use streaming pipelines instead of batch processing?

Use streaming when you need continuous, memory-bounded processing of unbounded data with controlled concurrency. Streaming excels for I/O-heavy workloads, backpressure-sensitive operations, and systems where resource predictability matters.

Do I need external dependencies to build and run streams?

No. This Skill has zero external dependencies, providing self-contained stream construction, transformation, and consumption with built-in resource safety and resilience patterns.