How do I install the Nestjs Interceptors skill?

Run npx skillmds@latest add dkmqflx/nestjs-interceptors in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Nestjs Interceptors safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Nestjs Interceptors?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Nestjs Interceptors free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Nestjs Interceptors?

dkmqflx (@dkmqflx) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Nestjs Interceptors by dkmqflx — Agent Skill

Name: Nestjs Interceptors
Author: dkmqflx

Nestjs Interceptors

NestJS interceptors best practices. Use when writing or reviewing NestJS interceptors — response transformation, logging, timeouts, or caching around handlers. Triggers on NestInterceptor, intercept(), CallHandler, map(), or @UseInterceptors.

dkmqflx dae2a1f 7 files · 11.6 KB Updated Sep 17, 2026

File contents

NestJS Interceptors

Interceptors are @Injectable() classes implementing NestInterceptor. Their intercept(context: ExecutionContext, next: CallHandler) method runs logic before the route handler and transforms the response stream returned by next.handle() using RxJS operators. They are the idiomatic place for cross-cutting concerns — response shaping, logging, timeouts, caching — that should stay out of controllers and services.

When to Apply

Apply these rules when you are:

Writing or reviewing a class that implements NestInterceptor.
Wrapping handler responses in a consistent envelope.
Adding request/response logging or latency measurement.
Enforcing per-request timeouts.
Caching GET responses with CacheInterceptor.
Deciding whether to bind an interceptor globally, per-controller, or per-route.

Do not reach for an interceptor when the work is core business logic — that belongs in a service (see interceptors-not-for-mutation-logic).

Rules

Rule	Impact	Summary
response-transform-interceptor	HIGH	Wrap responses in a consistent envelope via `map()`.
logging-interceptor	MEDIUM	Measure handler duration with `tap()`; log method/url/time.
timeout-interceptor	HIGH	Fail slow requests with `timeout()` + `RequestTimeoutException`.
cache-interceptor	MEDIUM	Cache GET responses with `CacheInterceptor` + `CacheModule`.
interceptors-not-for-mutation-logic	HIGH	Keep business logic in services; interceptors are cross-cutting only.
bind-globally-vs-scoped	MEDIUM	Prefer `APP_INTERCEPTOR` for DI-friendly global binding.

How to Use

Identify the cross-cutting concern (transform, log, timeout, cache).
Open the matching rule file and follow the Correct pattern.
Keep intercept() thin — pipe RxJS operators onto next.handle(), never put domain logic inside.
Choose a binding scope with bind-globally-vs-scoped: route, controller, or global via APP_INTERCEPTOR.

---name: nestjs-interceptorsdescription: NestJS interceptors best practices. Use when writing or reviewing NestJS interceptors — response transformation, logging, timeouts, or caching around handlers. Triggers on NestInterceptor, intercept(), CallHandler, map(), or @UseInterceptors.license: MIT---# NestJS InterceptorsInterceptors are `@Injectable()` classes implementing `NestInterceptor`. Their`intercept(context: ExecutionContext, next: CallHandler)` method runs logicbefore the route handler and transforms the response stream returned by`next.handle()` using RxJS operators. They are the idiomatic place forcross-cutting concerns — response shaping, logging, timeouts, caching — thatshould stay out of controllers and services.## When to ApplyApply these rules when you are:- Writing or reviewing a class that implements `NestInterceptor`.- Wrapping handler responses in a consistent envelope.- Adding request/response logging or latency measurement.- Enforcing per-request timeouts.- Caching GET responses with `CacheInterceptor`.- Deciding whether to bind an interceptor globally, per-controller, or per-route.Do **not** reach for an interceptor when the work is core business logic — thatbelongs in a service (see `interceptors-not-for-mutation-logic`).## Rules| Rule | Impact | Summary || --- | --- | --- || [response-transform-interceptor](rules/response-transform-interceptor.md) | HIGH | Wrap responses in a consistent envelope via `map()`. || [logging-interceptor](rules/logging-interceptor.md) | MEDIUM | Measure handler duration with `tap()`; log method/url/time. || [timeout-interceptor](rules/timeout-interceptor.md) | HIGH | Fail slow requests with `timeout()` + `RequestTimeoutException`. || [cache-interceptor](rules/cache-interceptor.md) | MEDIUM | Cache GET responses with `CacheInterceptor` + `CacheModule`. || [interceptors-not-for-mutation-logic](rules/interceptors-not-for-mutation-logic.md) | HIGH | Keep business logic in services; interceptors are cross-cutting only. || [bind-globally-vs-scoped](rules/bind-globally-vs-scoped.md) | MEDIUM | Prefer `APP_INTERCEPTOR` for DI-friendly global binding. |## How to Use1. Identify the cross-cutting concern (transform, log, timeout, cache).2. Open the matching rule file and follow the **Correct** pattern.3. Keep `intercept()` thin — pipe RxJS operators onto `next.handle()`, never put domain logic inside.4. Choose a binding scope with `bind-globally-vs-scoped`: route, controller, or global via `APP_INTERCEPTOR`.

Frequently asked questions