nx-import

Import, merge, or combine repositories into an Nx workspace using nx import. USE WHEN the user asks to adopt Nx across repos, move projects into a monorepo, or bring code/history from another repository.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/nx-import/SKILL.md

Quality

Content

72%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 body is dense, actionable, and well-structured with progressive disclosure into verified reference files. Its main weakness is workflow clarity: a batch, destructive operation (repo import / git merges) is presented as a troubleshooting catalog without a top-level sequenced workflow or explicit validation checkpoints, which caps workflow clarity.

Suggestions

Add a top-level numbered import workflow (detect app vs library -> choose strategy -> run nx import -> validate with nx sync + typecheck + lint -> then fix issues), so the destructive batch operation has explicit validation checkpoints.

Consolidate the repeated pnpm-workspace.yaml guidance into one section and cross-reference it, to remove redundancy and improve conciseness.

Make a few high-level fix steps fully executable by including the exact commands rather than intent (e.g. the directory-conflict 'import into alternate-named dir then rename' could show the concrete nx import + mv commands).

Dimension	Reasoning	Score
Conciseness	Largely lean and assumes competence — no basic concept explanations, dense with concrete gotchas and commands — but a few items recur (pnpm-workspace.yaml handling appears in both the workspace-glob and redundant-root-files sections), leaving minor tightening room short of anchor 5.	4 / 5
Actionability	Highly actionable with copy-paste commands and exact config snippets (e.g. `pnpm add -wD eslint@^9 ...`, the pnpm.overrides JSON, precise tsconfig field values), though a few fix steps describe intent rather than the exact command to run, keeping it just below anchor 5.	4 / 5
Workflow Clarity	Ordered fix sequences exist within several sections (ESLint 1-3, Jest 1-4, noEmit→composite 1-4), but the top-level flow is organized as a troubleshooting catalog rather than a single sequenced import workflow with validation checkpoints; for a destructive/batch repo-import operation the rubric caps this at 3.	3 / 5
Progressive Disclosure	The body is a well-signaled overview pointing one level deep to six verified reference files (ESLINT, GRADLE, JEST, NEXT, TURBOREPO, VITE), each summarized in the Technology-specific Guidance section for easy navigation, matching the anchor-5 structure.	5 / 5
	Total	16 / 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.

The description is strong: it pairs concrete capabilities with an explicit USE WHEN clause and natural trigger phrases, hitting both 'what' and 'when' clearly. The only minor gap is that the listed actions overlap semantically and lack synonym/extension breadth.

Dimension	Reasoning	Score
Specificity	Names the Nx workspace domain and several actions ('Import, merge, or combine repositories into an Nx workspace using nx import'), but import/merge/combine are near-synonyms rather than truly distinct capabilities, so it stops short of comprehensive anchor 5.	4 / 5
Completeness	Explicitly answers both 'what' (import/merge/combine repos into an Nx workspace) and 'when' with a concrete 'USE WHEN' clause enumerating specific trigger scenarios, matching the anchor-5 example.	5 / 5
Trigger Term Quality	Natural user phrases ('adopt Nx across repos', 'move projects into a monorepo', 'bring code/history from another repository') with good synonym coverage, though it omits file extensions and some common variants that anchor 5 would include.	4 / 5
Distinctiveness Conflict Risk	Clear niche (Nx import / monorepo adoption) with distinct triggers unlikely to fire for unrelated skills; minimal conflict risk.	5 / 5
	Total	18 / 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: nrwl/nx
Path: .agents/skills/nx-import/SKILL.md
Commit: 9064aa9

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