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

62%

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

57%

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

The content is well-structured and includes a genuinely executable example, but it is held back by a duplicated instruction, an empty first workflow step, placeholder templates, and a missing error-recovery feedback loop. Filling the gaps and de-duplicating would lift the weaker dimensions.

Suggestions

Fill in step 1 with the actual command to list generators and replace the 'nx generate [generator-path] [options]' placeholder with a concrete, copy-paste-ready form.

Add an explicit feedback loop after verification: if 'nx affected -t test' fails, fix the generated code and re-run before committing.

Remove the duplicated schema-tool instruction (it appears both in the priority section and in step 2) to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and avoids explaining concepts Claude already knows, but it repeats the schema-tool instruction twice ('Use the mcp__nx-mcp__nx_generator_schema tool...') and includes mild filler ('This automates all of the version bumping instead of manual file edits') plus emoji-laden best-practice bullets that could be tightened; not level 3 due to this redundancy.	2 / 3
Actionability	It provides a concrete, copy-paste-ready example (the bump-maven-version command with flags) and real commands ('nx affected -t test', 'npx prettier --write'), but step 1 ('List available generators') is empty with no command and the main run instruction is a placeholder template ('nx generate [generator-path] [options]'), leaving key details incomplete.	2 / 3
Workflow Clarity	The four-step sequence (list, get schema, run, verify) is clearly ordered and includes a verify step, but there is no feedback loop for error recovery (e.g. what to do when tests fail) and step 1 has no actual instruction; per the rubric, missing feedback loops for batch/file-generating operations caps this at 2.	2 / 3
Progressive Disclosure	No bundle files exist and the skill is single-purpose with well-organized sections (priority list, how to run, best practices, examples, when to use); per the rubric's simple-skill guidance, a self-contained skill with no need for external references and clear organization scores 3.	3 / 3
	Total	9 / 12 Passed

Description

67%

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

The description cleanly answers both what and when with an explicit trigger clause, but its capability list is a single action and its trigger terms lean generic rather than Nx-specific. Strengthening it with concrete Nx trigger phrasing would reduce conflict risk and raise specificity.

Suggestions

Add Nx-specific natural triggers users would say, e.g. 'nx generate', 'scaffold a new library/app', or 'create a generator'.

Spell out distinct concrete capabilities (e.g. 'scaffold libraries and apps, run migrations, bump internal tool versions') rather than one 'run generators' action.

Tighten the generic 'automating repetitive tasks in the monorepo' to a more distinctive Nx-scoped trigger to lower overlap with other codegen skills.

Dimension	Reasoning	Score
Specificity	Names the domain clearly ('Run Nx generators with prioritization for workspace-plugin generators') and lists several action contexts ('generating code, scaffolding new features, or automating repetitive tasks'), but the skill's core capability is a single action rather than multiple distinct concrete operations like the level-3 anchor.	2 / 3
Completeness	It explicitly answers both what ('Run Nx generators with prioritization for workspace-plugin generators') and when via an explicit 'Use this when...' trigger clause, matching the level-3 anchor; not below because neither half is missing or merely implied.	3 / 3
Trigger Term Quality	The 'Use this when generating code, scaffolding new features, or automating repetitive tasks in the monorepo' clause includes natural terms, but misses common Nx-specific variations a user would actually say (e.g. 'nx generate', 'create a new library/app', 'scaffold a project'), and 'automating repetitive tasks' is generic.	2 / 3
Distinctiveness Conflict Risk	The 'what' is niche (Nx generators, workspace-plugin, monorepo), but the trigger terms ('generating code, scaffolding new features, automating repetitive tasks') are generic and could overlap with other scaffolding/codegen skills, so it is not a clear level-3 niche.	2 / 3
	Total	9 / 12 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: 0abf7a4

Reviewed: 4 days 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.