CtrlK
BlogDocsLog inGet started
Tessl Logo

nestjs-patterns

NestJS architecture patterns for modules, controllers, providers, DTO validation, guards, interceptors, config, and production-grade TypeScript backends. Use when building or reviewing a NestJS backend — modules, providers, DTO validation, guards, or interceptors.

68

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

76%Weight 40%Scale 1-5

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

A concise, actionable patterns reference with executable examples across the NestJS stack. Its main gap is workflow clarity: as a patterns catalog it lacks an explicit sequenced workflow with validation checkpoints, and a few large code blocks could be offloaded to reference files for better progressive disclosure.

Suggestions

Add a short end-to-end workflow (e.g. scaffold module → add DTO + validation → add guard → write test) with an explicit validation/checkpoint step so workflow_clarity can rise above the catalog-style 3.

Move the longer code blocks (bootstrap, exception filter, test harness) into reference files under ./references/ and link to them from SKILL.md to improve progressive disclosure.

For destructive/batch patterns (transactions, multi-step writes), add explicit validate-before-commit guidance to avoid the workflow_clarity cap.

DimensionReasoningScore

Conciseness

Lean code blocks paired with terse bullet rules, assuming NestJS competence without explaining basics; a few explanatory bullets (e.g. "Controllers should stay thin: parse HTTP input, call a provider, return response DTOs") could be trimmed but earn their place.

4 / 5

Actionability

Copy-paste-ready executable TypeScript for bootstrap, modules/controllers/providers, DTOs, guards, exception filters, config, and testing, covering the common NestJS cases concretely.

5 / 5

Workflow Clarity

Content is organized by topic with rough progression (structure → bootstrap → modules → ... → testing) but there is no explicit multi-step workflow with validation checkpoints; the testing snippet shows setup but no validate-fix-retry loop.

3 / 5

Progressive Disclosure

Single well-organized SKILL.md with clearly headed sections and no nested references; no bundle files are present, so content stays one level deep, though some monolithic code blocks could live in reference files.

4 / 5

Total

16

/

20

Passed

Description

92%Weight 40%Scale 1-5

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

A strong, specific description with an explicit Use-when clause and concrete trigger terms anchored to a distinct framework niche. Minor room for broader synonym coverage in the trigger list.

DimensionReasoningScore

Specificity

Enumerates multiple concrete pattern targets — "modules, controllers, providers, DTO validation, guards, interceptors, config" — giving comprehensive coverage of the NestJS architecture surface, matching the multiple-specific-actions anchor.

5 / 5

Completeness

Explicitly states both what ("NestJS architecture patterns for...") and when ("Use when building or reviewing a NestJS backend — modules, providers, DTO validation, guards, or interceptors"), with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural phrases like "building or reviewing a NestJS backend" and the concrete trigger list map well to what a user would say; minor gaps in synonyms keep it just below the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

"NestJS" is a specific framework niche with distinct, framework-scoped triggers, giving minimal overlap risk with unrelated skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
affaan-m/ECC
Reviewed

Table of Contents

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.