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.

Quality

78%

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 ./.opencode/skills/nx-generate/SKILL.md

Quality

Content

70%Scale 1-5

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

This is a solid, well-structured skill with a clear multi-step workflow and good validation checkpoints. Its main weaknesses are moderate verbosity (explaining concepts like what generators are, detailed buildability comparisons) and lack of progressive disclosure—all content is inlined in a single file rather than splitting detailed reference material into supporting files. The actionability is strong with concrete CLI commands and practical gotchas.

Suggestions

Remove the opening paragraph explaining what Nx generators are—Claude already knows this. Start directly with 'This skill applies when...' or the Key Principles.

Extract the Library Buildability section into a separate reference file (e.g., BUILDABILITY.md) and link to it, keeping only a one-line summary inline.

Add one complete end-to-end example showing a full generator invocation from discovery through verification to strengthen actionability.

Dimension	Reasoning	Score
Conciseness	The skill contains some unnecessary explanations (e.g., the opening paragraph explaining what Nx generators are, the detailed buildability table that Claude could reason about). The --directory flag warning and library buildability sections add value but are somewhat verbose. Several sections could be tightened.	3 / 5
Actionability	Provides concrete CLI commands throughout (nx list, nx g with --help, --dry-run, nx format, nx run-many), specific flags like --no-interactive, and practical examples like the --directory gotcha. Minor gaps: no complete end-to-end example showing a full generator invocation with all common options filled in.	4 / 5
Workflow Clarity	Clear 9-step sequential workflow with explicit validation checkpoints: dry-run before execution (step 6), format and verify after generation (step 9), feedback loop for failures (fix manageable issues or escalate). The workflow includes error recovery guidance and a re-evaluation loop (step 4 back to step 2).	5 / 5
Progressive Disclosure	The content is a single monolithic file at ~150 lines with no references to supporting files. The library buildability section and the detailed source code reading instructions could be split into separate reference files. The mention of 'link-workspace-packages' skill is a nice cross-reference but overall the content is heavy for a single SKILL.md with no bundle structure.	3 / 5
	Total	15 / 20 Passed

Description

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

This description excels at trigger term coverage and completeness, providing explicit invocation guidance with natural user phrases. Its main weakness is that the 'what' portion is somewhat thin—it says 'generate code using nx generators' but doesn't enumerate specific capabilities (e.g., workspace configuration, plugin management). The priority instruction ('ALWAYS use this BEFORE calling nx_docs') is useful for disambiguation but reads more as an internal routing directive than a capability description.

Suggestions

Expand the capability description to list specific actions beyond 'generate code', such as 'create apps, libraries, configure workspaces, add plugins' to improve specificity.

Rephrase the internal routing instruction ('ALWAYS use this BEFORE calling nx_docs') as a boundary statement rather than a priority directive, e.g., 'Handles discovery of available generators internally without requiring nx_docs.'

Dimension	Reasoning	Score
Specificity	Names the domain (nx generators) and one concrete action (generate code), but doesn't list specific capabilities like creating apps, libraries, or configuring workspaces in detail. The trigger words hint at actions but aren't framed as capability descriptions.	3 / 5
Completeness	Clearly answers both 'what' (generate code using nx generators) and 'when' (explicit trigger words and scenarios like scaffolding, setup, creating apps/libs). The 'INVOKE IMMEDIATELY when...' clause serves as a strong explicit 'when' directive with concrete trigger phrases.	5 / 5
Trigger Term Quality	Excellent coverage of natural trigger terms including 'scaffold', 'setup', 'create a ... app', 'create a ... lib', 'project structure', 'generate', 'add a new project'. These are exactly the phrases users would naturally say when needing this skill.	5 / 5
Distinctiveness Conflict Risk	Fairly distinct with its focus on nx generators and scaffolding/project structure. The explicit instruction to use this BEFORE nx_docs helps disambiguate from related skills. However, terms like 'setup' and 'generate' could overlap with other code generation or project setup skills.	4 / 5
	Total	17 / 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: mlbymolly/ruview-t4est
Path: .opencode/skills/nx-generate/SKILL.md
Commit: 4d1716f

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