nx-workspace-patterns

Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.

Quality

63%

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 ./skills/nx-workspace-patterns/SKILL.md

Quality

Content

39%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 skill provides useful Nx configuration templates and commands but suffers from being a monolithic dump of configuration files without clear workflows or progressive disclosure. The large JSON templates inflate the token cost significantly while the actual instructional guidance ('Clarify goals, constraints, and required inputs') is vague. The skill would benefit greatly from moving templates to separate files, adding step-by-step workflows with validation, and trimming to essential patterns.

Suggestions

Move the large JSON/YAML templates (nx.json, project.json, .eslintrc.json, CI config) into separate referenced files and keep only minimal inline examples showing key patterns.

Add explicit step-by-step workflows for the main use cases (e.g., 'Setting up a new workspace', 'Adding module boundaries') with validation checkpoints like running `nx graph` to verify dependency constraints or `nx lint` to confirm boundary rules.

Replace the generic Instructions section ('Clarify goals, constraints, and required inputs') with specific decision logic: e.g., 'If setting up a new workspace, start with Template 1; if adding boundaries to existing workspace, start with Template 3.'

Remove explanatory content Claude already knows (library type descriptions, basic architecture concepts) and focus on Nx-specific configuration gotchas and non-obvious patterns.

Dimension	Reasoning	Score
Conciseness	The skill is significantly verbose with large JSON configuration templates that could be referenced in separate files. The library types table, architecture overview, and best practices sections explain concepts Claude already understands. The nx.json and project.json templates are extremely long and could be trimmed to essential patterns.	2 / 5
Actionability	The skill provides concrete, copy-paste ready configuration templates, CLI commands, and TypeScript code for custom generators. The CI workflow and remote caching setup are executable. Minor gap: the instructions section is vague ('Clarify goals, constraints, and required inputs') and doesn't give specific guidance on when to apply which template.	4 / 5
Workflow Clarity	There is no clear multi-step workflow with sequencing or validation checkpoints. The skill presents templates and commands but doesn't guide through processes like 'setting up a new workspace' or 'migrating to Nx' step-by-step. No validation steps are provided for verifying configurations work correctly after applying them. The 'Instructions' section mentions 'validate outcomes' but never specifies how.	2 / 5
Progressive Disclosure	The skill references `resources/implementation-playbook.md` but no bundle files are provided, making this reference unverifiable. All six large templates are inlined in the main file, creating a wall of configuration that should be split into separate reference files. The content is over 250 lines with no meaningful separation of overview from detail.	2 / 5
	Total	10 / 20 Passed

Description

87%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 is a strong skill description that clearly identifies its domain (Nx monorepo workspaces), lists specific capabilities, and includes an explicit 'Use when' clause with concrete trigger scenarios. Minor improvements could include additional trigger terms like 'nx.json', 'task pipeline', or 'dependency graph' to capture more user query variations.

Dimension	Reasoning	Score
Specificity	Lists several specific actions: setting up Nx, configuring project boundaries, optimizing build caching, and implementing affected commands. These are concrete and relevant, though coverage could be slightly more comprehensive (e.g., mentioning generators, plugins, task pipelines).	4 / 5
Completeness	Clearly answers both 'what' (configure and optimize Nx monorepo workspaces) and 'when' (explicit 'Use when' clause with four concrete trigger scenarios: setting up Nx, configuring project boundaries, optimizing build caching, implementing affected commands).	5 / 5
Trigger Term Quality	Includes strong natural keywords like 'Nx', 'monorepo', 'build caching', 'project boundaries', and 'affected commands' that users would naturally use. Missing some synonyms or related terms like 'task runner', 'nx.json', 'project.json', 'workspace.json', or 'dependency graph'.	4 / 5
Distinctiveness Conflict Risk	Highly distinctive with a clear niche around Nx monorepo tooling. The specific mentions of Nx, project boundaries, build caching, and affected commands create a well-defined scope that is unlikely to conflict with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/nx-workspace-patterns/SKILL.md
Commit: 0159794

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.