nestjs-expert
Use when building NestJS applications requiring modular architecture, dependency injection, or TypeScript backend development. Invoke for modules, controllers, services, DTOs, guards, interceptors, TypeORM/Prisma.
Install with Tessl CLI
npx tessl i github:jeffallan/claude-skills --skill nestjs-expert73
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillAgent success when using this skill
Validation for skill structure
Discovery
89%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 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: '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 | Reasoning | Score |
|---|---|---|
Specificity | 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. | 2 / 3 |
Completeness | 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' and 'Invoke for' clauses provide explicit trigger conditions. | 3 / 3 |
Trigger Term Quality | 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. | 3 / 3 |
Distinctiveness Conflict Risk | 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. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill has strong progressive disclosure with a well-organized reference table, but critically lacks actionable code examples. The content describes what to do conceptually but never shows how with executable code. The role-playing framing adds unnecessary tokens without improving guidance.
Suggestions
Add executable code examples for at least one common pattern (e.g., a basic controller with DTO validation and Swagger decorators)
Remove the role-playing framing ('You are a senior Node.js engineer...') - Claude doesn't need persona instructions
Add validation checkpoints to the workflow, such as 'Run `npm run lint` after implementing' or 'Verify DI with `nest info`'
Replace abstract constraints like 'Use dependency injection for all services' with concrete examples showing the pattern
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill 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 core content is reasonably efficient but could be tighter. | 2 / 3 |
Actionability | The skill provides no executable code examples, only abstract descriptions like 'Use dependency injection for all services' and 'Validate all inputs with class-validator'. There are no concrete code snippets, commands, or copy-paste ready examples. | 1 / 3 |
Workflow Clarity | The 5-step core workflow is listed but lacks validation checkpoints or feedback loops. Steps like 'Implement' and 'Secure' are vague without concrete verification steps or error recovery guidance. | 2 / 3 |
Progressive Disclosure | Excellent use of a reference table with clear one-level-deep links to specific topics. The 'Load When' column provides good navigation signals for when to access each reference file. | 3 / 3 |
Total | 8 / 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.
- 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.