nx-generate

Generate code using nx generators. INVOKE IMMEDIATELY when user mentions scaffolding, setup, structure, creating apps/libs, or setting up project structure. Trigger words - scaffold, setup, create a new app, create a new lib, project structure, generate, add a new project. ALWAYS use this BEFORE calling nx_docs or exploring - this skill handles discovery internally.

Quality

82%

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

Quality

Content

77%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.

A highly actionable, well-sequenced workflow with strong validation and feedback loops — the command-level guidance is exemplary. The weaknesses are padded intro/duplicative applicability sections and the absence of any progressive-disclosure structure, with detailed reference-grade material inlined in a single long file.

Suggestions

Delete the intro paragraph ('Nx generators are powerful tools...') and the 'This skill applies when' bullet list, which duplicate information already carried by the description.

Move the Library Buildability section and the '--directory' flag warning into a references/ file (e.g. references/generator-options.md), keeping SKILL.md as a lean overview with one-level-deep pointers.

Trim hedging asides like 'This example is for built-in nx formatting with prettier...' to a single directive plus a short caveat.

Dimension	Reasoning	Score
Conciseness	The intro paragraph ('Nx generators are powerful tools that scaffold projects... They ensure consistency across the codebase') and the 'This skill applies when' bullet list restate what the description already says, and hedging asides like 'This example is for built-in nx formatting...' pad the text. It sits between anchors 3 and 4: mostly efficient, dense with commands, but with several unnecessary explanations that could be trimmed.	3 / 5
Actionability	Every step gives copy-paste-ready commands: 'npx nx list @nx/react', 'npx nx g @nx/react:library --help', 'npx nx g ... --dry-run --no-interactive', 'node -e "console.log(require.resolve('@nx/<plugin>/generators.json'))"', 'nx format --fix', and correct/incorrect '--directory' examples. Common cases are concretely covered.	5 / 5
Workflow Clarity	A clearly sequenced 9-step workflow with explicit validation checkpoints: dry-run before the real run, a feedback loop ('After reading the source, reconsider: Is this the right generator? If not, go back to step 2'), verification via 'nx run-many -t build,lint,test,typecheck', and an explicit error-recovery/escalation path ('If issues are extensive... escalate to the user').	5 / 5
Progressive Disclosure	There are no bundle files at all — the entire ~160-line body is a single monolithic file with clear headers but no references. Self-contained material like the Library Buildability table and the '--directory' gotcha is inlined where a reference file with the body as overview would serve better; it is above anchor 2 only because section structure and navigation within the file are good.	3 / 5
	Total	16 / 20 Passed

Description

78%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 description that explicitly covers both what the skill does and when to invoke it, with an explicit trigger-word list. Weaknesses are the thin capability statement (only 'generate code') and somewhat generic trigger words like 'setup' and 'structure' that broaden conflict risk.

Suggestions

Enumerate the concrete capabilities in the description, e.g. 'Create apps and libraries, scaffold features, run custom workspace generators' instead of the single phrase 'Generate code using nx generators'.

Replace overly generic trigger words like 'setup' and 'structure' with more specific phrases (e.g., 'new workspace', 'new library') to reduce overlap with unrelated skills.

Dimension	Reasoning	Score
Specificity	The only capability stated is 'Generate code using nx generators' — one concrete action naming the domain. It does not reach anchor 4 because other capabilities (migrations, boilerplate reduction) are never stated, and it is above anchor 2 because the action and domain are concrete, not generic.	3 / 5
Completeness	Clearly answers 'what' ('Generate code using nx generators') and 'when' with explicit trigger phrases ('INVOKE IMMEDIATELY when user mentions scaffolding, setup, structure, creating apps/libs, or setting up project structure'), matching the anchor-5 example structure.	5 / 5
Trigger Term Quality	Lists explicit natural phrases users would say: 'scaffold, setup, create a new app, create a new lib, project structure, generate, add a new project'. Not 5 because common variations/synonyms (e.g., 'new library', 'scaffold a component', 'new workspace') are missing and words like 'setup' and 'structure' are overly generic.	4 / 5
Distinctiveness Conflict Risk	The Nx-generator niche is distinct (it even scopes itself against 'nx_docs'), but generic trigger words like 'setup', 'structure', and 'generate' create minor overlap risk with other scaffolding/codegen skills, keeping it below anchor 5.	4 / 5
	Total	16 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: nrwl/nx
Path: .opencode/skills/nx-generate/SKILL.md
Commit: ab845a8

Reviewed: 2 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.