nestjs-module-generator
Nestjs Module Generator - Auto-activating skill for Backend Development. Triggers on: nestjs module generator, nestjs module generator Part of the Backend Development skill category.
41
11%
Does it follow best practices?
Impact
99%
1.01xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/06-backend-dev/nestjs-module-generator/SKILL.mdQuality
Discovery
22%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 description is essentially a placeholder that relies entirely on the skill name rather than providing useful selection criteria. It lacks any explanation of what the generator actually produces, what file types or structures it creates, and provides no meaningful trigger guidance beyond repeating the skill name twice.
Suggestions
Add specific actions the generator performs, e.g., 'Generates NestJS modules with controllers, services, DTOs, and spec files following NestJS conventions'
Include a 'Use when...' clause with natural trigger terms like 'create nest module', 'scaffold nestjs service', 'generate nest controller', 'nest.js boilerplate'
Specify the scope more clearly to distinguish from other backend skills, e.g., mentioning TypeScript, decorators, dependency injection patterns specific to NestJS
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Nestjs Module Generator' and 'Backend Development' without describing any concrete actions. It doesn't explain what the skill actually does (e.g., generates controllers, services, DTOs, creates boilerplate code). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' clause is just a repetition of the skill name rather than meaningful trigger guidance. No explicit 'Use when...' clause with actionable triggers. | 1 / 3 |
Trigger Term Quality | Contains 'nestjs module generator' as a trigger term (duplicated), which is relevant but narrow. Missing common variations users might say like 'nest.js', 'create nest module', 'generate service', 'scaffold nestjs', or 'nest cli'. | 2 / 3 |
Distinctiveness Conflict Risk | The NestJS focus provides some distinctiveness from generic backend skills, but 'Backend Development' category is broad. Could potentially conflict with other Node.js or TypeScript backend skills without clearer scope definition. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is essentially a placeholder template with no actual instructional value. It contains only meta-descriptions of what a skill should do without any concrete guidance on NestJS module generation - no CLI commands, no code examples, no file structures, and no workflow steps. The content fails on all dimensions by being verbose yet empty of actionable information.
Suggestions
Add executable NestJS CLI commands for module generation (e.g., `nest generate module users` with expected output)
Include a concrete code example showing a complete module structure with controller, service, and module files
Define a clear workflow: 1) Generate module scaffold, 2) Add dependencies, 3) Configure providers, 4) Validate with `nest build`
Remove all generic boilerplate text ('provides automated assistance', 'follows best practices') and replace with specific NestJS patterns and conventions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actual information about NestJS module generation. | 1 / 3 |
Actionability | There is zero concrete guidance - no code examples, no commands, no specific steps for generating NestJS modules. The content describes what the skill supposedly does rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. Despite claiming to provide 'step-by-step guidance,' there are no actual steps, no sequence, and no validation checkpoints for module generation. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no structure for discovery. There are no references to detailed documentation, examples, or related files that would provide actual implementation guidance. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
994edc4
- 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.