effect-concurrency

Manage Effect application concurrency with fibers, forking, joining, and racing.

187|20|Updated Nov 20, 2025
One-click install
npx skills add https://github.com/TheBushidoCollective/han --skill effect-concurrency
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: effect-concurrency
Source: https://github.com/TheBushidoCollective/han/tree/main/jutsu/jutsu-effect/skills/effect-concurrency
Command: npx skills add https://github.com/TheBushidoCollective/han --skill effect-concurrency

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill covers concurrency patterns in Effect using fibers, forking, joining, and racing.

Core Features & Use Cases

  • Fibers & Fork/Join: Launch and join concurrent effects.
  • Parallel Execution: Run effects in parallel with control.
  • Race & Interruption: Race between effects and interrupt when needed.

Quick Start

Fork two effects, join their results, and race a timeout against a long operation.

Frequently Asked Questions about effect-concurrency

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

FAQPage Schema
How do I manage concurrent tasks in Effect applications?

Effect concurrency uses fibers to manage concurrent tasks. Fork effects to run them concurrently, join to collect results, and interrupt to stop tasks when needed. This gives you fine-grained control over lifecycle and coordination.

Can I run multiple Effect operations in parallel?

Yes. Effect provides parallel execution patterns like `all` and `forEach` to run effects concurrently with controlled concurrency levels. These compose multiple effects and coordinate their results automatically.

How do I add timeout handling to long-running Effect operations?

Use the race pattern to compete a timeout against a long operation. Effect's race logic interrupts the slower effect, allowing you to cancel operations that exceed your time limit.

What's the best way to coordinate workflows with precise task lifecycle control?

Fibers provide lifecycle operations: fork to launch, join to await results, await to block, poll to check status, and interrupt to stop. This enables coordinated workflows with exact control over when tasks start, complete, and terminate.

Can I handle concurrent data fetches and long-running tasks together?

Yes. Fork multiple data-fetch effects concurrently, join their results, and apply race or timeout patterns as needed. Effect's fiber model scales from simple data fetches to complex coordinated workflows.