CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

76

Quality

93%

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

SKILL.md
Quality
Evals
Security

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, token-efficient reference that excels at concrete commands and progressive disclosure; its main weakness is workflow clarity, since guidance is structured as a reactive issue catalog rather than a single sequenced, checkpointed import workflow.

Suggestions

Add a top-level sequenced import workflow (e.g. 1. Detect app vs library & dest convention → 2. Run nx import → 3. Merge root deps/targetDefaults/namedInputs → 4. Run nx sync & verify typecheck → 5. pnpm install) with explicit validation checkpoints, so the process is proactive rather than a reactive issue list.

Consolidate the scattered validation/feedback steps (nx sync, nx reset, typecheck verification, pnpm install retry) into a single 'Verify after import' checklist near the end of Quick Start.

Make the 'Fix' steps under each Common Issue consistently numbered with an explicit verification command as the final step, so every fix has a feedback loop rather than only some.

DimensionReasoningScore

Conciseness

The body is dense with specialized edge-case knowledge Claude would not already know (pnpm glob pitfalls, ESLint v9 pinning, tsconfig.base settings) with virtually no filler or explanation of known concepts.

3 / 3

Actionability

Provides concrete, copy-paste-ready commands and config snippets throughout — 'nx import <source> apps --source=apps', 'pnpm add -wD eslint@^9 ...', 'npx nx add @nx/jest', and explicit tsconfig/JSON overrides.

3 / 3

Workflow Clarity

Numbered fix sequences and a couple of feedback loops exist (e.g. 'nx sync --yes' then 'nx reset' retry), but the overall import process is not presented as one sequenced workflow with explicit validation checkpoints — it is organized as a reactive catalog of issues.

2 / 3

Progressive Disclosure

The SKILL.md overview points to six well-signaled, one-level-deep reference files (ESLINT, GRADLE, JEST, NEXT, TURBOREPO, VITE) that are real and each described with its scope, keeping tech-specific detail appropriately split out.

3 / 3

Total

11

/

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, third-person description that states concrete capabilities and provides an explicit 'USE WHEN' trigger with natural user phrasings and a distinct Nx-specific niche.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Import, merge, or combine repositories into an Nx workspace using nx import' — naming specific operations rather than vague abstractions.

3 / 3

Completeness

Explicitly answers both what ('Import, merge, or combine repositories into an Nx workspace') and when via a clear 'USE WHEN the user asks to...' clause.

3 / 3

Trigger Term Quality

Covers natural phrasings users would actually say: 'adopt Nx across repos', 'move projects into a monorepo', 'bring code/history from another repository'.

3 / 3

Distinctiveness Conflict Risk

The Nx workspace / monorepo / nx import niche is highly specific with distinct triggers, making conflict with unrelated skills unlikely.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
nrwl/nx
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.