nestjs-best-practices
NestJS best practices and architecture patterns for building production-ready applications. This skill should be used when writing, reviewing, or refactoring NestJS code to ensure proper patterns for modules, dependency injection, security, and performance.
Install with Tessl CLI
npx tessl i github:Kadajett/agent-nestjs-skills --skill nestjs-best-practices73
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
75%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 adequately identifies when to use the skill and targets a specific framework (NestJS), making it reasonably complete and distinctive. However, it lacks concrete action verbs describing what the skill actually does and could benefit from more natural trigger terms that users commonly use when working with NestJS.
Suggestions
Replace abstract 'best practices and architecture patterns' with specific actions like 'Configure guards and interceptors, structure module hierarchies, implement custom decorators, set up dependency injection'
Add more natural trigger terms users would say: 'Nest.js', 'decorators', 'guards', 'pipes', 'interceptors', 'providers', 'controllers', '@Injectable', '@Module'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (NestJS) and mentions some areas (modules, dependency injection, security, performance) but doesn't list concrete actions - 'best practices and architecture patterns' is somewhat abstract rather than specific actions like 'configure guards', 'implement interceptors', or 'structure module hierarchies'. | 2 / 3 |
Completeness | Clearly answers both what ('NestJS best practices and architecture patterns for building production-ready applications') and when ('when writing, reviewing, or refactoring NestJS code') with explicit trigger scenarios for modules, DI, security, and performance. | 3 / 3 |
Trigger Term Quality | Includes relevant keywords like 'NestJS', 'modules', 'dependency injection', 'security', 'performance' but misses common variations users might say such as 'Nest.js', 'nest framework', 'decorators', 'guards', 'pipes', 'interceptors', 'providers', or 'controllers'. | 2 / 3 |
Distinctiveness Conflict Risk | NestJS is a specific framework with distinct terminology; the description clearly targets NestJS-specific patterns and would be unlikely to conflict with general Node.js, Express, or other framework skills due to explicit NestJS mentions. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill excels as a well-organized index and navigation hub for NestJS best practices, with excellent conciseness and progressive disclosure. However, it critically lacks actionability - there are no concrete code examples, commands, or executable guidance within the skill itself, making it essentially a table of contents rather than a teaching document.
Suggestions
Add at least 2-3 concrete code examples for the highest-priority rules (e.g., arch-avoid-circular-deps, di-prefer-constructor-injection) showing incorrect vs correct patterns inline
Include a brief workflow section explaining how to apply these rules during code review or refactoring (e.g., 'Start with CRITICAL rules, validate with linting, then address HIGH priority items')
Add a quick-start example showing a minimal correct NestJS module structure that demonstrates multiple best practices together
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and well-organized as a reference index. It avoids explaining what NestJS is or basic concepts Claude already knows, using tables and bullet lists efficiently to maximize information density. | 3 / 3 |
Actionability | The skill provides no executable code examples, commands, or concrete implementation guidance. It's entirely a reference index pointing to external files without any copy-paste ready content in the skill itself. | 1 / 3 |
Workflow Clarity | The 'When to Apply' section provides clear use cases, and rules are prioritized by impact. However, there's no workflow for how to actually apply these rules, no validation steps, and no sequence for refactoring or reviewing code. | 2 / 3 |
Progressive Disclosure | Excellent structure with a clear overview, categorized quick reference, and well-signaled one-level-deep references to individual rule files. Navigation is straightforward with the rules/ directory and AGENTS.md for full content. | 3 / 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.
- 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.