nestjs-patterns

NestJS architecture patterns for modules, controllers, providers, DTO validation, guards, interceptors, config, and production-grade TypeScript backends.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is lean, highly actionable, and free of concept-explanation padding, with executable code throughout. Its weaknesses are the absence of validation-checkpoint workflows for risky operations and a lack of progressive disclosure into separate reference files.

Suggestions

Add an explicit validation/verification checkpoint workflow for transactional multi-step writes (e.g. open transaction -> perform writes -> commit/rollback with a re-verify step).

Split the larger reference material (e.g. full exception filter and project structure) into one-level-deep reference files linked from the overview to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Each section pairs a compact code example with 2–3 terse principle bullets and never pads with explanations of what NestJS or its primitives are, assuming Claude's competence throughout.	3 / 3
Actionability	Code blocks are executable NestJS TypeScript (ValidationPipe options, @Module/@Controller/@Injectable, class-validator DTOs, ExceptionFilter, Test.createTestingModule) with specific decorators and options, making them copy-paste ready.	3 / 3
Workflow Clarity	Content is well-organized topically and the bootstrap sequence is clear, but there is no multi-step workflow with explicit validation checkpoints, and risky operations like transactions are mentioned without feedback loops, capping the score at 2.	2 / 3
Progressive Disclosure	Section headers provide easy navigation, but the entire ~230-line skill is a monolithic single file with all content inline and no one-level-deep references to deeper materials (no bundle files exist).	2 / 3
	Total	10 / 12 Passed

Description

72%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is domain-rich and uses strong, natural NestJS trigger terms with a clear niche, but it reads as a noun-phrase capability list rather than concrete actions and omits an explicit 'Use when...' trigger clause.

Suggestions

Reword as concrete actions, e.g. 'Structure NestJS modules, controllers, and providers; validate DTOs; apply guards and interceptors; configure env-aware settings.'

Add an explicit trigger clause such as 'Use when building or refactoring NestJS APIs, services, or TypeScript backends.'

Dimension	Reasoning	Score
Specificity	The description names the NestJS domain and many building blocks ('modules, controllers, providers, DTO validation, guards, interceptors, config') but enumerates them as nouns/categories rather than concrete verb-based actions. It is richer than the vague anchor 1 but does not list specific actions like 'build', 'validate', or 'apply' required for a 3.	2 / 3
Completeness	It clearly answers 'what' (NestJS architecture patterns for the listed areas) but provides no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	'NestJS', 'controllers', 'providers', 'guards', 'interceptors', 'DTO validation', and 'TypeScript backends' are exactly the natural terms a user would say when requesting NestJS help, giving good coverage.	3 / 3
Distinctiveness Conflict Risk	'NestJS' is a strong, framework-specific trigger giving the skill a clear niche that is unlikely to conflict with other skills.	3 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Commit: 4130457

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.