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.
36
3%
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
7%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 extremely weak — it is essentially a title with no substantive content. It fails to describe what the skill actually does (e.g., what files it generates, what structure it creates), provides no 'Use when...' guidance, and repeats the same trigger term twice without any natural language variations. It would be very difficult for Claude to reliably select this skill from a pool of alternatives.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Generates NestJS modules with controllers, services, DTOs, and unit test files following NestJS conventions.'
Add an explicit 'Use when...' clause with trigger scenarios, e.g., 'Use when the user asks to create, scaffold, or generate a NestJS module, service, controller, or backend component.'
Diversify trigger terms to include natural variations like 'create nest module', 'scaffold NestJS', 'nest.js service', 'generate backend module', 'new NestJS component'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the domain ('NestJS Module Generator') but does not describe any concrete actions like 'generates module files', 'creates controllers, services, and DTOs', or 'scaffolds NestJS boilerplate'. It is essentially just a title repeated. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' clause is essentially absent — there is no 'Use when...' guidance or explicit trigger scenarios. The trigger terms are just the skill name repeated. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'nestjs module generator' repeated twice identically. It misses natural variations users would say like 'create a NestJS module', 'scaffold nest module', 'generate nest service', 'nest.js', or 'backend module'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'NestJS' provides some specificity that distinguishes it from generic code generation skills, but the lack of concrete actions or scope means it could overlap with other NestJS-related or backend scaffolding skills. | 2 / 3 |
Total | 5 / 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 is an empty template with no actual content. It contains only generic placeholder text that describes what a skill *would* do without providing any concrete guidance, code, commands, or workflows for NestJS module generation. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable code examples showing how to generate a NestJS module (e.g., `nest generate module <name>` command, or a complete module file template with controller, service, and module decorator).
Define a clear step-by-step workflow for creating a NestJS module, including validation steps such as verifying the module compiles and is properly imported into the app module.
Remove all the meta-description sections (When to Use, Example Triggers, Capabilities) that explain what the skill does abstractly, and replace them with actual actionable content like code templates, file structures, and configuration patterns.
Add specific examples showing common NestJS module patterns (e.g., a CRUD module with TypeORM integration, a module with guards/interceptors) with copy-paste ready code.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It explains what the skill does in abstract terms without providing any actual guidance, code, or commands. Every section restates the same vague concept. | 1 / 3 |
Actionability | There is zero concrete, executable guidance. No code examples, no commands, no specific steps for generating a NestJS module. The content only describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, and no validation checkpoints. The skill claims to provide 'step-by-step guidance' but includes none. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, no links to examples or API references, and no meaningful structure beyond boilerplate headings. | 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
3076d78
- 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.