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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill nestjs-module-generatorOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder with minimal useful information. It relies entirely on the skill name without explaining capabilities, use cases, or providing diverse trigger terms. The duplicate trigger term and boilerplate category text suggest auto-generated content that wasn't customized.
Suggestions
Add specific actions the skill performs, e.g., 'Generates NestJS modules, controllers, services, and DTOs with proper decorators and dependency injection setup'
Include a 'Use when...' clause with natural trigger terms like 'create nest module', 'scaffold nestjs service', 'generate controller', 'nest boilerplate', 'new nest component'
Remove duplicate trigger terms and expand to include variations users naturally say when working with NestJS projects
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the domain ('Nestjs Module Generator') but provides no concrete actions. It doesn't explain what the skill actually does - no mention of creating files, generating boilerplate, scaffolding components, etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' guidance is just a duplicate trigger phrase. There's no explicit 'Use when...' clause or meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('nestjs module generator' listed twice) and overly specific. Missing natural variations users would say like 'nest module', 'create nest service', 'scaffold nestjs', 'generate controller', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The NestJS focus provides some distinctiveness from generic code generators, but 'Backend Development' category is broad. Could conflict with other Node.js or TypeScript scaffolding skills without clearer boundaries. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%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 actual steps to follow.
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) Register in app.module.ts with validation steps
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 details. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.