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.

59

Quality

69%

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

Fix and improve this skill with Tessl

tessl review fix ./.kiro/skills/nestjs-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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.

The body is efficient, actionable, and well-structured with executable TypeScript across most topics, but it is a reference catalog without sequenced workflows or validation checkpoints, and a few sections lack code examples. Splitting the densest sections into reference files would improve progressive disclosure.

Suggestions

Add a short executable example to the Persistence/Transactions and Production Defaults sections to close the actionability gaps.

For destructive or multi-step operations (e.g., transactional writes), include an explicit validate-then-proceed checkpoint to raise workflow clarity.

Consider moving the full exception-filter and testing harness examples into one-level-deep reference files with clear links from SKILL.md.

DimensionReasoningScore

Conciseness

Each section pairs a tight code block with 2-3 terse bullet rules and assumes NestJS familiarity rather than explaining basics; a few advisory bullets could still be trimmed, keeping it just below the leanest anchor.

4 / 5

Actionability

Most sections (bootstrap, modules, DTOs, guards, exception filter, config, testing) give copy-paste-ready TypeScript, but Persistence and Production Defaults are bullet-only with no executable example, leaving minor gaps.

4 / 5

Workflow Clarity

The skill is a topical patterns catalog with logical section ordering rather than a sequenced multi-step workflow, and it lacks explicit validation checkpoints or feedback loops, so it sits at the midpoint.

3 / 5

Progressive Disclosure

A single well-organized SKILL.md with clear section headers and no nested references; content is appropriately placed inline for a patterns overview, though a couple of dense sections (exception filter, testing) could optionally split into reference files.

4 / 5

Total

15

/

20

Passed

Description

70%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.

The description is specific and distinctively NestJS-scoped with strong trigger terms, but it lacks an explicit "Use when..." activation clause, which caps its completeness. Adding a when-to-use phrase would lift the completeness and overall score.

Suggestions

Append an explicit trigger clause such as "Use when building or refactoring NestJS APIs, services, or modules" to satisfy the "when" half of completeness.

Mention exception filters, persistence/transactions, and testing in the description so capability coverage matches the body.

Add natural synonyms like "services" and "APIs" to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the NestJS domain and lists several concrete capability areas ("modules, controllers, providers, DTO validation, guards, interceptors, config"), but omits topics present in the body (exception filters, persistence, testing), leaving minor coverage gaps.

4 / 5

Completeness

It has a clear "what" (NestJS architecture patterns for the listed concerns) but no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Includes natural terms a user would say ("NestJS", "controllers", "providers", "guards", "DTO validation", "TypeScript backends") with good coverage, though a few natural synonyms ("services", "API", "modules" as a standalone trigger) are thin.

4 / 5

Distinctiveness Conflict Risk

NestJS-specific terms (guards, interceptors, providers, DTO validation) carve a clear niche with distinct triggers and minimal conflict risk against generic TypeScript or backend skills.

5 / 5

Total

16

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

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.