nestjs-expert
tessl i github:jeffallan/claude-skills --skill nestjs-expertUse when building NestJS applications requiring modular architecture, dependency injection, or TypeScript backend development. Invoke for modules, controllers, services, DTOs, guards, interceptors, TypeORM/Prisma.
Review Score
67%
Validation Score
12/16
Implementation Score
42%
Activation Score
90%
Generated
Validation
Total
12/16Score
Passed| Criteria | Score |
|---|---|
metadata_version | 'metadata' field is not a dictionary |
license_field | 'license' field is missing |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata |
body_examples | No examples detected (no code fences and no 'Example' wording) |
Implementation
Suggestions 4
Score
42%Overall Assessment
This skill has strong structural organization with excellent progressive disclosure through its reference table, but critically lacks actionable content. It reads more like a job description than executable guidance - telling Claude what a NestJS expert does without showing concrete code examples, specific commands, or copy-paste ready implementations.
Suggestions
- Add executable code examples for at least one common pattern (e.g., a complete controller with service, DTO, and Swagger decorators)
- Replace the abstract 'Output Templates' list with an actual example showing the expected output format
- Remove or condense the 'Role Definition' section - Claude doesn't need persona framing to execute the skill
- Add validation checkpoints to the Core Workflow (e.g., 'Run `nest build` to verify no TypeScript errors before proceeding')
| Dimension | Score | Reasoning |
|---|---|---|
Conciseness | 2/3 | The content is reasonably efficient but includes some unnecessary framing ('Senior NestJS specialist with deep expertise...', 'You are a senior Node.js engineer with 10+ years...') that Claude doesn't need. The role definition section adds little actionable value. |
Actionability | 1/3 | The skill provides no concrete code examples, commands, or executable guidance. It describes what to do ('Use dependency injection', 'Validate all inputs') but never shows how with actual code. The 'Output Templates' section lists what to provide but gives no examples. |
Workflow Clarity | 2/3 | The 5-step core workflow provides a clear sequence but lacks validation checkpoints or feedback loops. There's no guidance on what to do if something fails or how to verify each step succeeded before proceeding. |
Progressive Disclosure | 3/3 | Excellent use of a reference table with clear topics, file paths, and 'Load When' conditions. References are one level deep and well-signaled. The main skill serves as a proper overview pointing to detailed materials. |
Activation
Suggestions 2
Score
90%Overall Assessment
This is a solid skill description with excellent trigger term coverage and clear 'when to use' guidance. The main weakness is that it lists NestJS concepts without describing concrete actions the skill performs (e.g., 'create modules', 'configure dependency injection', 'generate DTOs'). The description tells Claude when to select it but not precisely what it will do.
Suggestions
- Add concrete action verbs describing what the skill does, e.g., 'Creates and configures NestJS modules, controllers, and services' rather than just listing component names
- Consider adding file extension triggers like '.module.ts', '.controller.ts', '.service.ts' for even better matching
| Dimension | Score | Reasoning |
|---|---|---|
Specificity | 2/3 | Names the domain (NestJS) and lists architectural concepts (modules, controllers, services, DTOs, guards, interceptors, TypeORM/Prisma), but doesn't describe concrete actions like 'create', 'configure', or 'implement'. It lists components rather than what the skill actually does with them. |
Completeness | 3/3 | Explicitly answers both 'what' (NestJS applications with modular architecture, DI, TypeScript backend) and 'when' with clear trigger guidance ('Use when building NestJS applications...', 'Invoke for modules, controllers...'). The 'Use when' clause is present and explicit. |
Trigger Term Quality | 3/3 | Excellent coverage of natural terms users would say: 'NestJS', 'modular architecture', 'dependency injection', 'TypeScript backend', 'modules', 'controllers', 'services', 'DTOs', 'guards', 'interceptors', 'TypeORM', 'Prisma'. These are all terms developers naturally use when working with NestJS. |
Distinctiveness Conflict Risk | 3/3 | Highly distinctive with NestJS-specific terminology (guards, interceptors, DTOs, TypeORM/Prisma integration). Unlikely to conflict with generic TypeScript or other backend framework skills due to the specific NestJS ecosystem terms. |