run-nx-generator

Run Nx generators with prioritization for workspace-plugin generators. Use this when generating code, scaffolding new features, or automating repetitive tasks in the monorepo.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/run-nx-generator/SKILL.md

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, mostly actionable guide with a clear workflow and verification step. Its main weaknesses are conciseness — duplicated instructions and an empty step — rather than missing capability.

Suggestions

Remove the duplicate 'Use the mcp__nx-mcp__nx_generator_schema tool...' line (it appears in both the priority list and step 2) and fill in or delete the empty 'List available generators' step.

Delete or trim the 'When to Use This Skill' section since its trigger list duplicates the frontmatter description.

Replace the generic 'nx generate [generator-path] [options]' and '@nx/devkit:...' ellipses with one or two fully concrete, copy-paste-ready examples.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with no concept-explaining padding, but includes tightening opportunities: the 'When to Use This Skill' section duplicates the description's triggers, the nx_generator_schema instruction appears twice, and step 1 ('List available generators:') is empty. Not a 4 due to these repeated/empty sections; not a 2 because it avoids verbose concept explanation.	3 / 5
Actionability	Provides concrete executable commands ('nx generate ...', 'nx affected -t test', 'npx prettier --write') and a complete worked example; minor gaps from placeholder/ellipsis forms ('[generator-path]', '@nx/devkit:...'). Not a 5 because some commands are generic templates rather than copy-paste ready.	4 / 5
Workflow Clarity	A clear 4-step sequence (list, get schema, run, verify) with an explicit verification checkpoint (review files, run tests, format); the empty step 1 and absence of an error-recovery feedback loop keep it from 5. Validation is present so the destructive/batch cap does not apply.	4 / 5
Progressive Disclosure	Well-organized into clearly labeled sections with no nested or buried references, and no bundle files exist to mis-reference; minor organization gaps (duplicate generator_schema line, redundant 'When to Use' section) keep it from 5.	4 / 5
	Total	15 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that clearly states both capability and trigger conditions with concrete, natural-language phrases. Minor room for more specific action enumeration and synonym coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Nx generators) and lists several concrete actions ('generating code, scaffolding new features, or automating repetitive tasks'), with only minor coverage gaps; not a 5 because the actions are somewhat generic rather than fully enumerated.	4 / 5
Completeness	Explicitly answers what ('Run Nx generators with prioritization for workspace-plugin generators') and when ('Use this when generating code, scaffolding new features, or automating repetitive tasks in the monorepo') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural trigger phrases users would say ('generating code', 'scaffolding new features', 'automating repetitive tasks', 'monorepo') with good keyword coverage; not a 5 because it lacks common synonyms or variations.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche ('Nx generators', 'workspace-plugin generators', 'monorepo') with distinct triggers and minimal overlap risk with unrelated skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: nrwl/nx
Path: .claude/skills/run-nx-generator/SKILL.md
Commit: 9064aa9

Reviewed: about 4 hours ago

Table of Contents

Discovery Implementation Validation

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.