nestjs-expert
Build Reliable NestJS Applications
NestJS architecture and debugging require careful module, provider, database, and authentication decisions. This skill guides diagnosis, implementation, review, and validation with established patterns.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "nestjs-expert" from https://skillstore.io/skills/sickn33-nestjs-expert.md and its manifest at https://skillstore.io/api/skills/sickn33-nestjs-expert/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "nestjs-expert". Nest cannot resolve OrdersService in OrdersController.
Expected outcome:
- Likely cause: OrdersService is missing from providers or is not exported by its owning module.
- Inspect OrdersModule imports, providers, exports, and the controller constructor token.
- Apply the smallest module metadata fix, then run build, unit tests, and relevant end-to-end tests.
Using "nestjs-expert". Review JWT authentication before production release.
Expected outcome:
- Confirm one validated secret source is shared by JwtModule and JwtStrategy.
- Check token expiry, bearer parsing, guard coverage, refresh handling, and configuration validation.
- Add negative tests for missing, expired, malformed, and incorrectly signed tokens.
Using "nestjs-expert". A TypeORM application reports repeated connection failures.
Expected outcome:
- Check entity decorator errors before treating the message as an infrastructure failure.
- Verify connection names, entity registration, file paths, retry settings, and startup error handling.
- Reproduce with one connection and validate each configuration change independently.
Security Audit
SafeAll 61 static findings are false positives caused by Markdown syntax, bounded diagnostic examples, documentation links, or security troubleshooting prose. No executable payload, credential access, exfiltration intent, prompt injection, or unsafe command construction was found.
Risk Factors
โ๏ธ External commands (37)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-nestjs-expert/audits/6?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-nestjs-expert?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-nestjs-expert?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-nestjs-expert/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-nestjs-expert.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
sickn33. (2026). nestjs-expert security audit report (audit version 6) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-nestjs-expert/audits/6BibTeX citation
@techreport{sickn33-sickn33-nestjs-expert-2026,
author = {sickn33},
title = {nestjs-expert security audit report (audit version 6)},
institution = {Skillstore},
year = {2026},
number = {6},
url = {https://skillstore.io/skills/sickn33-nestjs-expert/audits/6},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "nestjs-expert security audit report (audit version 6)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-08-04"
url: "https://skillstore.io/skills/sickn33-nestjs-expert/audits/6"
identifiers:
- type: other
value: "skillstore:sickn33-nestjs-expert:audit:6"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Repair Dependency Injection
Trace missing providers, exports, imports, scopes, and circular dependencies in a NestJS application.
Design a Tested Feature
Plan modules, controllers, services, DTO validation, mocks, and end-to-end coverage for a new feature.
Review Production Readiness
Assess authentication, database handling, errors, logging, caching, performance, and test coverage before release.
Try These Prompts
Diagnose this NestJS error: [error]. Explain the likely cause, files to inspect, smallest fix, and validation steps.
Design a NestJS module for [feature]. Include controllers, services, DTO validation, provider boundaries, error handling, and focused tests.
Review this NestJS architecture: [context]. Identify module boundary, dependency injection, database, authentication, testing, and performance risks. Prioritize concrete changes.
Plan the migration from [current design] to [target design]. Preserve behavior, stage database changes, address security, and define rollback and validation steps.
Best Practices
- Provide the exact error, relevant module metadata, framework version, and expected behavior.
- Match existing project conventions and request the smallest change that resolves the confirmed cause.
- Validate changes in order with build, unit, integration, and relevant end-to-end tests.
Avoid
- Do not add broad module imports or forward references before confirming the dependency path.
- Do not expose secrets, production tokens, or complete environment files in prompts.
- Do not accept framework examples without adapting them to project versions and infrastructure.