dist-build-migration

Migrate an Nx package to build to a local dist/ directory with nodenext module resolution, exports map, and @nx/nx-source condition.

Quality

73%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/dist-build-migration/SKILL.md

Quality

Content

77%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 highly actionable with a well-sequenced, validated workflow, but it is a long monolithic file that inlines a large optional sub-procedure and background rationale that would benefit from being split into reference files.

Suggestions

Extract the optional Step 14b lockdown sub-procedure into a references/ file (e.g. INTERNAL_LOCKDOWN.md) and link to it one level deep, leaving a brief decision summary inline.

Move the long 'Why:' gotcha narratives (Steps 0, 9, 15, 15b) into a references/GOTCHAS.md, keeping only a one-line summary plus a pointer in the main body to tighten conciseness.

Trim redundant restatements of the '@nx/nx-source condition resolves to source' explanation, which is explained in several steps.

Dimension	Reasoning	Score
Conciseness	The ~590-line body is mostly efficient and much of the prose encodes genuinely non-obvious domain knowledge (pnpm workspace resolution, published-version mismatch), but several 'Why:' paragraphs and gotcha narratives could be tightened, matching 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	Every step ships copy-paste-ready before/after JSON, TypeScript, and bash blocks plus exact commands (pnpm nx show target, grep invocations) and concrete file paths, fully covering the common migration cases.	5 / 5
Workflow Clarity	Steps are explicitly numbered 0–17 with validation checkpoints throughout — preflight hard-blocker detection (Step 0), inferred-output verification (Step 6), and the Step 17 verify loop with diagnostic feedback ('If nx affected fails... that's step 9') — giving clear sequencing with error-recovery feedback loops for this destructive batch operation.	5 / 5
Progressive Disclosure	No bundle files exist and the skill is a single monolithic SKILL.md; section headers give structure, but the large optional 14b sub-procedure and the deep gotcha narratives are inlined rather than split into one-level-deep reference files, matching 'some structure but could be better organized; content that should be separate is inline'.	3 / 5
	Total	16 / 20 Passed

Description

70%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 specific and distinctive, clearly conveying what the migration does, but it lacks an explicit 'Use when...' trigger clause, which caps completeness. Adding a usage-trigger sentence would raise it into the top band.

Suggestions

Append a 'Use when...' clause naming concrete triggers, e.g. 'Use when migrating an Nx package from the shared dist/packages layout to a local dist/ build.'

Add natural synonyms or file/path markers a user might actually say (e.g. 'project.json', 'tsconfig.lib.json', 'dist/packages/<name>') to broaden trigger term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain and several concrete specifics — 'local dist/ directory', 'nodenext module resolution', 'exports map', and '@nx/nx-source condition' — giving multiple specific actions with minor gaps in coverage, matching the 'lists several specific actions; minor gaps' anchor.	4 / 5
Completeness	It clearly states what the skill does but includes no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric guideline completeness is capped at 3 with the 'when' only weakly implied.	3 / 5
Trigger Term Quality	Terms like 'Nx package', 'dist/ directory', 'nodenext module resolution', and 'exports map' are the natural vocabulary an Nx monorepo maintainer would use, giving good keyword coverage, though common synonyms and file extensions are absent.	4 / 5
Distinctiveness Conflict Risk	The combination of Nx-package local-dist migration with the @nx/nx-source condition is a narrow, distinctive niche with clear triggers and minimal conflict risk with other skills.	5 / 5
	Total	16 / 20 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (591 lines); consider splitting into references/ and linking	Warning
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
referenced_paths_exist	Referenced path issues: 5 missing	Warning

	Total	13 / 16 Passed

Repository: nrwl/nx
Path: .claude/skills/dist-build-migration/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.