nestjs-project-starter
Scaffold a production-ready NestJS 10+ API with TypeScript strict mode, modular architecture, validation, Swagger docs, and database integration.
78
72%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./backend-node/nestjs-project-starter/SKILL.mdQuality
Discovery
67%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 excels at specificity and distinctiveness by clearly defining the NestJS framework, version, and specific features. However, it lacks explicit trigger guidance ('Use when...') which limits Claude's ability to know when to select this skill, and could benefit from more natural user-facing keywords beyond technical jargon.
Suggestions
Add a 'Use when...' clause with trigger terms like 'create NestJS project', 'scaffold backend', 'new API', 'nest.js setup'
Include common user variations: 'nest.js', 'backend API', 'REST API', 'Node.js API framework', 'create new project'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Scaffold a production-ready NestJS 10+ API' with specific features including 'TypeScript strict mode, modular architecture, validation, Swagger docs, and database integration.' | 3 / 3 |
Completeness | Clearly answers 'what' (scaffold NestJS API with specific features) but lacks explicit 'when' guidance - no 'Use when...' clause or trigger conditions specified. | 2 / 3 |
Trigger Term Quality | Includes relevant technical terms like 'NestJS', 'TypeScript', 'Swagger', 'API', but missing common user variations like 'nest.js', 'backend', 'REST API', 'create API', or 'new project'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting NestJS 10+ with particular configuration choices; unlikely to conflict with generic API or TypeScript skills due to framework-specific focus. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, highly actionable NestJS starter skill with excellent executable code examples and clear workflow guidance. The main weaknesses are moderate verbosity (explaining some concepts Claude knows) and a monolithic structure that could benefit from progressive disclosure via linked reference files for advanced patterns.
Suggestions
Remove explanatory statements Claude already knows (e.g., 'Services contain business logic; controllers are thin routing layers') to improve conciseness
Split detailed patterns (interceptors, filters, guards, entities) into a separate PATTERNS.md or REFERENCE.md file, keeping SKILL.md as a quick-start overview with links
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some content Claude already knows (e.g., basic NestJS concepts like 'Services contain business logic; controllers are thin routing layers'). The extensive code examples are valuable but could be trimmed in places. | 2 / 3 |
Actionability | Excellent actionability with fully executable, copy-paste ready code examples for every major pattern (main.ts, DTOs, controllers, services, entities, guards, interceptors, filters). Commands are specific and complete. | 3 / 3 |
Workflow Clarity | Clear sequential workflow in 'First Steps After Scaffold' section with numbered steps. The scaffold command section provides explicit ordering, and common commands are well-organized by purpose (dev, prod, test, migrations). | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but it's a monolithic document (~300 lines) that could benefit from splitting detailed patterns (TypeORM entity, interceptors, filters) into separate reference files. No external file references are provided. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- achreftlili/deep-dev-skills
- Commit
181fcbc
- 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.