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

81%

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

Quality

Content

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

A highly actionable, information-dense skill body with excellent concrete commands and well-signaled technology-specific references. Its main weakness is structure: it reads as a problem catalog rather than a sequenced import workflow with explicit validation checkpoints, which caps workflow clarity.

Suggestions

Add a numbered end-to-end import workflow at the top (detect app vs lib -> choose strategy -> import -> validate via `nx sync`/typecheck -> fix issues) with explicit validation checkpoints before proceeding, so the destructive/batch operations are gated by verification.

Move the detailed Common Issues and Non-Nx Source fixes into a reference file (e.g. references/TROUBLESHOOTING.md), keeping SKILL.md as a concise overview that points to it, to improve conciseness and progressive disclosure.

Consolidate the scattered validation guidance (nx sync/reset, typecheck, dep diffing) into a single 'Verify the import' checklist section so checkpoints are explicit rather than implicit.

Dimension	Reasoning	Score
Conciseness	The body is dense and operational with no padding about what Nx or monorepos are, assuming Claude's competence; not 5 because the sheer volume of inlined edge-case content and a few explanatory sentences could be trimmed, and not 3 because almost every line is concrete, earned content.	4 / 5
Actionability	Copy-paste-ready commands (e.g. `nx import <source> apps --source=apps`, `pnpm add -wD eslint@^9 ...`, `rm -rf imported/node_modules ...`), concrete JSON snippets, and exact tsconfig settings cover the common cases, matching the fully-executable anchor.	5 / 5
Workflow Clarity	Validation checkpoints exist but are scattered (e.g. `nx sync --yes` then `nx reset` retry, diffing package.json/nx.json) rather than sequenced into an end-to-end import workflow; the destructive/batch cap applies because the main flow lacks explicit ordered validation, fitting the 'sequence present but checkpoints implicit' anchor and not 4 which requires a clear sequenced workflow.	3 / 5
Progressive Disclosure	Six real one-level-deep references (ESLINT, GRADLE, JEST, NEXT, TURBOREPO, VITE) are listed with descriptive summaries under 'Technology-specific Guidance', giving good structure and clear navigation; not 5 because a large block of common-issue detail is inlined in SKILL.md rather than split into references, fitting the 'good structure; minor organization gaps' anchor.	4 / 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.

A strong description that crisply states both what the skill does and when to invoke it, with natural trigger phrases and a clear niche. Minor room to add synonyms and slightly more differentiated action verbs.

Dimension	Reasoning	Score
Specificity	"Import, merge, or combine repositories into an Nx workspace using nx import" lists several concrete verbs tied to a named domain, matching the 'several specific actions; minor gaps' anchor; not 5 because import/merge/combine are near-synonyms rather than truly distinct comprehensive actions, and not 3 because it clearly exceeds 1-2 actions.	4 / 5
Completeness	"Import, merge, or combine repositories into an Nx workspace" states the what, and "USE WHEN the user asks to adopt Nx across repos, move projects into a monorepo, or bring code/history from another repository" explicitly answers when with concrete trigger phrases, matching the top anchor exactly.	5 / 5
Trigger Term Quality	"adopt Nx across repos", "move projects into a monorepo", "bring code/history from another repository" are natural phrases users would say, giving good keyword coverage; not 5 because synonyms like 'consolidate repos' or 'migrate to Nx monorepo' are absent, and not 3 because coverage is clearly broader than 'some relevant keywords'.	4 / 5
Distinctiveness Conflict Risk	The scope is narrowly scoped to importing repos into an Nx workspace via the specific `nx import` command, with distinct triggers and minimal overlap risk with other skills.	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: whimzyLive/nightshift-ai
Path: .opencode/skills/nx-import/SKILL.md
Commit: a2b4df7

Reviewed: 4 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.