CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nx

Best practices for Nx monorepo development, project configuration, and code generation

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./nx/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The content is a lean, actionable Nx reference with real commands and copy-paste-ready configuration examples covering structure, boundaries, caching, and CI. Its weaknesses are the absence of any sequenced workflow with validation checkpoints (it is purely topical) and minor placeholder gaps like empty project.json targets.

Suggestions

Add one or two sequenced workflows with validation, e.g., '1. nx g @nx/react:lib shared-ui-button --dry-run 2. Review the printed file changes 3. Re-run without --dry-run 4. Verify tags in project.json match boundary rules'.

Fill in or remove the empty '{ }' placeholders in the project.json targets example, and complete the GitHub Actions snippet (trigger, steps, cache) so it is copy-paste ready.

Consider moving the CI/CD and Testing Strategy detail into one-level-deep reference files (e.g., references/ci.md) to keep SKILL.md a tighter overview.

DimensionReasoningScore

Conciseness

The body is dense and imperative — short bullets plus config and CLI snippets with almost no concept explanations Claude already knows. It is not 5 because of minor trimmable filler like 'You are an expert in Nx, the smart, fast, and extensible build system for monorepos' and a few generic bullets ('Implement proper type exports from libraries'), and not 3 because padding is limited to isolated lines rather than whole sections.

4 / 5

Actionability

Provides concrete, executable guidance: 'nx g @nx/react:app my-app', 'nx run-many -t build', 'nx affected -t test', 'nx graph', plus complete nx.json and ESLint depConstraints JSON examples. It is not 5 because of minor gaps — the project.json 'targets' are empty '{ }' placeholders and the GitHub Actions snippet is a fragment rather than a complete workflow.

4 / 5

Workflow Clarity

The skill is organized by topic rather than as a sequenced workflow — there are no ordered multi-step processes and checkpoints are only implicit (the single '--dry-run to preview changes' hint). It exceeds 2 because the topical sections themselves are coherent and each gives usable direction, but lacks the explicit sequence and validation checkpoints of 4; the simple-skill exception does not apply since this is a multi-topic reference well over 50 lines.

3 / 5

Progressive Disclosure

A single well-sectioned file with clear headers (Project Structure, Workspace Configuration, Module Boundaries, etc.) and appropriately overview-level content, with no external references to manage. It is not 5 because at ~130 lines it exceeds the under-50-line simple-skill case, and sections like CI/CD Integration and Testing Strategy carry detail that could live in one-level-deep reference files; it is clearly above 3 because nothing is buried and all content reasonably belongs in an overview.

4 / 5

Total

15

/

20

Passed

Description

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

The description names a specific, recognizable domain (Nx monorepos) with a couple of concrete focus areas, giving it good distinctiveness and decent keywords. Its main weakness is the complete absence of 'when to use' trigger guidance, which caps completeness, and its actions remain topic-level rather than concrete.

Suggestions

Add an explicit trigger clause, e.g., 'Use when working in an Nx workspace or monorepo, running nx commands, or configuring project.json/nx.json.'

Replace the generic 'Best practices for ... development' framing with concrete actions such as 'Configure nx.json and project.json, generate apps and libraries, enforce module boundaries, and set up caching and affected-based CI.'

Include natural trigger terms users would actually say: 'Nx workspace', 'generators', 'nx g', 'affected', 'Nx Cloud', 'monorepo'.

DimensionReasoningScore

Specificity

Phrases like 'Nx monorepo development', 'project configuration', and 'code generation' name the domain plus two capability areas, matching the anchor for domain with 1-2 concrete actions. It falls short of 4 because 'Best practices for ... development' is generic framing with no concrete actions (e.g., 'generate apps', 'configure caching'), and above 2 because more than one specific focus area is named.

3 / 5

Completeness

The 'what' is clear (best practices for Nx monorepo development, configuration, and code generation), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is above 2 because the 'what' is concrete, not vague.

3 / 5

Trigger Term Quality

Includes the natural terms users would say — 'Nx', 'monorepo', 'project configuration', 'code generation' — giving good keyword coverage. Not 5 because common variations and specifics like 'Nx workspace', 'generators', 'affected', 'nx.json', or 'build system' are missing.

4 / 5

Distinctiveness Conflict Risk

'Nx' is a highly specific, distinctive trigger creating a clear niche with minimal conflict risk against unrelated skills. Not 5 because the phrase 'Best practices for ... development' could mildly overlap with general monorepo, CI, or DevOps skills, and no explicit trigger phrases further isolate it.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

Mindrally/skills

Path

nx/SKILL.md

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.