nestjs-expert

Creates and configures NestJS modules, controllers, services, DTOs, guards, and interceptors for enterprise-grade TypeScript backend applications. Use when building NestJS REST APIs or GraphQL services, implementing dependency injection, scaffolding modular architecture, adding JWT/Passport authentication, integrating TypeORM or Prisma, or working with .module.ts, .controller.ts, and .service.ts files. Invoke for guards, interceptors, pipes, validation, Swagger documentation, and unit/E2E testing in NestJS projects.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Failed to scan

The risk profile of this skill

Quality

Content

86%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 well-structured and highly actionable, with executable examples, real reference files, and a verification checkpoint. The only slack is minor: a redundant buzzword "Knowledge Reference" line and an implicit rather than explicit fix-and-retry loop.

Suggestions

Remove or shrink the "Knowledge Reference" buzzword line—it lists tools (TypeORM, Prisma, Jest, etc.) Claude already knows and adds no signal.

Make the workflow's feedback loop explicit in step 5, e.g. "If lint/tests fail, fix and re-run before proceeding."

Consider trimming the inline controller/service/module examples since equivalent guidance lives in references/, keeping SKILL.md as a tighter overview.

Dimension	Reasoning	Score
Conciseness	Largely lean—Core Workflow, constraints, and templates are tight—but the "Knowledge Reference" line is a buzzword list Claude already knows and inline code examples partially duplicate the reference files. Not 5 due to that minor padding; not 3 because the bulk of every section earns its place.	4 / 5
Actionability	Four complete, copy-paste-ready TypeScript blocks (DTO+controller, service, module, unit test) plus concrete commands ("npm run lint", "npm run test", "nest info") cover the common cases fully. Not below 5 because guidance is executable end-to-end with no pseudocode.	5 / 5
Workflow Clarity	The 6-step Core Workflow has an explicit Verify checkpoint (step 5) before testing, but the fix-and-re-validate feedback loop is only implicit. Not 5 because the retry loop is not stated; not 3 because a real validation checkpoint with concrete commands is present.	4 / 5
Progressive Disclosure	A Reference Guide table signals six real one-level-deep reference files (verified present in references/) with "Load When" navigation, while SKILL.md stays an overview. Not below 5 because the split is clean and navigation is explicit.	5 / 5
	Total	18 / 20 Passed

Description

100%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 exemplary: third-person voice, a comprehensive concrete capability list, explicit "Use when"/"Invoke for" triggers, and distinct NestJS-scoped keywords including file extensions. It cleanly satisfies every dimension at the top anchor.

Dimension	Reasoning	Score
Specificity	Enumerates concrete artifacts—"modules, controllers, services, DTOs, guards, and interceptors"—giving comprehensive, specific actions rather than generic language. Not below 5 because coverage is broad and each named item is a concrete NestJS construct.	5 / 5
Completeness	Explicitly answers what ("Creates and configures NestJS modules...") and when ("Use when building...", "Invoke for...") with concrete trigger phrases. Not 4 because both halves are fully explicit rather than weakly implied.	5 / 5
Trigger Term Quality	Natural user-facing terms ("NestJS REST APIs", "JWT/Passport authentication", "TypeORM or Prisma") plus file extensions (".module.ts, .controller.ts, and .service.ts") give comprehensive synonym and extension coverage. Not below 5 because both colloquial and file-level triggers are present.	5 / 5
Distinctiveness Conflict Risk	A clearly bounded NestJS niche with file-extension triggers and framework-specific terms minimizes overlap with other skills. Not below 5 because the triggers are unmistakably NestJS-scoped.	5 / 5
	Total	20 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Jeffallan/claude-skills
Path: skills/nestjs-expert/SKILL.md
Commit: 882ef55

Reviewed: 5 days 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.