CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

71

Quality

89%

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

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

An operationally dense, highly actionable reference: nearly every bullet is an executable command, exact config change, or error-message-to-fix mapping, with genuine feedback loops and a sensible split between critical in-body fixes and deeper per-technology reference files. The main improvements are consolidating duplicated cleanup guidance, unifying post-import verification into one checklist, and describing the two bare reference entries.

Suggestions

Merge the duplicated stale-artifact cleanup guidance ('Redundant Root Files' and 'Stale node_modules and Lockfiles' both cover node_modules/, pnpm-lock.yaml, pnpm-workspace.yaml, .gitignore) into one section to tighten conciseness.

Add a consolidated end-of-import verification checklist (e.g., nx sync --yes, pnpm install, run a build/typecheck per imported project) so scattered checkpoints form one explicit sequence, and add a verify step before/after the rm -rf cleanup.

Add one-line scope descriptions for references/GRADLE.md and references/TURBOREPO.md to match the signal quality of the other four reference entries, and clarify what stays in SKILL.md vs ESLINT.md for the overlapping ESLint guidance.

DimensionReasoningScore

Conciseness

Nearly every line is a specific command, error string, version pin, or config key — no padding or explanations of concepts Claude already knows. Minor trims remain: stale node_modules/lockfile cleanup is duplicated across 'Redundant Root Files' and 'Stale node_modules and Lockfiles', and the 'After nx 22.6.0... For earlier versions' branch echoes the penalized version-conditional pattern.

4 / 5

Actionability

Fully executable guidance throughout: exact commands ('nx import <source> apps --source=apps', 'npx nx add @nx/jest', 'pnpm add -wD eslint@^9 @nx/eslint-plugin typescript-eslint'), a copy-paste pnpm.overrides JSON block, exact tsconfig keys, and exact error messages to recognize ('MultipleProjectsWithSameNameError', 'Cannot read properties of undefined (reading 'version')') with numbered fix orders.

5 / 5

Workflow Clarity

A coherent sequence is present (app/library detection → strategy choice → import → post-import fixes → sync/install) with real feedback loops ('run nx sync --yes. If it reports nothing but typecheck still fails, nx reset first, then nx sync --yes again'). Validation is not missing, so the destructive/batch cap does not apply, but checkpoints are scattered across issue sections rather than a consolidated verification pass, and the 'rm -rf imported/node_modules...' cleanup has no verify step.

4 / 5

Progressive Disclosure

Six real one-level-deep reference files, mostly well-signaled: ESLINT/JEST/NEXT/VITE each get inline pointers plus one-line scope descriptions in the 'Available references' list. Minor gaps: GRADLE.md and TURBOREPO.md are listed bare with no description, and the body's ESLint sections partially overlap ESLINT.md's scope.

4 / 5

Total

17

/

20

Passed

Description

91%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 description: it names the exact command and target ecosystem, lists concrete actions, and provides an explicit USE WHEN clause with three realistic trigger scenarios. The only weaknesses are the near-synonymous action verbs and a slight overlap risk between 'merge/combine repositories' and generic git-merge requests.

DimensionReasoningScore

Specificity

Names the exact tool ('using nx import') and target ('into an Nx workspace') with concrete verbs, but 'Import, merge, or combine' are near-synonyms for a single operation rather than the multiple distinct actions anchor 5 demands; it is well above anchor 3's '1-2 concrete actions'.

4 / 5

Completeness

Explicitly answers both 'what' (import/merge/combine repositories into an Nx workspace using nx import) and 'when' ('USE WHEN the user asks to adopt Nx across repos, move projects into a monorepo, or bring code/history') with three concrete trigger phrases — matches the anchor-5 pattern exactly.

5 / 5

Trigger Term Quality

Covers the natural phrasings comprehensively: 'import, merge, or combine', 'adopt Nx across repos', 'move projects into a monorepo', 'bring code/history from another repository' — synonym coverage matches the anchor-5 example's breadth.

5 / 5

Distinctiveness Conflict Risk

Clear Nx/monorepo niche anchored by the distinctive 'nx import' command, but 'merge, or combine repositories' carries minor overlap risk with generic git-repo-merging requests, fitting anchor 4 ('minor overlap risk with closely related skills') better than anchor 5.

4 / 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

whimzyLive/nightshift-ai

Path

.github/skills/nx-import/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.