What problem does it solve? Writing deterministic tests for concurrent Effect code is difficult: fibers race, PubSub subscriptions miss events, and TestClock gets misused for non-time-dependent logic. This Skill provides proven patterns for testing Effect's concurrency primitives without flaky race conditions. ## Core Features & Use Cases - Fiber Coordination Patterns: Use Effect.yieldNow, Latch, Deferred, and fiber.pollUnsafe() to coordinate and inspect fibers deterministically. - PubSub and SubscriptionRef Testing: Verify published events with scoped subscriptions, readiness signals, and latch-gated stream subscriptions. - Stream and Interruption Testing: Collect stream results, verify finalizers, and assert interruption with Exit.hasInterrupts and Cause.hasInterruptsOnly. - Use Case: When testing a service that publishes user events to a PubSub, subscribe inside Effect.scoped, trigger the service method, and assert the exact events received with PubSub.takeAll. ## Quick Start Ask the agent to write a deterministic test for a concurrent Effect workflow using the effect-concurrency-testing skill, for example testing a PubSub event publisher or a latch-coordinated fiber.