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.
90
86%
Does it follow best practices?
Impact
91%
1.01xAverage score across 6 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that thoroughly covers the NestJS domain with specific actions, comprehensive trigger terms, and clear guidance on when to invoke the skill. It uses proper third-person voice throughout and provides enough specificity to distinguish it from general TypeScript or other backend framework skills. The description is detailed without being unnecessarily verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: creating modules, controllers, services, DTOs, guards, interceptors, implementing dependency injection, scaffolding modular architecture, adding JWT/Passport authentication, integrating TypeORM or Prisma, and more. | 3 / 3 |
Completeness | Clearly answers both 'what' (creates and configures NestJS modules, controllers, services, etc.) and 'when' with explicit trigger clauses ('Use when building NestJS REST APIs...', 'Invoke for guards, interceptors...'). The 'Use when' and 'Invoke for' clauses provide comprehensive trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'NestJS', 'REST APIs', 'GraphQL', 'dependency injection', 'JWT', 'Passport', 'TypeORM', 'Prisma', '.module.ts', '.controller.ts', '.service.ts', 'guards', 'interceptors', 'pipes', 'Swagger', 'unit testing', 'E2E testing'. These are all terms a developer would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche focused specifically on NestJS framework. The mention of NestJS-specific concepts like .module.ts files, NestJS guards/interceptors/pipes, and NestJS-specific tooling (TypeORM/Prisma integration in NestJS context) makes it very unlikely to conflict with generic TypeScript or other backend framework skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured NestJS skill with strong actionability through complete, executable code examples and a well-organized reference table for progressive disclosure. Its main weaknesses are moderate verbosity (some inline content could be in reference files, and there's some fluff text) and a workflow that lacks explicit feedback loops for error recovery. The constraints section is particularly strong with clear MUST DO / MUST NOT DO lists.
Suggestions
Add explicit feedback loops to the Core Workflow (e.g., 'If lint/tests fail → fix issues → re-run before proceeding') to improve workflow clarity.
Remove the introductory tagline and the 'Knowledge Reference' keyword list at the bottom — they add no actionable value and waste tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary elements. The opening line 'Senior NestJS specialist with deep expertise in enterprise-grade, scalable TypeScript backend applications' is fluff. The 'Knowledge Reference' section at the bottom is just a keyword list that adds no value. The code examples are thorough but lengthy — the module definition and unit test examples could arguably be in reference files rather than inline. However, the constraints and output templates sections are tight and useful. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready TypeScript code examples covering controllers, services, modules, DTOs, and unit tests. The constraints are specific and concrete (e.g., 'Use `@Injectable()` and constructor injection', 'enable `ValidationPipe` globally'). The output templates section gives a clear ordering for deliverables. | 3 / 3 |
Workflow Clarity | The Core Workflow provides a clear 6-step sequence with a verification step (step 5: `npm run lint`, `npm run test`, `nest info`), which is good. However, there's no explicit feedback loop — no 'if lint fails, fix and re-run' or 'if tests fail, debug and re-verify' guidance. For an enterprise-grade skill involving DI wiring and module configuration, the absence of explicit error recovery/validation loops is a gap. | 2 / 3 |
Progressive Disclosure | Excellent use of progressive disclosure with a clear reference table pointing to 6 separate reference files with explicit 'Load When' conditions. The main skill provides a concise overview with inline examples for the most common patterns, while deferring detailed guidance to one-level-deep references. Navigation is clear and well-signaled. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- jeffallan/claude-skills
- Commit
3d95bb1
- 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.