Skip to content
Back to skills

Effect Module Request

ASecurity

Guidance for `effect/Request` focused on APIs like of, fail, and succeed. Load after `effect-skill-router` when this module is the primary owner.

  • 57 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added October 17, 2026
documentationapi

Works with

  • api

Security analysis

A100/100

Scanned October 17, 2026

npx -y skills add diegosouzapw/awesome-omni-skill --skill effect-module-request --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Effect Module Request?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Effect Module Request
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/diegosouzapw-effect-module-request/badge)](https://www.skillsdirectory.com/skills/diegosouzapw-effect-module-request)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: effect-module-request
description: Guidance for `effect/Request` focused on APIs like of, fail, and succeed. Load after `effect-skill-router` when this module is the primary owner.
---

# Effect Module Request

## Owned scope

- Owns only `effect/Request`.
- Source of truth: `packages/effect/src/Request.ts`.

## What it is for

- The `Request` module provides a way to model requests to external data sources in a functional and composable manner. Requests represent descriptions of operations that can be batched, cached, and executed efficiently.

## API quick reference

- `of`
- `fail`
- `succeed`
- `Services`
- `failCause`
- `makeEntry`
- `isRequest`
- `Any`
- `Class`
- `Entry`
- `Error`
- `Result`
- `tagged`
- `Request`
- `Success`
- `complete`
- `Variance`
- `Constructor`
- Full API list: `references/api-reference.md`

## How to use it

- Start with constructor-style APIs to build values/services before composing operations.
- Use the reference docs to select the smallest API surface that solves your task.
- Validate behavior against existing tests before introducing new usage patterns.

## Starter example

```ts
import type { Request } from "effect";

// Define a request that fetches a user by ID
interface GetUser extends Request.Request<string, Error> {
  readonly _tag: "GetUser";
  readonly id: number;
}

// Define a request that fetches all users
interface GetAllUsers extends Request.Request<ReadonlyArray<string>, Error> {
  readonly _tag: "GetAllUsers";
}
```

## Common pitfalls

- Prefer explicit, typed combinators over ad-hoc casting or unchecked assumptions.

## Not covered here

- Adjacent modules in `effect/*` and `effect/unstable/*` are out of scope for this owner.

## Escalate to

- `effect-skill-router` for routing and ownership checks.

## Reference anchors

- Module source: `packages/effect/src/Request.ts`
- Representative tests: `packages/effect/test/Request.test.ts`
- API details: `references/api-reference.md`
- Usage notes: `references/usage-reference.md`
- Ownership mapping: `references/owner.md`

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.