CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nx-workspace-patterns

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

62

Quality

78%

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

Quality

Content

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

Highly actionable reference material with excellent copy-paste templates and commands, but it is a monolithic catalog: weak workflow sequencing and no progressive disclosure. Splitting templates into reference files and replacing the generic Instructions with a concrete Nx workflow would lift the lower dimensions.

Suggestions

Replace the generic 'Instructions' bullets with a concrete Nx workflow (e.g., assess tags -> configure boundaries -> enable caching -> run affected -> verify graph) with explicit validation checkpoints such as `nx graph` and `nx affected -t lint`.

Move the six full templates into separate files under references/ (e.g., references/nx-json.md, references/project-json.md, references/module-boundaries.md) and link to them one level deep from SKILL.md to improve progressive disclosure and token efficiency.

Add verification steps for batch/destructive operations like `nx migrate` (e.g., review migrations file, run on a branch, re-run affected tests) so workflow clarity is not capped.

DimensionReasoningScore

Conciseness

The body is mostly concrete config blocks, but the generic 'Instructions' bullets ('Clarify goals...', 'Apply relevant best practices...') add no Nx-specific value, and six full templates inlined together make the token budget heavier than necessary.

3 / 5

Actionability

Six complete, copy-paste-ready config templates (nx.json, project.json, eslintrc, generator, CI, remote caching) plus an executable 'Common Commands' block cover the common Nx workspace cases fully.

5 / 5

Workflow Clarity

There is only a vague three-bullet generic flow ('Clarify goals... Apply... validate outcomes') with no real sequence or validation checkpoints; the skill is a patterns catalog rather than a sequenced workflow, and batch/destructive operations like 'nx migrate' lack verification steps.

2 / 5

Progressive Disclosure

Sections are clearly labeled and well-organized, but all six large templates are inlined in SKILL.md with no bundle files (references/, scripts/, assets/ absent) and no one-level-deep references to split the material.

3 / 5

Total

13

/

20

Passed

Description

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

A strong, third-person description that pairs a concise capability statement with an explicit, multi-trigger 'Use when' clause. It is specific, well-triggered, and distinct, with only minor room to broaden keyword coverage.

DimensionReasoningScore

Specificity

Lists several specific actions ('setting up Nx', 'configuring project boundaries', 'optimizing build caching', 'implementing affected commands') but the lead verbs 'Configure and optimize' are generic, leaving minor coverage gaps versus a fully comprehensive listing.

4 / 5

Completeness

Explicitly answers both what ('Configure and optimize Nx monorepo workspaces') and when ('Use when setting up Nx, configuring project boundaries...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural terms like 'Nx monorepo workspaces', 'project boundaries', 'build caching', and 'affected commands' map to what users would say, though synonyms like 'monorepo', 'Nx Cloud', or 'CI' are missing.

4 / 5

Distinctiveness Conflict Risk

Targets a clear Nx-specific niche with distinct triggers (project boundaries, build caching, affected commands), giving minimal conflict risk with other skills.

5 / 5

Total

18

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

rmyndharis/antigravity-skills

Path

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