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.
86
82%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
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 covers all evaluation dimensions at the highest level. It provides specific concrete actions, comprehensive trigger terms that developers would naturally use, explicit 'Use when' and 'Invoke for' clauses, and is clearly distinguishable as a NestJS-specific skill. The description is thorough 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 triggers ('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 development. The mention of NestJS-specific concepts like .module.ts files, NestJS guards/interceptors/pipes, and NestJS-specific tooling makes it very unlikely to conflict with generic TypeScript or other backend framework skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable NestJS skill with excellent executable code examples covering the core patterns (controller, service, module, DTO, test). Its main weaknesses are the lack of explicit validation/feedback loops in the workflow for what is a multi-step, multi-file process, and some verbosity in areas where Claude's existing knowledge could be assumed. The reference table is well-designed but unverifiable without bundle files.
Suggestions
Add explicit feedback loops to the Core Workflow, e.g., 'If lint fails, fix errors before proceeding to test' and 'If DI graph shows circular dependencies, refactor module imports before continuing.'
Consider moving the large inline code examples to a referenced file (e.g., references/examples.md) and keeping only a minimal example inline to improve the overview-to-detail ratio.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but the opening line ('Senior NestJS specialist with deep expertise...') is unnecessary persona fluff, and some constraints restate things Claude already knows (e.g., 'never instantiate services with new', 'don't expose passwords'). The code examples are substantial but justified given the complexity of NestJS patterns. | 2 / 3 |
Actionability | Excellent actionability — provides fully executable, copy-paste-ready TypeScript code for controllers, services, modules, DTOs, and unit tests. Each example includes proper imports, decorators, and realistic error handling patterns. The constraints and output templates give concrete, specific guidance. | 3 / 3 |
Workflow Clarity | The Core Workflow section provides a clear 6-step sequence, and step 5 includes specific verification commands (`npm run lint`, `npm run test`, `nest info`). However, there are no explicit validation checkpoints or feedback loops between steps — e.g., no 'if lint fails, fix before proceeding' or 'if DI graph shows issues, resolve circular deps before testing.' For an enterprise-grade workflow involving multiple interconnected files, this gap is notable. | 2 / 3 |
Progressive Disclosure | The reference table is well-structured with clear 'Load When' guidance, pointing to six separate reference files. However, since no bundle files are provided, we cannot verify these references exist. The main SKILL.md also includes substantial inline code examples (~100+ lines) that could arguably live in a referenced examples file, making the main file heavier than ideal for an overview. | 2 / 3 |
Total | 9 / 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
5e8b6b8
- 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.