oh-my-ai/nestjs
NestJS architecture, dependency injection, validation, security, errors, testing, persistence, APIs, microservices, and deployment patterns with prioritized rule tiers and companion rule files.
99
100%
Does it follow best practices?
Impact
97%
1.12xAverage score across 2 eval scenarios
Advisory
Suggest reviewing before use
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 thoroughly covers capabilities, trigger terms, outputs, and explicit exclusions. It provides comprehensive NestJS-specific terminology that makes it highly distinguishable from other backend framework skills. The inclusion of both positive triggers and negative exclusions ('Do NOT use for') is a strong pattern for avoiding conflicts.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and technologies: modules, controllers, providers, guards, interceptors, pipes, middleware, JWT, ValidationPipe, microservices, GraphQL, Bull queues, Prisma, TypeORM. Also specifies outputs ('tier-ordered review checklists and/or concrete code edits with cited rule filenames'). | 3 / 3 |
Completeness | Clearly answers 'what' (NestJS production patterns for specific features, outputs review checklists and code edits), 'when' (explicit trigger terms listed), and even 'when NOT' (non-Nest backends, frontend-only, etc.). The explicit 'Triggers:' clause serves as the 'Use when' equivalent. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'NestJS', 'Nest.js', 'Nest module', 'dependency injection', 'class-validator DTO', 'exception filter', 'testing module', 'GraphQL resolver', 'Bull queue', 'microservice client'. These are terms developers naturally use when working with NestJS. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche (NestJS specifically), explicit exclusions ('Do NOT use for: non-Nest backends, frontend-only frameworks'), and domain-specific trigger terms that are unlikely to conflict with general backend or frontend skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that efficiently organizes a complex domain (NestJS production patterns) into a tiered workflow with clear navigation to 40+ detailed rule files. The content is concise, assumes Claude's competence, provides executable code examples for the most common patterns, and includes explicit validation checkpoints in the review workflow. The anti-patterns section adds practical value by naming specific mistakes with rule citations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It assumes Claude knows NestJS fundamentals, avoids explaining what DTOs or guards are, and every section serves a clear purpose — workflow ordering, code patterns, anti-patterns, and navigation to deeper rules. | 3 / 3 |
Actionability | Provides fully executable TypeScript code snippets for common patterns (DTO + ValidationPipe, JWT guard), a concrete tiered workflow with specific actions at each level, and an integrated example showing how rules compose for a real endpoint. Anti-patterns are specific and actionable. | 3 / 3 |
Workflow Clarity | The refactoring/review workflow is clearly sequenced with explicit priority tiers (1-6), includes a validation checkpoint ('run nest build and automated tests after each tier'), and has a clear stopping rule ('stop reranking within a tier unless a higher tier introduces new breakage'). The feedback loop of build-then-proceed is explicit. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure: the SKILL.md serves as a concise overview with a rules map table, then clearly signals one-level-deep references to `rules/<slug>.md`, `rules/_sections.md` for ordering, and `rules/_template.md` for creating new rules. No nested reference chains. | 3 / 3 |
Total | 12 / 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