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 ... app, create a ... lib, project structure, generate, add a new project. ALWAYS use this BEFORE calling nx_docs or exploring - this skill handles discovery internally.
68
83%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
89%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 is a strong skill description with excellent trigger term coverage and clear 'when to use' guidance, including priority ordering relative to other skills. The main weakness is that the 'what' portion could be more specific about the concrete actions beyond just 'generate code using nx generators'—listing specific capabilities like creating workspaces, generating components, or configuring build targets would strengthen specificity. The use of imperative/instructional voice ('INVOKE IMMEDIATELY', 'ALWAYS use this') is unusual but functional for skill selection.
Suggestions
Expand the capability description to list specific concrete actions, e.g., 'Generate code using nx generators: scaffold new apps and libraries, set up project structure, configure workspace settings, add new projects to monorepos.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (nx generators) and the general action (generate code), but doesn't list multiple specific concrete actions like 'create apps, create libraries, scaffold project structure, configure workspaces'. The specificity is moderate—it mentions scaffolding and creating apps/libs but mostly in the trigger section rather than as described capabilities. | 2 / 3 |
Completeness | Clearly answers both 'what' (generate code using nx generators) and 'when' (explicit trigger words and scenarios like scaffolding, setup, creating apps/libs). It even includes priority guidance about when to use this skill relative to other skills (before nx_docs or exploring). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'scaffold', 'setup', 'create a ... app', 'create a ... lib', 'project structure', 'generate', 'add a new project'. These are terms users would naturally say when needing this skill, and the description explicitly lists them. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to nx generators specifically, with distinct triggers around scaffolding and project structure in the nx ecosystem. The explicit note about using this BEFORE nx_docs further disambiguates it from related skills, reducing conflict risk. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill with a well-defined multi-step workflow and excellent validation checkpoints. Its main weakness is moderate verbosity—the introductory paragraph and some explanatory passages could be trimmed since Claude already understands Nx concepts. The content would also benefit from splitting reference material (like the buildability table) into separate files for better progressive disclosure.
Suggestions
Remove or drastically shorten the opening paragraph explaining what Nx generators are—Claude already knows this.
Consider extracting the Library Buildability section and the --directory flag guidance into a separate reference file to reduce the main skill's length and improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary explanation. The opening paragraph explaining what Nx generators are is redundant for Claude. Phrases like 'This step is critical' and some explanatory text about buildable vs non-buildable libs could be tightened. However, most content earns its place with actionable guidance. | 2 / 3 |
Actionability | The skill provides concrete, executable commands throughout (nx list, --help, --dry-run, nx generate, nx format, nx run-many). The --directory flag example with correct/incorrect usage is particularly actionable. Commands are copy-paste ready with clear explanations of when to use each. | 3 / 3 |
Workflow Clarity | The 9-step workflow is clearly sequenced with explicit validation checkpoints: dry-run before execution (step 6), format and verify after generation (step 9), and a feedback loop for handling failures (fix manageable issues, escalate extensive ones). The workflow also includes a re-evaluation loop at step 4 ('Is this the right generator? If not, go back to step 2'). | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and numbered steps, but it's a fairly long monolithic document (~150 lines of substantive content) with no references to supporting files. The buildability table and directory flag guidance could be split into reference files. The mention of 'link-workspace-packages' skill is a good cross-reference, but overall the document could benefit from splitting detailed reference material out. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- Ensono/stacks-nx-plugins
- Commit
e887790
- 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.