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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

77%

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 checkpoints and feedback loops. It loses points on conciseness (conceptual padding and repeated caveats) and progressive disclosure (a monolithic single file with no externalized detailed reference).

Suggestions

Conciseness: trim the conceptual intro and the buildable/non-buildable explanations that restate how such libs work; keep only the decision guidance and the specific flags.

Conciseness: consolidate the "these targets are just an example, use what's appropriate for this workspace" caveat — it currently appears in both Key Principles and Step 9 — into a single statement.

Progressive disclosure: move the detailed Library Buildability table and the --directory flag gotcha into a referenced file (e.g. references/library-options.md) so SKILL.md stays a lean overview with one-level-deep, clearly signaled references.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and command-driven, but the conceptual intro ("Nx generators are powerful tools that scaffold projects... ensure consistency... reduce boilerplate work") and the buildable/non-buildable explanations restate concepts Claude already knows, and the "just an example" verify caveat recurs in both Key Principles and Step 9.	2 / 3
Actionability	It provides concrete, copy-paste-ready commands throughout (npx nx list, --help, --dry-run --no-interactive, the node -e require.resolve trick, npm run format, nx run-many -t build,lint,test,typecheck) plus specific flags (--bundler=vite/swc) and worked ✅/❌ directory examples.	3 / 3
Workflow Clarity	Nine clearly sequenced steps with explicit validation checkpoints (dry-run to verify placement, build/lint/test/typecheck verification) and feedback loops ("If not, go back to step 2"; fix-then-retry or escalate on verification failure).	3 / 3
Progressive Disclosure	Sections are well-organized, but the ~160-line body is a single monolithic file with no one-level-deep reference files, and detailed asides (the buildability table and the --directory flag gotcha) are inline rather than split into clearly signaled, referenced materials.	2 / 3
	Total	10 / 12 Passed

Description

100%

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, well-scoped description that clearly answers both what the skill does and when to invoke it, with concrete, natural trigger terms and a distinct nx-generators niche. The only minor weakness is slight redundancy: trigger terms appear both in prose and in the explicit trigger-word list.

Dimension	Reasoning	Score
Specificity	"Generate code using nx generators" names the domain, and "scaffolding, setup, structure, creating apps/libs, or setting up project structure" lists multiple concrete actions, matching the anchor for several specific concrete actions.	3 / 3
Completeness	It states what ("Generate code using nx generators") and when ("INVOKE IMMEDIATELY when user mentions scaffolding, setup, structure, creating apps/libs") with explicit triggers, satisfying both halves.	3 / 3
Trigger Term Quality	An explicit trigger list — "scaffold, setup, create a ... app, create a ... lib, project structure, generate, add a new project" — gives good coverage of natural terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	The nx-generators niche is clear, monorepo-specific triggers ("create a ... lib", "add a new project") are distinct, and it explicitly de-conflicts against the nx_docs skill.	3 / 3
	Total	12 / 12 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: leboncoin/spark-web
Commit: 13e119c

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